SaaS · Messaging·Illinois, USA
Treply
SMS / MMS engagement for nonprofits & agencies
Treply was a two-year engagement where Fluid Web's founder led engineering and, in practice, ran the company's delivery function. The platform peaked at two million messages a month across enterprise tenants and white-label agency partners.
What we walked into
Treply set out to give nonprofits and the agencies serving them a real messaging platform rather than a thin wrapper over a provider API. Customers were coming off tools like Attentive, Crisp and Bird — products built for retail marketing that fit the nonprofit motion badly.
Our founder joined to lead engineering and ended up leading considerably more than that. Over two years the role covered technical leadership, product design, client communication and, when the chief executive was away, running payroll for the local team.
The problem
The platform had to serve two different customers at once. Enterprise nonprofits needed their own tenant with real volume behind it, while agencies needed to run branded workspaces for the organisations they served — which is a white-label problem, not a permissions problem.
Underneath that sat the harder constraint: messaging at scale is governed by carriers, not by your roadmap. Consent, registration, opt-out handling and throughput all had to be correct before volume could grow, because getting them wrong means filtering rather than an error message.
Multi-tenant from the foundation, not retrofitted
Treply was built as a multi-tenant platform from the start, with enterprise tenants and agency workspaces modelled as first-class concepts rather than as an access-control afterthought. That decision is the reason white-label support was possible at all later on.
At its peak the platform ran six to seven enterprise tenants alongside two white-label agency partners, each operating under their own brand while running on a single deployment.
- Tenant isolation designed before feature work began
- Agency workspaces managing their own downstream organisations
- Branding and identity stored as tenant data, never as a fork
- One codebase and one deploy serving every brand on the platform
Volume that carriers would actually accept
The platform peaked at roughly two million SMS and MMS messages a month and sustained an average near seven hundred thousand. Reaching those numbers is less about throughput engineering than about compliance being correct from the beginning.
Consent capture, opt-out enforcement and carrier registration were modelled in the product rather than handled by process. A send that would damage sender reputation had to be difficult to perform by accident, because at that volume a reputation problem is not recoverable in a sprint.
- Consent and opt-out enforced in the data model, not in support process
- Carrier registration tracked as product state
- Throughput control and retry logic that never double-sent
- Delivery health surfaced to the operators running campaigns
Leading the team and the delivery function
The team reached ten people, and our founder led it across scrum, stories, technical direction and design. In practice the remit extended past engineering — client communication and, at times, paying the local team's salaries.
That is unusual to say in a case study, but it is the honest description of the engagement and it is why the pattern repeats. Several of the engineers led on Treply are, two years later, working under Fluid Web again.
Shipping the marketing site alongside the product
The marketing site was part of the same engagement rather than handed to a separate vendor. For a product selling into nonprofits and agencies, the site and the onboarding flow are one continuous experience, and splitting them across two teams creates a seam that nobody owns.
The hard parts
Two customer shapes on one platform
Enterprise tenants and white-label agencies want incompatible things. Agencies need control over branding and their own customer hierarchy; enterprises need isolation and their own scale. Serving both without forking the product is a tenancy design problem you only get one chance at.
Deliverability as a growth ceiling
At two million messages a month, carrier filtering is an existential risk rather than a support ticket. Compliance had to be built into the send path itself so that the safe action was also the default one.
Leadership load beyond engineering
Running design, client communication and payroll alongside technical leadership is not a structure we would recommend, and it taught us where the boundaries of an engagement should sit. It is part of why Fluid Web engagements now include delivery management explicitly.
How it ran
Greenfield build
Platform built from an empty repository — tenancy, messaging pipeline, campaign tooling and the marketing site.
Enterprise and agency onboarding
Six to seven enterprise tenants brought on alongside two white-label agency partners running their own branded workspaces.
Volume scale
Sustained averages near 700,000 messages a month, peaking around two million, with compliance and deliverability holding at that scale.
Handover
Our founder moved on after roughly two years. Work added to the platform after that point is not ours to claim.
Results
Treply went from an empty repository to a production messaging platform running six to seven enterprise tenants and two white-label agency partners on a single deployment.
Volume peaked at approximately two million SMS and MMS messages a month with a sustained average around seven hundred thousand, replacing tools like Attentive, Crisp and Bird for customers whose needs those products were never designed around.
The engagement ran two years with a team of up to ten. Several of those engineers work under Fluid Web today, which is the clearest signal we can offer about how the team was run.
Built with
Scope of our work
Our involvement covers the platform, agency and admin consoles, and the marketing site during a roughly two-year period. Features added after our founder's departure — including later faith-specific donation functionality — are not our work and we make no claim to them.
Got something similar?
Tell us where delivery is stuck. We will give you an honest read on scope and shape before anyone talks contracts.
Book a technical review
