Routing and ownership
Lead source, territory, booked rep, fallback owner, stage placement, and follow-up rules do not behave consistently.
I help HubSpot partners, RevOps consultants, CRM consultants, and agency delivery teams build or repair HubSpot workflows, routing, field mapping, Make, Zapier, n8n, APIs, webhooks, QA, and handoff.
Best for partner overflow and defined workflow problems that need proper execution.
I work between the approved business rule and the live system. That means turning routing, matching, fields, exceptions, and handoff into something the team can trust.
Lead source, territory, booked rep, fallback owner, stage placement, and follow-up rules do not behave consistently.
Fields arrive incomplete, matching is weak, repeated runs create duplicates, or nobody is sure what can safely overwrite live data.
Booked calls, outreach, emails, transcripts, or ATS activity are trapped in another tool instead of reaching the right CRM record.
The happy path works, but retries, missing access, API limits, partial failures, logging, review cases, and documentation were never finished.
I do not replace the senior RevOps or CRM strategist. I make the agreed process work in the tools, test it with real examples, and hand it back clearly.
One defined CRM or automation problem, designed, built or repaired, tested with real records, and handed back properly.
Best when there is a real workflow owner, a defined business rule, and enough access to test the system properly. The scope and delivery window are agreed after I review the issue.
Client systems stay private. These examples show recent HubSpot, CRM, integration, and production workflow delivery, including what I personally built, how risk was controlled, and the status that is safe to state.
Multiple live HubSpot automations were interacting around enrollment, re-enrollment, marketing-contact state, cooldowns, and Salesforce-synced eligibility.
Audited the live workflow family, mapped conflicting state and dependencies, defined contained fixes, tested guard logic, and moved into remediation work across the client account.
The work focused on stopping separate automations and Salesforce updates from creating contradictory HubSpot state, using controlled changes and QA instead of blind rewrites.
Calls, interview notes, transcripts, CRM emails, and account-channel updates were spread across several systems.
n8n workflows for Fireflies processing, Salesforce logging, Lever notes and transcript files, Slack routing, dedupe ledgers, and review paths.
Safe matches created usable records. Ambiguous cases went to review, and production failures could be diagnosed instead of hidden.
New Pipedrive Leads needed repeated manual company and lead research before the records were useful.
A label-triggered Make workflow with sourced AI research, structured fields, a review sheet, and a controlled writeback path.
The team received usable enrichment without allowing uncertain AI output to become unquestioned CRM truth.
Sales state was spread across Gmail, spreadsheets, quote logs, contact systems, and employee memory, making ownership and follow-up hard to trust.
A sales-operations layer around Gmail, Airtable, Make, and AI with Contacts, Companies, Leads, Lead Events, Tasks, Quotes, routing, dedupe, quote follow-up, order and payment review, and QA views.
In the documented accountability period, 930 Lead Events processed with zero errors, and all 57 Quote Sent events created the required Quote Follow Up.
Selected feedback from completed client projects. Client identities are omitted here for privacy.
“I also greatly appreciate the depth of Michael's documentation on the project, outlining his process step-by-step.”
“The automation processes he built saved our team over 20 hours per week.”
“Very strong on the technical aspects of Make workflows.”
The goal is not a clever diagram. The goal is a workflow that behaves predictably with real records, bad data, retries, missing access, and edge cases.
Review the current workflow, records, payloads, fields, errors, and real examples, not only the intended process.
Confirm the source of truth, matching keys, routing, overwrite rules, review cases, and what must never be guessed.
Implement the bounded flow, then test happy paths, duplicates, missing data, bad access, retries, and partial failures.
Document the trigger, fields, logic, limitations, review process, and what the team should do when the workflow cannot decide safely.
My strongest work is implementation, repair, integration cleanup, data flow, QA, and handoff. I am most useful when the process direction is understood, but someone still needs to handle the routing logic, field mapping, APIs, webhooks, dedupe, review paths, production debugging, and documentation.
A rough Loom or screenshot is enough. You do not need to prepare a polished brief.
Email: michael@byteescape.com