Skip to content
GullySales

Your sales database decides how far your outreach can reach.

Gully Sales builds your prospect database from named sources, verifies every contact against reality, enriches it with the fields your segmentation needs, and hands it over deduplicated, segmented and documented.

  • A written field specification before a single record is collected
  • Contacts checked against live sources, with bounces and dead numbers removed
  • Records deduplicated against your CRM and segmented before handover

Gully Sales Private Limited builds sales data for small and medium businesses across India.

In one paragraph

What is Sales Database Building and Verification?

Sales database building, verification and enrichment from Gully Sales turns scattered contact lists into one governed asset. We agree the fields you need, collect records from named sources, verify them, add the firmographic detail your segmentation depends on, remove duplicates, and hand over a segmented file with a refresh routine your team can maintain.

The problem

Your team is spending its selling hours fixing the list.

Most sales databases in growing Indian businesses were never built. They accumulated. An exhibition badge scan here, a downloaded directory there, a spreadsheet an old salesperson left behind, a few thousand rows someone bought in a hurry. Each part was reasonable on the day it arrived. Together they now decide who your team calls, and nobody can say how much of it is still true.

You will recognise it as

  • Emails bounce in numbers you have stopped counting, and the campaign report is unreadable because of it.
  • Two salespeople call the same company in the same week, from two different sheets.
  • A quarter of the numbers reach a person who left the company, or a landline nobody answers.
  • Nobody can tell you how many companies in your target market you hold, or which ones you are missing.
  • Filters break because industry is written five different ways in the same column.

What it costs the business

  • Sender reputation drops as bounces rise, so even the correct addresses stop reaching the inbox.
  • Your team's connect rate falls, and confidence in outbound falls with it.
  • Territory and target-setting rest on a count of rows, not a count of real companies.
  • Campaign results cannot be compared, because you never know whether the list or the message caused the difference.

Why it persists. Data work has no owner. It is not a sale, so it never reaches the top of anyone's week, and it stays invisible until a campaign fails. Buying a fresh list feels faster than fixing the one you have, so the pile grows instead of getting cleaner. And contact data decays quietly on its own: people change roles, companies shift offices, numbers get reassigned, and nothing in the sheet tells you it happened.

If it stays unresolved. The database keeps ageing while your team keeps working from it. Outreach costs more per meeting, reporting stays unreliable, and each new salesperson inherits the same confusion. The longer it runs, the harder it becomes to separate a weak market from a weak list.

What changes

One database, checked, deduplicated and safe to dial.

In the first weeks

  • You know the size of your addressable market as a number of verified companies, not a row count.
  • Bounce and wrong-number rates fall from the first campaign after handover.

In how the work runs

  • One database, one field dictionary, one owner, so two people stop calling the same account.
  • Territories and target lists can be cut cleanly because the segmentation fields are complete.
  • Your team spends its calling hours calling, not hunting for a number.

In sales and marketing

  • More conversations per hour worked, because a higher share of attempts reach a real person.
  • Campaign results can be read, so you learn what the market thinks instead of what the list did.

In what management can see

  • A coverage view showing which parts of your target market you hold and which are blank.
  • Reporting on data quality: completeness, duplicate rate and verification age, refreshed monthly.

Over the longer term

  • A database that stays usable because refresh and suppression are routines, not rescue jobs.
  • An asset you own outright, documented well enough for the next person to run it.

We control the specification, the sourcing, the verification method and the state of the file we hand over. Response, meetings and pipeline depend on your offer, your market and how the data is worked, so we report those honestly rather than promise them.

Who it is for

This is for you if outbound is real work and the data is not ready.

The businesses it suits

  • SMBs starting outbound sales and needing a defined market list before the first call is made.
  • Businesses with several old lists in several places that need to become one usable database.
  • Companies whose email campaigns are bouncing enough to threaten deliverability.
  • Teams adding salespeople or territories and needing accounts split without overlap.
  • Manufacturers and distributors who sell to a definable set of companies rather than to the public.
  • Businesses moving into a new state, city or industry with no contact base there.

