The work, shown honestly
Proof, not promises.
Every case here is real operational work, written from the evidence — verified before-and-after numbers, and an honest line between what was built, what it changed, and what was still being designed. Clients are anonymised by choice.
- Revenue Operations · B2B SaaS
Lead scoring in HubSpot, built as a decision engine
A living lead-scoring system that turned a flood of undifferentiated leads into a ranked, self-updating queue — and became the decision engine an entire revenue org ran on.
- 80+ days → 71 min
- Inbound lead assignment time
- $1.39M
- Product-only pipeline (routed MQL cohort)
- 27 → 16
- Meetings booked → opportunities created
- Service Operations · B2B SaaS
Bi-directional HubSpot–ClickUp ticket sync via Zapier
Replacing manual email support with a two-way HubSpot ↔ ClickUp ticket sync — eight Zapier automations, an SLA engine, and an escalation gate.
- 8 live automations
- Coordinated Zaps forming the two-way HubSpot ⇄ ClickUp sync
- 200+ tickets in Q1
- Synced, organised and resolved within SLA in the first quarter
- 3-tier SLA
- P1/P2/P3 with automated due dates (8h · 2 days · 10 days)
- Service Operations · B2B SaaS
Why most SLAs fail — and the HubSpot system that doesn't
A governance-grade SLA system in HubSpot — objective severity scoring, separated triage and resolution clocks, and early breach warnings.
- 6 SLA workflows
- Severity → triage → resolution → breach → closure, end to end
- Dual SLA clocks
- Triage (1h first-response) separated from resolution (8h · 2d · 10d)
- 27-combo matrix
- Priority computed from Impact × Scope × Urgency — not opinion
More case studies are added as work becomes publishable — each one verified against real records before it appears here.
Something here feels familiar?
Maybe you have a similar problem. Maybe you disagree with how we approached it. Maybe you’re just curious. Either way, we’re happy to talk.