Own it

When I'm done, you hold the keys.

You've heard the story — maybe lived it. The developer who registered the domain under his own name. The website that vanished when the relationship soured. The database nobody's allowed to touch because the guy who built it is gone. Everything on this page exists so that story can't happen to you.

What "you own it" means, item by item

• The code. It lives in an account that belongs to you, from day one. Not "transferred at final payment" — day one. I work in your account; you can lock me out any time.
• The accounts and the domain. Hosting, domain, email — registered to you, paid by you, inventoried in writing with every login listed. Nothing of yours sits under my name.
• The manual. Plain English, written for your office — how to use it, and a separate page for whatever developer comes after me: what it's built with, how to run it, what to check first when something looks wrong.
• The boring-technology promise. Everything I build uses documented, mainstream tools any developer can maintain. No exotic anything. Boring is a feature; it's what makes the manual short.

See an actual handover

Every build ends with a handover folder. Here is a real example — built for the demonstration project on this site, so you can see exactly what you'd be holding:

• README — what this is, how to run it, and who to call if it breaks (any developer — and here's what to tell them).
• MANUAL — the user manual, written for the office, not for developers.
• ACCOUNTS — the inventory of every account, domain, and login you own (passwords redacted in this public example, obviously).
• DECISIONS — one page of why-it's-built-this-way, in plain English.
• the source code — browsable. (Lands here together with the live demo it belongs to — being built right now.)

Browse the example handover folder →

The contract, before you ever call

Here is the actual contract you'd sign — the warranty, the response time, the ownership terms, all of it. Download it, print it, read it at your kitchen table, show it to your accountant. No email address required.

The honest part

I do this work on a contract basis and take a limited number of builds at a time. You get a realistic schedule up front, in writing. And if something I built breaks, that's mine to fix — free for the first 60 days, with a response within one business day, both in the contract. After that, the optional support plan covers it — or any developer can step in, because you own the code and the manual.

Questions about any of it? Call or text me: [FILL: phone]