You own it or you rent it

Custom SaaS Development for Nontechnical Founders: Hold the Keys Even If You Never Touch the Code

You will probably never open the code. That is fine. Most people never open the engine of a truck they own. They do keep the title in a drawer and the spare key on a hook, and they know whose name is on the registration. Software asks for the same three things.

November 19, 2026 · 10 min read

acmeclaimlog.com · who holds the keys
If the developer stopped answering tomorrow
Five of eight checks pass, and the code is not one of them
  • PassDomain registrant is the company
  • PassStripe account owned by the company
  • PassHosting on a company card
  • PassEmail sending account
  • PassError monitoring login
  • FailCode repositorydeveloper's account
  • WarnDatabase and backupsshared login
  • FailSigned copyright transfernot on file
Illustrative: a sample review for a fictional one-person software company

The short answer

A nontechnical founder can own a custom SaaS without reading code by holding the repository, domain, hosting, database and Stripe accounts in the company's name, with developers invited as users, and by getting a signed written transfer of copyright. Paying an invoice may not transfer ownership, so have your attorney check. Your job in the build is the rules, examples and testing.

On this page
  1. You know the trade, and that is the scarce part
  2. Eight accounts that should carry your company's name
  3. Paying the invoice may not make the code yours
  4. Moving a repository to your own account, step by step
  5. Work that stays on your desk, whoever writes the code
  6. A first scope that protects you from everyone, including us

You know the trade, and that is the scarce part

Say a former insurance adjuster in Mobile, invented for this example, knows exactly how a claim photo log has to be kept to survive an argument. She has watched three companies get it wrong. She cannot write a line of code. A developer can learn how to build the screen quickly. Learning what twenty years of bad claims taught her would take twenty years. In this partnership, she is the expert.

Founders in her position tend to apologize for not being technical, and then behave as if that apology were a contract. They hand over the logins. They let the developer set up the accounts because it seems polite. Nothing in this is foolish, and most developers are honest. But it means the only working copy of the company belongs, in practice, to someone who has other clients.

Keep two things separate. Checking the quality of a developer's work is one job, and our fractional CTO page for non-technical founders covers how to do that without a code editor. Holding the keys is another job, and you can do it yourself this week, for free, before a single feature exists. This page is about the second one, plus the work that only you can do.

Eight accounts that should carry your company's name

For each item, the test is simple: if your developer stopped answering tomorrow, could you log in, see everything and add someone new? Set them up yourself before work begins, with a company email address you control and two-factor authentication turned on. Then invite the developer in. Doing this first takes an hour or two. Unwinding it later can take a dispute.

What a nontechnical founder should hold from the first day
What it holdsWhat goes wrong if it is not yours
Code repositoryEvery version of the productYou paid for software you cannot lay hands on
Domain registrarYour address on the internetThe product and its email can vanish at renewal
HostingThe running productSomeone else's card, someone else's off switch
Database and backupsYour customers' recordsThe business is the data, and you cannot reach it
StripeSubscribers and their payment methodsYour recurring revenue sits in another party's account
Email sendingYour sending reputation and templatesPassword resets stop, and you do not know why
Error monitoring and analyticsWhat is breaking and who uses whatYou learn about problems from customers
Apple and Google developer accounts, if anyStore listings and reviewsYour app is published under a stranger's name
Dark green chalkboard with chalk arrows and doodled boxes, a black-and-white halftone cutout of a heavy ring of keys in front, no words or numbers
Eight accounts, one ring. Whoever holds it can change developers without asking anyone.

The Stripe row surprises people most. A subscriber's relationship and saved payment method live in the Stripe account the product was set up on, so a developer's account is the wrong home for your revenue. The domain row has an outside authority behind it. In a March 26, 2018 post, ICANN advised against listing website designers, hosting providers or other third parties as the registrant of your domain, and said you should never give anyone your account login. An expired domain is its own small emergency.

Paying the invoice may not make the code yours

Here is the awkward part, and we are not lawyers, so take this section to your own attorney before relying on it. Many founders assume that paying for code means owning it. U.S. copyright law does not work on that assumption. The U.S. Copyright Office's Circular 30, revised August 2024, says a commissioned work is made for hire only if it falls into one of nine listed categories, and there is a signed written agreement saying so.

Read that list and you will find atlases, translations and instructional texts. Software is not named. Whether a given product could fit some category is a question for your attorney. The point for you is that "work for hire" typed into a contract may not do what you assume. 17 U.S.C. 204(a), as published by Cornell's Legal Information Institute and read November 6, 2026, says a transfer of copyright ownership is not valid unless it is in writing and signed by the owner of the rights.

Practical control and legal ownership are different protections, and you want both. A signed transfer with no copy of the code gets you an argument. A copy of the code with no transfer may get you a different argument. The page on outsourcing a SaaS as a solo founder goes through the rest of the contract in plain words.

Moving a repository to your own account, step by step

