01 — Technology consulting
A plan you can fund.
We turn a fuzzy technology decision into options, tradeoffs, and a sequence. The output is something your team can still read in a year.
A useful first conversation is one decision you are about to spend money on, and the people who will live with the result.
Scroll and this stack opens.
Watch it happen
What we offer
-
01
A picture of what you actually run
Systems, spreadsheets, vendors, and the workarounds people trust more than the official tool. Named, not implied.
-
02
Options with the tradeoff attached
Buy, build, integrate, or wait. Each option is scored against the outcome you named, including cost, risk, and who has to change how they work.
-
03
A roadmap with owners
What to do now, what to leave alone, and what to revisit. The first project is small enough to start, not a three-year transformation slide.
-
04
Decision records
A short note for each important choice: the context, the options, and why this one. So the next person does not reopen it from scratch.
How we do it
-
01
Listen for the constraint.
We interview the people who feel the problem and walk the systems they use. We write down what is contractual, what is habit, and what is actually broken.
You see: a constraint list, in your words. -
02
Map the moving parts.
Applications, data, owners, and the handoffs between them. A capability map, not a tool inventory with logos.
You see: a map your operators recognise. -
03
Score the options.
We put two or three real paths next to each other. Vendor names show up only after the job is clear. We say what we would not do.
You see: a comparison and a recommendation. -
04
Sequence the work.
A roadmap with a first project, the people it needs, and the decisions that can wait. Then we can stay and build it, or hand it to your team.
You see: a sequence you can put on a calendar.
What the work is made of
-
Capability maps
What the business must be able to do, separate from the product that happens to do it today.
-
Architecture options
Boundaries, integrations, and what stays put. Written so an engineer and a budget owner can both use them.
-
Risk and dependency notes
The contracts, data, and people a plan quietly depends on. Named before the project starts.
-
An investment sequence
Order of spend, not a shopping list. Each step has a reason to exist without the ones after it.