Skip to content
Octrix woven logooctrix.

Creative technology. Unconventional answers.

Bring me the problem.Not the solution.

If you could solve it internally, you probably wouldn’t be here.

Bring me the problem, the context and the ambition. Then give me the room to solve it.

The answer might be software. AI. Data. A process change. Or something nobody had considered yet.

That’s usually the point.

When your team gets stuck, I step in.

Give me the room to solve it properly.

01 / 08One strand. No standard route.

Problem → investigation → insight → solution↓OCTRIX / INVESTIGATE · BUILD · CHANGE

01 / The starting point

If your team already knew the answer, you probably wouldn’t need me.

Octrix is for problems where the usual approach isn’t working.

Maybe you’ve already tried internally. Maybe several agencies have looked at it. Maybe everyone can see what’s wrong, but nobody can work out how to fix it.

That’s where I come in. To do more than add another opinion.

To solve the problem.

02 / How I work

There is one condition.

Don’t hire me to simply execute your solution. Bring me the problem.

Let me into:

  • 01The data.
  • 02The people.
  • 03The systems.
  • 04The processes.
  • 05The customer.

Give me the room to challenge the assumptions.

Because sometimes the best answer to:

“Can you build this for us?”

“No. You need something else.”

The outcome matters more than the brief.

03 / Room to solve

The problem determines what we build.

01

Think

What is actually going on?

Business models, processes, customer behaviour, performance, organisation.

02

See

Can we even see the problem clearly?

Data, analytics, reporting, models, insight.

03

Make

What needs to exist to solve it?

Software, automation, AI, agents, tools, platforms.

04

Change

What needs to work differently?

Pricing, operations, e-commerce, workflows, decision-making.

You don’t need to know which ‘service package’ your problem fits into. I don’t particularly believe in those anyway.

04 / Look again

The obvious solution is rarely the interesting one.

A website problem

can turn out to need

a data problem.

A reporting problem

can turn out to need

a decision-making problem.

An AI opportunity

can turn out to need

no chatbot at all.

A technology problem

can turn out to need

no new technology.

I keep pulling at the problem until we find where it really lives. Only then do we build something.

05 / Selected work

Problems that needed a different answer.

01

Retail / e-commerce

Revenue doesn’t tell the whole story.

The problem
Ad platforms, the store and the warehouse each show a different picture of performance.
What we discovered
Margin, returns and logistics costs need one shared model; revenue alone isn’t enough.
What we built
An integration layer and contribution-margin visibility by product and channel.
Why it was different
The question shifts from more revenue to understanding what is actually left over.
Result
A shared view of product and channel profitability.
Explore the example
02

Professional services

Hours delivered. But what was left?

The problem
Project margins and overruns only become clear after the fact.
What we discovered
Time, costs and invoicing need to be considered together to understand project profitability.
What we built
One model for project margins, exceptions and automated reporting.
Why it was different
More than another hours report. A system that shows where to intervene.
Result
Margin visibility by project and client, with overrun alerts.
Explore the example

06 / Up front

We probably won’t fit if…

  • you mainly want an extra pair of hands
  • the solution is already completely fixed
  • every idea needs six layers of approval
  • you mainly want confirmation that your original idea was right
  • the safest answer automatically wins

But if your team is stuck on an important problem, and you’re open to an answer you haven’t considered yet — we should talk.

07 / Your problem

Got a problem you can’t solve?

Good.

Bring it along

It doesn’t need to be a perfect brief yet.