NexBroad-Reach: Building Our Own SMS & Voice Platform
A multi-tenant SMS and voice broadcasting platform, built by the same team that takes on client work — the standard we hold for a client's software, applied to our own.
What we set out to build
We wanted a project that would test the same practice we sell to clients: real multi-tenancy, real billing, real telephony, built and operated end to end rather than handed off after launch.
The shape of the problem was concrete. An organisation needs to reach a list of people by SMS or voice, read what comes back in one place as a team, and pay for what it actually sends — without a subscription tier standing between a small org and a large one.
None of that is unusual on its own. Doing all of it under one multi-branch, role-scoped account, on carrier-grade telephony, with billing that meters usage exactly rather than in bundled tiers, is the part that took real architecture.
How it was built
Model the tenancy first
Organisations, branches and roles — org admin, branch admin, admin, broadcaster — went into the schema before any product code, so access boundaries are enforced by the platform rather than by convention layered on later.
Build the telephony spine
SMS and voice broadcasting on carrier-grade infrastructure, with text-to-speech calls that capture a DTMF keypress as structured data — not a transcription to parse, a digit to branch on.
One inbox, not one phone
Every reply — to a text or a voice call's follow-up message — routes into a shared inbox the whole team can work from, with STOP/START/HELP handled automatically and custom keyword rules layered on top.
Meter usage, not seats
A prepaid credit balance shared at the org level, drawn down per message and per voice-minute, so cost tracks what actually gets sent instead of a subscription tier chosen in advance.
Report delivery per recipient
Sent, delivered and failed status tracked per person on every broadcast, so a campaign's outcome is a report rather than a guess about who received it.
What shipped
NexBroad-Reach is live and running — every capability described above is in the product today, not on a roadmap. The interactive demo at /demo is the same interface, on sample data.
We don't publish user counts, revenue, or client names for it, for the same reason we don't invent them for anyone else's project: we haven't measured what we're not willing to state precisely. What's verifiable is the product itself.
See it, don’t take our word for it
The product this case study describes is running today.
Tell us what you want built
A short brief is enough to start — what you're trying to do, and roughly for whom.