Collapser — working note, 15 July 2026
You don’t have an email problem. You have a billing misunderstanding that grew an email problem around it.
01 / What went wrong
Every project got its own Google account. Five accounts, five bills, five inboxes, five spam folders. About thirty-five dollars a month to check five places.
That felt expensive, so the workarounds started: forwarders, routing services, a small app to move mail around. Each one solved a piece and broke something else. The last one broke spam filtering — junk started arriving that Google would have caught, because mail that gets forwarded and rebuilt loses the fingerprints that prove who really sent it.
None of that was necessary. Every workaround existed to route around a cost that was never real.
02 / The one rule
Google charges for people, not for addresses, domains, or companies.
An address is a name. A mailbox is a login. You can hang as many names as you like on one login — Google has never charged for that. It charges when a second human needs their own login. That’s the whole pricing model, and everything below is just applying it.
03 / The shape
A domain lives in exactly one Google organisation. Never two. That single constraint decides everything else, and it sorts your domains into three piles on its own.
Domains you own, where you’re the only person sending. Every address here is a free name on the one mailbox you pay for. Nothing forwards.
Not your domains. Other people need addresses here, so it runs its own organisation. It issues you a seat — the ordinary cost of employing you.
Same shape. Their domain, their organisation, their seat for you. You forward it home and reply through it.
04 / Who pays for what
Read down the right column. Almost everything is free, and the parts that aren’t are somebody’s payroll expense, not yours.
| Item | What it is | Cost |
|---|---|---|
| geo@seedbed.studio | Your one real mailbox. The only thing you open. | $7.20 |
| Five more domains | Secondary domains in your org. Adding one costs nothing. | free |
| Every address on them | geo@fieldbasehq.com, desk@kataro.studio, support@sameorbit.com, and 27 more. | free |
| Sending as any of them | Same organisation, so it just works. Nothing to configure per address. | free |
| Morley | A second human who needs to send as fieldbasehq.com. Fieldbase pays. | $7.20 |
| Your Enlighten seat | Covers enlightenlab.ai and ritareader.ai together. EnlightenLab pays. | $7.20 |
| Your Luze seat | Luze pays. | $7.20 |
| Out of your pocket | $7.20 / month |
05 / The asymmetry
Every domain you care about can live in one organisation, so every address you own is just another name on the mailbox you already have. Mail arrives at Google and stops. There’s no forwarding anywhere in your setup — which is exactly why the spam filter stays intact.
Your colleagues can’t do that. Morley’s home inbox lives somewhere else, and no address crosses between organisations. So his Fieldbase mail has to forward. Same for Julie, same for anyone whose real inbox is elsewhere. That’s structural. No product fixes it.
The lesson isn’t that forwarding is bad. It’s that forwarding unfiltered mail is.
06 / Three checkboxes
The architecture is most of the work, but these three settings are what turn it from “technically correct” into something you stop noticing.
On any seat in someone else’s organisation. Mail arrives, leaves, and nothing stays behind. The account stops being an inbox and becomes a pipe — nothing accumulates, so there’s nothing to check.
When you add a sending address, this checkbox decides whether the address is youor a costume. Leave it unticked and recipients see “on behalf of” — the mask slips.
The one nobody knows exists. Mail to hello@fieldbasehq.com arrives, you hit reply, and the right name is already on it. You never choose a hat. This is the setting people are actually asking for.
07 / Doing it
One user: geo@. This is the only bill you’ll ever pay. Business Starter, about $7.20 a month, less if you pay yearly.
collapser.one, kataro.studio, fieldbasehq.com, sameorbit.com, sameorbit.app. Adding them is free — you only ever pay when you create a person on one. Pick the right kind: see the first deep dive below, because the wrong choice looks identical and quietly can’t do what you want.
A record to prove you own it, one for mail delivery, three for signing and policy. You add them wherever your DNS already lives. Your nameservers don’t move. Your sites don’t notice.
geo@fieldbasehq.com, hello@fieldbasehq.com, desk@kataro.studio, support@sameorbit.com, privacy@collapser.one. Thirty of them, free, any mix of domains. Then turn on the three settings above.
EnlightenLab and Luze already exist and already issue you an address. Set each to forward-and-delete into your inbox and add it as a sending address. Nothing announced, nothing coordinated, invisible to everyone else.
Morley is the full pattern — different organisation, wants both identities, needs real sending. If he works, everyone works. Until then this is a plan that’s only been tested on the person who wrote it.
08 / If you want the mechanism
Not a manual. Just the handful of things where knowing why saves you from a choice that looks fine and isn’t.
When you add a second domain, Google offers two kinds. They sound like synonyms. They aren’t.
A user alias domain is free and automatic: every person in your organisation instantly gets their same username at the new domain. Add kataro.studio and geo@seedbed.studio also becomes geo@kataro.studio. Done, no work.
But that’s allyou get. When you go to create desk@kataro.studio, the domain isn’t in the list. It can’t be. Alias domains only ever mirror usernames you already have. If you want addresses that aren’t your own name — support@, hello@, desk@ — this option can never give them to you.
A secondary domain shows up in the list. You type desk, pick kataro.studio, done. And the domain itself is free — the charge is per person you create on it, which for your own domains is nobody.
There’s a second reason too. Alias domains always stamp your primary domain on the outgoing envelope, so one of the two signatures that proves you’re really you never lines up. It’s survivable — the other signature carries it — but there’s no reason to accept a broken half when the alternative is free.
Gmail’s spam filter isn’t mostly about the words in a message. It’s about the sender. Google has seen that domain send millions of messages to millions of people, and it knows what happened to them.
Mail carries signatures proving which domain really sent it. The old setup received mail, pulled out the text, and sent a brand new message from your own address — a perfectly valid message from a domain you own and correspond with constantly. Google’s filter looked at it and saw mail from you. Of course it let it through.
Two things make the new setup immune. Your own mail never forwards at all — it arrives at Google and stops, so there’s nothing to launder. And when a colleague’s mail does forward, it forwards after Google has already filtered it. Gmail forwards from the inbox, never from spam. Only clean mail travels.
Receiving is easy — mail can be handed off to anyone, anywhere. That’s why an address costs nothing.
Sending is a claim. When a message goes out saying it’s from you@yourdomain.com, the receiving server checks whether whoever actually sent it was allowed to. That check needs a cryptographic signature that only the organisation holding the domain can produce.
So if Morley’s home inbox is somewhere else, his Gmail can’t just assert it’s Fieldbase. It has to hand the message to Fieldbase’s mail servers and let them sign it. That handoff needs a login. The login is the seat. The seat is the $7.20.
The trap: Gmail offers an easier-looking option that skips the handoff and sends directly. It appears to work. But the message goes out signed by the wrong domain, and increasingly, recipients silently drop it. The harder path is the only one that’s real.
This is also why you pay nothing for six identities and Morley costs money for one. Your domains are all in your organisation — you’re already logged in. He isn’t.
Three separate things get confused constantly:
So per domain you add five records where your DNS already lives: one proving ownership, one directing mail to Google, and three for signing and policy. Your site keeps serving exactly as it does now.
Every person’s collapse is independent. You do yours today. Andrew asks in two weeks and gets his in ten minutes. Julie can keep two inboxes for a year and nothing about that blocks anyone.
That’s because the domain-level work is already done — the organisations exist, the addresses exist. What’s left is two settings on one account, and those settings are local to the person. Nobody else can tell.
So there’s nothing to announce and nothing to sell. You do yours, someone notices you stopped checking three accounts, they ask. It spreads by envy.
What doesn’t work this way: merging two organisations into one. That’s a real migration with real destruction, and it saves $7.20 a month and buys nothing anyone can feel. Don’t.
09 / State of understanding
Calendars.If someone sends a meeting invitation to desk@kataro.studio, we don’t know whether it lands on your calendar with working buttons, or just sits in your inbox as an attachment you add by hand. Nothing gets lost either way — an address with no mailbox has nowhere else to put it. But the difference between “seamless” and “a small chore forever” is real, and it’s the one thing here that could change the shape.
And invitations to your seats at other organisations land on their calendars. You can overlay all of them into one view, but the same meeting invited to two of your identities will show up twice. One view, not one event.
Test it early. It costs two minutes and it’s the only unknown that matters before you move anyone else.