Skip to content
GullySales

IT staffing and contract hiring firms · CRM

Hold the client, the requirement and the candidate in records that agree with each other.

A CRM for an IT staffing firm links a client company to its requirements, and a candidate to the submissions and consent they have given. GullySales works on the record layout, the stages and the habits that keep both sides current.

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

Recruitment colleagues discussing candidate requirements and interview notes

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 IT staffing and contract hiring firms

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

  • “A requirement needs its own record”

    A hiring manager's email is not a record. Role, skills, budget, notice period and status belong in a field-based entry the whole team can search.

  • “Candidates and clients are different kinds of record”

    A candidate's profile, consent and submissions are not a company's account. Mixing them hides both, so separate them and link where needed.

  • “Duplicates damage trust”

    The same candidate sent twice to a client, or called by two recruiters, embarrasses the firm. The record should show who has the candidate and for which role.

  • “Consent has to travel with the CV”

    Where a candidate agreed to be submitted, and to whom, must be visible at the moment of sending. A note buried in a chat does not protect anyone.

What we do

What we deliver for IT staffing and contract hiring firms.

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

  1. A record layout for clients, requirements and candidates

    Fields for company, contacts, requirement, skills, budget, candidate profile, consent and submissions.

    Result: Both sides sit in one searchable system.

  2. Stages for requirements and for candidates

    Open, sourcing, submitted, interviewing, offered, joined and closed for requirements, with matching stages for candidates.

    Result: Reports show where roles stall.

  3. A duplicate check

    A rule that flags a candidate already submitted to the same client before a profile is sent.

    Result: Double submissions are caught.

  4. A consent field with a date

    A required entry showing what the candidate agreed to and when.

    Result: No profile goes out without a consent entry.

  5. An import and clean-up

    Existing sheets, email contacts and CV folders moved in, deduplicated and checked.

    Result: The record starts clean.

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

The fields that keep clients, requirements and candidates agreeing with each other.

Requirement stack and level
Filled by the account recruiter from the client's brief. It drives the bench search and shows when a role is repeated.
Date a profile was first submitted
Filled at submission. It settles disputes over who sent a candidate first when a client has several vendors.
Candidate consent with date and source
Filled when the CV is received. It shows that sharing the profile was agreed and when.
Notice period and counter-offer risk
Filled by the recruiter after the screening call. It warns the account owner that an offer may not convert to a joining.
Client rate and margin band
Filled by the account owner, visible only to people who need it. It lets you argue a rate request from your own record.

Who it is for

This is written for these IT staffing and contract hiring firms.

  • Contract developers and testers for product companies
  • Contract-to-hire engineers for services firms
  • Permanent hiring for startups and GCCs
  • Data, cloud and DevOps specialist hiring
  • IT support and infrastructure staff
  • SAP, Salesforce and other platform consultants
  • Bulk campus and fresher hiring support
  • Third-party payroll for contract IT staff

Before you decide

When this may not be the right fit.

  • Your team keeps candidate lists in personal sheets and has not agreed to move them to one shared system.
  • You have no rule about who may see client rates, and putting them in a shared record would expose them to everyone.
  • You place only a few candidates a year and can recall each one without help.

Before you decide

Agree the work. Know how to judge it.

CRM for IT staffing firms: 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 IT staffing and contract hiring firms. Anything missing is noted in the written scope, with who will supply it.

