Skip to content
GullySales

Every lead record is complete, unique and safe to act on.

Gully Sales rebuilds your lead database record by record: one agreed set of fields, sources that write them correctly, duplicates merged with their history, gaps filled from traceable sources, and segments your team can sell into.

  • One company, one record, one owner, with the earlier conversations kept.
  • Phone numbers and email addresses checked before your team spends a rupee.
  • Segments your salespeople can work today, and rebuild the same way next quarter.
Book a free auditTalk to us

Gully Sales Private Limited works on lead data for Indian SMBs, and also runs the sales and marketing teams that have to use it.

In one paragraph

What is Lead Database Management in India?

Lead database management makes your lead records usable: one agreed field specification, controlled sources, validated contact details, enriched company information, merged duplicates, working segments and a named owner. Gully Sales cleans and rebuilds your existing database, fixes the routes that feed it, and hands over rules that keep it accurate as new leads arrive.

The problem

Your team does not trust the list it is asked to work.

Almost no SMB lead database was designed. It grew. An exhibition list here, a website form there, a spreadsheet a salesperson kept on a laptop, a CRM import done in a hurry before a campaign. Nothing looks wrong on any single day. Then a customer receives the same offer three times, a caller reaches a number that stopped working two years ago, and the report says four hundred leads when the team knows there are perhaps ninety worth a call. Nobody chose this. It is where a database ends up when it is filled by many hands and owned by nobody in particular.

You will recognise it as

  • The same company appears three or four times under slightly different spellings, and each version has a different owner.
  • Nobody can say where a lead came from, because the source field is blank, free text, or filled in later from memory.
  • Every campaign starts with the same manual cleaning of the same export, done again the following month.
  • Salespeople keep private lists, because the shared database is missing the details they actually need to make a call.
  • Emails bounce heavily and WhatsApp messages fail, because country codes and mobile digits were never standardised.
  • Counting the database gives a different number depending on who exports it and which filter they used.

What it costs the business

  • Selling hours go into finding and repairing records instead of talking to buyers, and that cost never appears in any report.
  • Campaign money is spent reaching dead addresses, duplicate contacts and people who were never in your market.
  • Reviews turn into reconciliation meetings, because two teams arrive with two numbers drawn from the same system.
  • Contactability falls with every large send, as bounces and blocks damage the channels you still need to reach real buyers.

Why it persists. Cleaning data is nobody's job title. It becomes urgent only on the day a campaign misfires, and the fastest fix that day is to clean that one export by hand, which rescues the campaign and leaves the database exactly as it was. The tools make it easy to add a record and hard to merge two. Without an agreed field list, a rule for the source field and one named owner, every repair is temporary and the next quarter looks the same.

If it stays unresolved. The database keeps growing while the share of it worth working keeps falling. Automation, dashboards and attribution built on top of it inherit the same errors and present them with more confidence than before. In time the team stops using the system for anything except recording what has already happened, and the real selling list moves back into private spreadsheets.

What changes

What changes once your lead data is under control.

In the first weeks

  • You know how many real, reachable leads you hold, and how far that differs from the row count in your system.
  • Duplicates are merged with their history kept, so one company has one file, one owner and one next step.
  • Invalid numbers and undeliverable addresses are marked and grouped before the next campaign is sent.

In how the work runs

  • New leads arrive with source, campaign and the fields your team needs already filled, because capture enforces it.
  • Lists come out ready to use, so a campaign or a calling day starts without a cleaning round in front of it.
  • Each segment has a written definition and a saved view, so the same list can be rebuilt and compared later.
  • Records without an owner, an activity or a next step surface in a weekly check rather than being discovered by chance.

In sales and marketing

  • Sales effort concentrates on the segments that match the buyers you actually win, not on the whole list.
  • Waste in every send becomes visible, because the reachable count is known before the campaign goes out.
  • Handover between marketing and sales gets shorter, since the record already carries what the caller needs.

In what management can see

  • Source and campaign values sit on every record, so reporting and attribution finally have something to read.
  • Data completeness is a monthly number rather than an opinion, and the trend shows whether capture is holding.

