Architecture before recruitment: why we will not hire a single engineer before the roadmap is signed.

The usual order, and why it fails

The conventional sequence is: approve a budget, write job descriptions, hire whoever the market offers, and work out the architecture once the team is in the room. It feels fast. It is the slowest possible route, because every decision that should have been made on paper is made instead by whichever engineer arrived first, and remade when they leave.

It also explains the numbers everyone quotes about hiring: six to nine months to fill a senior role, recruiter fees of twenty to thirty percent, and attrition in the first year that resets the clock. A team assembled without a design has no capability slots to recruit to, no acceptance criteria for the first month, and no way to tell a good hire from a lucky one.

What four weeks of architecture produces

The Solution Architecture phase is short by design. A senior Solution Architect, supported by a Cybersecurity Engineer and a DevOps Engineer, spends two to four weeks inside the business and returns with seven documents:

1. A 1–2 year IT roadmap, sequenced by quarter.
2. A team structure with every role, its capability slot and the month it is needed.
3. Architecture decision records for the target architecture and the stack.
4. A milestone plan with acceptance criteria and the KPIs the team will be managed to.
5. A budget model, month by month, locked at sign-off.
6. A risk register with owners and mitigations already scheduled.
7. A security and compliance baseline for the industry's obligations.

Every one of these is an input to recruitment. The capability slot tells the recruiter what to test. The milestone plan tells the new engineer what their first deliverable is. The KPIs tell the manager what to report in week one.

The approval gate

Nothing proceeds to recruitment until the client has approved the roadmap. This is the point most staffing firms skip, because it delays the moment they can start billing for people. We keep it because it is the moment the client's risk drops. After sign-off the budget is fixed, the team shape is fixed and the first ninety days are planned. What remains is execution, and execution is what Recruit · Train · Manage is for.

Why the package stands alone

Because the documents are useful whoever executes them, the Solution Architecture Package is offered as a standalone fixed-fee engagement. Some clients use it to brief their own recruiters. Some use it to hold a vendor to a design. Most, once they have seen the team structure, ask Webist to build it. Either way the architecture came first, and the team that follows is the team the business needed rather than the team the market happened to offer.