Free tool · No signup · Runs in your browser
Lead Routing Contract Builder
Define your intake fields and your routing rules. Get back a validated event contract, a priority hierarchy, a decision object and an idempotency key format. The same architecture I ship for clients, in a form you can paste into a Make.com scenario, a webhook receiver or a CRM workflow.
1. Your intake fields
Every source, a form, an ad platform, a spreadsheet, a chat widget, has to deliver the same fields in the same shape. Start from the canonical set and add what your business needs.
What the contract actually is
A lead routing contract is a fixed, named set of fields that every source delivers in the same shape, plus the ordered rules that decide who owns the lead. It sits between your form and your CRM. It is what stops form labels, ad platform payloads and spreadsheet columns from quietly controlling your revenue operations.
Most broken CRM automation I work on is not a tool problem. It is a missing contract problem. A Zapier Zaps to a form, a Make.com scenario fed by Meta Lead Ads, a manual import from a sheet, and a chat widget will all write different shapes into the CRM, and every downstream rule then has to defend itself against all of them. You can see the full failure list in my guide to broken CRM automation, and the architecture that replaces it in automated lead routing in CRM.
Search before create
The contract is useless without it. Match the contact by email, the company by domain, the open deal by contact and pipeline, then create only after the search layer clears. This is the single highest value fix in the list.
One key, one retry
Build the idempotency key from source system, source record id and email, and pass it on every write. A retried webhook becomes a no-op instead of a second contact with a second owner.
Rules you can read
The decision object records which rule fired, why, and which owner it chose. A routing layer you cannot audit is a routing layer nobody will trust with the good leads.
The fields that make a contract work
These are the fourteen fields I put in every routing contract. Each one exists because something broke without it.
Where this fits
If you want the same architecture delivered and running on your stack, Fix your pipeline is the engagement that builds and ships it. If you want to run it yourself, the lead routing kit is the whole layer as a free workbook, and the CRM automation repair kit is the data layer underneath it.
If you are not sure which of those three you need, send the broken path to the free AI systems diagnostic and get the failure point in writing first. The proof is in the Meridian Legal Group CRM overhaul: 94% fewer duplicate contacts across three offices and twelve intake channels, with assignment inside ten seconds, and the managing partner no longer reassigning leads by hand every morning.
Questions
What is a lead routing contract?
A lead routing contract is a fixed, named set of fields that every lead source must deliver in the same shape, plus the ordered rules that decide which owner gets the lead. It is the layer between your form and your CRM, and it is what stops form labels, vendor payloads and random spreadsheet columns from controlling your revenue operations.
Why do I need an idempotency key?
Because a webhook retry or a form resubmission will otherwise create a second contact and a second owner for the same buyer. A key built from source system, source record id and email makes the retry a no-op instead of a duplicate, which is the cheapest fix in CRM automation.
Should routing rules run on the form or in the CRM?
In the CRM, or in a controlled workflow in front of it. The form should only collect and shape the payload. If a rule runs on the form, every change to the form silently changes who gets routed, and a second intake path means re-implementing every rule.
Is this tool really free and does it send my data anywhere?
Yes, free with no signup, and it never leaves your browser. The whole thing runs client side, there is no server, no API key, and nothing is logged or stored. You export the contract as JSON, the routing matrix as CSV, or a checklist you can work through.
Next step
Send the thing that needs fixing
Paste the broken workflow or the messy handoff, get the failure point and a fix path in writing. Free, no call, reply within 24 hours.
Run the free diagnostic →Stay in the loop.
Technical breakdowns, new system builds, and lessons from deploying autonomous AI. One email a week, direct to your inbox.
One email a week. Leave with one click.