Single roles, filled properly
Back-end, front-end, full-stack, mobile, QA (manual and automation), DevOps or UI/UX. One seat is a normal order. We would rather fill one role well than talk you into three because a bigger contract is easier for us to staff.
They work in your tools, not ours
Your Jira or Linear, your GitHub, GitLab or Bitbucket, your Slack, your branching model, your pull-request template, your definition of done. Nothing about the way your team already works has to change to accommodate the engineer you are adding.
Onboarding onto a codebase nobody documented
The first fortnight is deliberately small tickets and a lot of reading. Every question the engineer has to ask gets written down and turned into onboarding notes that stay with you — so the next person you hire, ours or yours, starts faster than this one did.
Your lead reviews the work, and there is no PM fee
Priorities, code review and performance feedback stay with your technical lead, because splitting them across two managers is how augmented engineers quietly end up idle. You are not billed for a project manager you did not ask for. If you would rather someone else ran delivery, that is the dedicated-team model instead.
Per-person access, revoked the same day
Named accounts, least privilege, and a written access list agreed before day one covering repositories, cloud consoles, production data and devices. The offboarding steps are agreed at the same time, so removing access is a checklist rather than a scramble.
Seats that flex with the reason you added them
Cover a parental leave, backfill a resignation while you recruit, add a pair of hands for a release crunch, or bring in DevOps for the length of a migration. Add or drop on the notice period in your contract. Nothing auto-renews and nothing is bundled.