Over the longer term

  • The database stays usable as it grows, because the checks that keep it clean run every month, not once.
  • New salespeople, agencies and tools inherit a written standard instead of somebody's habit.

Gully Sales controls the field standard, the clean-up, the matching rules, the enrichment sourcing and the governance routine. Conversion and revenue still depend on your offer, your market and your follow-up. Better data makes those efforts measurable and cheaper to run; it does not replace them.

Who it is for

Who this is for, and when it is worth doing.

The businesses it suits

  • SMBs holding a few thousand to a few lakh lead records spread across a CRM, spreadsheets and inboxes.
  • Marketing leaders whose campaign results are questioned because the underlying list is questioned first.
  • Founders who have collected or bought lists over years and cannot say what is still usable.
  • Sales heads whose team keeps private lists because the shared system is incomplete or out of date.
  • Businesses moving to a new CRM or marketing tool who do not want to carry the old mess across.
  • Companies whose email or WhatsApp sending has started to fail after large sends to an unmanaged list.

What usually prompts the call

  • A campaign went out with duplicate or wrong contact details, and a customer noticed before you did.
  • A CRM migration is planned, and the import will only be as good as the export that feeds it.
  • Two reports of the same pipeline disagree, and the disagreement traces back to the records themselves.
  • Email deliverability or sender reputation dropped after a bulk send to the full database.
  • A new salesperson joined and cannot work the list without spending a week cleaning it first.

What Gully Sales does

The work, component by component.

Data specification and field standard

We agree what a lead record must hold: identifying fields, contact fields, firmographic fields, source fields and sales fields. Each one gets a definition, a format, a picklist where it needs one, and a rule saying whether it is mandatory at capture or filled later. The specification covers both companies and people, and states how the two are linked.

Why it matters:
Without a written specification every person adds what they think matters, and no two records can be compared, filtered or counted the same way twice.
You receive:
A field specification sheet covering every lead field, its format, its picklist values and whether it is mandatory.
Business value:
Your team stops arguing about what a field means, and the same filter returns the same list on two different days.

Source mapping and capture rules

We trace every route a lead takes into your database — website forms, WhatsApp, phone enquiries, exhibitions, referrals, marketplaces, agency handovers and manual entry — and fix what each one writes. Forms collect the required fields, source and campaign values are set automatically where the route allows it, and import templates are standardised so a spreadsheet cannot bring in a new format.

Why it matters:
Most data problems are entry problems. Cleaning history without fixing capture means the same clean-up is needed again within two quarters.
You receive:
Source inventory, form and import specification, and a standard import template with validation built in.
Business value:
New records arrive correct, so the database stops degrading between clean-ups and the source field becomes worth reporting on.

Validation and contactability checks

Every record is checked for whether it can actually be reached. Phone numbers are normalised with country and mobile prefixes corrected, email addresses are syntax-checked and tested for deliverability, and websites or addresses are checked where they matter to your sales process. Records that fail are marked with the reason, grouped and shown to you.

Why it matters:
Sending to unreachable contacts costs money, damages sender reputation, and hides the real size of the audience you can talk to.
You receive:
Validation report by field and by source, with every record marked valid, correctable or unreachable.
Business value:
You know the reachable count before you commit a campaign budget, and your sending channels stay in good standing.

Enrichment and gap filling

Missing fields that decide how a lead is treated are filled: industry, company size band, location, designation, website and the second contact at an account. We fill from your own records first — past invoices, quotations, email threads and existing customers — and then from public or licensed sources. Every enriched value is stamped with where it came from and when.

Why it matters:
A record with no industry or size cannot be segmented, routed or prioritised, so it defaults to whatever the salesperson guesses that morning.
You receive:
Enriched database with source and date recorded against each filled field, plus a list of records that could not be completed.
Business value:
Routing and segmentation work on real attributes, and you can always tell an enriched value from one the customer gave you.

Deduplication and merge rules

