You pay for it.
You end up owning it.
If you are asking me to build something, this is the route — every time, whatever the software is for. It is not cheap, and the reason it is not cheap is the thing you are left holding at the end.
Full handover is priced in, not sold back
Handing the whole thing over is part of the commission, not an upgrade to it. Source, database, deployment, IP — all of it transfers to you when the work is done, so what you paid for is yours to run, change or take elsewhere.
That transfer is built into the price of every commission from the outset, business or private — which is exactly why the number is what it is. Nobody gets a discount for giving it up, because it is not on the menu separately.
Five steps, no surprises
A conversation, free
You tell me what you are trying to do. I tell you whether software is the answer, whether I am the right person, and roughly what scale of thing we are talking about. Sometimes the answer is that you do not need this built at all, and I would rather say so now.
Paid discovery
Before anyone commits to a number, I get paid to work the problem out properly — what it does, who uses it, where the edges are, what it talks to. You end up with a written specification you own, and you can take it elsewhere if you would rather. Quoting a fixed price on a guess helps neither of us.
A fixed price against that spec
The specification is what gets quoted, so the price holds. A deposit books the work, the middle is tied to milestones you can see, and the balance falls due at sign-off. Anything beyond the spec goes through a written change to the scope rather than quietly onto the bill.
Built, in the open
You see it working as it goes, not at the end. Short cycles, real deployments, no long silence followed by a reveal.
Handover
On final payment you take the source code, the database and its structure, the deployment setup and the intellectual property in it. Yours outright. You can hire anyone to take it further, including nobody.
What you get at the end
- The complete source, in a repository you control
- The database and its structure, with your data in it
- The deployment setup, documented enough to rebuild
- The intellectual property, transferred on final payment
- No obligation to keep me involved afterwards
What this is not
It is not a retainer, and it is not a subscription with a build attached. Once it is handed over it is genuinely yours to run, change or abandon.
If you want somebody looking after it afterwards — updates, backups, fixes, someone to ring, or your people shown how to use it — that is Kalkman Tech, and it is a separate arrangement you opt into rather than something bundled in to keep you tied.
Quoted, never listed
There is no price list here and there is not going to be one. Two builds that sound identical in a sentence can differ by a factor of five once you know what they actually have to do — which is what discovery is for. Quoting before that is guessing, and the guess gets paid for later.
Start with a paragraph
What it is meant to do, who would use it, and roughly when you need it.
Start a conversation