Writing on the operating layer
52 published pieces on business operations, automation, CRM systems and revenue operations — written to be used, not to rank. Start with the newest, or go straight to a shelf.
Latest
Newest first
Business automation: removing repetition without automating bad decisions
How to choose what to automate, design workflows that survive contact with reality, and avoid the failure modes that make automation more expensive than the manual work.Business automationCRM architecture: making the system operate the process, not record it late
How to design CRM lifecycle stages, ownership rules, automation and reporting so the system drives the next action instead of storing history nobody trusts.CRM systemsMarketing operations: turning demand into something sales can actually work
What marketing operations owns, how lead management and qualification are designed, honest attribution boundaries, and the handoffs that decide whether demand becomes revenue.Marketing and revenue operationsCustomer success operations: making delivery repeatable after the sale
Onboarding design, service checkpoints, health signals, escalation paths and the operating cadence that keeps customer experience consistent as volume grows.Customer success operationsDigital growth: buying demand the business can actually absorb
Funnel architecture, paid acquisition, measurement and e-commerce growth — run as an operating problem with unit economics, not as a channel-performance exercise.Digital growthLeads go cold after form submission
Why inbound leads stall between capture and sales contact, how to find where the time is actually lost, and the routing, SLA and escalation design that fixes it.Marketing and revenue operationsThe CRM nobody trusts
Why CRM data stops being believed, how to tell whether the problem is definitions, adoption or hygiene, and the order of operations that restores trust without a migration.CRM systemsShelves
Eight kinds of material.
Each shelf answers a different question, so the same subject can be read as a problem, run as a playbook or settled with a calculator.