What you'll get
- 4 copy-ready blocks
- 5 min read
- Part 1: The client criteria
- Part 2: The four signals worth watching daily
- Part 3: Outreach that leads with a person
- Part 4: The two-week rhythm
How to get clients for IT staffing is usually answered with speed: watch the portals, race the CV, undercut the rate. That wins requisitions and never clients, because the relationship starts and ends with one req. This plan builds the other machine: 30 named companies, watched for hiring signals, approached person-first, worked on a two-week rhythm.
Part 1: The client criteria
Build the list from the clients that pay you best today, using the target account list structure:
Stack fit They hire the skills your candidate network is
genuinely deep in. Depth beats breadth: own two
stacks, not nine.
Hiring volume Enough engineering hiring to need help repeatedly:
growing product teams, projects with deadlines,
known attrition. One-off hirers are requisitions,
not clients.
Decision shape Companies where engineering managers influence agency
choice, not just a vendor-locked procurement list.
Rate reality Segments that pay for speed and fit. Knock out the
bodies-by-the-pound buyers early; that race is lost
even when won.
Knock-outs Exclusive rival MSP/RPO in place, pays in 90 days,
burned your candidates before.Thirty accounts, tiered: ten where you want to own the hiring, twenty watched.
Part 2: The four signals worth watching daily
1. The job-ad cluster Three or more similar engineering roles
posted at once: a funded project with a
deadline and an internal team that cannot
fill it alone.
2. The long-running ad The same role reposted or open 60+ days:
pain, and openness to help, whatever the
official agency policy says.
3. The funding or project New money, a big contract win, a digital
programme announced: hiring follows within
a quarter. The full list is the trigger
event list.
4. The leader move A new CTO or engineering director rethinks
suppliers in their first 90 days, and their
old company's agencies rarely follow them.Part 3: Outreach that leads with a person
The staffing cold email that works is the one that arrives carrying value in hand:
Subject: your [role] search
[First name], the [role] opening has been up [n] weeks. One reason
that profile is hard right now: [the honest market reason: niche
skill, salary band, location mix].
We have [two or three] people with exactly that profile, one
available from [date]: [two-line anonymised snapshot of the
strongest].
Want the profile? No terms conversation needed to look.The anonymised snapshot is the whole trick: it proves the network is real before any agreement exists, and engineering managers forward it. The companion set for the sector is the IT services cold email templates; the variant for managers you know is a one-line text with the same snapshot.
Part 4: The two-week rhythm
Daily, 20 min Signal sweep across the 30 accounts: job pages,
LinkedIn, trade press. Date what you find.
Twice weekly One person-first email per live signal, and one
relationship touch on a Tier 1 account that has no
signal: a market note, a salary data point, a
candidate trend their manager would care about.
Fortnightly Review the list: signals worked, replies, meetings,
reqs won. Rotate out accounts silent for a quarter.
The question per Tier 1 account: do we know one more
hiring manager there than two weeks ago?Worked example (illustrative, not a real company)
A 15-person staffing firm deep in data engineering builds its 30-account list around two stacks. The daily sweep catches a cluster signal: Harbourline Foods posts four data roles in one week after announcing a supply-chain programme. The email to their engineering manager names the hardest of the four profiles, the honest market reason it is hard and a two-line snapshot of a candidate available in three weeks. The manager asks for the profile the same day, the candidate interviews that week, and the terms conversation happens after the value is visible. Two placements later, the firm is on the preferred list the portal racers are still trying to join. All names are invented.
Five mistakes to avoid
- Living on the portals. The posted requisition is the most expensive place to compete: maximum rivals, minimum relationship, procurement rates. The signals in Part 2 arrive before the portal does.
- Claiming every stack. "We do all IT roles" reads as "we search LinkedIn when you call". Owning two stacks makes the snapshot email possible, and the snapshot email is the plan.
- Leading with terms. Agreements before value is the sequence buyers hate. Lead with a real profile; the terms conversation goes better when they want the person in it.
- Treating a placement as the finish. The placement is the entry. The fortnightly question (one more hiring manager known than before?) is how a req becomes a client.
- Spraying candidates at cold companies. The snapshot only lands when the role, the pain and the profile genuinely match, which takes the research the list exists to focus. A wrong-fit CV blast is remembered longer than silence.
Why this works on named accounts
Common questions
How do IT staffing companies find clients?
The durable way: a named list of 30 companies that hire your stacks repeatedly, watched daily for signals (job-ad clusters, long-running roles, funding, leadership moves) and approached with a real anonymised candidate snapshot rather than a terms pitch. Portals and reposted reqs supplement that motion; they cannot be it.
What should a staffing cold email say?
Name their open role, the honest market reason it is hard to fill and a two-line anonymised profile of a genuinely matching candidate, with the offer to share the full profile before any terms conversation. Proof of network beats description of network, every time.
How long does it take to win a staffing client?
A signal-led approach with a real candidate can produce the first requisition inside weeks, because it attaches to live pain. The client relationship (preferred status, repeat reqs, the quiet call before the role is posted) is a two-to-three-quarter build, which is what the fortnightly rhythm and the one-more-manager question are for.
More from the Academy
The Trigger-Event List: When to Approach an Account
For sellers with a good account list and no idea which account to work this week.
You leave with 12 trigger events, where to spot them and who to approach when one lands.
Cold Email Templates for IT Services
For IT services firms selling projects and managed work.
You leave with ten templates built on real openings: trigger events, new leaders, hiring signals, peer proof, partner routes and a break-up that keeps the door open.
Target Account List Template
For founders and sales heads who have chosen their accounts and need one place to work them.
You leave with a 25-row sheet, a rule for how many accounts to keep and a weekly review in five questions.
Want this in your inbox?
Optional. We use your email only to send you this, nothing else.