Every business that exists online started with somebody typing a name into a search box to see if it was taken. What happens in the hours after that is the part nobody warns you about.
The setup tax
Here is the usual shape of it.
You buy the domain at a registrar. The registrar sells you privacy protection, then tries to sell you hosting, then tries to sell you email. You decline, because someone told you to use a different provider for email. So you open a second account somewhere else, and that provider asks you to prove you own the domain — by pasting a string into a DNS record back at the registrar, in a control panel with a table of TXT and MX and CNAME rows you have never had a reason to think about.
An hour later the verification still says pending, because the change has not propagated, or because the row went in the wrong column. Then there is a third account for the website, a fourth for the payment processor, and a fifth for whatever runs your customer list. Each one wants the domain proved again in its own dialect.
None of this is your business. It is the toll you pay before your business is allowed to start, and it is charged in the currency you have least of in week one: attention.
Step one: the domain arrives already configured
Buying a domain should be the moment everything else gets easier, not the moment five other setups begin.
So the purchase does the configuration. You search, you pick a name, you pay. Behind that, the platform is the registrar of record, which means the DNS is not something you are then sent off to go and edit — it is something already written on your behalf. The sending identity is registered. The DKIM records, the custom MAIL FROM, the DMARC policy: written through the registrar at purchase time, exactly the rows a bring-your-own-domain customer would have been handed as homework.
Ownership is not a claim to be verified either. The platform registered the domain, so ownership is a fact it created rather than a question it has to ask you. There is no verification dance, because there is nothing to verify.
The domain lands owned, resolved, and mail-ready. That is the whole point of doing it in one place.
Step two: mailboxes for you, and for everyone you hire
A business email address is the first thing that makes a company look like a company. It is also, traditionally, its own project: another subscription, another admin console, another per-seat bill that grows every time you hire.
Because the domain is already configured, the mailboxes are the easy part. You get an address on your own domain, and so does everyone on your team — assigned the same way you assign anything else here, to a person or to a department. The front desk address routes to the front desk. The hiring address routes to whoever is hiring. Someone leaves and their mail follows the role, not the person.
The test we set for ourselves on this was blunt: if the owner cannot sign into their own business email on their iPhone, it is not really theirs. So mailbox access is being built to work in the mail app people already use, not only in a web page we control.
Step three: the site, on the domain you just bought
Now the website has somewhere to live, and the pieces underneath it already exist.
You are not standing up a payment system, a login system, a customer database, and a scheduler before you can publish a page. Those are running already. Building the site is choosing what it says, what it collects, and what it looks like — and the forms on it are wired into the customer list from the first submission rather than after a project to connect them.
It publishes to the domain from step one. Not a subdomain of ours with your name in front of it. Yours, in the address bar, where a customer's bookmark and your search ranking both accumulate to you.
We wrote about that part on its own, if you want the longer version: building a real website with no developer and no code.
Step four: the part that lasts
The first three steps take an afternoon. The fourth one takes years, which is why it is the one worth choosing carefully.
The quote you send is attached to the customer who asked for it. The job that comes out of the accepted quote is attached to both. The invoice is attached to the job, the payment to the invoice, and the review request goes out after the work is done because the work being done is a thing the system knows. Your staff see the parts they manage. You see all of it.
That continuity is the whole argument for starting in one place. Not that any single step is dramatically faster on its own, but that step four inherits everything the first three set up, instead of asking you to reconcile five accounts that each know a quarter of your business.
Where this stands today
Being straight about the current state, because the sequence above is not all equally open yet.
- Domain purchasing and hosted business email are in a limited beta. Both are built, connected to each other, and running — for our own workspace while we finish the production chain behind them. They are not open to every workspace yet.
- The website, the forms, the CRM, quoting, jobs, invoicing, the storefront, and the team tools are shipped and in daily use.
The reason to talk about the sequence before every step of it is open is that the sequence is the actual product. Domains and mailboxes are not features we added because they were adjacent; they are the front door, and a front door that opens onto a different building than the rest of the house is not worth much.
The beginning of the journey and the running of the company were always meant to be the same system. We are most of the way there.