[{"data":1,"prerenderedAt":214},["ShallowReactive",2],{"blog-article-project-your-recruiter-cant-place":3},{"id":4,"title":5,"body":6,"date":203,"description":204,"extension":205,"image":206,"meta":207,"navigation":208,"path":209,"seo":210,"stem":211,"tags":212,"__hash__":213},"blog/blog/project-your-recruiter-cant-place.md","The Project Your Recruiter Can't Place: Why Complex Builds Are a Revenue Opportunity, Not a Rejection",{"type":7,"value":8,"toc":191},"minimark",[9,13,16,19,22,27,30,33,36,39,43,46,53,59,65,68,72,75,78,81,85,88,91,94,97,100,103,107,110,113,116,119,123,126,129,132,135,138,141,144,147,150,154,157,160,164,167,170,173,176,179],[10,11,12],"p",{},"Your best client just called. Not to hire: to build. They need a team to take over a half-finished platform, architect something from scratch, or deliver an outcome that doesn't decompose into \"find me three React developers.\" You know the brief is real. You know the budget is there. And you know your firm has no clean answer.",[10,14,15],{},"So the conversation dies. Not dramatically: nobody hangs up angry. It just... tapers. \"We'll keep you in mind.\" The client finds a dev shop through someone else's network. That dev shop delivers (or doesn't), and either way, they're now in your client's trust circle. Sitting in the seat you spent three years earning.",[10,17,18],{},"This is not an edge case. If you run a tech recruitment firm in the UK or South Africa, this conversation happened last month. It will happen again next month. And every time it does, you are handing qualified, budgeted demand back to the market: demand that arrived through relationships you built, using trust you earned, generating revenue for someone who did neither.",[10,20,21],{},"The custom software development market is projected to hit $146 billion globally by 2030, growing at over 20% annually. That is not a niche. That is a market category flowing through your client conversations, and flowing straight past your P&L.",[23,24,26],"h2",{"id":25},"the-conversation-you-keep-having-and-keep-losing","The conversation you keep having (and keep losing)",[10,28,29],{},"Every technical recruiter has a version of this story. A client's engineering lead calls to ask if you know anyone who can \"finish a build\" or \"take over a project.\" The recruiter hears the brief, recognises it's not a placement, and faces a choice: over-promise something the firm can't deliver, or say \"that's not really what we do\" and watch the client's mental model of your firm shrink by one category.",[10,31,32],{},"Most recruiters, sensibly, choose honesty. They say no. But honesty has a cost here that nobody tracks.",[10,34,35],{},"The project enquiry doesn't just represent one lost fee. It represents intelligence about the client's technical roadmap. It represents wallet share that your BD team is measured on but can't capture. And it represents the moment a competitor enters the room: not another recruiter, but a delivery firm that will build a relationship with your client's CTO while you're still placing mid-level developers into their existing teams.",[10,37,38],{},"That shift is structural, not cyclical. And it means the volume of \"can you build this?\" conversations arriving in recruitment firms is going up, not down.",[23,40,42],{"id":41},"staff-augmentation-works-until-it-doesnt","Staff augmentation works, until it doesn't",[10,44,45],{},"Recruitment firms are excellent at placing skilled individuals into existing teams, within established architectures, where someone on the client side owns the technical direction. That model works. It's proven. But there's a category of work where it breaks down.",[10,47,48,52],{},[49,50,51],"strong",{},"The project has no existing team to augment."," The client needs to go from zero to a working system. They don't have an architect, a tech lead, or a delivery framework. Placing three developers into a vacuum doesn't produce a product; it produces three people waiting for direction that isn't coming.",[10,54,55,58],{},[49,56,57],{},"The scope requires unified ownership."," When the deliverable is a system, someone needs to own the architecture, the integration points, the deployment pipeline, and the production environment. Staff augmentation distributes responsibility across individuals who each own their function but nobody owns the outcome.",[10,60,61,64],{},[49,62,63],{},"The risk profile doesn't fit the placement model."," A placed developer who underperforms gets replaced. A project that fails architectural review at month four doesn't have an equivalent recovery mechanism. The client isn't buying time; they're buying an outcome.",[10,66,67],{},"79% of IT outsourcing spend is focused on application and software development. That's not staff augmentation; that's project delivery. Recruitment firms sit adjacent to that spend every day. They hear it. They qualify it, informally. And then they let it go.",[23,69,71],{"id":70},"what-the-firm-is-actually-losing","What the firm is actually losing",[10,73,74],{},"A senior developer placement in the UK might generate a fee of �15,000 to �25,000. The same client's project-build requirement (the one the recruiter turned away) might represent a delivery engagement worth �150,000 to �500,000 over six to twelve months. Even a modest referral arrangement on that engagement represents multiples of a single placement fee, generated from a conversation the recruiter was already having.",[10,76,77],{},"Now multiply that by every account director in the firm. Every client relationship where the conversation has drifted toward \"we need something built.\" Every time someone said \"that's not what we do\" and moved on.",[10,79,80],{},"And here's the competitive dimension nobody wants to think about. When your client takes that project enquiry to a dev shop, the dev shop doesn't just deliver the project. They build a relationship with the client's CTO. They learn the client's architecture, their roadmap, their pain points. They become a trusted partner. And trusted delivery partners have a habit of being asked: \"Do you also know any good developers?\" That question is the sound of your placement revenue being flanked.",[23,82,84],{"id":83},"the-improvised-referral-and-why-it-usually-goes-wrong","The improvised referral, and why it usually goes wrong",[10,86,87],{},"Some recruitment firms have tried to address this informally. A recruiter knows a freelance team, or has a contact at a small dev shop, and makes an introduction. The intent is good. The execution is almost always a disaster.",[10,89,90],{},"The problem is structural. The recruiter becomes an informal intermediary in a technical engagement they're not equipped to manage. Requirements get translated through a non-technical layer. Scope disputes land on the recruiter's desk. Timeline slippage becomes the recruiter's problem to communicate. And when the delivery fails (which, without proper discovery and architecture, it frequently does) the recruiter's client relationship absorbs the damage.",[10,92,93],{},"This is the pattern that makes recruitment firm founders reluctant to try again. They've been burned. Not by the concept of referral partnerships, but by the absence of a delivery partner with the process discipline to protect the referral source.",[10,95,96],{},"The failure mode is worth naming explicitly. Most dev shops, when presented with a partially built system and a client who believes \"a few weeks of work\" remain, will quote against the client's timeline estimate. The problem is that the client's timeline estimate is almost always wrong. Not because clients are dishonest, but because assessing remaining work on a codebase you didn't build requires a structured audit that most shops skip in favour of speed-to-quote.",[10,98,99],{},"Six months later, the project is over budget, behind schedule, and the recruiter who made the introduction is fielding calls from an unhappy client who holds them partially responsible. The recruiter didn't scope it, didn't build it, didn't manage it, but their name is on the introduction. Their reputation absorbed the impact.",[10,101,102],{},"So the lesson the firm learns is: don't refer project work. The actual lesson should be: don't refer project work to partners who skip discovery.",[23,104,106],{"id":105},"what-a-clean-referral-motion-actually-looks-like","What a clean referral motion actually looks like",[10,108,109],{},"The mechanics matter here, because the mechanics are exactly what distinguishes a defensible referral partnership from the informal brokering that burned everyone last time.",[10,111,112],{},"A clean model works like this. The recruiter identifies a project-build conversation: a client who needs something delivered, not someone placed. The recruiter makes an introduction to a delivery partner. From that point, the delivery partner owns qualification, scoping, technical assessment, and delivery. The recruiter stays in the client relationship. Referral economics flow back to the firm. The recruiter's operational footprint does not increase.",[10,114,115],{},"Three things have to be true for this to work without damaging the recruiter's reputation.",[10,117,118],{},"First, the delivery partner must qualify honestly: saying yes to everything eventually produces a failure with the recruiter's name on it. Second, the delivery partner must not compete with placement: if they also place developers, the referral creates channel conflict. Third, the delivery partner must make the recruiter look good, which means surfacing uncomfortable truths about project complexity before the client commits budget based on false assumptions.",[23,120,122],{"id":121},"the-project-that-almost-wasnt-referred","The project that almost wasn't referred",[10,124,125],{},"This is where the theory meets something that actually happened.",[10,127,128],{},"A boutique tech recruitment firm had an active placement relationship with a growing product company. The relationship was healthy: regular placements, good communication, the kind of client account that generates steady revenue. Then the client's technical lead called with a different kind of request. A previous dev shop had abandoned a partially built internal platform. The client believed a short sprint of focused work would get it to a shippable state. Could the recruiter help find someone to finish it?",[10,130,131],{},"The recruiter had no delivery capability. The honest answer was no. And saying no meant the client would find a dev shop independently, which meant a new technical partner entering the client relationship. The recruiter was about to lose the conversation entirely.",[10,133,134],{},"Instead, the recruiter made an introduction to Vanrho.",[10,136,137],{},"The client believed the platform was close to completion. Most dev shops, presented with that brief, would have quoted against the client's estimate. Vanrho recommended a Discovery engagement first: a structured codebase audit, architecture assessment, and delivery options analysis before any delivery commitment.",[10,139,140],{},"Vanrho's Discovery phase revealed a fundamental flaw in the data layer: invisible at development scale, catastrophic under production load. The kind of defect that would have surfaced as a critical incident three weeks after launch, with the client's customers in the system and the recruiter's reputation attached to the introduction.",[10,142,143],{},"Vanrho produced a Discovery report with three delivery path options: a full rebuild with an accurate timeline, a patched workaround with documented technical debt, and a hybrid staged approach. The client selected the full rebuild. The engagement was materially larger than the client's original estimate, but it was scoped against reality, not against hope.",[10,145,146],{},"The recruiter's introduction led to a meaningful delivery engagement. Referral economics flowed back to the firm. The client relationship not only survived; it strengthened, because the recruiter had connected them with a partner whose first move was to tell the truth about the project's actual state.",[10,148,149],{},"The intelligence from the project - roadmap signals, upcoming hiring needs, architecture decisions that would drive future team composition - never left the room. It flowed back through the recruiter's relationship, reinforcing their position as the client's trusted advisor.",[23,151,153],{"id":152},"the-revenue-line-hiding-inside-your-existing-client-base","The revenue line hiding inside your existing client base",[10,155,156],{},"Those same client relationships produce project-build demand. Not occasionally, but regularly. Every client who is growing, modernising, integrating systems, or launching new products will eventually need something built. That demand currently has no route through the recruitment firm's commercial model. It arrives, it's acknowledged, it's turned away.",[10,158,159],{},"Vanrho operates as a delivery engine behind the referral. The recruiter makes the introduction. Vanrho qualifies the opportunity within 48 hours, engages directly with the client on technical scope, and delivers against defined outcomes. The recruiter's workflow does not change. Their operational footprint does not increase. Their client relationship is not transferred; it's reinforced by an introduction that made the client's problem smaller instead of larger.",[23,161,163],{"id":162},"the-question-nobody-is-tracking","The question nobody is tracking",[10,165,166],{},"Most recruitment firms measure placement volume, time-to-fill, client retention, fee income per consultant. Nobody measures the project enquiries that arrived and left without being captured. Nobody tracks the revenue that evaporated from conversations the firm was already having.",[10,168,169],{},"Start tracking it. Ask your account directors this week: in the last quarter, how many client conversations included a request that wasn't a placement? How many times did someone ask \"can you build this?\" or \"do you know anyone who could take this over?\" How many of those conversations ended with \"that's not really what we do\"?",[10,171,172],{},"The number will be higher than you expect. And every one of those conversations represents a client who went looking for a delivery partner somewhere else, possibly finding one who is now sitting in the room you used to own alone.",[10,174,175],{},"Whether that demand stays in your commercial orbit or funds someone else's growth comes down to one thing: whether you have a delivery partner to route it to before you close the conversation.",[177,178],"hr",{},[10,180,181],{},[182,183,184,185,190],"em",{},"Vanrho partners with recruitment firms to deliver the project work your clients are already asking for. No channel conflict, no operational overhead. Just a referral partner that makes your introduction land. ",[186,187,189],"a",{"href":188},"/#contact","Start a conversation about how it works",".",{"title":192,"searchDepth":193,"depth":193,"links":194},"",2,[195,196,197,198,199,200,201,202],{"id":25,"depth":193,"text":26},{"id":41,"depth":193,"text":42},{"id":70,"depth":193,"text":71},{"id":83,"depth":193,"text":84},{"id":105,"depth":193,"text":106},{"id":121,"depth":193,"text":122},{"id":152,"depth":193,"text":153},{"id":162,"depth":193,"text":163},"2025-03-22","Tech recruitment firms hear project-build requests every month and turn them away. That demand represents a revenue line hiding inside your existing client base.","md","/images/blog/project-your-recruiter-cant-place.webp",{},true,"/blog/project-your-recruiter-cant-place",{"title":5,"description":204},"blog/project-your-recruiter-cant-place","recruitment, partnerships, enterprise, delivery","m-1zrd3POazh8tCX4k4GIsMDE0VolVQcSuWPk4Tun0A",1776068107548]