Skip to content
GullySales

Detective and private investigation agencies · CRM

Keep every enquiry and engagement on record without exposing a single case.

A CRM for a detective agency is a record of who enquired, which check they asked about and where the matter stands, kept apart from case files. GullySales sets up the fields, the routine and the rules on who sees what.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

An investigation team reviewing case documents at an office table

What CRM means

A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.

Last updated 14 Nov 2026.

For detective and private investigation agencies

Where it usually goes wrong, and what we would do.

  • “Enquiry records and case files are different things”

    The CRM should know that a family asked about verification and received an estimate. The findings of any case belong in a separate, secured file and never in a sales tool.

  • “A shared spreadsheet leaks”

    Passing a sheet around on messaging apps puts names and phone numbers where the owner cannot control them. Access should sit with those who answer enquiries.

  • “Corporate accounts need a history”

    An HR head who used the agency last year should be recognised on the next call. The CRM holds the contact, the checks ordered and the date of the last job.

  • “Declined enquiries are information”

    Recording why an enquiry did not proceed, whether price, scope or an unlawful request, shows where the pages and scripts need work.

What we do

What we deliver for detective and private investigation agencies.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. Fields for enquiry, not for findings

    Name, contact, type of check, source, stage and next action, with no case details.

    Result: The record is useful and holds nothing sensitive.

  2. Stages from first call to engagement letter

    Enquiry, call held, estimate sent, letter signed, closed, declined.

    Result: The owner sees how enquiries are spread across the stages.

  3. Access rules

    A written list of who may view and edit records, and how a leaver's access is removed.

    Result: Access matches roles.

  4. Corporate account records

    A view of each firm: contact, checks ordered, vendor registration and renewals.

    Result: A repeat client is recognised on the call.

  5. A review view for the owner

    One page showing source, stage and reason for decline.

    Result: The owner sees which sources become engagement letters.

  6. A routing rule by type of check

    A written rule on who picks up an enquiry for each type of check and who covers when that person is away.

    Result: Each enquiry has a named owner on the record.

  7. A tidy-up rule for old records

    A rule on when closed enquiries are archived or deleted, agreed with your adviser.

    Result: The record holds personal details no longer than it needs to.

How the result is measured

  • Enquiries logged in the CRM
  • Data completeness
  • Reports generated from CRM data

Recorded as a baseline before work starts, so every later report has an honest comparison.

Fields worth keeping

What the enquiry record holds and what it must not.

Where the enquiry came from
Filled by whoever takes the call. It tells the owner whether work comes from search, an advocate, an HR referral or a past client.
Type of check and buyer role
Entered at intake so the call routes to the right investigator. No names of the person being checked go here.
Stage of the enquiry
From first call to engagement letter signed. The owner uses it to see which enquiries are waiting for a reply.
Corporate account contact and agreement status
Filled by the account lead. It lets the agency see which HR or law-firm contacts have a vendor agreement and which expire.
Reason for decline
A short coded note when an enquiry is declined, such as unlawful request or out of scope. It keeps a pattern the owner can read.

Who it is for

This is written for these detective and private investigation agencies.

  • Pre-marriage verification for families, including matches with NRI and overseas proposals
  • Post-marriage and matrimonial dispute support for families and their advocates
  • Pre-employment and background verification for HR teams and staffing firms
  • Corporate due diligence on vendors, distributors and joint venture partners
  • Insurance claim verification for insurers and their surveyors
  • Litigation support for advocates, such as tracing a witness or serving a notice
  • Verification of tenants, domestic staff and drivers for housing societies and households
  • Brand protection and counterfeit investigation for manufacturers and consumer brands

Before you decide

When this may not be the right fit.

  • You plan to store findings and names of the people being checked in the same sheet, which exposes case data to staff who do not need it.
  • The team shares one login, so a record of who changed what would not exist.
  • You have a few corporate accounts and one person remembers them, so a tool would add work before it adds value.

Before you decide

Agree the work. Know how to judge it.

CRM for detective agencies: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.

Make the scope clear

Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.

Check the work in use

Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.

Know when to change course

If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.

These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.

Before we start

What to have ready before the work starts.

