The work is a system, not a screenshot.
Migrations, revenue operations, integration and platform work — described by what was rebuilt rather than by a number we cannot show you the working for.
Kohr Wealth
Wealth management, CalgarySophisticated internal processes redesigned technology-agnostically, then implemented in HubSpot — a system built around how the firm actually works.
Protege
AI and data exchange, United StatesSales through to delivery orchestrated across HubSpot, Make, ClickUp, Slack and Linear, with HubSpot as the single source of truth.
Regency Health Care
Home care, New York CityHIPAA-compliant process transformation from intake to aide management, modelled in BPMN before a pipeline was built.
Jamming
Events, LimaB2B and B2C operations cleanly separated, overlapping tools removed, and a lean stack built around HubSpot.
Five problems that repeat.
A migration nobody will sign off
Years of history in a system the business has outgrown, and no plan that proves the records will survive the move.
Three teams, three numbers
Marketing, sales and finance each reporting a different funnel, with the monthly meeting spent reconciling rather than deciding.
A portal nobody owns
A HubSpot instance configured by four people over six years, where every new request contradicts an older one.
A forecast built by hand
One spreadsheet, one maintainer, and no way to interrogate the number in front of a board.
An integration that lies quietly
Two systems syncing with no owner, no conflict rules, and duplicates arriving faster than anyone can merge them.