Search the library
Every published resource in one index. Filter by what you need — a problem to fix, a playbook to run, a calculator to settle an argument — or search across the lot.
52 of 52 resources
Business operations: the layer that decides whether growth holds
What business operations actually covers, how an operating model is designed, the implementation sequence, and the mistakes that quietly cost the most.
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.
CRM 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.
Marketing 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.
Customer 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.
Digital 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.
Leads 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.
The 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.
Marketing and sales disagree on lead quality
The structural causes behind the lead-quality argument, and how to settle it with shared definitions, a working handoff, closed-loop outcomes and one set of numbers.
Every customer gets a different onboarding
Why onboarding drifts between customers, how to define completion as an outcome, and the milestone, ownership and exception design that makes delivery repeatable.
Work leaks between teams
Why work slows and disappears at team boundaries, how to write a handoff contract, and how to instrument the boundary so failures surface before customers notice.
Reporting that explains the past but changes nothing
How to replace activity dashboards with decision-grade reporting: choosing numbers that change behaviour, reporting exceptions, and running a cadence that produces decisions.
The process changes depending on who runs it
How to write SOPs people actually use, assign single accountable owners, and build checkpoints into the workflow so standards survive without supervision.
Skilled people spend their week on copy-paste
How to find the transport work hiding inside skilled roles, size it honestly, decide what deserves automation, and remove it without freezing an unagreed process.
Growth is arriving faster than the operation can absorb it
How to tell whether growth is breaking capacity, process or ownership — and what to fix first so volume stops turning every weak handoff into a fire.
You hear about problems from the customer, not the system
How to build internal escalation triggers, severity levels with owners and response times, and the health signals that surface delivery risk before a customer complains.
Lead routing playbook: from form submission to owned follow-up
A sequenced plan for designing lead routing: assignment rules, response standards, out-of-hours behaviour, escalation, and the reporting that keeps it honest.
CRM cleanup playbook: restoring a system people believe
A four-week sequence to repair CRM trust: freeze changes, rebuild stage definitions, cut fields, clear dead data with a published rule, and rebuild reporting.
Customer onboarding playbook: designing the first forty-five days
How to design onboarding that produces the same outcome for every customer: outcome definition, milestone spine, ownership, exception handling and handover.
Marketing-to-sales handoff playbook
Build a handoff both teams accept: joint qualification criteria, required context, acceptance and rejection with reasons, return rules and one shared funnel report.
Operations audit playbook: finding the constraint in two weeks
A two-week audit that maps the real flow, measures wait time, tests ownership and documentation, and produces a ranked list of fixes with owners rather than a report.
What is marketing operations, and when does a company need it?
A working definition of marketing operations, what the function owns day to day, how it differs from RevOps and demand generation, and the signals that say you need it.
When to automate a process — and when automation makes it worse
A decision framework for automation: the four gates a process must clear, the arithmetic that decides whether it pays, and the situations where manual is the correct answer.
n8n vs Zapier: choosing for business workflows, not for demos
A practical comparison of n8n and Zapier for operations work: branching, error handling, data volume, maintenance ownership, hosting and where each one stops fitting.
How to hire a business operations manager
What the role should own, how to write the brief, the interview exercises that reveal real operating skill, and the signals that separate operators from coordinators.
Operations manager vs project manager: which role do you actually need?
The difference between running a repeating system and delivering a bounded project, how to tell which gap you have, and what happens when you hire the wrong one.
What a Head of Customer Success should actually own
The real scope of a customer success leadership role: delivery standards, onboarding, health and escalation, retention economics — and the authority the role needs to work.
Break-even ROAS calculator
Work out the ROAS you must hit to break even, the ROAS that keeps your target contribution, and the maximum cost per acquisition and per lead — from your own margin.
Lead response leakage calculator
Size the revenue gap created by uncontacted and slowly-contacted leads, using only your own numbers — no industry multipliers, no assumed uplift.
Automation readiness score
Ten questions that tell you whether a specific process should be automated now, standardised first, or left alone — scored across worth, readiness, feasibility and safety.
CRM health check
Ten questions across lifecycle, ownership, data, automation and reporting that show whether your CRM operates the process or merely records it — with the first fix to make.
SOP template: one page people will actually use
A thin standard operating procedure template built around decisions and exit conditions rather than keystrokes, with the prompts, an example and the maintenance rule.
Lead routing matrix template
A one-page matrix that records assignment rules, fallbacks, response standards, out-of-hours behaviour and escalation, so routing logic exists outside the automation tool.
Customer onboarding checklist template
A milestone-based onboarding checklist with owners, target days, exit conditions and slip actions — plus the handoff requirements that decide whether day one starts well.
Escalation matrix template
A three-severity escalation matrix with definitions, owners, response times, communication rules and the internal triggers that fire before a customer complains.
Documented lead-generation campaign: 1,335 leads at $6.92 cost per lead
A bounded case study of one documented lead-generation campaign — what the record shows, how campaigns like it are run, and precisely what the numbers do not prove.
Account-level snapshot: $3.32M conversion value against $161K cost
A documented account performance snapshot showing 2,060.66 percent ROAS and 43.1K recorded conversions — with the measurement boundaries stated in full.
Messaging campaigns at scale: 33,171 conversations across 18 campaigns
A documented 18-campaign account view recording 33,171 messaging conversations and 54.2M impressions — and what operating at that volume actually requires downstream.
Growthiffy: selling growth as one system instead of five services
Why I built Growthiffy around a connected growth system — demand generation, conversion, CRM, follow-up and reporting — and what that structure changes about delivery.
Budget Flow: designing and building a local-first finance app
The design and engineering decisions behind Budget Flow — a private, on-device personal finance app that forecasts cash flow instead of categorising the past.
Lead routing
Lead routing is the rule set that assigns every incoming lead to an accountable owner automatically, with a fallback so no record is left unowned.
Lifecycle stage
A lifecycle stage is a defined position in the customer journey, entered by an observable event and left by a written exit condition — not a description of how a deal feels.
MQL — marketing qualified lead
An MQL is a lead that meets the qualification criteria marketing and sales agreed in writing — a shared definition, not a score marketing sets alone.
SQL — sales qualified lead
An SQL is a lead that sales has accepted and verified as a genuine opportunity — the acceptance step that turns a marketing judgement into a commercial one.
CRM hygiene
CRM hygiene is the maintained state of the data: no duplicates, no orphaned records, no stale deals, and required fields limited to what reporting actually consumes.
Attribution
Attribution assigns credit for a conversion to marketing touchpoints. It is a decision-support model with stated boundaries, not a measurement of truth.
Customer health score
A customer health score combines observable delivery signals into a rating that triggers defined action — not a sentiment gauge, and not a dashboard colour.
SLA — service level agreement
An SLA is a committed standard for response or resolution, with a defined measurement point, an owner and a consequence when it is breached.
Process owner
A process owner is the single named role accountable for a process working — with the authority to change it, not merely to report on it.
Operating cadence
An operating cadence is the fixed rhythm of reviews where exceptions surface and decisions get made — each meeting defined by the decision it must produce.
Workflow automation
Workflow automation executes a defined sequence of steps across systems when a trigger fires — moving data, creating records, notifying people and enforcing standards.
Speed to lead
Speed to lead is the elapsed time from lead creation to the first genuine human contact — measured from creation, not from assignment, and not counting unanswered attempts.