CModel Data, Inc · More Work
Additional case studies — Salesforce builds, HubSpot automation, and the diagnosis behind them.
Case Study 02
Walked into an org untouched for years. No lead process, no attribution, no routing. Built the full system from scratch — five flows, HubSpot integration, contact attribution, engagement scoring, and a 200+ entry change log. Nobody asked for most of it.
Case Study 04
Built a bridge flow that mapped the existing Amount field to a new data structure automatically on every update. Reps kept doing exactly what they'd always done. The new structure populated silently around them. When they finally saw it, the section header read "Auto Populates — For Open Stages Only." It felt like a feature.
Case Study 05
Built a loop-over-loop flow exactly as instructed. It hit Salesforce's Apex CPU governor limit at 45.17 seconds — every time. Flagged it. No response. So I stopped forcing a broken solution, put quarterly quota directly on the User object — unconventional, nobody does this — and built a projected amount formula field instead. Seven dashboards. 42 reports. No developer required.
Case Study 06
No territory structure existed in Salesforce — no object, no regions, no rep assignments. Built a custom Territory object, defined six regions, mapped every AE, audited account ownership against the new structure, and ran a bulk ownership transfer. Caught two edge cases mid-audit: a duplicate state in two reps' lists and an unassigned inside-sales rep. Both resolved. Fully governed, validated, user-accepted.
Case Study 07
The Head of Marketing was chasing deal-close data in HubSpot — a system that was never built to give it to her. Reframed HubSpot as the marketing-quality layer and Salesforce as the deal layer, then built the tooling to match: a marketing ROI report, a formal sync-direction decision with Salesforce as source of truth, and a HubSpot identity layer with full source attribution. Built over time through the working relationship, not a training session.
Case Study 08
Leadership wanted to know if reps' emails were being consistently captured in Salesforce — a months-old, unresolved request. Diagnosed the wrong tool being measured, then found Einstein Activity Capture had 7 licenses and 0 configuration, all tied to employees who'd left years earlier. Fixed the licensing — then it broke again a day later, this time from a Microsoft-retired auth method underneath. Migrated to the current supported auth, coordinated the Microsoft-side consent, and confirmed a live, working sync across all 11 current users.
Case Study 09
With email capture finally working end to end, the project shifted to rollout — and hit a communication problem, not a technical one. Leadership had told a stakeholder an integration was "connected." It wasn't the one they meant — four separate systems had been getting called by the same word. Untangled all four, diagnosed the real license bottleneck, personally verified a live customer email before training anyone, and shipped individually tested, individually delivered instructions to each rep.
Case Study 11
A required field with nothing populating it was blocking Lead-to-Opportunity conversion. The instinct was a new field and a five-way mapping table — until a multi-select platform limitation and two values with no obvious home ruled that out. The real answer was already sitting upstream: an existing domain-matching flow had already determined new-vs-existing before conversion ever happened. Read that value instead. No new field. No mapping table. Two production-only timing bugs caught and fixed live.