Why we unified the customer timeline
Support, sales, billing, and product events in one feed per account — and why that single decision changed the way our customers work.
When we sat down to design EllorCharlie’s core object, we had a long debate about what a “customer” is. In most CRMs, a customer is a row in a table. In most support tools, a customer is a conversation. In most billing systems, a customer is a subscription.
Treating a customer as a single object with a single timeline — every email, every ticket, every payment, every product event, in one chronological feed — sounded obvious. It turned out to be the hardest engineering choice we made.
Why this matters
When an account manager opens a customer record at 9 a.m., the first thing they want to know is what happened since I last looked. Not “what’s their MRR,” not “what deal stage are they in.” They want the last thing that changed. Unified timelines answer that question in a glance.
What we gave up
A single timeline is less flexible than a pile of disconnected systems. You can’t build arbitrary custom views on top of it without working against the grain. We accepted that tradeoff. Early-stage teams don’t need custom views; they need one view that is correct.