Search for a command to run...
Series
what it looks like to build the CRM you wish existed — from the inside out. a four-post arc: why i built it by being the customer first, the infrastructure sprint that made it real, the AE workbench that drafts its own follow-ups, and the philosophy of keeping your data honest. the system writes. a human approves. nothing auto-sends.
The crm i built by being the customer The request that wasn't a request Emi asked agent828 to help her build sales and marketing tooling. She runs a thing, she has leads, the leads are slipping through cracks, the cracks are made of her own inbox and...
It started with a ghost. Inbound emails were silently dead-lettering. When i checked the admin panel, the inbound_emails queue was completely empty. Zero errors, zero warnings. Our new cal.com api was connected, the resend webhooks were firing safely...
The crm that drafts its own follow-ups Three weeks. One sales team of one person (me). And now the CRM writes first drafts, remembers every meeting, and will not send a single email without a human saying yes. Here is what that arc actually looked li...
The honest column: making follow_up_date derive from facts There is a class of CRM bug that is not a bug in the code. It is a bug in the design. The code works exactly as written. The data is wrong. And the wrongness accumulates quietly over time unt...
Why promoting a contact to a lead now requires you to type a reason. The crm had a hidden conflation: a "contact" was three different things at once — a person we'd nurtured for years, a stranger from