We find the duplicates tools miss: the same company under two spellings, a person with a personal and an official email, a lead entered twice by two salespeople months apart. Matching runs on a rule set you approve, matches are scored, and only high-confidence matches merge automatically. The rest go to a review list. Merges keep the history, the earliest source and the agreed owner.

Why it matters:
Blind merging loses conversations and starts ownership disputes. Doing nothing sends the same message twice to the same person on the same day.
You receive:
Duplicate report, approved matching and survivorship rules, and a merged database with a reversible log of every merge.
Business value:
One company means one record and one owner, and nobody loses a conversation they had already taken the trouble to record.

Segmentation and list building

Working segments are defined against the fields that now exist: industry, size, geography, source, lifecycle stage, engagement recency and product interest. Each segment gets a written definition and a saved view or filter inside your own system, so it can be rebuilt on demand instead of exported once and passed around by email.

Why it matters:
Sending everything to the whole database is the main cause of unsubscribes, and the main reason nobody can read the result.
You receive:
Segment definition document and saved segments or views built inside the system your team already uses.
Business value:
A campaign list or a calling list is drawn in minutes, and the same segment can be compared quarter on quarter.

Governance, ownership and retention

Somebody has to own the database. We name that owner, write the rules for adding, editing, merging and archiving records, set unsubscribe and preference handling so an opt-out is honoured everywhere, and agree how long unworked records are kept before they are archived. A short monthly routine keeps the checks running after we leave.

Why it matters:
Rules that live in one person's head end when that person changes role, and a database with no owner drifts back within two quarters.
You receive:
Data governance note with ownership, editing rules, unsubscribe handling, retention rule and a monthly checklist.
Business value:
The standard survives staff changes, and requests to be removed or corrected are handled the same way every time.

What you will have at the end.

  • Database audit report with record counts, duplicate estimate, field completeness and a usable-versus-total figure.
  • Field specification sheet for company and lead records, with formats, picklists and mandatory fields.
  • Source inventory showing every route into the database and what each route currently writes.
  • Form, import and capture specification, plus a standard import template with validation built in.
  • Validation report marking each record valid, correctable or unreachable, with the reason recorded.
  • Cleaned and normalised database, delivered inside your system and as a dated export you keep.
  • Duplicate report with approved matching and survivorship rules, and a reversible merge log.
  • Enriched fields with the source and date recorded against each value that was filled by us.
  • Segment definition document with saved views or filters built inside your own system.
  • Data governance note covering ownership, editing rules, unsubscribes, opt-outs and retention.
  • Monthly data health checklist and a one-page report format your team can run without us.
  • A training session and a recorded walkthrough for the people who will maintain the database.

How it runs

