Every Kindra engagement starts with a free 20-minute meeting. Inside it, when the drag looks like leaking revenue, we run a Leak Check — map where hours and money walk out, and tell you what’s worth fixing. That produces a written Blueprint with costed options. You decide whether to build. No obligation between any two stages. Even if we never work together, you walk away knowing.
Not a demo. Not a capability presentation. A free 20-minute meeting about how work actually moves through your business, and where it stalls. When the drag looks like leaking revenue, we run a Leak Check — the tool, not the whole offer. Even if we never work together, you walk away knowing.
Most of it is listening. The useful information is usually in an aside — "oh, and then Sharon re-types it into the other system" — not in the answer to the question we asked.
Bring the person who does the admin, not only whoever owns the budget. Those are frequently different people, and the second one has a tidier and considerably less accurate picture of how the work actually moves. If only one of them can make the call, make it the first.
The questions we ask, and why they’re not a fixed list
There is no standard set of fourteen questions, and publishing one would be a marketing exercise rather than a method. The questions differ by trade, because the leaks differ by trade. What you ask a signage business about artwork approval has no equivalent in a plumbing business, and asking it anyway wastes the twenty minutes.
What is constant is the shape: we follow one real job from enquiry to paid invoice, and at every handoff we ask who touches it, what they re-type, and what happens when it goes wrong. You can prepare for that without a list — pick a recent job that was annoying and have it in mind.
Each increment: agreed scope, agreed cost, working software at the end. Not a demo — something you can use.
You can stop after any increment. That is the point of the structure. A twelve-week project quoted as one number is a bet; the same project in six increments is six decisions, and the most you can be wrong by is one increment.
1
2
3
4
5
6
Stage 04Code · keys · docs
Stage 4: handover — code, docs, keys
Less of an event than it sounds, because repository access has been yours since the first commit rather than arriving at the end. What changes at handover is that the running system, its credentials and its documentation are formally yours, and ownership transfers on payment of the final invoice.
The full set of commitments behind that — hosting, backups, the restore-test date — is on ownership and security.
Stage 05Back to the numbers
Stage 5: the check-in nobody else does
The first one happens two days after the proposal goes out. After that we come back to the numbers from the Blueprint and ask the uncomfortable question: did it do what we said it would?
Sometimes it didn’t. That conversation is the most useful one in the engagement, and it is the reason the Blueprint quantifies things in the first place — a promise you cannot check later is just a nice sentence.
It is also the stage most firms skip, and the reason is obvious: a check-in against published numbers is a standing opportunity to be wrong in front of a client. We would rather be wrong early and fix it than have you quietly conclude a year later that it did not do much.
Objections · answered straight
Before you ask.
"Is the Leak Check a disguised sales meeting?"
It’s how we work out whether there’s a job worth doing. The Leak Check is the revenue-leak tool inside the free meeting, not the whole offer. Even if we never work together, you walk away knowing. About 40% don’t lead to a proposal. You keep the findings regardless, and we would rather find out in twenty minutes than three weeks in.
"What if the Blueprint says don’t build anything?"
Then it says that. You’ve paid for an answer, and "don’t" is a legitimate one. It’s considerably cheaper than finding out after the build.
"Who owns the Blueprint if we don’t proceed?"
You do. Take it to another firm if you want. It’s specific enough to quote from, which is the test of whether it was worth writing.
Free 20-minute meeting · Leak Check when revenue’s leaking
Stop bending. Start shipping.
Bring the one flow that keeps costing you a Tuesday afternoon. We map it live and tell you what’s worth fixing. Even if we never work together, you walk away knowing. We fix the boring so your staff can do the high-value work.