Every sheet and tool that holds data today
List where client and candidate details live, including personal files, shared drives and recruiters' phones. A record missed now becomes a duplicate later, and a duplicate sent to a hiring manager twice damages trust. If someone keeps a private list, the owner asks for it before the import. We work from what is declared, so the list should be complete.
The owner's rule on who sees rates
Decide which people may see client rates and candidate expected pay. Recruiters may need the candidate figure but not the margin. This is an owner decision and we cannot guess it. Without it, we hide both and recruiters ask, which slows them.
Your consent wording and evidence
Bring the message or form by which a candidate agrees to be submitted, and show where those agreements are held. The consent field in the system must reflect something real. If consent was taken by phone, say so, and the plan sets a way to note it.
A recruiter to test with real requirements
One recruiter must try the system on live work and say what is awkward, such as a field that has no place for a notice period. A system tested only by the owner fails on the desk, because the owner does not enter the detail of a working day. Their findings change the fields before launch, and the plan records what was changed and why.
A decision on how long data is kept
Decide with your own adviser how long a candidate record stays after a role closes. We build the field and the reminder; we do not set the period. Without a decision we flag old records and leave them untouched.

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

    Export the current client and candidate sheets

    We begin with whatever holds your data now: spreadsheets, a recruitment tool, a mailbox, recruiters' phones. You tell us which is the source of truth for clients and which for candidates. We take a copy and look for duplicates, missing consent and records without an owner. What exists afterwards is a count of what is clean and what is not, before anything is moved.

  2. 2

    Draw the path of one requirement on paper

    With the lead recruiter we trace a single requirement from the client's email to the joining: who receives it, who allocates it, where profiles are sent, how feedback is logged. We note each point where information is lost, such as a profile sent from a personal mailbox. The owner agrees the stages a requirement should pass through, and the stages a candidate should pass through, as separate lists that the tool will later copy.

  3. 3

    Decide the fields for clients, requirements and candidates

    A client record, a requirement record and a candidate record need their own fields. We propose them and your recruiters strike out what they will never fill. The owner decides who sees client rates and candidate expected pay. Consent gets a field with a date. The result is a record layout everyone has seen before any tool is configured.

  4. 4

    Build in a test copy and load sample records

    We set up the stages and fields in a test copy, load a small set of real records after removing sensitive details, and check that a requirement links to its candidates and its client. Recruiters try it with last month's work. You decide what to change before the real data is loaded.

  5. 5

    Clean and import the live records

    Duplicates are merged under the owner's rule about which record wins. Candidates without consent are flagged and not messaged. We import clients, then requirements, then candidates, and check a sample by hand against the old sheet. Anything we are unsure of is left aside for the recruiter who knows.

  6. 6

    Read the pipeline against the old tracker

    After the desk has used the system, we compare requirements open, profiles submitted and joinings with the counts recorded from the old sheet. We also check how many records carry a consent date and an owner. You decide which stages to rename and who keeps the record clean. No gain is promised and only the figures decide.

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.

Do we need a recruitment tool or a general CRM?
Either can work if it handles requirements, candidates, consent and submissions. Test it with your last ten requirements. If you must work around it, it is the wrong tool.
How long should candidate data be kept?
Set a retention rule, tell candidates what it is and delete on request. Rules on personal data change, so check the current position with your own legal adviser.
Who should have access to client rates?
Only the people who need them. Restrict the rate fields by role, and keep the candidate's pay expectations separate from the client's budget.
Should candidates be deleted when a role closes?
No, keep them while their consent stands. A candidate who was not right for one role may suit the next, and the consent field shows whether you may still call. Review old records against the retention rule your firm has set.
Can we keep using our spreadsheets while the system is built?
Yes, and you should until the cut-over day. The desk keeps working in the sheets, and we copy the data at the end so nothing is lost. We ask recruiters to note changes made after the copy, and we repeat the import for those rows just before the switch. After the switch the sheets become read-only. Running two live systems for long invites differences, so the owner names the day the old sheets close and tells the desk beforehand.
Who looks after the system once you leave?
A person in your firm must, and we name that person before the build begins. They add users, correct fields and remove duplicates. GullySales hands over a short guide in plain language, covering stages, consent and the duplicate rule, and the person is trained on a test record. If nobody can take this on, tell us at the start, because a system with no owner decays into the sheets it replaced. We can discuss support separately if you want it.
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.
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.
What if we are not happy with the work?
Tell us and the plan changes. Everything is reported against the baseline, so a number that is not moving is visible to both sides. The term is in your written scope, and the refund and cancellation policy sets out the rest.

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.