Kindra charges in three stages: the Leak Check is free, the Blueprint is a fixed fee quoted
before you commit, and builds are quoted from the Blueprint in two-week increments. You own
the result — no per-seat licence, no subscription. Every number is agreed in writing before
work starts.
Leak CheckFree20 minutes, written findings
BlueprintFixed feeQuoted first · 3 days · yours to keep
BuildPer incrementWorking software every two weeks
The Blueprint: fixed fee, quoted before you commit
You know the number before you say yes, and it doesn’t move. If the scope changes materially during the Blueprint we tell you before doing the work, not after — the whole point of a fixed fee is that the surprise risk sits with us.
It is also the cheapest way to find out we are the wrong firm. About 40% of Leak Checks never reach a proposal at all, which is a number we would rather publish than hide.
Builds: why we quote per two-week increment
A twelve-week project quoted as one number asks you to trust an estimate made when we knew least about your business. Two-week increments mean the estimate is made when we know most.
Each increment: scope agreed, price agreed, working software delivered. You approve the next one or you stop. The structure exists to cap your downside, not ours — and it is the first thing to look for in anyone else’s quote too, which is why it is on the red flags list.
What drives cost up
In rough order of how often they bite:
Systems without a usable APIScraping or database-level work is slower to build and far more fragile to maintain. This is the single biggest multiplier.
Data migration from a legacy systemRarely the hard part technically. Almost always the hard part in practice, because the old data is messier than anyone remembers.
Multi-entity or multi-site structuresTwo companies sharing one process is more than twice the work of one, because the exceptions multiply.
The number of exception pathsNot the main flow — the "except when" cases. Ten exceptions cost more than the happy path they hang off.
Compliance requiring formal sign-offNot the controls themselves, the evidence and the review cycles around them.
What drives cost down
A process that is already documentedEven badly, even one page. It removes the most expensive unknown in the build.
Modern systems with real APIsThe nine we have built against are all in this category, which is why we can move quickly on them.
One decision-makerTwo is workable. A committee turns a two-week increment into a four-week one without adding any software.
Willingness to change the processRather than replicate a bad one in code. Frequently the cheapest change available.
Starting with one workflowInstead of all of them. It is the default here, and it lets you judge us cheaply.
Several of these are things you can influence before you talk to anyone —
what you should not automate covers the
documentation point in more detail, and it will save you money whoever builds it.
What recurs and what doesn’t
What recurs: hosting, model and API usage, and any third-party apps or integrations. What does not: the build itself. You are not renting the thing we made you.
That is the whole difference between this and a per-seat product, and it compounds. A
subscription rises with your headcount whether or not the software does more for you; a
system you own does not. The clause that makes that real is on
ownership and security.
Terms
A 50% deposit to start. Ownership of what gets
built transfers on payment of the final invoice. Our minimum engagement is around
$5,000 — below that the payback usually is not
there and we will say so rather than take the work.
If you stop mid-project you keep everything delivered to that point, including the code,
which has been in your repository since the first commit rather than arriving at the end.
Exactly what a wind-down looks like depends on which increment you stop at, and it is written
into the engagement rather than left to be negotiated at the worst moment.
Objections
"Why don’t you publish prices?"
Honestly: People do not understand it until it is explained and they can see it — and until they get it, the value scares them. A band published without knowing your systems
would mislead you in one of two directions — too low and you feel misled later, too high
and you never call.
What you get instead is a fixed Blueprint fee quoted before you commit, and a build price
quoted from that Blueprint before any build work starts. You never see a number for the
first time on an invoice. It is still the softest point on an otherwise unusually open
site, and we know it.
"How do I know it won’t blow out?"
Two-week increments. The most you can be wrong by is one increment, and you decide whether there is another.
"Can we start small?"
That’s the default. Most engagements start with one workflow — usually the one that pays back fastest rather than the one that is most interesting to build.
Book a free Leak Check
20 minutes. We find where the money's going. No pitch.
