UBIKON.ioThe Walk-Away Guarantee
Every Ubikon engagement is structured so you can leave at any milestone with working code, your IP and documentation. That is the guarantee — not a refund scheme with small print, but a structure in which the safest thing you can do is stay, because leaving was never made hard. Each commitment below already appears elsewhere on this site; this page names them and puts them in one place you can link to. It is the fourth pillar of the Glass-Box Method.
Six commitments
What we put in writing, in public.
Each one is stated on the page where it operationally lives — linked so you can check the context, not just the claim.
You can walk away at any milestone
Engagements are milestone-based specifically so neither side is locked into a bad fit. If it is not working, you stop at a milestone boundary with working code, a private repository and documentation — not a half-finished dependency on us. Also stated on /how-we-work
Everything built is yours, even mid-engagement
Full IP transfer applies to work delivered, not only to completed projects — source, infrastructure configuration and documentation, on a mainstream stack any competent team can pick up. There is no proprietary runtime holding the product hostage. Also stated on /engagement-models
The fixed quote holds — our underestimates are our cost
The number holds for the scope it describes. If Ubikon underestimated, that is Ubikon’s cost to absorb, not a change order. If you add scope, it is quoted separately before any work starts, so you always see the number before it becomes a commitment. Also stated on /why-ubikon
You see the real product every week
A build you can open, a video walkthrough and a written changelog, every week. If a week produces nothing openable, that is the signal something is wrong — and you find out that week, not at a launch date months away. Also stated on /how-we-work
Ongoing work ends on 30 days notice
The monthly product squad has no minimum term and ends on 30 days notice. You keep everything regardless of how long the engagement ran — which is exactly why staying is safe: leaving is easy. Also stated on /engagement-models
You hear "we are the wrong fit" from us first
Sub-$5,000 budgets are referred to freelancers. Certified-compliance work — HIPAA-grade clinical systems, formal audit trails — is referred to specialist firms. You are told during scoping, plainly, rather than sold a package that does not fit. Also stated on /why-ubikon
What this is not
The honest edges.
A guarantee that claims to cover everything covers nothing. These are the boundaries, stated plainly.
It is not a money-back scheme — payment is milestone-based, with the split agreed in writing before the first line of code. It does not freeze the price against scope you add — new scope is quoted before it is built. And it does not promise outcomes no engineering team can honestly promise: store approval decisions, user growth, or revenue are your product's to earn.
What it does promise is the thing that actually goes wrong with agencies: being trapped — by withheld code, by proprietary runtimes, by sunk cost, by a rewrite held hostage. Every commitment above exists to make that structurally impossible.
Straight answers
What buyers ask about the guarantee
Is this a money-back guarantee? +
No, and it is deliberately not framed as one. Refund promises are usually hedged into meaninglessness by their small print. This guarantee is structural instead: the payment schedule is milestone-based and agreed in writing before work starts, and full IP transfer on delivered work means you keep what you paid for whenever you stop. There is nothing to claw back, because payment tracks the agreed milestones rather than running ahead of them.
What happens to the quote if I change the scope mid-build? +
Added scope is quoted separately, against the same line-item delivery data as the original quote, and agreed before anyone builds it. It is never silently absorbed into a larger final invoice. The guarantee covers the number you agreed: for that scope, it holds even if we underestimated.
If I leave at a milestone, what exactly do I get? +
The private repository, infrastructure configuration, documentation, and every deliverable completed to that milestone — with IP transferred. The stack is Flutter, Next.js, FastAPI and PostgreSQL, chosen precisely so any competent team can take it over without us.
Why publish this as a page rather than put it in a contract? +
It is in the agreement too — the written contract covers scope, milestones, payment schedule and IP transfer before work starts. Publishing it here means you can hold us to it before you have signed anything, and compare it line by line against what any other studio is willing to put in writing in public.
One call. One fixed number.
Test it — book a scoping call.
30 minutes, no deck. A fixed, line-item quote follows within 48 hours, and every commitment on this page applies to it.