Skip to content
GullySales

IT staffing and contract hiring firms · Follow up systems

Chase the feedback, the offer and the joining, not just the requirement.

A follow-up system for an IT staffing firm is the routine that gets interview feedback from the client, keeps candidates warm through an offer and confirms the joining. GullySales works on the steps, the owners and the record.

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 follow up systems means

A follow-up system is the set routine for calling, messaging or emailing an enquiry more than once, since most buyers do not decide on the first conversation. GullySales sets the number and timing of follow-ups so an undecided buyer keeps hearing from you until they decide either way.

Last updated 14 Nov 2026.

For IT staffing and contract hiring firms

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

  • “Feedback is the slowest part”

    A hiring manager interviews and goes quiet. A candidate waiting for news starts to talk to other firms. A prompt, polite request to the manager is the firm's job.

  • “Candidates need updates even when there is none”

    A short message to say the client has not replied is better than silence. It keeps the candidate in the process.

  • “Offer to joining is where roles are lost”

    Between acceptance and the first day, a counter-offer or a doubt can appear. Contact in that gap is what keeps the joining on track.

  • “Existing clients need a check after the joining”

    A call to the manager after a month asking how the engineer is doing finds problems early and starts the next requirement.

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 feedback chase for each interview

    A message to the hiring manager after each interview, with the next reminder date logged.

    Result: Candidates are not left waiting without a reason.

  2. Candidate update messages

    Short templates for no news, a rejection, an offer and a joining, sent by the recruiter in their own words.

    Result: Candidates hear from you at every step.

  3. A joining tracker

    From acceptance to day one, with notice period, documents and check-ins logged.

    Result: Drop-outs are visible before the date.

  4. A post-joining check-in with the client

    A call to the hiring manager after the engineer starts, with notes on fit and the next role.

    Result: Problems are found while they can be fixed.

  5. A review of stalled requirements

    A list of requirements with no movement, discussed with the owner of each.

    Result: Stalled roles get a decision.

How the result is measured

  • Follow-up completion rate
  • Average number of follow-ups before close
  • Enquiries closed after repeat follow-up

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

What to capture or send

The moments between submission and joining that each need a next step.

Profile submitted, no reply
Message the hiring manager with a one-line question on whether the profile fits. Record the reply and who sent it.
Interview done, feedback awaited
Ask for feedback as soon as the interview ends, and tell the candidate what you asked. Record the date requested.
Offer released
Call the candidate and note their reaction, their notice period and any counter-offer. Share the note with the account owner.
Notice period running
Keep in touch with the candidate and record anything that changes the joining date or the candidate's mind.
After the engineer joins
Ask the hiring manager how the engineer is settling in, and record what they say for the next requirement.

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 recruiters carry too many open roles to contact each candidate, and a chase routine would turn into a list nobody works.
  • The client assigns no single person to give feedback, so a chase would only reach people who cannot decide.

Before you decide

Agree the work. Know how to judge it.

Follow-up systems for IT staffing firms: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

Trace recent enquiries from arrival to the last recorded action. Include a won enquiry, an unsuitable one, and one that went quiet, with personal details removed for the initial discussion.

Make the scope clear

Agree who accepts each enquiry, what makes it qualified, and how ownership changes. Include a rule for missed replies and a clear reason for closing an enquiry.

Check the work in use

Pick an enquiry at random and ask the team to find its owner, latest conversation, and next action. Check that the record agrees with what actually happened.

Know when to change course

If no one has capacity to respond, assign that responsibility before buying more leads. Automation can support the owner, but it cannot replace an unresolved handover.

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.

The current interview tracker, even if untidy
Bring the sheet or tool in which interviews and feedback are noted, along with any recruiter's private version. It tells us how much is already recorded and by whom, and which clients are missing from it. If each recruiter has their own, collect them into one folder. A tracker with gaps is the reason for the work, so it need not be neat.
A list of clients and their feedback habits
Ask the account leads to mark which clients reply to feedback requests, which need a nudge and which never do, and who inside the client is the right person to ask. We use this to set the chase rule. If the knowledge is only in people's heads, a short meeting is enough to put it down, and we write it in the record.
Two or three declined-offer cases
Recall a few candidates who accepted and then declined or withdrew, with the reason and the stage at which it happened. They show where the checklist needs a step, for example a delayed offer letter or a counter-offer from the current employer. Names are not needed; the story and the stage are enough for us to work from.
The owner's rule on counter-offers
Decide what the firm does when a candidate's employer counters. Some firms warn candidates early, others do not discuss it. We write the message to match your stand, so it must exist before drafting.
A named person for each stage
Someone must own feedback chasing, someone the offer stage, someone the joining check. If the desk is small, one person may hold several, but each stage still needs a name against it. Without owners the routine is a list nobody follows, and the stalled requirements stay stalled while each recruiter assumes another is on it.

