Day 10: Franchise Architecture
ViberNet is expanding through franchise partners. I'm building the system to manage it. Here's what that actually looks like.
Growth creates complexity.
When ViberNet was one location, one team, everything lived in one portal and one person's head.
Now we're expanding through franchise partners. Each partner operates part of our network under the ViberNet brand, handles their own customers, collects revenue, and shares margins with us.
Our existing software wasn't built for that. So I'm building a franchise management system from scratch.
What it needs to handle:
- → Each partner sees only their customers, collections, and outstanding amounts
- → We get a consolidated view across all partners
- → Commission calculations automated, no manual reconciliation
- → Partners can never see each other's data
The architecture:
Single Laravel app. Multi-tenant by partner_id. Every query scoped. One database, separate databases per partner would add ops complexity that isn't justified at this stage.
The right architecture isn't the most elegant one. It's the one you can actually operate.
The hardest part:
Not the code. It's modeling the business logic before writing a single line.
Get the data model wrong and you rebuild everything six months later. That expensive week of thinking upfront is happening right now.
On that note, if you're based in J&K and interested in becoming a ViberNet franchise partner, we're actively onboarding. DM me or write to hey@vibernet.in.
Day 10 of my 30-day build-in-public series, sharing what I'm actually building at ViberNet and OpenLoop every day.