I’ve decided I really like coding in Softr and whilst I’m not an expert I think I could offer some app development help alongside my existing data management consultancy work. If you do this already, how do you manage Softr accounts for projects that you create - do you get the client to purchase an account of their own, do you build in your account and leave it there or do you transfer it afterwards?
I operate in the non-profit/Charity space, so non-profit discounts would be a consideration.
Simon
Hey Simon,
I always work in my clients’ accounts.
I wouldn’t recommend transferring apps created in your workspace to your clients’ workspaces, as it involves additional work and can lead to various edge cases.
The client is always the owner of the app (and the workspace), as doing otherwise would create numerous conflicts regarding data ownership and your responsibilities as a developer.
2 Likes
For client work, I would avoid keeping production apps in your own account long term.
The cleanest pattern is: prototype in your own sandbox only when needed, then have the client own the Softr workspace before launch. You stay on as an admin/collaborator, document the app map and billing owner, and leave them with the non-profit discount path, DNS/access notes, and a short handoff checklist. That keeps billing, data ownership, and continuity clean if they later change consultant.
For smaller non-profit builds, I would also separate the consulting fee from the Softr subscription in the proposal. It makes the discount conversation clearer and avoids you becoming the accidental reseller/support desk for their plan.
TinyOps Studio uses this kind of ownership/handoff checklist for fixed-scope workflow and no-code builds. Happy to share the checklist if useful: Softr Client Handoff Checklist - TinyOps Studio
1 Like