How it works

How the follow up systems 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

    Open the interview and offer records

    We start with where interview dates, client feedback, offers and joining dates are written today, whether a sheet, a tool or a recruiter's notebook, and we look for the gaps. Your recruiters tell us which clients reply and which never do. We count how many submissions have no recorded feedback. What exists afterwards is a list of points where a candidate or a client is left waiting, each with the recruiter who held it.

  2. 2

    Decide when a silent client counts as closed

    The owner and account lead decide what happens when a client gives no feedback: when to ring, when to ask their manager, when to treat the profile as rejected and tell the candidate. We write the rule per type of client. It is a decision about people and relationships, so it is made before any message is drafted.

  3. 3

    Draft the candidate update messages

    We write short messages a recruiter sends after an interview, while waiting, on rejection, on offer and before joining. Each is plain and truthful, including the message that says there is no news. Recruiters change the wording to sound like themselves, and the owner approves the final set.

  4. 4

    Write the offer to joining checklist

    With the recruiter who has handled counter-offers, we list what to confirm between acceptance and the first day: notice served, documents ready, the date in writing, contact with the joining manager. The checklist becomes tasks on a joining tracker, each with an owner and a date field.

  5. 5

    Run the routine on live requirements

    We apply the tasks to current requirements and watch what the desk does with them over the first requirements handled. Recruiters tell us which tasks are useless and which are missing, for instance a call to the joining manager the day before the start. We adjust, then hand the tracker to the team lead. You decide who reviews stalled requirements and how they are handled.

  6. 6

    Compare stalled and lost roles with the starting count

    We compare the number of submissions without feedback, offers that did not become joinings and requirements with no activity against the counts taken before the routine began. The owner decides which tasks to keep and which clients need a different approach. No improvement is promised, and each figure is read next to its cause.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 2, qualification. The audit comes before it, and sales management keeps it running.

  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 · you are here

    Sales process design

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

    Start here if every salesperson sells differently.

  3. Step 3

    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.

How do we handle a client who never gives feedback?
Ask for it in the agreement and in each submission note, and log every chase. If silence continues, tell the hiring manager how it affects the candidate's other offers.
Should we tell candidates when a client rejects them?
Yes, plainly and soon after you know, with whatever the client has said that is useful. A clear no helps the candidate move on and keeps their trust.
What if a candidate accepts and then declines?
Record the reason, tell the client promptly and offer the next best profile. The reason is worth studying, because it shows where the process failed.
How should we handle a counter-offer after acceptance?
Ask about it before the offer is made. A candidate who has told their manager may already be wavering, so your screening call should cover it. Keep a short note of the candidate's reasons, and let the client know early if the joining looks doubtful.
How much should a recruiter message a waiting candidate?
As much as is true and no more. A candidate who hears nothing assumes the worst, but a message with nothing to say is noise. We write a plain note for the stage, including one that says the client has not replied and the recruiter has asked, and we let the recruiter decide when to send it. If a candidate asks for news, they get an answer the same day, even if the answer is that there is none. The owner approves the wording so recruiters do not promise outcomes.
Can the system chase clients automatically?
It can remind your recruiter, but the chase itself should be a person writing or ringing. An automatic message to a hiring manager reads like a vendor machine and may harm a relationship that took years. We set tasks with dates so a chase is not forgotten, and write a few phrases the recruiter can adapt. Automation suits internal reminders and candidate acknowledgements, with the candidate's consent. Where a client has a vendor portal, feedback is also entered there.
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.
What do you need from us?
Your brief, and a conversation. After that, access to whatever this work touches, such as your website, your accounts or your enquiry record, and time with the people who handle your enquiries.

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.