I built a full multi-tenant CRM SaaS from scratch. Here's what I'd do differently. Knit CRM start...I built a full multi-tenant CRM SaaS from scratch. Here's what I'd do differently. Knit CRM start...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Sunil's avatar
Sunil Kumar
• Sep 6
I built a full multi-tenant CRM SaaS from scratch. Here's what I'd do differently.
Knit CRM started as a "small internal tool." It became a multi-tenant SaaS with per-workspace billing, role-based access, and a pipeline view that people actually use daily.
3 things that saved me weeks 👇
1. Multi-tenancy from day one. Retrofitting it later is the most expensive mistake in SaaS.
2. Ship the boring dashboard first. Clients care about "can I see my numbers today," not animations.
3. One stack, no experiments. Laravel + Next.js for this one. Django + React when the data model is heavier.
1 thing I'd change: I over-built settings pages nobody opened. Build the settings *after* your first users complain.
Currently taking on 1-2 new SaaS / CRM / dashboard builds this month. If you've got an idea stuck in Notion, DM me. Happy to give you an honest scoping call, no pitch.
Quick question for the builders here. What kills more SaaS MVPs?
A) Building too much before launch
B) Launching too early with a broken core
Drop A or B in the comments 👇
Full Stack DevelopmentsaasWeb Development
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started