Enterprise Experience SaaS

The problem

The CEO of a large enterprise asks one question every Monday morning: "How are my people doing?"

Most of the time, the honest answer is "we don't know yet." The annual engagement survey was three months ago. The results came back as a long PDF that nobody read past the first few pages. Three months from now, the next survey will go out and nobody will remember the action items from the last one.

That's the state of most large organizations today. And that's with the big incumbents in the space. The tools are decent at running the survey. They're terrible at turning the survey into something a CEO, an ops leader, and a line manager can all act on today.

Our client had a vision for something better — a complete experience platform that:

• Runs every kind of survey from one place — annual, pulse, onboarding, exit, lifecycle
• Shows the answers in real time as responses come in
• Slices the data any way someone needs and stays fast
• Finds the why behind the what
• Maps the organization as a network, not just an org chart
• Reads thousands of free-text comments without anyone having to
• Answers natural-language questions about the data
• Turns insights into action plans tied to specific items
• Runs as multi-tenant SaaS so multiple client companies live on the same product
• Passes the kind of security audit a US enterprise demands

And one more constraint that made the project actually difficult: they had a launch customer ready to go live in two months.

---

The approach

A project of this scope can fail in two opposite ways. You can build everything halfway and ship something nobody trusts. Or you can perfect each module before moving on and never reach a launch date.

We chose a third path: build the spine first, ship it, then layer the smart features on top.

The spine looked like this:

1. Multi-tenant from day one. Every decision in the architecture had to assume multiple customer companies would live on the same platform. We never built a "single-tenant version" we'd later have to retrofit.
2. The workforce data is the foundation, not the survey. Most survey tools start with the survey. We started with the data — get it in cleanly first, with proper validation, history tracking, and segmentation — and the survey results become slicing-and-dicing exercises on top of a solid base.
3. Permissions are a first-class feature, not an afterthought. A US enterprise will not adopt a platform where every user can see everything. We built role-based access at multiple levels from the very first commit.
4. The dashboards have to be the main product. Not the survey-builder. Not the export. The dashboards. Anything that doesn't help a person see and understand the data faster gets cut.
5. Then layer on the differentiators — the analytics, the network insights, the AI, the auto-generated reports — once the spine was rock solid.

We sequenced the work so that week one of the engagement, the platform could already accept a data upload and run a basic survey. Every subsequent week added a layer.

The other key decision: we treated the platform owner and the launch customer as two different stakeholders with two different needs. The launch customer needed the actual product. The platform owner needed the operational tooling to run the platform — a way to onboard new clients, switch between them for support, impersonate users to debug issues. We built both in parallel because we knew that if the platform owner couldn't run the platform smoothly, the second client would never happen.

---

The hard part — and how we solved it

There were three "hard parts" on this project, and they all happened in parallel.

Hard part #1 — Building a slicing engine that doesn't slow down

A scoring tool is easy. You compute averages and show them. A real slicing engine — where any chart, any score, any comment can be filtered by any combination of segments and stay responsive — is one of the hardest things to build in a SaaS product. At enterprise scale with hundreds of survey items, "filter the dashboard by location × tenure × manager" can mean recalculating thousands of numbers.

We solved this by separating the operational data from the analytics data from day one. The operational data lives in one database optimized for writes and updates. The analytics data — the slicable, filterable, "every chart on every dashboard" data — lives in a separate analytics warehouse optimized for reading huge amounts of data fast. Background jobs continuously sync the operational data into the analytics warehouse so the dashboards always have fresh data without slowing down the operational side.

The result: an executive can change the global filter and watch every dashboard repaint in under a second, even at full enterprise scale with a year of survey history loaded.

Hard part #2 — Permissions that go several levels deep without becoming a maze

Most enterprise SaaS gets permissions wrong in one of two ways. Either it has too few (everyone can see everything, which kills the deal) or too many (the customer can't figure out how to set it up, which also kills the deal).

We built a multi-level permissions model but layered it on top of a role-based system so the customer admins never have to think about individual permissions. They create roles, they configure what each role can see once, then they assign users to roles. New user joins? Pick their role. Done.

On top of that, the platform owner has a "super admin" layer that bypasses the customer's permissions entirely — so they can support any customer without becoming entangled in that customer's permission setup. This is the kind of thing that sounds easy but is full of edge cases. We thought about every one of those edge cases up front and the platform handles them gracefully.

Hard part #3 — Shipping an enterprise-grade SaaS in two months

This is where most projects of this scope fail. The temptation is to build everything to 70% and ship something soft. We built it the other way: picked the spine, built that to 100%, shipped it, then added layers.

In practice this meant every week shipped something the customer could actually use. Nothing waited for "the big launch." By the time the launch week came, the customer had already been using the platform for weeks and was asking for refinements, not bug reports.

The other thing that made this work: we sequenced the customer's expectations alongside the build. They knew exactly what would be live in each week. They were never surprised, they were never blocked, and they had time to upload their data, train their team, and prepare their first survey before the platform was fully complete.

---

The outcome

• Live in production at a real US enterprise customer running their program on the platform
• Delivered in two months from project start to launch
• Passed an external Vulnerability Assessment and Penetration Test (VAPT) — the security audit a US enterprise actually requires before adopting a vendor
• Multi-tenant from day one — the platform owner can onboard new customers in minutes and run the platform centrally
• Sub-second slicing at enterprise scale — global filter changes recompute the entire dashboard in real time
• Multi-level permissions through a clean role-based system that customers can manage themselves
• Real organizational network analysis — most competitors in the space don't have this
• Built-in AI assistant that answers natural-language questions about the data — most competitors don't have this either
• Auto-generated reports so ops teams stop building decks by hand
• Multi-channel distribution — email, Slack, Microsoft Teams
• Full audit trail and impersonation — built for the compliance-heavy environment a US enterprise lives in

The big-picture outcome: a brand new experience SaaS that competes credibly with the heavyweight incumbents in the space — built and launched in two months for a real US enterprise customer.

---

In the client's words

"We only had a skeleton of a Next.js app. t3c built on that foundation and translated my vision for the product into reality."

"We started with a website project that went really well — both the collaboration and the results. That gave us the confidence to go beyond the website and partner on the full app build."

"I really appreciate the flexibility and agility. I come in with a point of view and mockups, but sometimes seeing the enhancement come to life changes my view on the UX. The collaboration across those iterations has been excellent — exactly what we needed to get the product to this point."

"I highly recommend t3c. They've been a great partner, and the flexibility to adapt to the changing nature of the product and the needs of our customers has been critical to our success. t3c brings the entire set of capabilities needed to translate a founder's vision into an enterprise-ready application we can bring to market fast."

— Founder, the US employee-experience SaaS