Work tmc
platform

TMC

Headless SMS-marketing + outreach platform with a public health dashboard. Sister system to ESDBooking.

TMC is a headless SMS-marketing and outreach platform — no GUI of its own, just an API surface and a queue of cron-driven jobs handling Twilio-backed sending, DNC compliance scrubbing, drip-campaign pacing, and analytics rollups. Sister system to ESDBooking; the booking platform calls TMC's endpoints, TMC handles the messaging side, the two share a customer model. The public-facing surface is the ESD Quest status dashboard at tmc.quest itself — a deliberately public health board with version state, resource utilization, and live aggregate counts. Transparency-as-product.

  • PHP
  • MariaDB
  • Twilio
  • REST API
  • cron
  • JavaScript
  • nginx
TMC — Headless SMS-marketing + outreach platform with a public health dashboard. Sister system to ESDBooking.

TMC is a headless SMS-marketing and outreach platform — no GUI of its own, just an API surface and a queue of cron-driven jobs handling Twilio-backed sending, DNC compliance scrubbing, drip-campaign pacing, and analytics rollups. Sister system to ESDBooking; the booking platform calls TMC's endpoints, TMC handles the messaging side, the two share a customer model. The public-facing surface is the ESD Quest status dashboard at tmc.quest itself — a deliberately public health board with version state, resource utilization, and live aggregate counts. Transparency-as-product.

The numbers are the pitch

  • Approaching $5M in pipeline value generated, on under $100k in total operational spend.
  • ~36x ROI — every dollar spent has returned roughly $36 in net revenue.
  • Sub-$500 customer acquisition cost end-to-end, all-in.
  • ~97% margin at the operational layer.
  • Tens of thousands of unique leads, thousands of qualified appointments, hundreds of closed deals — every stage of the funnel measured and a cost-per-stage tracked against it.

Architecture, in broad strokes

  • API-first — TMC exposes REST endpoints for sending, scheduling, suppression-list management, and reporting. There is no admin UI to log into; if a partner system wants to talk to TMC, it does so through the API or it doesn't talk at all.
  • Cron-driven workers for send pacing, drip-step advancement, DNC re-checks, and rollups — every periodic job is a discrete script, idempotent, observable from the public dashboard.
  • Twilio for the messaging carrier layer, with retry + delivery-receipt handling on the TMC side so the rest of the system never has to think about carrier flakiness.
  • The public status surface at tmc.quest is the only thing on the internet — it shows commit hash, version, RAM/disk utilization, and live aggregate counts. Internal endpoints are not advertised.

Why no internals walkthrough?

TMC is production telephony infrastructure. The architecture stays in the repo, not on the marketing site. The dashboard you can see at tmc.quest is the only surface that is intended to be public.

Build something like this

Want a tool like this for your shop?

We've shipped this kind of thing before. Twenty-minute intro call, no slides.