RIGTech

Product Strategy

Deciding what to build before building it: scoping the work, cutting it to something shippable, and putting a fixed price against it.

What this covers

The work that happens before any code, and that determines whether the code was worth writing.

• Turning a broad ambition into a specific, buildable scope.
• Separating what has to exist at launch from what can wait, honestly.
• Sizing the work, so the budget conversation happens early rather than at the end.
• Mapping how the software fits the process around it, including the parts that stay manual.

How the work runs

A short, concentrated engagement rather than a long consultancy. We spend time with the people who will use the thing, not only the people commissioning it, because the gap between those two accounts is where most rework comes from.

The output is a written scope you could hand to any competent team, with the decisions and their reasoning recorded — including the options we rejected, so nobody relitigates them in six months.

It ends with a fixed price and a timeline against that scope.

What you have at the end

A document that makes the project fundable and buildable, and is yours whatever you do next.

• A defined scope, prioritised, with what is out of scope written down as plainly as what is in.
• A fixed price and timeline for building it.
• The reasoning, so a decision can be revisited on purpose rather than by accident.

You are free to take that document elsewhere. It happens, and the work was still worth doing.

Who this suits

Anyone who has been quoted wildly different prices for what they thought was the same project — that spread is almost always a scope that has not been pinned down.

Also teams who know something needs building but cannot yet write down what "done" looks like.