The complete checklist for launching a SaaS, from domain to first payment

Every step between a working app and a product strangers can pay for, in the order that avoids rework: domain, DNS, hosting, database, email, payments, analytics.

Why the order matters

Most first launches take days longer than they should, and the reason is rarely the code. It is doing the setup in the wrong order. You create the payment webhook before the domain exists, so you create it again. You verify email on a temporary address, so you verify it again. Each redo is small. Together they are your weekend.

The order below is the one where every step can rely on the step before it. Follow it top to bottom and you set up each thing once.

1. Domain first

Everything else hangs off the domain. Your sending email address uses it. Your payment provider wants to see it. Search engines index it. Your webhook addresses include it. If you start on a temporary address from your host, you will rewire all four later.

Pick a name that is short and easy to say out loud, and check it is free before you get attached. Buy it at a registrar that also runs your DNS if you can: it removes one connection you would otherwise have to make by hand.

2. DNS zone

DNS is the address book that says where the domain points. You need a zone for the domain and, later, a handful of records in it: one or two for the website, three or four for email, one for search verification. Create the zone now, add records as each later step asks for them, and never edit a record you do not recognise.

3. Repository

Create the repository before the hosting project, because modern hosts deploy from it. Keep it private, commit a starter app that runs, and decide the branch that goes to production. Every later step that produces a secret must write it to the host, never into this repository.

4. Hosting and database

Create the hosting project and connect it to the repository so that every push to the production branch deploys. Add the database in the same project when the host offers one: one bill, one set of logs, and the connection string is wired for you.

Wait for the first deploy to finish before you move on. A surprising number of later problems are a first build that never went green.

5. Point the domain at the site

Add the domain to the hosting project, create the records the host asks for, and wait for the certificate. On a domain you bought minutes ago this can take a while, because the rest of the internet has to learn the domain exists before a certificate can be issued. It is waiting, not a fault.

6. Sending email

Transactional email means sign-in links, receipts and notifications. Mail from a brand-new domain is distrusted until the domain proves who it is, which is done with DNS records called SPF, DKIM and DMARC. Add the domain at your email provider, create the records it gives you, wait until it shows as verified, and only then create the API key your app will send with.

Also decide where mail sent to you lands. If nothing is set up, mail to hello@yourdomain bounces, including replies from your first customers. Forwarding to an inbox you already have is enough.

7. Payments, in test mode

Create the product, the price and the webhook endpoint in test mode. The webhook is how your app learns that someone paid, so its address must be your real domain. Make a full test purchase with a test card and confirm your app received the event before you think about real money.

8. Secrets in the right place

By now you hold a dozen keys. Each belongs in the host's environment variables, read by name in your code. None belongs in the repository, in a chat window or in a screenshot. Write down only the names, so your coding tool knows what exists without ever seeing a value.

9. Health check

Before you tell anyone, test four things against the live domain: the site answers over HTTPS, the database accepts a query, an email is accepted for delivery, and a test payment event arrives. If all four pass, the foundations are sound.

10. Then, and only then, build

With the setup live, give your coding tool a brief that names what exists: the host, the database, the variable names, the webhook path, the sending address. An AI that knows the real stack builds on it. An AI that has to guess invents its own.

How long this takes

By hand, with accounts to create and docs to read, plan for a day or two the first time. The steps never change from product to product, which is exactly why they are worth automating. Shipyard runs this checklist for you in the same order, on your own accounts, and asks before the one step that costs money.

Launch in an hour, not a weekend

Shipyard connects your accounts once, then sets up the domain, hosting, database, email and payments for every new product.

See how it works

Read next

The complete checklist for launching a SaaS, from domain to first payment – Shipyard