Who this is for
A sales or marketing manager whose web leads reach the CRM through several forms and tools, and whose duplicates, unowned leads and sync gaps all need fixing together.
Fixing one problem has exposed the next: de-duplicated contacts still reach no owner, an owner is assigned but the sync overwrites their notes, and nobody is told when a form stops working.
The result
For each of up to three named form paths, a synthetic lead submitted at the start reaches HubSpot as one contact and one company, receives the owner your approved table names, raises an alert if the path fails and, where agreed, syncs its agreed fields without error. You accept the finished paths, not each internal step.
What is included
- Up to three web-form paths into one HubSpot account, with a written map of each path from form to owner
- Correction of duplicate creation, assignment and alert for each path, against a rule table you approve
- For up to two agreed fields, correction of the HubSpot–Salesforce mapping, if the integration is in use
- An end-to-end synthetic lead through each path after the corrections, and a short runbook
You receive
- A one-page map of each form path and its matching, assignment, alert and sync steps
- The approved rule table and the corrected workflows, form settings or integration steps, with change notes
- The end-to-end synthetic lead log for each path
- A runbook: who owns each path, what each alert means and how to retest after a team change
What is not included
- Designing territories, scoring, nurture or advertising, or consent and data-protection advice
- Changing a form on your own page that HubSpot collects through its tracking code: it can be mapped, but HubSpot adds every submission from one browser to one contact there, so moving it to a HubSpot form or the Forms API is a separate quote
- Merging, reassigning or deleting existing records
- More than three form paths, two synced fields or one HubSpot account
- Changing seats, subscription tiers, billing or Salesforce flows, validation rules and permissions
- Any promise about how quickly a lead is contacted, or real contacts used in tests
What we need from you first
- The form paths and tools involved, and roughly how a lead is meant to reach a salesperson
- What goes wrong today on each path: duplicates, no owner, a missed alert or a sync problem
- Who approves the rules, and who administers Salesforce if it is in use
- Do not send contact lists, passwords, API keys or an account invitation in the first enquiry
Never send passwords, keys, customer records or confidential code in the first enquiry. Secure handover is agreed after scoping.
How we check it is done
- A synthetic lead submitted through each named form path creates exactly one contact and is associated with exactly one company for its domain.
- Each synthetic lead is assigned to the owner your approved rule table names, and a lead that matches no rule is assigned to the named fallback owner.
- A deliberate failure on each path raises an alert at the shared place, and the named owner and backup confirm receipt.
- Where sync is in scope, each agreed field crosses in the agreed direction on a synthetic record and shows no sync error.
You accept the finished paths after reading the logs and the runbook. You apply the changes yourself, and you can send any path back with comments before you accept.
When we would stop or decline
- The routing rules are undecided or disputed inside your team
- The paths can only be tested with real leads or real salespeople would be notified
- A Salesforce-side cause cannot be changed by anyone on your side
Questions
Why a project and not three separate repairs?
Each stage can be correct alone and still lose or duplicate a lead in combination. A project tests each path from form to owner as a whole, and you accept the finished path.
Do you change our Salesforce setup?
We name any Salesforce-side change needed. Your administrator makes it, because flows, validation rules and permissions are yours to approve.
How is this different from keeping leads owned month after month?
A project ends when the agreed paths pass their tests. The standing service continues, with a weekly check and repairs, until you end it.
Price and terms
From £1,500 · untested offer price. The payment schedule is set in the written proposal. Nothing is charged until you have agreed it.
This is a new service with no published client results. The price is a starting point we have not yet tested with buyers. Nothing is ordered or charged by the enquiry. The full specification is on the Synthetic Industry catalogue.