Skip to main content
GullySystem
Professional services

Business solutions for Recruitment agencies

Explore software for work such as “IT and software talent search”. Review each business function below, including when it fits and what to check before implementation.

Recruitment agencies

How the business operates.

The fee is earned on joining day. It is kept only if the candidate is still at the desk when the replacement window closes. Most agencies watch the first half of that closely and the second half not at all.

Mandate and job description register

Hold each client requirement with its fee terms, replacement clause, number of positions and the recruiter it belongs to, so nobody works a mandate that closed last week.

Candidate pipeline

Move candidates through sourced, screened, submitted, interviewed, offered and joined, with a duplicate check running at submission.

Résumé database and search

Upload résumés and search by skill, role, location and notice period, so an old profile surfaces when a new role fits it.

Interview line-up and feedback

Hold the slot, the round and the panel for each candidate, with pending feedback listed by client so somebody chases it.

Offer and joining tracker

Record the offer, the joining date and the documents collected, with the notice period followed through to joining day.

Placement billing and replacements

Raise the invoice on the trigger agreed with the client, and run the replacement clock from every joining date until it closes.

Recruiter reports and targets

Pull the day’s screening calls, submissions and interviews out of the pipeline, and show each recruiter against target.

Client submission log

The account manager sees what a client has not yet answered. Silent shortlists are chased.

Reference and background checks

Referee names, calls made and replies received are recorded for each shortlisted candidate. The recruiter sees which checks are pending before the offer goes out. Reports stay attached.

Candidate consent and data requests

Consent to hold a résumé, the date given and any request to delete are recorded per candidate. The compliance lead sees records past their retention date. A removed profile leaves a dated note.

The records that hold the operation together.

  • Client records and fee terms. Keep each client company, its hiring contacts, the fee basis agreed, payment days and the replacement window on one record.
  • Mandates and job orders. Record every requirement with the job description, seat count, location, salary band, priority and closing date against the client who raised it.
  • Candidate database. Hold candidate profiles with their CVs, current role, notice period, expectation, skills and every mandate the person was considered for. Recruiters look a candidate up by skill, role, location or notice period.
  • CV sourcing and intake. Add CVs from mail, portal downloads, referrals and walk-ins, catch duplicates on phone or mail, and tag each one to a mandate.
  • Screening and shortlists. Record screening calls, availability and expectation, rate a candidate against the mandate, and build the shortlist the client will receive.
  • Client submissions. Send shortlisted profiles with a submission date, keep the client reply on each profile, and block a repeat send of the same candidate.
  • Interview scheduling and feedback. Book rounds with the client panel, confirm slots with candidates, and write the verdict and the reason behind every round.
  • Offers and joining. Record the offer, the joining date, documents collected and whether the candidate reported, with notice period followed through to joining.

Operational bottlenecks to check

The same résumé goes twice

Two recruiters submit one candidate to the same client, and the client notices before either of them does. Your credibility takes the hit.

Client feedback never comes back

Candidates sit after the first or second round with nobody chasing the panel. A good profile goes cold. The mandate stays open.

Offers end in a backout

The candidate’s notice period stretches, a counter-offer lands, and nobody calls until the morning the candidate does not turn up. The client is left waiting.

Replacement windows are not counted

A placement leaves in the seventh week, the client asks for the replacement you had forgotten you owed, and the fee turns into a credit note.

Report writing eats every evening

Recruiters copy calls and submissions into a sheet instead of making one more call. That is lost selling time, every day.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Mandate taken

    A client sends a requirement. The role, seat count, location, salary band, fee basis and closing date are recorded against that client company.

  2. 2. Sourcing

    Recruiters pull CVs from the database, portals, referrals and walk-ins. Every CV attaches to a candidate record. Tagging then links it to the mandate it answers.

  3. 3. Screening

    The recruiter calls the candidate and notes current role, notice period and expectation. A rating against the mandate decides who enters the shortlist.

  4. 4. Submission and interview

    Shortlisted profiles go to the client with a submission date. Rounds are booked with the panel, and each verdict is written on the candidate’s row.

  5. 5. Offer and joining

    The offer, the joining date and the documents collected are recorded. Notice period and the day the candidate reports are followed until joining is confirmed.

  6. 6. Invoice and replacement window

    The fee is invoiced on the trigger agreed with that client. The replacement clock starts at joining, and collection follow-up sits with accounts.

Roles and responsibility boundaries.

For agency owners

See open mandates, the pipeline at every stage, closures made, invoices raised and dues outstanding across each recruiter and client.

For recruiters

Work your own mandates: CVs to source, screening calls due, submissions awaiting a client reply, interviews today and offers pending joining.

For team leads and account managers

Read the mandates for your clients, who is working each one, what has been submitted, and where client feedback has stalled.

For accounts

Read closures ready to invoice, invoices raised, part payments received, ageing dues and credits arising from replacement cases.

Reports your managers need.

  • Open mandates by client, recruiter and age
  • Pipeline count at sourced, screened, submitted, interviewed and offered
  • Closures made, offers declined and backouts before joining
  • Candidate sources that end in a placement
  • Invoices raised, collected and outstanding by client
  • Replacement cases and free replacements given
  • Recruiter targets against submissions and closures

Connections to scope

  • WhatsApp
  • SMS and email
  • Mailbox pickup for CV attachments
  • Calendar for interview slots
  • Job portal CV import
  • Payment links and gateways
  • Accounting software export on request

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Your mandate types and fee basis

Permanent, contract and search mandates go in with the fee basis, the payment trigger and the replacement window each client has agreed.

Your pipeline stage names

Stages follow what recruiters already say on the floor, whether that is sourced, screened, submitted, interviewed and offered, or fewer steps than those.

Candidates and clients migrated

CV folders, client lists and past closures come across from your sheets and mail boxes, and recruiters review the loaded records before go-live.

Submission and message formats

The profile summary a client receives, and the reminders a candidate gets, follow your present formats in English or the local language.

Hosting and later changes

GullySystem runs the hosting, so recruiters at home and in the office read one candidate list. Edits to stages and formats are done by GullySystem staff.

Limitations to settle before implementation

  • A lone recruiter closing two or three mandates a month manages with a spreadsheet and a mail folder.
  • An HR team hiring only for its own company is better served by Employee Records and Self Service Software.
  • Labour-supply firms whose main work is site attendance and wages for deployed labour need a payroll-led system instead.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • IT and software talent search
  • Sales and business development hiring
  • Senior leadership and executive search
  • Bulk hiring for factory and warehouse roles
  • Contract and temporary staffing
  • Campus and fresher hiring
  • Healthcare and clinical staffing
  • Retail and hospitality staffing
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements