Hiring it out, eyes open
Outsourced SaaS Development for Solo Founders: What Goes Wrong, What to Sign and Who Holds the Keys
Nobody plans the last day of a software project at the start. There is a kickoff call, a cheerful spreadsheet and a logo. The last day arrives anyway, sometimes after a clean handoff and sometimes after an email nobody answers. This page is mostly about making that day uneventful.
November 19, 2026 · 10 min read
- repo clone from company account: ok
- second developer runs project from notes: ok
- backup restored, 212 records checked by owner: ok
- deploy without original developer: FAILED, key on his laptop
- last payment held until release process is written down
The short answer
A solo founder can outsource SaaS development safely by holding every account from the first day, signing an attorney-reviewed contract with a written copyright transfer, paying against features you can click on a private link, and rehearsing the exit before the final payment. Choose freelancer, shop or studio by who answers once the project ends, not by the lowest hourly rate.
On this page
- Six quiet ways an outsourced build comes apart
- Four ways to buy the work, and where each tends to break
- What the contract should say, in words you can repeat
- Milestones that cannot be faked with a nice slide
- An exit rehearsal, before the final payment
- Warning signs, and what to do on the bad day
- The same questions, turned on us
Six quiet ways an outsourced build comes apart
Say a former property manager in Omaha, invented for this example, hires out a move-out inspection tool. Nobody in this story is a crook. Her developer is capable and pleasant. She has paid most of the budget, she has seen a good demo twice, and she has no idea what would happen if he took another job. That is the usual shape of the problem: nothing looks wrong until something does.
The laptop demo
It works beautifully in the meeting, on the developer's machine. There is no link you can open on your own, so the product exists as a performance.
The hidden team
You hired a person. Your code is being written by someone he subcontracted to, whose contract with him nobody has seen, and whose rights nobody has transferred.
The scope that grew from both ends
You kept adding small requests, and each one seemed reasonable. The vendor kept agreeing, then billing. Nobody kept the list.
Ninety percent done
The early screens come quickly, so the project feels nearly finished. Billing, permissions, errors and every odd case are still ahead, and these take far longer than the visible part.
The sole deployer
One person knows how to put a new version live, using steps that exist only in their head and a key on their laptop.
The disappearing act
A new job, a family problem, a better client. Rarely malice. Your repository is in their account, and they are not answering email.
Each of those has a cheap prevention, and all of them are easiest to fix before the first payment. A solo founder has no in-house engineer to notice any of this early, and no spare budget to absorb it late. You can check the work without reading code, too: our fractional CTO page for non-technical founders covers those signals, so we will spend this page on the buying decision, the paperwork and the exit.
Four ways to buy the work, and where each tends to break
No option here is the good one. Each suits a different founder, and each has a typical failure. We looked for a neutral figure on what each costs a solo founder and found none we trust, so there are no market ranges below. Ask for written scopes and compare those. One outside number for scale: the U.S. Bureau of Labor Statistics put the median software developer's pay at $135,980 a year in May 2025, which is why hiring an employee rarely fits a product that is not yet earning.
| Suits you when | Typical failure | Ask first | |
|---|---|---|---|
| Solo freelancer | Small scope, and you can stay close | One person is your whole risk | Who covers if you are sick for a month? |
| Overseas development shop | A clear scope and a budget that needs stretching | Hand-offs, turnover and scope read too literally | Who exactly works on this, and what happens if they leave? |
| Small studio | You want one accountable party who stays after launch | Costs more per hour, and you may wait your turn | Show me software you still run today |
| AI tools plus a paid reviewer | You can follow code a little, and the idea is unproven | A demo that passes for a product | Who reviews sign-in and billing before strangers use it? |