What usually prompts the call

  • You are about to hire an SDR, a telecaller or an agency and have nothing clean to hand them.
  • A campaign went out and the bounce report was worse than the response report.
  • You are moving to a CRM and do not want to carry the mess into it.
  • A new product needs a different buyer than the one your existing list contains.

What Gully Sales does

The work, component by component.

Data specification

We agree, in writing, what a usable record is for your business: which fields are mandatory, which are useful, how each is formatted, and the accuracy standard each must meet before it enters the database. Company name, entity type, industry, location, size band, contact name, designation, direct number, email, source and date collected are typical; yours may differ.

Why it matters:
Without a specification, every batch is collected to a different standard and the database can never be compared with itself.
You receive:
A one-page field dictionary with formats, mandatory fields and accuracy standards.
Business value:
Every record afterwards is judged against the same standard, so quality becomes something you can check rather than sense.

Source planning

We identify where records for your market can legitimately be found and in what volume: public company registers, trade body and association directories, exhibition and trade fair listings, industry directories, company websites, professional networks, your own past enquiries, badge scans, dealer records and dormant CRM entries. Each source is recorded against the records it produced.

Why it matters:
Sources differ in accuracy and in what they may be used for, so an unrecorded source is a record you cannot defend or refresh.
You receive:
A source plan naming each source, its expected yield, and the fields it can supply.
Business value:
You can see where your market coverage will come from before the work starts, and where it will be thin.

Verification

Every record is checked before it counts. Email addresses are tested for domain and mailbox validity, phone numbers are line-checked and a sample is dialled by a person, company websites are checked as live, and entries whose company appears closed or renamed are held back for review. Records that fail are marked and quarantined, not silently deleted.

Why it matters:
A record that has never been checked costs your team the same effort as one that has, and returns nothing.
You receive:
A verified file with a status and check date on every contact, plus a quarantine list.
Business value:
Bounce rates and wrong numbers drop, so campaign reports start describing your market instead of your data.

Enrichment

We add the fields your targeting needs but your existing lists do not carry: turnover or size band, employee count, number of plants or branches, states operated in, industry classification in your own words, buying role and designation, alternate contacts within the same account, website presence, language preference, and trigger details such as a recent expansion.

Why it matters:
Segmentation, routing and message relevance all depend on fields that a name and a number cannot supply.
You receive:
An enriched database with the agreed firmographic and role fields populated and sourced.
Business value:
Your team can prioritise by fit rather than by row order, and write messages that sound informed.

Deduplication and reconciliation

We match records across every list you hold and against your CRM, using company identity rather than spelling, then apply merge rules that say which version of a conflicting field survives. Existing customers, live opportunities and do-not-contact entries are matched out, so nobody is approached as a stranger.

Why it matters:
Duplicates cause two calls to one company, inflate your market size, and quietly destroy trust in every report drawn from the data.
You receive:
A deduplicated master file with a merge log and a suppression list.
Business value:
One company, one record, one owner, so coverage numbers and territory splits mean what they say.

Segmentation

The clean database is cut into the segments you will actually work: fit tiers, industry, region or territory, size band, and where relevant, buying stage or relationship history. Each segment is defined by rules on the fields, not by hand-picking rows, so it can be regenerated whenever the data changes.

Why it matters:
An unsegmented database forces one message on every buyer, which is why generic outreach underperforms.
You receive:
Segment definitions with record counts, and the database tagged accordingly.
Business value:
Campaigns and territories can be planned against real counts, and results can be compared segment by segment.

Governance and refresh

We set the rules that keep the database usable: who may add records, what a new record must contain, how often each segment is re-verified, how unsubscribes, do-not-disturb registrations and opt-outs are recorded and honoured, and how the source and date of every record is retained. Ownership is assigned to a named person on your side.

Why it matters:
Contact data decays every month, and without a routine the file you paid to clean returns to its old state within a year.
You receive:
A short data governance note, a refresh calendar and a suppression register.
Business value:
The database keeps its value after we finish, instead of becoming another old list in the pile.

