Overhaul · Fixed price
A fixed-price reset of your CRM.
Overhaul fixes what Preflight finds. It covers duplicates, broken links between records, messy values, empty fields, pipeline rules, automations and role views. It’s built to a checklist you sign at kickoff, and every line on it is pass/fail.
The price, the terms, the guarantee.
Two prices only. The founding price is for the first 3 clients. After that it’s $3,500. There’s nothing to add on to make the checklist pass.
Payment. 50% when you sign, 50% when the checklist passes.
Migration. One simple migration: one source (a CSV export or one CRM), up to 10,000 records, into Attio or HubSpot, standard fields mapped and reconciled row for row. Anything bigger is quoted separately.
Automations. Founding clients get Flight Plan and Radar free for their first 60 days once each launches.
$2,500
Founding price for the first 3 clients, then $3,500.
- 50% when you sign, 50% when the checklist passes.
- Includes one simple migration: one source, up to 10,000 records.
- Founding clients get Flight Plan and Radar free for their first 60 days once each launches.
Every item on the checklist we agree at kickoff passes within 7 business days of access, or the second half is on us.
The clock pauses while we’re waiting on you.
What’s in it
| Area | What we do | How “done” is measured |
|---|---|---|
| Duplicates | Merge duplicate contacts and companies using a rule you can read | Under 2% duplicates on each (Uniqueness score 95+) |
| Relationships | Link contacts to their companies by email domain | Zero unresolved matches. Exceptions listed by name. |
| Normalization | Map every job title to a seniority and function. Put industry, lead source and region on picklists. | 100% of titled contacts mapped. Zero free-text values left. |
| Enrichment | Backfill the fields you pick: headcount, industry, HQ, domain, LinkedIn URL | The fill rate you set for each field at kickoff |
| Pipeline rules | Make your stage exit criteria required fields at each stage | Every listed stage, 100% |
| Owners | Give every open deal an active owner | 100% |
| Deal hygiene | Every open deal gets an amount, a close date on or after handover day, a next step, and at least one contact and a company | 100% of open deals, checked by script |
| Automations | Build the trigger → action pairs you name at kickoff, like a task on stage change, a closed-won post to Slack, or owner reassignment | Each one fires correctly on a live test record. None points at a deleted field or a removed user. |
| Role views | A view for each role you name, showing only what that role needs | Checked by logging in as each role, or by the view configuration |
| The headline | Re-run Preflight on the finished workspace | The before-and-after scan goes in your handover pack |
One migration, included
One simple migration: one source (a CSV export or one CRM), up to 10,000 records, into Attio or HubSpot, standard fields mapped and reconciled row for row. Anything bigger is quoted separately.
- One source. A CSV export, or one CRM such as Pipedrive, HubSpot or Salesforce. Up to 10,000 records.
- Mapped field by field. Standard fields go through a mapping sheet we agree at kickoff. Fields not on the sheet aren’t moved. We don’t guess mappings.
- Every row accounted for. Source and destination counts reconcile, and every difference has a named reason in the reconciliation report.
- Owners mapped. Source-system owners are mapped to the users in your CRM.
- Source frozen. You freeze the source system during the move, so the counts don’t drift.
What we need at kickoff
One 30-minute call and one form. It covers:
- Access. Build access to your CRM, scoped to the job.
- Stages. Your pipeline stages, what must be true to leave each one, and who owns each.
- Required fields. The fields required at each stage.
- Taxonomy. Your values for titles, industries, lead sources and regions. If you don’t have them, we use ours.
- Enrichment. Which fields to backfill, and whose enrichment credits pay for it.
- Automations. The automations you want, as “when X, do Y”.
- Roles. The roles on your team and what each should see.
Anything not on the form is a new piece of work, not a surprise on this one.
What you get at handover
One 20-minute call and a handover pack:
- Before-and-after scan, same seven dimensions, showing the change.
- Automation test log, one timestamped entry per automation.
- Role views, as screenshots or the view configuration, one per role.
- Data dictionary: every field we touched, its allowed values, and what fills it from now on.
- Exception list: anything that couldn’t be resolved by rule, handed to you rather than guessed.
- Snapshot of your data from before we started.
- Confirmation that our access is revoked and our keys deleted.
How the build runs
Four rules on every job:
- One access grant up front.
- “Done” means the checklist passes. No taste calls.
- Nothing is sent to the outside world on your behalf.
- Everything we change is snapshotted first. Everything we add is tagged and removable.
No check-ins. After kickoff, we build. You hear from us at handover.
The clock. Every item on the checklist we agree at kickoff passes within 7 business days of access, or the second half is on us. The clock pauses while we’re waiting on you.
Not included
- Migrations beyond the one included (more sources, or more than 10,000 records). Quoted separately.
- Enrichment beyond the fields and records agreed at kickoff.
- Contract-PDF extraction, web-form and meeting-notes wiring, and meeting-scheduler routing. Each of these is available as its own piece of work.
- Custom objects not named at kickoff.
- Automations, which are subscriptions, apart from the founding-client inclusion above.
- Judgement calls on ambiguous data. Those go on the exception list.
Every Overhaul starts with a Preflight.
Free, read-only, and the quote at the end of it is the price you pay.