The engagement, step by step.

  1. 1

    Audit and profiling

    We take a full export and profile it: how many records exist, how many are duplicates under different matching rules, how complete each field is, which sources produced which quality, and how much of the database has had no activity for a year or more. You see the state of your data as numbers before anything is touched.

    You provide:
    A full export of the database, or read access to the CRM and to any spreadsheets still in daily use.
    We produce:
    A profiling report with record counts, duplicate estimates, completeness by field and quality by source.
    Done when:
    You accept the profile as an accurate picture of the database as it stands today.
  2. 2

    Field specification

    We sit with your sales and marketing people to agree what a record must hold and what each field means. Existing fields are kept, merged or retired. Picklists are written down. Fields that are mandatory at capture are separated from fields filled later. Anything ambiguous is settled now, rather than in the middle of a clean-up.

    You provide:
    Two working sessions with the people who use the data, and your view on which fields decide how a lead is handled.
    We produce:
    The field specification sheet with definitions, formats, picklist values and mandatory rules.
    Done when:
    Sales and marketing sign off the same specification together.
  3. 3

    Capture and source fix

    Before cleaning history we stop the leak. Website and landing page forms, WhatsApp and phone intake, exhibition capture sheets, marketplace feeds and manual entry are each changed to write the specified fields, with source and campaign values set automatically wherever the route allows it.

    You provide:
    Access to your forms, your website team or agency, and the people who enter leads by hand.
    We produce:
    Updated forms and import templates, an agreed source value list, and written capture instructions for the team.
    Done when:
    A test lead from each live source arrives with every required field populated.
  4. 4

    Validation and clean-up

    Records are standardised — names, phone formats, cities and states, industry values — and then checked for reachability. Emails are verified, numbers normalised and tested, junk entries flagged. Nothing is deleted at this stage. Records are marked and grouped, so you decide what happens to each group.

    You provide:
    A decision on how to treat unreachable and junk records, and notice of any list you consider sensitive.
    We produce:
    A standardised database and a validation report grouping records by exactly what is wrong with them.
    Done when:
    You have approved the treatment for every group of failed records.
  5. 5

    Deduplication and merge

    Matching rules are proposed, tested on a sample and approved by you. High-confidence matches merge automatically and the rest go to a review list. Survivorship decides which value wins field by field, and the activity history, earliest genuine source and agreed owner stay on the surviving record.

    You provide:
    Approval of the matching and survivorship rules, and a decision on ownership when two salespeople claim one account.
    We produce:
    A deduplicated database with a reversible merge log and a review list of the uncertain matches.
    Done when:
    The duplicate rate is measured again and reported against the audit figure.
  6. 6

    Enrichment and segmentation

    Gaps that block segmentation are filled from your own history first and then from public or licensed sources, with provenance recorded on each value. Segments are then defined against the fields that now exist, built as saved views your team can run, and paired with the routing rule that decides who works which segment.

    You provide:
    Your priority segments, the industries and sizes you actually sell to, and access to past invoices or quotations.
    We produce:
    Enriched records with provenance, a segment definition document and saved segments inside your system.
    Done when:
    Each priority segment returns a list your sales team agrees is workable.
  7. 7

    Governance, handover and training

    We name the data owner, write the rules, set the monthly checklist and train the people who will run it. The team is walked through adding, merging, archiving and honouring an opt-out. The database is handed over with a dated export and a written description of everything that was changed.

    You provide:
    The named data owner, and one to two hours of the team's time for the training session.
    We produce:
    Governance note, monthly checklist, training session, recorded walkthrough and a dated handover export.
    Done when:
    Your named owner completes one monthly data health check without our help.

Ways to work with us

Ways to work with us on your lead data.

Database audit and specification

A short engagement that profiles your existing data, agrees the field specification and gives you a prioritised clean-up plan. Suitable when you need to know the size of the problem before committing to the work.

One-time clean-up and rebuild

The full sequence on your existing database: validation, deduplication, enrichment, segmentation and a governance note. Suitable when the database has never been cleaned and the team has stopped trusting it.

Clean-up with capture fix

The rebuild plus the work on forms, imports and intake routes that stops the same problems returning. Suitable when leads arrive from several sources and each source writes something different.

Ongoing data management

A monthly routine: checks on new records, duplicate sweeps, validation of recent additions, segment maintenance and a data health report. Suitable when volume is high or several people add records every day.

Pre-migration data preparation

Cleaning, mapping and structuring your data before it moves into a new CRM or marketing tool, so the new system starts correct instead of inheriting the old problems. Suitable when a migration is already planned.

Why Gully Sales

What you are actually choosing when you choose us.

We work the data we clean.

Gully Sales also runs sales and marketing for Indian SMBs. The database is judged by whether a caller can work it on Monday morning, not by whether it passes a technical check.

Capture is fixed, not only history.

Cleaning without changing the forms, imports and intake habits buys a few months. We treat the routes into the database as part of the job, so the improvement holds after handover.

Nothing disappears behind your back.

Records are marked, grouped and shown to you before anything is removed or merged, and every merge is logged so it can be reversed. You decide what leaves the database.

The standard lives in your CRM, not in a tool only we can run.

The specification, the segments and the checklist live in your CRM or your spreadsheets, so your team is never dependent on a tool that only we know how to operate.

Written down and handed over.

You receive the field specification, the rules and the monthly checklist as documents. If you stop working with us, the standard stays inside your business.

