"Done-for-you" sounds like the whole thing is handled. Sometimes it is. Sometimes what you actually bought is access to someone else's system, dressed up as your own business.
Two founders can buy the exact same package, from the exact same seller, and land in two completely different places six months later — one with a business she genuinely owns end to end, one quietly renting her own infrastructure back from the person who built it. The pitch sounds identical either way, the invoice is identical, the kickoff call covers the same ground. The divergence doesn't show up until someone actually needs to touch the system without the original builder in the room.
The difference was never in the deliverable. It was in the three things nobody puts in the sales page.
Here's the version nobody warns you about: the builder goes quiet — a slow season, a pivot, a falling-out that has nothing to do with you — and suddenly the person who has the only login to your email platform, the only person who knows how your booking system talks to your website, is unreachable. You don't own a broken system at that point. You own a system you can't touch, which is worse, because at least a broken thing you own can be fixed.
This isn't a rare, unlucky-client story — it's the default outcome of any build where ownership was never written down, because nobody had to lie to you for it to happen. The builder didn't set out to trap you. They just built the fastest way to get you live, which was usually to build it inside their own accounts, under their own logins, because that's the workflow they already had running for every other client. It works fine right up until it doesn't, and by the time it doesn't, the fix costs a lot more than the conversation would have.
What actually has to be in the package
Full login credentials, in your name, not theirs. If the account that runs your email list, your booking system, or your website login belongs to the agency and not to you, you don't own it — you have visitation rights to your own business.
Real documentation, not a video you'll forget exists. A written record of what was built and how it connects — which tool talks to which, where the automations live, what breaks first if one piece goes down — so a bad week for your builder isn't automatically a bad week for your business. A thirty-minute screen recording you'll never rewatch is not documentation. It's a goodbye video.
A named exit. What happens, in writing, if you want to leave? Does the account transfer to you cleanly, does the automation keep running while you find someone new, is there a hand-off call included or is that a separate invoice? If the honest answer is "we're not sure, nobody's asked that," that's the answer, and it's worth hearing before you sign, not after.
Ownership of the underlying tools, not just the workflow built on top of them. A booking system, an email platform, an automation tool — these all have their own subscriptions, and someone has to hold them. If the builder's own account is what your business quietly runs on, you're not just missing documentation, you're missing a business. The invoice you pay them monthly and the invoice that actually keeps your website's booking form working might not be the same invoice at all, and you won't know that until the day the first one stops.
Why this gets skipped
Because in the excitement of finally handing something off, asking about the exit feels like planning a breakup at the wedding. It isn't. It's the difference between a service and a system — one you can walk into cold and still recognize, versus one that only makes sense to the person who built it. 🧰 Nobody wants to introduce distrust into a relationship that's just getting started, so the question gets swallowed, and it stays swallowed until the day it can't be.
A founder who asks these questions upfront isn't being difficult. She's the only one in the conversation checking whether "done for you" means done, or just done for now, as long as the original builder stays reachable. Good builders don't flinch at the question — they've usually already thought about their own exit, because they'd rather hand you three documents up front than field a panicked message eight months from now from someone who can't get into her own account.
The takeaway
Before you sign the next "done-for-you" agreement, ask for three things in writing: who holds the login, where the documentation lives, and what leaving actually looks like. If any answer is vague, that vagueness is the real price of the package — you just haven't paid it yet. It usually doesn't show up on the invoice. It shows up eight months later, at the exact moment you can least afford to go looking for it.
A good builder will have all three ready before you ask, usually in the same document as the proposal itself, not bolted on afterward because a client finally thought to ask. 🤍
Want a build that's actually yours from day one? Start here: Discover