Location matters less than founders assume. We ran the local versus offshore math for San Antonio owners, wages and copyright included. Plenty of excellent developers work far away, and plenty of bad ones live down the road. What matters is overlap in the working day, written communication that you can understand, and a person who stays reachable after launch. We work across the US by phone, video and a shared project page, so we are hardly in a position to insist on a handshake. For a wider set of questions, read how to choose a technology partner.
What the contract should say, in words you can repeat
We are not lawyers. This list is a set of questions to bring to your own attorney, not legal advice, and you should have an attorney read anything before you sign it. The reason this matters more than usual: the U.S. Copyright Office's Circular 30, revised August 2024, says a commissioned work is made for hire only if it falls in one of nine listed categories, with a signed written agreement. Software is not named on that list.
- A written transfer of copyright. 17 U.S.C. 204(a), as published by Cornell's Legal Information Institute and read November 6, 2026, says a transfer is not valid unless it is in writing and signed by the owner of the rights.
- Subcontractors. Whether they are allowed, and that each signs the same transfer. Otherwise your rights may stop one person short.
- Earlier code and libraries. What the developer already owned and is reusing, what license you get to it, and a list of open source components.
- Payment tied to accepted work. Each payment names something you can click, with a set way to say no.
- Change requests. How a new idea gets priced and approved, in writing, before anyone builds it.
- The ending. Either side can stop with notice. On stopping, you get the code, data, keys and notes, and the contract says how.
- Confidentiality. Your customer data and your idea, with limits your attorney is comfortable with.
- Support after launch. Who fixes bugs, for how long, how fast and at what rate.
Milestones that cannot be faked with a nice slide
If a payment is tied to a percentage, you will reach ninety percent very quickly and stay there for a long time. Tie money to behavior you can test yourself on your own phone, on a private working link, using your own example data. If you cannot click it, it did not happen. The wording matters, so here are a few rewrites of the kind you will see in real proposals.
| Weak version | Strong version | |
|---|---|---|
| Sign-in | Authentication module complete | I can sign up, sign in, and reset my password from my phone |
| Data rules | Database designed | Signed in as customer A, I cannot reach customer B's record by editing the address |
| The main job | Backend 50% complete | I finish one real inspection with my own photos and get the report |
| Billing | Stripe integrated | I subscribe, get charged, cancel, and lose access, in a sandbox |
| Handoff | Documentation delivered | A second developer gets the project running from the written notes |
Hold back a meaningful share of the money for the last line. It is the only milestone that protects you from the failure modes above. Every other one can pass while the project stays dependent on one person. Stage-by-stage deliverables show what you should be holding before a build even starts, and what it costs to build and run keeps the monthly bill in view so a low quote cannot hide it.
An exit rehearsal, before the final payment
Fire drills exist because a burning building is a poor time to find the stairs. Run this one while everyone is still on good terms, ideally before you release the last payment. A competent developer will not be offended. A good one may even suggest it. Our page on holding the keys as a nontechnical founder lists the accounts that should already be in your name, so this rehearsal is about proving they work without your developer.
- 1
Hire one independent hour
Pay a second developer for a short review. Ask just one question: starting from the repository and the written notes, can you get this running without talking to the person who built it?
- 2
Deploy a change without the original developer
A small text edit is enough. If the release only works from one person's laptop, you have found the most important item on the punch list.
- 3
Restore a backup and open it
Use a safe copy. Look at real records with your own eyes. A log that says backups ran has told you nothing yet.
- 4
Clear out access
GitHub's documentation, read November 6, 2026, says the original owner is added as a collaborator on a transferred repository, and that secrets and deploy keys stay associated. When an engagement ends, remove access deliberately and change the keys.
- 5
Then write the last check
Pay promptly and with thanks. You now have a product someone else could take over, which also happens to be a product someone could buy.
A product only one person can deploy is a job for that person, whoever paid for it.
Warning signs, and what to do on the bad day
Some drift is normal. Dates slip, and people get sick. But a few patterns should change your behavior right away. Two or more of these together mean you should stop adding features, get a copy of the code and pay for an outside opinion before the next invoice. Few of these prove bad faith. They do mean your risk has grown while your bargaining position has shrunk, and neither gets better with time.
- Requests for access to your accounts are fine, but requests that you log in to theirs are not.
- Three status meetings in a row with the phrase "almost done" and no new link.
- New names on the commits or emails that nobody mentioned.
- Invoices that describe hours and never finished items.
- A refusal, however friendly, to put the repository in your account.
- A reply time that has quietly gone from hours to a week.
If someone has already gone quiet, our page on a disappeared web developer works through domain, hosting, code and logins in order. On domains, ICANN says, as read November 6, 2026, that you can start a transfer only if you are the registered name holder, the administrative contact or someone explicitly authorized to act for them. If you want someone on your side for a messy handoff, the fractional CTO seat was built for that situation.
The same questions, turned on us
You should ask us everything on this page. DataCram is a web studio in San Antonio, Texas, building for the web since 1999. We do not claim a shelf of solo-founder success stories. We can show you our own software, which we built and still run, and the rest of our work. Web apps start from $575, depending on complexity. A real SaaS costs more than that, so we quote it after a conversation, and our other prices are published.
On websites we build, the code, domain and hosting account are in your name. Ask us to write the same into any app scope, and read that clause with your attorney. We promise no outcome for your business, because no builder can. If demand is still a guess, test the idea first. The small software entry page, the wider custom software page and the hub for very small businesses cover the rest. Or call (210) 346-0848 and ask the awkward question directly.
Questions owner-operators ask
It can be, and location alone will not tell you. The risks that matter are the same everywhere: who holds the accounts, whether rights are transferred in writing, how much the working hours overlap and who stays reachable after launch. Enforcing a contract across borders can be harder, so practical control of the code and accounts matters even more. Ask your attorney about the contract's jurisdiction.
Fixed price suits a scope you can describe fully, and it moves the estimating risk to the builder, who will price that risk in and resist changes. Hourly suits work that is still being discovered, and it moves the risk to you. For most solo founders, we would cut the first version until a fixed price is possible, then handle changes as separate written requests.
Enough that the handoff still matters to the vendor, and not so much that a fair developer cannot pay rent while waiting. No standard number exists, so settle it in the contract with your attorney. Tie that last payment to a second developer getting the project running from the written notes, not to a calendar date.
That is a common and sometimes reasonable position, since they do not want to hand over unpaid work. A fair compromise is a repository in your account from the first day, with payment tied to accepted pieces and rights transferring as each is paid. Ask your attorney how to word it. A flat refusal to let you see the code is a different matter.
Yes, and for a founder who cannot read code, it can pay for itself by catching bad estimates and shortcuts early. That person can write the specification, review the work and run the exit rehearsal above. Check that they have no stake in the vendor they are grading. DataCram offers a fractional CTO seat, and we would disclose it if we were also the builder.
Keep reading
- You own it or you rent itCustom SaaS Development for Nontechnical Founders: Hold the Keys Even If You Never Touch the CodeCustom SaaS development for nontechnical founders: the eight accounts to hold, why paying for code may not transfer it, and the work only you can do.
- When the builder goes quietWhat to Do When Your Web Developer Disappears: The Domain First, Then Everything ElseYour web developer stopped answering. Secure the domain, hosting, code and logins in that order, using ICANN's rules, and know when to call an attorney.
- Hire them like a rooferHow to Choose a Technology Partner When the Money Is Your Own: Ten Questions, Asked of Us TooHow to choose a technology partner for a small business: who should own what, ten questions for any builder, and how DataCram answers those same ten.
- One owner, one phoneWeb Design for One-Person Businesses: What You Need and What to RefuseWebsite design for one-person businesses: the short page list, what to refuse to pay for, and fixed prices from $1,500, or when a builder plan is better.
- The build sideSmall Business Website Development: Who Holds the Keys When the Builder LeavesWebsite development for independent contractors: who owns the code, domain and accounts, what custom means at $1,500, and what you must maintain yourself.
- Probably not. Sometimes yes.iOS App Development for Small Businesses: When an iPhone App Earns Its KeepWhen an iPhone app makes sense for a very small company, what from $3,750 buys, Apple's fees and rules as of 2026, and what to try before you build.
- Everything in MicrobusinessSee the section
From the Insights desk
- Twelve Questions to Ask Before You Sign With Any Web CompanyBuying a website means judging work you cannot inspect, in a vocabulary chosen to keep you from inspecting it. Twelve questions that sort the field faster than any proposal — ask them of us, too.
- The Websites That Have to Behave: Dental, Medical, Legal, and Med SpaIn most industries a dropped form is an inconvenience. In a dental office, a clinic, a med spa, or a law firm, that form carried something private. Most of them are built so nobody can say where it went.
Get a second opinion before you sign or pay again
Tell us who is building it, what you have seen working and which accounts you hold. A person replies with what we would check first, and a quote if you want us to build or take it over.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.