What $25K in sales taught me about backends
Quota, retention and why CRM empathy makes better API design.
Quota teaches you what users actually do
Eighteen months of consultative selling and 50+ accounts rewired how I design APIs. A CRM ticket is not a row — it is a frustrated agent with a queue, a supervisor with a dashboard, and a customer waiting. That empathy decides which fields are required, which are searchable, and what p95 actually costs the business.
Retention is a backend metric
My 85% account retention came from follow-through, and backends retain users the same way: predictable errors, honest status pages, idempotent retries. Nobody churns because your schema is inelegant; they churn because a double charge or a lost ticket broke their week.
What I carried into engineering
Write the error message you would want to read on a sales call. Index the query behind the dashboard your champion opens every morning. Ship the audit trail that lets support answer without escalating. Backends that sell are backends that respect the humans on both sides of the screen.
Building something that needs this rigor?
Send a 2-line brief — I reply with architecture thoughts, not fluff.
Hire me