Where it applies

The same service, in different businesses.

Industrial manufacturing and supplies

The situation:
Enquiries arrive from the website, a marketplace, exhibitions and dealer referrals, and each route creates records in a different shape.
How it applies:
One specification covers all four routes, imports are standardised, duplicates across exhibitions and the marketplace are merged, and records are segmented by industry and order size.
Likely benefit:
The team calls one list of accounts instead of four overlapping ones, and dealer enquiries stop competing with direct enquiries.

Healthcare clinics and hospitals

The situation:
Patient enquiries and business enquiries sit in the same list, and the same person appears once under a mobile number and again under a landline.
How it applies:
Enquiry types are separated, contact fields are normalised and verified, communication preferences are recorded, and only business-development contacts are used for campaigns.
Likely benefit:
Communication reaches people who asked for it, in the right category, and sensitive records stay out of marketing lists altogether.

Real estate and interior design

The situation:
Portal leads, walk-ins and referrals overlap heavily, and two consultants often work the same buyer without either of them knowing.
How it applies:
Matching rules are built for individuals rather than companies, ownership is decided on the earliest genuine source, and segments are built by budget band, locality and project stage.
Likely benefit:
The same buyer stops receiving two follow-ups, and consultants can see which stage a lead has really reached.

Education and training

The situation:
Enquiry data collected at events and on forms is incomplete, so counselling calls begin by asking questions the enquirer already answered.
How it applies:
Capture forms record course interest, city and preferred intake, older records are enriched from application data, and segments are built by course and intake.
Likely benefit:
Counsellors open a record that already says what the enquirer wants, and campaigns can address one course at a time.

Technology and professional services

The situation:
A large list built over years from webinars, downloads and purchased data has been sent to repeatedly, and email performance has fallen steadily.
How it applies:
The list is validated for deliverability, unverifiable and long-inactive records are separated, permission status is recorded, and active segments are built by role and company size.
Likely benefit:
Sending goes to a smaller, reachable and permissioned list, which protects the sending domain and makes results readable again.

Distribution and dealer networks

The situation:
Dealer, sub-dealer and end-customer records are mixed together, so campaigns regularly reach the wrong level of the channel.
How it applies:
Record types are separated, the link between dealer and end customer is mapped, territory and dealer ownership fields are added, and lists are built per territory.
Likely benefit:
Each level of the channel receives communication meant for it, and territory conflicts surface before they turn into disputes.

Proof

Work we can point to.

Premier Marketing

The problem:
A distributor of pumping and water management solutions whose earlier digital presence did not support content updates, product listing expansion or strong customer engagement.
What we did:
GullySales built a login-based admin system with product, category and blog management modules, and a lead capture and contact management system for enquiries.
Over:
The result:
An easy-to-maintain backend system that supports daily operations, and a digital platform that acts as both a product catalogue and a lead generator.
Read the case study

Kambar Group

The problem:
Sales processes needed structure, from how leads were generated and recorded through to how they were worked and closed.
What we did:
Gully Sales improved Kambar Group's sales processes with strategic planning, lead generation, sales enablement and closure techniques.
Over:
The result:
More efficient sales processes across planning, lead generation and closure.
Read the case study

Questions buyers ask

Before you enquire, the answers you will want.

Which fields are essential, and what accuracy should we expect?

Every record needs an identifier, a reachable contact, a source and an owner. Beyond that, the essential fields are the ones that change how you treat a lead: industry, size band, location, designation and product interest. We agree thresholds with you rather than assuming them, for example that mandatory fields are filled on nearly all new records and that phone and email pass validation. The thresholds are written into the specification and measured monthly, so they are commitments and not intentions.

How long does a lead database engagement take?

It depends on record volume, the number of systems involved and how much duplicate review needs a human decision. A profiling audit is short. A full clean-up, deduplication, enrichment and segmentation on a database of moderate size is a project of several weeks, run in the sequence described above so you see progress at each stage. We give you the sequence and the checkpoints in writing before starting, and we do not commit to a date until the audit has shown what the data actually holds.

