01 — The problem
Why leads slip through the cracks between marketing and sales
The handoff is where leads get lost. Marketing passes a list, sales calls it weak, and nobody agrees what "qualified" means. Leads from events, forms and referrals land in spreadsheets with duplicates and no owner.
Generic lead management tools assume a standard funnel. Yours has territory rules by state, a partner channel that must never be cold-called, or a product line for specialists. When routing lives in someone's head, speed to lead depends on who is in.
02 — What to build
Core features of a lead tracking app
Focus the first version on speed to the right person:
Lead intake from several sources, tagged by campaign
Duplicate detection by email domain and company name
Qualification fields like company size, industry and timeline
Lead scoring rules you can read and adjust, not a black box
Routing by territory or product interest, with a fallback queue
Follow-up alerts when a new lead goes untouched
Roles
marketing ops, SDR, account executive, sales manager
03 — How to build it
How to build a lead management system with Henosia
Start a private project, your sandbox until you publish.
Upload mock leads, such as an anonymized CSV from recent campaigns plus your territory list.
Connect a database for leads, accounts, owners and activity.
Use Plan mode to describe qualification and routing. The agent asks questions and proposes a plan before anything is built.
Build a first version and submit test leads from each source to check routing.
Iterate on scoring weights, edge cases and the handoff view reps use.
Publish with access for marketing and sales roles only.
An example Plan-mode prompt:
Build a lead management app for marketing and our SDR team.
Leads come from web forms, events and partner referrals. Merge duplicates by email domain.
Mark a lead MQL when company size is 200+ and the timeline is under 6 months.
Route MQLs by US region to the SDR on that territory; partner referrals go to the partner manager.
Flag any MQL with no logged follow-up after one business day.Paste it into a private Henosia project in Plan mode. The agent asks questions and proposes a plan first.
04 — Before you go live
Making the handoff production-ready
Before live leads flow in, agree on:
- One shared definition of MQL and SQL, owned by a named person
- Edit rights: who can change lead status, and who only views
- Integrations with a CRM or marketing tool. Henosia can work with data connections and API-based data; scope each per system, data direction and access level.
- Publishing approval and who reviews changes to scoring rules
Use fixed rules for routing and AI for interpretation, such as summarizing a free-text inquiry. If marketing and sales disagree on what qualified means, automation only speeds up the argument.
Once a lead becomes an opportunity, it moves to your sales pipeline app for deal stages and forecasting.
Start a private project in Henosia, upload a sample of last quarter's leads and plan your routing rules with the agent.
Start a private project05 — FAQ
Frequently asked questions
What is lead management software?
Lead management software handles leads from first capture to sales follow-up. It collects leads from forms, events and referrals, removes duplicates, qualifies and scores them, routes them to the right rep and tracks follow-up. A custom build encodes your own qualification criteria and territory rules.
Is lead management the same as a CRM?
Not quite. A CRM usually manages accounts, contacts and deals across the whole relationship. Lead management covers the earlier stage: capturing, qualifying and routing new leads until sales accepts them. Some teams build a focused lead tracker in Henosia alongside their CRM for intake and handoff rules.
Do I need a developer to build a lead tracker?
Not for a first version. Marketing ops or a sales manager can describe the process in Plan mode and build without writing code themselves. Bring in IT when you connect live lead sources, sync with other systems or decide who can publish and access the app.
How do you keep lead data secure?
Henosia projects start as private sandboxes, so you can build on mock leads first. When you publish, Henosia Authentication can limit access to your company email domain, set app-level permissions and optionally restrict by IP address. Decide which roles can see contact details, and confirm specific security requirements with Henosia.