What you will have at the end.

  • A written field specification and data dictionary, agreed before collection begins.
  • A source plan naming every source used, its yield and the fields it supplies.
  • A pilot batch and an anonymised sample extract for your sign-off before the full build runs.
  • The built database in your chosen format, with source and collection date on every record.
  • A verification report showing pass, fail and quarantine counts by field and by source.
  • An enrichment layer with the agreed firmographic, role and trigger fields populated.
  • A deduplication and merge log, plus a suppression and do-not-contact register.
  • Segment definitions with rules and record counts, applied as tags in the database.
  • A market coverage view showing where your target market is held and where it is blank.
  • A CRM-ready import file mapped to your fields, with a dry-run check before loading.
  • A one-page governance note and refresh calendar naming the owner on your side.
  • A handover walkthrough for the people who will use and maintain the database.

How it runs

The engagement, step by step.

  1. 1

    Define the market and the record

    We start with who you sell to, not with data. We agree the industries, sizes, regions and roles that make a company worth your team's time, then translate that into the fields a record must carry and the accuracy standard each field must meet.

    You provide:
    Your view of the ideal customer, past won and lost accounts, and any existing lists or CRM exports.
    We produce:
    A market definition and a written field specification with accuracy standards.
    Done when:
    You have signed off what a usable record looks like.
  2. 2

    Plan and test the sources

    We identify the sources that can supply your market, check what each actually yields, and drop the ones that cannot meet the specification. A small test batch is pulled from each, so the estimate of coverage rests on real records rather than hope.

    You provide:
    Any memberships, directories, dealer lists or event records you already have access to.
    We produce:
    A source plan with expected yield per source and a tested sample from each.
    Done when:
    You know how much of your market is reachable, and from where.
  3. 3

    Build the pilot batch

    We build a small batch to the full standard, including verification and enrichment, and put it in front of you. You check whether these are the companies and people you want to talk to. The specification is corrected here, while correcting it is cheap.

    You provide:
    A working session to review the sample and tell us what is wrong with it.
    We produce:
    An anonymised sample extract and a revised specification.
    Done when:
    You have approved the record standard on real records, not on a description.
  4. 4

    Build, verify and enrich at scale

    The full database is collected against the approved plan. Each record is verified before it is accepted, then enriched with the agreed fields. Failures are quarantined with a reason, so you can see what the market itself does not disclose.

    You provide:
    Prompt answers on edge cases, and access to your CRM export for matching.
    We produce:
    The verified and enriched database, with a verification report by source and field.
    Done when:
    Every accepted record carries a source, a check date and a status.
  5. 5

    Deduplicate, suppress and segment

    Records are matched across sources and against your CRM, duplicates merged under agreed rules, and existing customers, live deals and do-not-contact entries suppressed. The surviving database is then tagged into the segments you will work.

    You provide:
    Your customer list, open pipeline and any do-not-contact instructions.
    We produce:
    A deduplicated master file, a merge log, a suppression register and segment tags.
    Done when:
    One company holds one record, and every record sits in a named segment.
  6. 6

    Load and hand over

    The database is mapped to your CRM or calling tool, dry-run on a small load, then imported. We walk the people who will use it through the fields, the segments and the rules, so the standard survives contact with daily work.

    You provide:
    CRM or tool access, and the team who will use the data for one session.
    We produce:
    A mapped import file, a completed load and a handover walkthrough.
    Done when:
    Your team is working from the database inside their own tools.
  7. 7

    Govern and refresh

    We set the refresh cadence, the rules for adding new records, and the way opt-outs and do-not-contact requests are recorded. A named owner on your side takes it forward, with a review of data quality and market coverage at an agreed interval.

    You provide:
    A named data owner and time for the agreed review.
    We produce:
    A governance note, a refresh calendar and a data quality review.
    Done when:
    The database has an owner, a standard and a date for its next check.

Ways to work with us

Clean what you have, or build the database from nothing.

Database audit

We assess the lists and CRM records you already hold, report duplicate rate, field completeness, verification age and market coverage, and tell you what is worth keeping. Often the honest first step.

One-time database build

A defined market list built, verified, enriched, deduplicated and segmented once, delivered CRM-ready with a governance note. Suited to a new market entry or a new outbound programme.

Build with managed refresh