What do we need to provide from our side?

A full export or read access to your CRM and any spreadsheets in use, access to your forms or your website team, and time from the people who use the data. The decisions we cannot make for you are which fields matter to your sales process, how to treat unreachable records, who owns an account when two salespeople claim it, and who will be the named data owner afterwards. Two working sessions and a few short approvals usually cover it.

How is success measured?

Against the baseline taken in the audit. We measure data completeness by field and source, the duplicate rate on a fixed matching rule, reachability by email and phone, how long it takes to build a list, and how much of your pipeline carries a usable source value. Commercial measures such as cost per contactable lead follow later, because they need a few months of the new rules running. Every number is reported with the definition that produced it.

What will you not do with our lead data?

We do not buy lead lists for you, and we do not scrape contacts from sources that prohibit it. We do not write your campaigns, run your outbound calling or build dashboards as part of this engagement, though Gully Sales offers those separately. Legal advice on data protection is outside our scope: we set practical consent, opt-out and retention handling, and recommend you have your legal adviser confirm it against your obligations.

Will you delete records without asking us?

No. During validation and deduplication, records are marked and grouped rather than removed, and you approve the treatment for each group. Merges use rules you have signed off, and every merge is logged so it can be reversed. Where a record is unreachable but potentially valuable, we suggest archiving rather than deleting, so the history stays available if that company approaches you again next year.

Can you work with our existing CRM, or do we need new software?

We work inside what you already use, whether that is a CRM, a shared spreadsheet system or a mix of both. The specification, segments and checklist are built there, so nothing depends on a tool only we can operate. If your current system genuinely cannot hold the fields or rules the work needs, we will say so plainly and show you what it is costing, rather than quietly building around the limitation.

Where does enrichment data come from, and can we use it?

Your own records come first: past invoices, quotations, email threads, existing customer files and the information the lead gave you. After that we use public sources such as company websites and directories, or licensed data where you already hold a subscription. Every enriched value carries its source and date, so you can see the origin of any field. We do not add contacts from sources whose terms forbid it.

4 more questions

We bought a list two years ago. Can it be salvaged?

Partly, usually. Validation will show how much of it is still reachable, which is often less than expected. The bigger question is permission: a purchased list of people who never asked to hear from you should not be treated like your enquiry database. We separate the two, tell you what remains usable, and recommend working the purchased portion through calling or a permission step rather than adding it to your regular sending.

How is this different from marketing operations or marketing automation?

Marketing operations designs the process around campaigns, and marketing automation builds journeys inside your tools. This engagement works on the records themselves: the fields, the sources, the validation, the duplicates, the segments and the ownership. Process and automation both sit on top of the data, so if the records are unreliable, neither of them can produce a number you trust. Many businesses need this one first.

Who keeps the database clean after you leave?

Your named data owner, using the monthly checklist we hand over. That routine takes a couple of hours a month: checking new records against the specification, running a duplicate sweep, validating recent additions and reporting the health numbers. We train the team and record a walkthrough so a new joiner can learn it. If you prefer, the ongoing data management option keeps that routine with us.

Cleaning will shrink our database. How do we explain that internally?

By reporting both numbers. The row count falls because duplicates merge and unreachable records move to an archive, while the count of records you can actually work usually holds steady or rises once enrichment fills the gaps. We report total, usable and reachable side by side from the audit onwards, so the drop is explained the day it happens rather than questioned in a review three months later.

Talk to us

Request a marketing operations assessment of your lead data.

Nothing is sold at the audit. We look at a sample of your database with you, show what it contains and what it does not, and say whether this needs a full rebuild or a short piece of focused work.

  • No obligation and no sales script
  • A reply from someone who does the work
  • Your details are never sold or shared

Your export, contact records and customer information stay confidential, are used only to prepare and conduct the audit, and are returned or deleted on request once the assessment is over.

Protected by reCAPTCHA — Google’s privacy policy and terms apply.

Get a free audit of how you sell, and a scored report of where the work is.

Book a free audit
Book a free audit