The records, access and decisions this work needs from detective and private investigation agencies. Anything missing is noted in the written scope, with who will supply it.

The current sheet or register of enquiries
Whatever the desk uses now, a shared spreadsheet or a notebook, shows the stages in real use. It need not be tidy. Without it, we design stages from how agencies in this trade work, and your team will find some of them foreign.
A decision on what may be stored
Only you can say which details about an enquirer belong in the CRM. Decide with your adviser before we build. If this is open, we create the narrowest set of fields, name, number, check type and source, and add nothing else.
A named owner of the CRM
One person must keep the records current and grant access. If it is the owner, say so. If no one is named, stage changes stop being recorded and the CRM becomes another spreadsheet that leaks.
The list of corporate accounts and contacts
Corporate buyers need a history of past jobs and who approved them. Bring a list of accounts with the contact and the services bought, without findings. If the list is thin, the corporate record starts empty and fills as jobs arrive.
Phones and logins for each person
Investigators in the field will use the CRM on their phones, so each needs a working device and an email. Shared logins are not acceptable because access rules depend on named users. If a person has no phone suitable for work, they are left out.

How it works

How the CRM work runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Walk the path from first call to letter

    We sit with your desk and an investigator and trace what happens to an enquiry, from the first call to the signed engagement letter. We write down each hand-off and where a note gets lost, including the moment an investigator in the field passes a caller's number to the desk on a scrap of paper or a text. This path, drawn from how your office works, decides the stages of the CRM.

  2. 2

    Draw the line between enquiry and case file

    You tell us what stays in the case file and what may sit in a CRM. We set the fields to hold contact details, check type, source and stage, and nothing about findings. Your adviser looks at the list. A field that could expose a matter is not created, and a free-text box is limited to the stage remark, because a box left open soon fills with names, places and details nobody should keep beside a phone number.

  3. 3

    Set up a test copy with dummy enquiries

    We build the CRM in a test space and fill it with invented enquiries so no real caller appears. The desk tries the stages, the source field and the corporate account record. You decide whether the screens match how your team talks before any real data goes in.

  4. 4

    Write the access rules and test them

    We list who sees what: the desk, investigators, the owner, any outside accountant. Corporate account records get tighter access than family enquiries, since they hold vendor details, NDA dates and the names of approvers at the client firm. Then we log in as each role and check what shows. A role that sees too much is corrected before launch.

  5. 5

    Move over a small set of live enquiries

    You choose a handful of current enquiries and the desk enters them in the new CRM while the old sheet stays. We watch for any step the desk skips because the screen asks for something it does not have at the first call. If the stages hold and nothing leaks, we move the rest. Old shared spreadsheets are closed or locked by you once the move is checked.

  6. 6

    Read stage counts against the old register

    We compare the stage counts and source field with the register the office kept before the CRM. You see how many enquiries reached a letter, how many were declined and where they stalled. The tidy-up rule for old records is then set, and ownership passes to your desk.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales management. A target, a review routine and someone who owns the number.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3 · you are here

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Which CRM should we use?
One the team will open. Choose a tool in ordinary use in India with controlled sign-in, and keep it simple. We set up the fields and the routine, not a brand preference.
Is it lawful to store enquirers' details?
Personal data rules apply to your records. Check what applies with your own adviser, collect only what routing needs, and keep case findings outside the CRM.
Can the team use it on phones?
Yes, where the tool supports sign-in controls and the phone itself is locked. Treat a lost handset as a data matter and have a plan for it.
Who should see the corporate account records?
The owner and the account lead only. A sales assistant needs routing fields, not contract terms or contact history for a law firm. Give each person only the fields the work needs, and remove access the day someone leaves the agency.
Can investigators add notes about a matter in the CRM?
No. The CRM holds the enquiry and the engagement, not the findings. A note about a person's movements or a family's circumstances belongs in the case file under your own controls. We set the notes field to accept stage remarks only, and the access rules keep the case file out of the CRM entirely.
What happens to our existing spreadsheet?
It stays untouched until the CRM has run beside it on a small set of live enquiries. After you confirm the stages work, you lock or archive the old sheet yourself, since it may hold details you must keep for your own reasons. We do not delete it. A shared sheet left open is the leak the CRM was meant to close.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.