If the code already sits in your developer's account, moving it is usually a polite email and a few minutes of their time. The steps below follow GitHub's documentation on transferring a repository, read November 6, 2026, and other hosts have their own versions. Two of them matter more than they look, because the transfer leaves the former owner with access by design.

  1. 1

    Create a company account or organization

    Use a company email address and turn on two-factor authentication. GitHub says the person moving a repository needs administrator access to it, plus permission to create repositories in the organization receiving it.

  2. 2

    Ask the developer to transfer it

    GitHub says issues, pull requests, the wiki, stars and watchers move with it, commit history is preserved, and links to the old location redirect.

  3. 3

    Review who still has access

    GitHub says the original owner is added as a collaborator on the moved repository. That can be perfectly fine while they still work for you. Decide deliberately, and set a reminder for the day they stop.

  4. 4

    Treat the secrets as still shared

    GitHub says webhooks, secrets and deploy keys remain associated after a transfer. Our advice: at the end of an engagement, have someone change the keys the former developer could have seen.

  5. 5

    Keep your own copy somewhere else

    A second backup of the code and database under your control, somewhere other than the main host, means a locked account is an inconvenience rather than a disaster.

If a developer balks at step two, listen carefully to the reason. There may be a legitimate unpaid invoice, which you can settle. But a developer who will not let you hold a copy of what you are paying for is telling you how the end of this relationship will go. When someone has already vanished, read what to do when your web developer disappears, which covers domains, hosting and logins in order.

Work that stays on your desk, whoever writes the code

Hiring a developer does not hire a product owner. A good builder will ask you hundreds of small questions, and each unanswered one gets answered by a guess. Those guesses become your product. These are the five jobs a nontechnical founder cannot hand off, and they are also where your experience earns more than any framework could.

The rule book

Every rule in sentences, with two real examples. "A claim photo needs a date and a room name, and cannot be edited after the claim closes." Developers can build a sentence.

Example data

Twenty realistic records, including the ugly ones. Edge cases come from your memory, and test data invented by a developer never includes the customer with two addresses.

Acceptance

You test each finished piece on your own phone against the rule book, and you say yes or no. Silence gets read as yes.

Customer conversations

Nobody else should run these. Sit in on the validation calls yourself, and keep doing them after launch.

Saying no

Scope grows through small agreeable requests, many of them yours. Keep a later list so that every idea has a home that is not the current invoice.

Every question you leave unanswered gets answered by a guess, and the guess ships.

A first scope that protects you from everyone, including us

A scope is the document that says what you are buying. A poor one lists features. A good one lists what someone can do, what the system refuses to do, and how you will know it works. If the stages from idea to web app are new to you, start there. Whoever you hire, make sure the page answers the questions in the left column, and be wary of the items on the right.

Get in writing

  • Every screen, and who can see it
  • The accounts and whose name each sits in
  • The monthly running cost by line
  • How payment ties to things you can click and test
  • What happens to the code and keys if either side stops
  • How a customer exports their records

Leave out for now

  • A native phone app
  • Dashboards for numbers you do not yet have
  • "AI-powered" as a requirement with no job attached
  • A second kind of customer
  • Anything justified by the word "eventually"

Our own side of this: web apps at DataCram start from $575, depending on complexity, and a real SaaS costs more, so we quote it after a conversation. On websites we build, the code, domain and hosting account are in your name, and on any app scope you should ask for that same sentence in writing, from us or anyone else. Published prices are here, and financing for web applications takes 25% down with up to 12 months at 0%. Our custom software page covers smaller tools.

We also have a conflict worth naming. We bill for building, so we are not a neutral judge of whether you should build. If you want someone on your side of the table, the fractional CTO seat exists for that, and our page on choosing a technology partner lists questions to ask any builder. Our starting point for small software products and the wider small-business section cover the rest. A call to (210) 346-0848 gets you a person, and no pretense that you should learn to code first.

Questions owner-operators ask

Not for a small product with one job. A narrow subscription tool can be built by a contractor or studio if you hold the accounts and own the rules. A co-founder makes more sense when software is the entire long-term business and needs constant judgment. Giving away half a company is a much larger price than most first versions, so compare carefully.

Make a list of every service the product uses, then ask, without drama, for each to be moved to a company account with your email as owner. Frame it as housekeeping, because it is. Start with the domain and repository, since those are hardest to replace. Most honest developers will be relieved. Note any refusal and its stated reason.

You can often build a working demo, and that is a cheap way to test whether anyone wants it. Before strangers trust it with payments and records, have someone who can read code review how logins, data separation and billing work. We use these tools ourselves, and the mistakes they make look exactly like working software until someone tries something unusual.

Test it like a customer, against your written rules. Ask for a staging link, which is a private working copy, and use it on your own phone. Try the three things customers do most, then try the wrong things: an empty form, a wrong date, another customer's address. Write down what happened, and let the developer decide why.

We are not lawyers, so ask yours. Our concern with a generic template is that the words may not match the law you assume applies. The U.S. Copyright Office says commissioned works are made for hire only within nine listed categories. A short, attorney-reviewed agreement with a signed written transfer of copyright is usually inexpensive compared with arguing over ownership later.

Keep reading

Free · No obligation

Tell us what you know and what you cannot see

Describe the product, who has built what and which accounts you hold today. A person replies with what to secure first and what a build would involve, in plain words.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote