You own the code: custom software without vendor lock-in

Lock-in never looks like a cost on day one. It looks like convenience: the platform hosts everything, the agency holds the code, the tool “just handles it.” The bill arrives later, when you want to change vendors, add a feature they will not build, or simply negotiate, and discover you cannot leave.

How does lock-in actually show up?#

• Platform lock-in — your site, store, or app lives inside a tool you rent and cannot export cleanly.
• Code lock-in — an agency built it but keeps the source, so only they can change it.
• Data lock-in — your customer and business data sits in a format you cannot easily take with you.

Each one quietly shifts control to the vendor. Renewal prices rise because they can. Feature requests get slow or expensive because you have nowhere else to go. The switching cost, not the monthly fee, becomes the real price, and it grows the longer you stay.

Lock-in is not the monthly fee. It is the price of leaving, and it rises the longer you cannot.

Why does ownership change your position?#

When you own the source code, the design files, and the accounts, the relationship is voluntary. You stay with a team because the work is good, not because leaving is impossible. You can bring in another developer, host it anywhere, or take it in-house. That option is worth real money even if you never use it: it keeps everyone honest and keeps your costs down over time, because every renewal conversation happens between equals instead of between a captive customer and the only company that understands the system.

What should “you own it” actually mean?#

Ownership is specific, not a slogan. It means the full source code in a repository you control, the design files, the domain and hosting accounts in your name, and no clause that traps your data. If a vendor cannot hand you all of that on request, you do not own your software, you are renting it. This is also why our protections are written down rather than implied: NDA first. Full handover of code and documents. No lock-in. 30-day warranty.

What does a healthy vendor relationship look like instead?#

You can tell almost immediately. A request for source access or a data export is treated as routine, not as a negotiation. Pricing for the next phase is a quote, not a renegotiation of your entire position because you have nowhere else to go. The team can explain, in plain terms, exactly what happens to your code and your data if you decided to leave tomorrow, without getting defensive about the question. None of this requires you to actually leave. The option to leave, held in reserve and never used, is what keeps a vendor relationship honest for years instead of turning into a slow-motion standoff.

How do you protect yourself before you build?#

Ask three questions before signing anything: Do I get the source code? Are the accounts in my name? Can I export my data in a standard format? If the answer to any is no, or “sort of,” price in the switching cost before you agree to anything.

What would we build first?#

Whatever the first piece is, we would hand it over exactly the way we hand over everything: source in a repository you control, a walkthrough, and the accounts in your name from the start, not promised for later. That is also why the team stays small and senior; see how that shapes speed in our note on senior-only teams. You can see the full delivery rhythm on how we deliver.

Where should you start?#

Review where you are trapped today: which platform, which agency, which export you have never actually tried. We build with fixed scope and price agreed in writing up front, and full ownership handed over, no lock-in. Book a 20-minute call to talk through what you would take back first.

Questions people ask#

What is vendor lock-in and why does it cost more?

Vendor lock-in is when your software, code, or data is trapped inside a platform or agency you cannot easily leave. It costs more because the switching cost, not the monthly fee, becomes the real price: renewals rise, feature requests get slow or expensive, and you have nowhere else to go to negotiate.

What should "you own the software" actually mean?

It should mean the full source code in a repository you control, the design files, the domain and hosting accounts in your name, and data you can export in a standard format. If a vendor cannot hand all of that over on request, you are renting your software, not owning it.

How do I avoid lock-in before I start a build?

Ask three questions before signing: Do I get the source code? Are the accounts in my name? Can I export my data in a standard format? If any answer is no, price in the switching cost. Full handover from day one avoids the trap entirely.