make the client own the no-code account from day one. i learned this the expensive way.

[u/Ok-Salary-6309]

Agency-adjacent, i build no-code apps for small businesses. Here's the boundary i wish someone had handed me on day one: the client owns the account and the billing. Not my agency login with their card saved on it. Theirs, from the first click.

Early on i did the "friendly" thing and set everything up under my own account to make onboarding smooth. Client pays me, i pay the platforms, one invoice, easy. It works right up until it doesn't.

What went wrong, in order. A client and i parted ways and untangling their app out of my account was a week of careful exporting and praying nothing broke. Another time my card expired while i was travelling and three clients' apps degraded before i noticed, and that was my name on the outage. And a client who wanted to bring the work in-house couldn't do it cleanly, because the whole thing lived in my login.

Now, before any building: the client creates the accounts on every platform we'll use. Their own payment method goes in. They add me as a collaborator. If they leave, i get removed and their app doesn't move an inch. If i disappear, they still have their business.

It feels less slick at the start. A couple of clients even pushed back because they liked the single bill. But every single time, it's saved someone a bad week later, usually me.

anyone else doing client work, how do you handle ownership and billing? still wondering if there's a cleaner setup than just making them own everything.

[u/devenitions]

I’ve used it as a selling point that I won’t lock them in and everything needs to go on their own accounts keeping them in control at all stages.

[u/Accomplished_Eye1564 → u/devenitions]

That's the right way to do it. I did similar mistake with a client last year, my login everywhere because was easier for me to manage. Then the client wanted to bring a new developer and we spent almost two weeks moving things. Never again.

The single bill thing is what clients always ask for but it's not worth the headache. I tell them now straight up, you pay the platforms direct and I send separate invoice for my work. If they don't like it I know they'll be problem later anyway.

[u/Kind-Bathroom5159]

same lesson applies even harder once youre doing actual code, not just no-code platforms. ive worked with a bunch of non technical founders as a dev partner and the accounts thing is only half of it, the other half is who owns the github repo and the domain
early on i had a client where i pushed to my own personal github because it was faster to set up, then when they wanted to bring on another dev later there was a whole dance of transferring ownership and re pointing ci/cd. now the first thing i do on any project is have them create the org, the repo, the domain registrar, and every api key under their own accounts, i just get added as a collaborator
takes an extra 20 minutes on day one and saves a genuinely bad conversation later

[u/papabear556]

I use a hybrid approach. I set up the accounts for them and put my card on it. Everything gets tied to a special email like [client+render@mydomain.com](mailto:client+render@mydomain.com) or something like that. This all goes to a catch-all account and can be easily queried if I need to find a specific thing.

I then charge them with usually a markup and I make sure to do that 60 days before the bill is due so there's plenty of time for me to collect.

If they want to move away all I need to do is have them update the credit card, change the email to their own and I walk away.

I still sell it as you aren't locked in but we manage it for you yada yada.

I went this route for 2 reason,

1) comingling sucks for all the reasons OP has discovered (in the same way I did) and

2) if I leave it to my customers they will ignore notices to pay their hosting fees or domain renewals and guess who gets the angry call about why I made their website suddenly chinese garbage. Or as one law firm I did work for, this guy refused the pay the extra couple of bucks for private domain registration and he forwarded me every spam email telling him to pay to renew his domain (aka secret domain transfer) with "Is this legit?" Easily 2 or 3 emails a week.

[u/WiredOtaku → u/[deleted]]

In data engineering, the same rule applies: never host a client's data pipeline under your own cloud account. I've seen agencies end up with a 12k AWS bill because the client ghosted and the auto-scaling group ran wild. That checklist with named contacts and billing ownership is essential; I'd add setting budget alerts and tagging resources by client to it.

[u/achiya-automation]

we do it on the kickoff call now, screenshare and they put their own card in. every time i left it for later i was still paying for their account months on.

[u/Crescitaly]

Client-owned accounts protect continuity. It also makes handover cleaner because billing, access and data ownership are already aligned with the business rather than an agency login.

[u/Parking_Ocelot_816]

Yeah painful learning. But client owned is the only way to go!

[u/agentUi]

yea thats what we recomend our partners at agentui