The build, followed by a standing arrangement to re-verify segments on a cycle, add new records to the specification and keep the suppression register current.

Clean-up and enrichment of your own data

We leave your record base where it is and work on it: verify, enrich, deduplicate, suppress and segment what you already own, without collecting new records.

Data foundation for an outsourced sales programme

The database is built as the first stage of a wider engagement, so the SDRs, telecallers or field team who follow start from a list that has already been checked.

Why Gully Sales

What you are actually choosing when you choose us.

We build the specification before the data.

Most data problems are specification problems wearing another hat. Agreeing what a usable record contains, and to what standard, is the part that decides whether the file is still useful a year later.

Verified means checked, not claimed.

Every accepted record carries a check date and a status, and a sample is dialled by a person. You can audit our work instead of taking it on trust.

We design for how Indian SMBs actually buy.

Company names spelled three ways, GST states, dealer networks, regional language preference and a decision-maker who is often the owner: our field design assumes these rather than fighting them.

The data is handed over, not held.

The database, the source records, the merge log and the governance note are yours. Nothing sits in a tool you cannot open, and nothing depends on us to stay usable.

It connects to the selling, not just the spreadsheet.

We work across sales and marketing, so the fields are designed for the campaigns, calls and territories that will use them, rather than to make the file look complete.

Where it applies

The same service, in different businesses.

Industrial manufacturing

The situation:
A components manufacturer sells to a few thousand OEMs and fabricators across four states, but its contact base is a mix of exhibition scans and an old dealer file.
How it applies:
We define the account universe by industry, size and state, build and verify it, and add plant locations and purchase-role contacts alongside the proprietor.
Likely benefit:
The sales team works a known universe with clean territory splits, rather than calling whoever appears next in the sheet.

Business services

The situation:
A consulting firm's outbound emails began bouncing heavily after a purchased list was loaded, and deliverability for its genuine mail suffered.
How it applies:
We quarantine the unverifiable records, verify and enrich what remains, suppress the risky domains and rebuild the target list from named sources.
Likely benefit:
Mail reaches inboxes again, and the campaign report finally reflects the market's response rather than the file's condition.

Healthcare suppliers

The situation:
A medical equipment distributor wants to reach hospitals, diagnostic centres and clinics, but each category needs a different contact role.
How it applies:
We build separate segments by facility type and size, and map the purchase, biomedical and administrative contacts within each account.
Likely benefit:
Each segment gets an approach suited to it, and coverage gaps by city become visible on a map rather than in hindsight.

Building materials and interiors

The situation:
A tiles and fittings brand sells through architects, contractors and dealers, and holds three separate lists with heavy overlap between them.
How it applies:
We deduplicate across the three, define influencer and buyer roles as separate record types, and tag projects and territories.
Likely benefit:
One company is contacted once, through the right channel, with the influencer and the buyer no longer confused for each other.

IT and software services

The situation:
A services firm is entering a new metro with no contact base, and needs to know whether the market is large enough before it hires.
How it applies:
We size and build the addressable account list for that city first, verified and segmented by fit tier, before any hiring commitment is made.
Likely benefit:
The hiring decision rests on a counted market rather than an assumption about it.

Agriculture and agri-inputs

The situation:
A farm-input company needs to reach dealers and producer organisations across districts where records exist mostly on paper and in field notebooks.
How it applies:
We consolidate the field records, verify numbers by call, add district, crop and season fields, and set a refresh routine after each season.
Likely benefit:
Field coverage becomes a plan on paper instead of the memory of whoever last visited the district.

Proof

Work we can point to.

Kambar Group

The problem:
Sales planning, lead generation and closing were running as separate efforts rather than as one process.
What we did:
Gully Sales worked on strategic planning, lead generation, sales enablement and closure techniques for the group's sales function.
Over:
As reported in the published case study
The result:
The case study reports improved sales processes and greater efficiency. for the record counts and contact accuracy behind it.
Read the case study

Questions buyers ask

Before you enquire, the answers you will want.

Which fields and accuracy thresholds are essential?

