Uoma LabsLLC

Proof of concept · Internal SaaS

A proof-of-concept command center for a trucking-software company's customer success team.

A working CSM prototype — health scoring, activity logging, account intelligence, and renewal pipelines — designed and built end-to-end to show what a purpose-built tool could do for the client's customer success org.

Build something like this Inside the prototype
B2B trucking SaaS 2026 Proof of concept
CSM dashboard showing total accounts, NPS average, upcoming renewals, at-risk count, team focus tasks, accounts needing attention, and upcoming renewals.

The brief

Not another generic CRM.

The question was whether a single internal cockpit, purpose-built for how the client's customer success team actually works, could beat the tools they already had.

Off-the-shelf CRMs force a team to bend its workflows around someone else's data model. The custom metadata that actually drives the client's CS motion — BCH type, accounting software, historical TMS, per-unit pricing, truck tier — had nowhere to live, and the cross-account intelligence the team needed every morning was scattered across spreadsheets and dashboards.

Uoma Labs designed and built a working proof of concept end-to-end: a tabbed account record purpose-built for CS work, an activity feed that captures every customer touch, a reporting view with one-click export, and a daily dashboard that surfaces what's overdue, at-risk, and renewing soon. Google SSO keeps it locked to the client's team.

The build ran on sample data and stopped at the proof-of-concept stage — it was never rolled out to the team. What it left behind is a complete, working picture of what a tool shaped around this CS motion looks like.

Inside the prototype

Built around the work, not the schema.

Three of the surfaces the prototype was built around.

Reporting view with filters for BCH, type, material sales, health, CSM, state, historical TMS, and accounting software; live rollups for total accounts, ARR, BCH count, and material sales; sortable table of accounts with health badges, ARR, BCH status, CSM assignment, and next renewal date.
01 — Reporting

Reporting a team would actually open.

Slice the book by BCH, type, material sales, health, CSM, state, TMS, or accounting software. The rollups update live, the table re-sorts, and the export button hands over a clean CSV.

  • Nine filter dimensions with instant rollups for accounts, ARR, BCH, and material sales
  • Configurable columns and sort order, saved between sessions
  • One-click CSV export of the current filtered view
Activity feed showing the 40 most recent activities across all accounts, with type filters for call, email, meeting, and note, a search box for subject/account/notes, a CSM filter, and timestamped entries linking to each account and CSM.
02 — Activity feed

One source of truth for every customer touch.

Calls, emails, meetings, and notes — all logged against the account, all in one feed. Search by subject, account, or note content; filter by CSM to see exactly who's moving.

  • Unified feed across calls, emails, meetings, and notes
  • Full-text search across subject, account, and notes
  • Filter by activity type and by individual CSM
Account detail page for CloudFirst Inc with at-risk health badge, ARR, next renewal date, conversion date, BCH status, material sales, editable BCH type, and tabs for Details, Tasks, People, Activity Feed, Renewals, Tickets, NPS and Usage, Product Feedback, and Playbook. The Details tab shows editable fields for MRR, EDI, org slug, accounting software, historical TMS, latest per-unit price, and current truck tier.
03 — Account record

Designed for CS work, not generic CRM fields.

Every client-specific signal lives where a CSM would expect it. Health badge and ARR up top, renewal countdown next to the next-renewal date, and a tabbed record that follows the actual customer journey.

  • Nine purpose-built tabs: Details, Tasks, People, Activity, Renewals, Tickets, NPS & Usage, Product Feedback, Playbook
  • Industry-specific metadata — BCH type, MRR, EDI, accounting software, historical TMS, per-unit price, truck tier
  • Inline edits with optimistic save and a renewal countdown surfaced at a glance

Outcome

What the prototype showed.

The proof of concept never went into production, but it demonstrated that a scatter of spreadsheets and dashboards could collapse into one place built for CS work.

  • A single source of truth is achievable — every account and every customer touch modeled in one system.
  • CS metadata can have a home — BCH type, MRR, EDI, historical TMS, per-unit price, and truck tier live on the record instead of in side spreadsheets.
  • Self-serve reporting works — nine live filter dimensions and one-click CSV, with no analyst in the loop.
  • A functional build, not a mockup — real auth via Google SSO and working screens, exercised with sample data.

Under the hood

The shape of the engagement.

A focused, end-to-end proof of concept — designed and engineered by Uoma Labs.

Client
Confidential · B2B trucking SaaS
Surface
Internal web platform
Auth
Google SSO · team-only
Engagement
2026
Status
Proof of concept · not deployed