Building and shipping a customer-support SaaS

Context

ThriveDesk was a new entrant in a category with entrenched incumbents. The product needed to be feature-competitive at launch and fast enough that speed itself was a reason to switch — a hard combination, since features usually arrive at the cost of performance.

Constraint

Email ticketing is deceptively hard. Inbound mail has to be received, parsed, threaded, and attributed to the right conversation, across every mail client’s interpretation of quoting and reply formatting. Real-time updates then have to reach every agent viewing a conversation without polling.

What we built

We architected and built the platform end to end: a Laravel core, Go services for the throughput-sensitive paths, a Postfix-based inbound mail pipeline, and a custom real-time layer. The front end went through React and Angular as the product’s needs changed.

Multi-tenancy went into the data model from the first migration. Retrofitting tenant isolation into a schema that did not plan for it is one of the most expensive corrections in SaaS, and we had no interest in paying it later.

Outcome

ThriveDesk reached roughly $250,000 in lifetime-deal sales by its first public launch, with a feature set that matched established competitors.

Having operated the product rather than only built it changed how we build for clients. The parts that hurt in production — plan changes mid-cycle, tenant-scoped queries that stopped being fast, support tooling nobody wanted to use — are now things we design for at the start.