What this is not
A feasibility study, a cost estimate, or an audit of a system you already have.
For founders and executives
Before you commit six figures to building a system, spend three to four weeks finding out what to build, and whether to build it at all.
01 The question
Diagnosis comes first. I map how the business actually works, put the real constraints on the table, and end with a recommendation and the options beside it.
A feasibility study, a cost estimate, or an audit of a system you already have.
"Don't build this" is a legitimate, fully-paid outcome. Arguably the most valuable one.
02 What you get
The recommendation, the options considered, the trade-offs between them, the risks, and the constraints that shaped the answer. Written for someone who has to defend the decision to a board, a bank, or a co-founder.
Build-ready to the standard that any competent engineering team could execute it, not only mine. That is deliberate. What you receive has to be worth what you paid whether or not I build it. Yours to keep, outright.
03 How it runs
A fixed window, not a day rate. I am never full-time on a single engagement, and the window is sized to absorb that. You get a date.
Two to three weeks with your people and your systems. What the work actually is, who owns what, where the record lives, and which constraints are real rather than assumed.
A decision document: the recommendation, the alternatives considered, the trade-offs, the risks. Including the option of not building.
An architecture and specification detailed enough that any competent team could execute it. Yours to keep whether or not I build it.
04 Conditions of starting
Non-negotiable, because the work is worthless without them. If these are difficult, the engagement is not ready to start. Better to know that now.
One person, senior, accountable.
Whoever actually knows how the business runs.
Where the record actually lives, read-only.
Within an agreed period after handover.
05 Who does the work
I started as a developer and I still write code. Most of the largest systems I have worked on were bespoke builds well into six figures: finance systems, payment platforms, infrastructure a business runs on.
Most people selling strategy have only ever consulted. The reason I start with the workflow instead of the technology is that I have been on the other side of it.
06 Terms
A fixed fee, payable 100% on signature.
Why upfrontA client who won't commit the fee won't commit a sponsor and system access either, and those matter more to the outcome than the money.
A fixed window from kickoff to handover.
The fee is credited in full against the build.
Why the credit expiresThe 90 days line up with the go/no-go decision you commit to at the start. A specification goes stale; the credit shouldn't outlive its accuracy.
The price holds at €25,000, including for the first clients. The fee is part of the filter: it is how both of us know the decision is being taken seriously before a sponsor, access, and a go/no-go commitment are put behind it.
Always after the diagnostic, never bundled, never pre-committed. If the recommendation is to build, Demon Dog, the company I run, can deliver it, and the €25,000 comes off the price.
07 Who it's for
If the recommendation is to build it differently, or not at all, you have a document that says so and the specification to act on when the time is right. Either way you own the thinking.
What you're considering building, roughly what it's worth to the business, and who would sponsor it internally. If it's a fit I'll come back with next steps. If it isn't, I'll tell you that too.
Prefer email? Send three sentences on what you are weighing to hello@bjornnystrom.com and I will reply with next steps.
The first call
Long enough to hear the shape of the build and say whether The Build Decision is the right next step. If it is not, I will say so on the call.
Reading the calendar.
A calendar invitation will follow to your email.