It depends on how you sell, but a workable minimum is company name, industry, location, size band, contact name, designation, a reachable phone number, a valid email, and the source and date of collection. We set a threshold per field rather than one for the whole file: mandatory fields must be verified before a record is accepted, while useful fields may be left blank rather than guessed. A blank field is honest; an invented one is expensive.

How long does building and verifying a database take?

We do not quote a fixed timeline before seeing the market, because a specialist list of two thousand companies and a general one of fifty thousand are different jobs. What we do commit to is the sequence: specification first, then a pilot batch you approve, then the full build in tranches so your team can start working the early segments while the rest is still being verified. You will have a dated plan before work starts.

What do you need from us before the build starts?

Your definition of a good customer, a list of won and lost accounts, whatever contact records you already hold including CRM exports, your current customer list, and any do-not-contact instructions. We also need one person who can answer edge-case questions within a day and sign off the pilot batch. Access to the CRM or calling tool is needed only at the loading stage, not before.

How is the quality of the finished database measured?

In two layers. Data quality is measured directly: bounce rate, wrong-number rate, duplicate rate, field completeness and how much of your defined market you now hold verified. Commercial effect is measured through the outreach that uses the data: contacts reached, response rate, meetings held, qualified opportunities, pipeline created and conversion by segment, each compared with the baseline we record before starting. We report both, because good data used badly still produces nothing.

What is not included in the database service?

We do not run the outreach itself under this service, write the campaign messages, or reconfigure your CRM beyond mapping and loading the file. We do not supply personal contact details unrelated to a business role, and we do not collect from sources whose terms forbid it. If you want the calling and emailing done as well, that belongs to our outsourced sales services and is scoped separately.

Is buying a ready-made database not cheaper?

It usually costs less on the invoice and more everywhere else. Purchased files are collected to somebody else's specification, rarely carry a check date, often duplicate what you already hold, and can damage your sender reputation within a single campaign. We are not against using a purchased file as raw material, but it then has to be verified, deduplicated and enriched to your own standard before your team works it.

How do you handle data protection and consent?

Every record carries its source and the date it was collected, so you can always show where it came from. We work from sources that permit business contact use, honour do-not-contact instructions and unsubscribes through a suppression register, and keep that register with the database rather than in somebody's inbox. We are not your legal advisers, so we build the record-keeping that lets your own adviser confirm your position.

How quickly does a sales database go out of date?

Faster than most owners expect. People change roles, companies move premises, numbers are reassigned and businesses close, and none of it announces itself in your spreadsheet. That is why we treat refresh as a routine rather than a project: segments are re-verified on a cycle, new records must meet the same specification, and every record carries a check date so its age is visible at a glance.

4 more questions

Can you work with the data we already have instead of building new?

Yes, and it is often the cheaper starting point. We audit what you hold, report duplicate rate, completeness and verification age, then verify, enrich, deduplicate and segment the records worth keeping. Anything unverifiable is quarantined rather than deleted, so nothing is lost by accident. We only build new records for the parts of your market that the audit shows you do not cover.

Will the database work with our CRM?

That is part of the handover. We map the fields to your CRM or calling tool, run a dry-run load on a small batch to catch format and duplicate issues, then complete the import and walk your team through the fields and segments. If you have no CRM yet, we hand over a structured file that a CRM can take later without rework, and tell you what to look for when you choose one.

What happens to records that fail verification?

They are quarantined with a reason, not deleted. A number that never answered is different from a company that has closed, and both are different from a record whose email domain no longer exists. Keeping them separately, with the reason recorded, stops the same dead record being collected again from the same source in six months, and lets you decide whether a manual check is worth it.

Do we own the database afterwards?

Yes. The database, the source and merge logs, the field specification, the segment rules and the suppression register are handed to you, and are yours to keep and use. Nothing sits inside a tool that only we can open, and nothing stops working if you stop working with us. If you later want the refresh handled elsewhere, the documentation is written for someone else to pick up.

Talk to us

See how much of your contact data is still true.

A first conversation is a working one. Bring a sample of the list you have now, and we will tell you what is wrong with it and whether a rebuild or a clean-up is the sensible route, before anything is quoted.

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

Your list samples and enquiry details are used only to prepare your review, and are never added to any database we build for another client.

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