Best fit
A CRM or contact file with inconsistent fields, obvious duplicates, stale records, or unclear merge rules.
Create a safer working set before another campaign, import, handoff, or sales push adds more noise.
A CRM or contact file with inconsistent fields, obvious duplicates, stale records, or unclear merge rules.
Service scope contract
This page is a scoping guide. The written quote controls the actual engagement.
A CRM or contact file with inconsistent fields, obvious duplicates, stale records, or unclear merge rules.
An export or approved access, field definitions, match rules, and the source-of-truth policy.
A cleaned dataset or approved update set, duplicate decisions, exceptions, and a handoff log.
Usually a Defined Project. A smaller, clean export may fit a Quick Task; repeated list hygiene can graduate to an Ongoing Support Desk.
Record count, source condition, number of systems, match-rule complexity, exception volume, and required handback format.
NBW pauses or declines when data ownership, permitted use, backup, or destructive-merge authority is unclear. Compliance advice is routed to a qualified professional.
What you send
An export or approved access, field definitions, match rules, and the source-of-truth policy.
What comes back
A cleaned dataset or approved update set, duplicate decisions, exceptions, and a handoff log.
Inside the quote
Visible boundaries
The route
The exact scope controls over this general outline.
Confirm the source of truth
Agree cleanup rules
Work in a protected copy
Review exceptions
Return the clean set and log
Human QA
A human reviews match logic, spot-checks changed records, and separates ambiguous decisions instead of forcing a merge.
Quote-first pricing
A service label is only the starting point. The real inputs below determine the responsible boundary.
The size, complexity, and number of outputs that must come back finished.
The condition, completeness, and organization of the material provided.
The tools, accounts, permissions, and risk controls involved.
The timing posture, dependencies, milestones, and coordination required.
The review, revision, documentation, and transfer requirements.
NBW scopes the work, sends a fixed quote, and begins only after you Approve.
Engagement progression
The work can graduate when its real coordination needs change—not because a larger package is being pushed.
One bounded deliverable, quoted before work begins, with one included revision pass where appropriate.
Use this whenOne bounded output with ready inputs.
A written scope for multi-step work, with agreed inputs, exclusions, milestones, and change handling.
This becomes a Defined Project whenMultiple dependent steps, systems, owners, or milestones.
A capacity-honest monthly relationship with a maintained queue and a clear delivery summary.
A Desk is usually the better fit whenRepeated work benefits from retained context and a prioritized queue.
Send the source material, desired handback, and constraints. Nothing begins until you approve the written scope and quote.
Start this work