Rung 1 · Read-only · 3 weeks
Three weeks of looking before anyone touches anything.
Ten surfaces of your automation platform, CRM and the connectors between them, read-only, with every finding tied to an export you can re-run. The first decision on an inherited stack should be made on evidence, not on whoever tells the most confident story in week one.
A fit when
- You are new in role and inherited a portal, a CRM and a connector nobody can explain.
- A rebuild or a re-platform is being quoted and you want a second, evidence-based opinion first.
- The duplicate rate, the funnel numbers or the sync error queue are known problems with unknown causes.
- You need something you can show the board in the first 90 days.
Not a fit when
- You already know the exact fix and just need hands — go to the Sprint or Build.
- The portal has under 10k records and one workflow; a one-hour call will do.
- You want the audit to double as a vendor-selection RFP. It doesn't.
What you get
Deliverables
Scored findings deck
Ten surfaces scored, each with the evidence export behind it: object inventory and surplus rate, duplicate provenance, lifecycle definitions, handoff integrity, workflow and import history, connector configuration, field hygiene, the reporting spine, access and credentials.
Evidence exports
Every number in the deck comes from an export you can re-run in your own portal. No screenshots as evidence.
Recorded walkthrough
A 45–60 minute recorded session walking your team through the findings, kept for whoever inherits it next.
Scope memo
What a fix requires: the route the platform gives you, the guards it needs, the order it runs in, and what it costs. Where the honest answer is "don't touch this yet", that is the recommendation.
Provenance over counts
Not how many duplicates, but which import, which workflow, which connector rule made them — that is what tells you whether to fix a sync or an import standard.
100% credit
The audit fee is credited in full against a Systems Rescue Sprint or Custom Build started within 30 days of the readout.
How it runs
Timeline
Week 1
Read-only access set up (a dedicated user, no edit rights). Object inventory, import and workflow history pulled. First provenance pass.
Week 2
Connector configuration, lifecycle and handoff analysis, field hygiene, reporting spine traced from dashboard to source field. Interim note to you with anything urgent.
Week 3
Scoring, the scope memo, and the recorded readout. Access revoked on delivery unless you start the next rung.
What you have on day 30. A scored map of the stack with evidence you can re-run, a written scope for the fix with a fixed price, and a recorded walkthrough your team can replay. Nothing in the portal has changed.
Two rules on every engagement
Nothing irreversible runs without a captured before-state and your explicit authorisation.
Every engagement leaves recordings and a runbook your team can operate from.
Questions
What access do you need?
A dedicated read-only user on the automation platform and the CRM, plus read access to the connector's configuration and error queue. No admin rights, no API keys that leave the platform. Details are on the Data handling page.
Which stacks?
HubSpot, Marketo, Pardot, Eloqua, Braze and Klaviyo on the automation side; Salesforce, Dynamics 365 and HubSpot CRM as the system of record. The method is the same across them; the connector rules differ, and that is where most findings live.
Why is it priced by record count?
Above 100k records the exports, the provenance work and the sampling take materially longer. USD $4,500 covers up to 100k records in the largest object; $7,500 to 500k; larger portals are quoted after a 30-minute look.
Can the audit be done in a week?
A one-week version exists for portals under 25k records, at the same price; it drops the connector deep-dive. Most inherited stacks need the three weeks.
Is CAD pricing available?
Yes — quoted at the current rate on the call and fixed for the engagement.
Other rungs
6 weeks · one named deadlock, fixed end to end
Systems Rescue Sprint
Dedupe, a lifecycle rebuild, attribution, a migration reconcile, a broken sync. Gated rollout, before-state captured for every irreversible action, and the upstream rule that stops it recurring.
USD $14,500
4–8 weeks
Custom Build
The executor or integration the platforms don't offer: a guarded merge executor, a Marketo–Salesforce sync repair, a HubSpot–Dynamics ownership layer, a reverse-ETL reporting spine.
USD $9,500 – $28,000
Standing hours inside your team
Embedded Ops
The senior pair of hands for the backlog: connectors, hygiene, reporting, enablement. Weekly recorded sessions; documentation is the by-product, not a deliverable.
USD $6,500 / mo
Start with the audit.
A 30-minute scoping call tells you which rung you need — or that you don't need one. No deck, no discovery theatre.