Independent consulting and delivery
Your strategyisn't shippingitself.
A three-year plan with nothing shipped is a document, not evidence. So we start with the problem and build the first working piece.
AI is the new norm. The problems worth solving are as old as business: cost, speed, and what to build next.
01Approach
Every project ends with something running.
Most consulting projects end with a recommendation and a page count. Ours end with viable code in your repository, running against your data.
We start with the problem, not with a product. No cloud vendor pays us and no licence revenue reaches us, so the answer is not decided before we arrive.
02Impact
What we have built.
Three projects, and what each one changed
Agentic assisted delivery
A client came to us with an application build quoted above two hundred thousand dollars and a schedule measured in months. We ran the delivery with agentic assisted engineering and it was production ready in twelve weeks at half the proposed spend. The agents did the volume work. We did the judgment about what to build.
Program options, simulated before the spend
A healthcare delivery client was choosing between several ways to run a proposed program change, with millions of dollars in cost savings resting on which one they picked. We modeled multiple simulations, varying the cost drivers and the acceptance rates the savings actually turned on. They funded the one that held up, and they knew before starting what it would cost and which assumption would sink it.
Manual routines turned into running software
One pattern repeats: a manual routine becomes a small application the whole organization then uses, and AI tooling now gets it built in a fraction of the time. Tooling we wrote ourselves has cut provisioning and profile verification by ninety-five percent, content compliance checking across thousands of pages by eighty-five percent, and deployment time by half. A first working piece is usually this small, and the below-the-line cost savings accrue quickly.
03Complexity
Your business problems are never only technical.
Decades of delivery teach you that the thing blocking a programme is rarely the thing named in the status report. We work through all of it, in the order that matters.
Technology
What is actually running, what still depends on it, and what it costs to keep alive.
Culture
What gets rewarded, what gets quietly ignored, and what nobody will say in the meeting.
Habits
The workaround that became permanent, invisible now to everyone who built it.
Process
Steps that survive because of a problem somebody solved years ago and nobody has revisited.
Strategy
Whether the plan on paper still matches what the business actually needs this year.
Market
What customers will pay for, and what competitors have already made table stakes.
Delivery context
What your teams are already committed to, and what that realistically leaves for anything new.
We unwind these until something moves on the top line or the bottom line. That is the only reason to touch any of them.
04Questions
Which of these is yours?
01
You have an AI or modernization strategy. How much of it has actually shipped?
02
Are you still paying, year after year, for inventory nobody uses?
03
You built something other companies would pay for. Is platformizing it worth the cost?
04
Your teams are fully committed. Who is preparing the thing that is six months out?
05
Is a deliverable off track, carrying unresolved issues, and not ready for production or scale?
06
Are you about to hire an AI strategist or architect without being sure what the role should deliver?
05Work
What we take on.
01
First working piece
A rough idea becomes something running in hours or days, tested against your data.
02
Accelerator adoption
Someone already published most of your system. We finish the fifth that is yours.
03
Platformization assessment
We price what taking internal software to market actually costs.
04
Make or buy
Build it, buy it, or leave it alone. The decision turns on integration, not features.
05
Data put to work
Modeling and optimization that end in a decision, not another dashboard.
06
Duplicative inventory reduction
Systems you replaced but never switched off. We take them off the bill.
07
Impact measurement
Measurement wired in before the spend, so the next funding decision has evidence.
08
Back on track
A build that stalled short of production. We get it to where your team can carry it.
06Principles
How we work.
01
Go simple. It'll complicate itself soon enough.
Start with the plainest thing that could work. Once it is running, most of the real solution reveals itself on its own.
02
We'd rather bet on your people than on a tool.
Tools get replaced every four years. The engineer who understands your system does not. We hand over what we build, so the knowledge stays after we go.
03
Strategy is a dream until you execute.
A plan shows you what you hope is true. Executing a piece of it shows you what is true. Only one of those changes a decision.
04
Be prepared. Always scout.
Know the terrain before you commit the budget. Dependencies, owners, data quality, and the thing nobody wants to mention in the kickoff meeting.
05
Risk is good. Manage the mitigation.
Avoiding risk is how organizations stop moving. Name the risk, size it, plan the way back, then take it deliberately rather than by accident.
06
Demonstrate it.
Design and ideas hold little value until someone can use them. Show the working thing. Every argument gets shorter once it is on screen.
07AI
AI is an enabler. It doesn't replace people.
Martin was part of early cloud development, and is part of early AI adoption now. The same argument ran then, and it resolved the same way.
Impact
AI should make your best people more effective at the work only they can do. If it is not doing that, it is a subscription.
Responsible use
Know what the system was trained on, what it is allowed to touch, and who reviews the output before it reaches a customer.
Security and vulnerability
New capability is new exposure. Data handling, model access, and prompt paths belong in the threat model from the first sprint, not the last one.
08Topics
What we are asked about.
- Product development01
- Modeling, forecasting, and optimization02
- Agentic workflows03
- Supply chain, transactions, and inventory04
- Make or buy decisions05
- Integration, security, and resilience06
- Cloud and platform modernization07
- Program evaluation and impact evidence08
We do not run managed services or take on long-run application support. If that is what you need, we will say so on the first call.
09Pricing
How we price, and why.
The way we charge follows from the way this practice is built. Both are deliberate.
You are not funding overhead
There is no bench to keep busy, no sales organisation, and no floor of offices to carry. You pay for the work and the judgment behind it.
Nobody else is paying us
No vendor margin, no referral fee, no resale commission. What we recommend is what we would do if the budget were ours.
Scoped to the question
We size the work to what needs answering, not to what is available. If a smaller piece settles it, we will say so and do that instead.
Light on administration
Delivery is hard enough. We do not add change-order cycles, weekly status theatre, or a discovery phase you pay for before anything is built.
Measured on impact
Projects end with something running and a number you can defend in a review. That is the deliverable. Hours are only how we got there.
10Tech for good
Tech for good
If you are a nonprofit, or you serve people who are underserved or disadvantaged, get in touch! We are convinced we can help, and we will find a way to make the project work.
11Fit
Built for companies of any size.
Global enterprises, start-ups, and public sector. What matters is the problem, not the headcount.
Find what is actually wrong, build the piece that proves it, hand it back. Size changes the constraints. It does not change the method.
12Martin
Martin Haase
Founding Partner
Over thirty years of building the thing rather than describing it.
Martin recently retired as a Senior Director at Microsoft. Much of that time was spent with hundreds of customers working through modernization, which is a polite word for deciding what to keep.
Practice areas
- Delivery and modernization
- Data, modeling, and decision systems
- Product strategy and make-or-buy
- Platform and go-to-market readiness
Status
Taking new projects
Direct
13David
David Nguyen
Partner
Fifteen years building enterprise applications end to end.
He works the whole stack rather than a slice of it. That is what makes a small practice viable: one person who can define the schema, write the service, build the screen, and own the pipeline that ships it.
Practice areas
- Full stack application development
- APIs, services, and integration
- Database design and performance
- Test automation and quality engineering
- Deployment pipelines and release
Status
Taking new projects
Direct
14Contact
Start with one conversation.
No vendor margin, no referral fee, no resale commission. What we recommend is what we would do if the budget were ours.