Why We Built TalentDesk
Most consulting firm operations live in a tangle of spreadsheets, Slack threads, and email chains. This is the story of how a missed placement red flag turned into a structured operations tool for the full talent lifecycle.
The client called on a Thursday afternoon. Their words were measured but the message was clear: the engineer we had placed three months ago wasn't working out. Communication issues, missed deadlines, a general sense that something wasn't aligned. We had no early warning. No weekly signal. No structured feedback from the engineer's side either. The first we heard was when the client was already at the decision point.
What made it worse was that the data existed. Account Managers had spoken to both sides. Notes lived in different places — a Slack message here, an email thread there, a cell in a shared spreadsheet that nobody had updated in six weeks. The information that would have told us something was wrong was there; it just wasn't organised anywhere we could act on it.
The spreadsheet problem
Consulting and staffing firms run on relationships, and relationship data is notoriously hard to structure. You have clients with multiple open positions, each at a different hiring stage. You have engineers — some deployed, some on bench, some mid-transition. You have feedback flowing in both directions: clients telling you how the placement is going, engineers telling you whether they feel stretched, supported, and like they're growing. And you have a constant operational backdrop: onboarding checklists, background checks, contract dates, and the bureaucratic tail of every placement ending.
Most firms manage all of this in Excel or Google Sheets, with some combination of email and Slack stitching the gaps. It works until it doesn't. It breaks when:
- Two account managers are working the same client and neither knows what the other logged
- A placement's weekly health signal hasn't been updated in three weeks and nobody flagged it
- An engineer was placed without a technical screening being completed, but the process doc said one was required
- You're trying to answer "who on bench has Node.js and more than 4 years of experience" and the answer is buried in a cell somewhere
What we actually needed
We didn't need a CRM. We didn't need an ATS. We needed something that understood the specific shape of a consulting firm's operation — the triangular relationship between a firm, its client, and its deployed engineer, and the feedback loops that keep that triangle healthy.
Specifically, we needed:
- A single source of truth for every client and every open position, with a structured hiring pipeline that anyone on the team could read in 30 seconds
- A quality gate that made placement standards non-optional — not a process document, but a checklist that physically prevented deputation until it was cleared
- A structured feedback loop from the engineer's side: not annual reviews but regular, lightweight 1-on-1s with consistent structure so you could track trends over time
- A weekly signal from the account manager's side: a color-coded health check per placement that forced someone to say, every week, whether things were green, amber, or red
- An action center that surfaced everything overdue — incomplete gates, missed health updates, hiring deadlines — so nothing fell through the gaps between roles
What we built
TalentDesk is a Next.js 14 application with a SQLite backend, built to be self-hosted by small and mid-sized consulting and staffing firms. It is not a general-purpose HR tool. Every module is specific to the consulting firm context: clients have hiring needs with skill requirements and target dates; engineers have talent profiles with pulse-score timelines; deployments track the assignment of an engineer to a client with a manager, dates, and allocation percentage.
The Placement Quality Gate is one of the features we're most deliberate about. Before any engineer can be marked Deputed, four checkboxes must be ticked: pre-screen completed, technical bar passed, background check cleared, client alignment confirmed. Clearing all four automatically transitions the engineer's status. It's a small thing, but it makes the standard enforceable rather than aspirational.
The Weekly Engagement Health Signal is the other one. Every active placement has a weekly update slot — Green, Amber, or Red — with a free-text note. The Action Center flags any placement that hasn't had a health update in the past seven days. This is the mechanism that would have caught the problem that prompted us to build TalentDesk in the first place.
We built TalentDesk because we'd seen what happens when the feedback loops break. If you run a consulting or staffing operation and your client relationship data lives in a spreadsheet, this is for you.