“We just need an extra set of hands.” The work is piling up: a system that needs connecting, a report that takes a day to build, a website that needs fixing. Nobody on the team has time for it, and the obvious answer, hiring a developer, feels like a big step.
There are three common ways to get this kind of work done. They sound similar but ask very different things of you. This guide explains each one, and in particular who ends up managing the work.
Three ways to get development work done
- Staff augmentation. You bring in developers from an outside company to work alongside your team, usually for a set period.
- A fractional or managed team. You get part of an experienced team’s time, and that team manages the work and delivers the result.
- Hiring in-house. You recruit and employ your own developer.
The biggest difference between them isn’t the price. It’s who directs the work, makes the technical decisions and answers for the result. For a broader comparison that also covers working with individual contractors and traditional agencies, see comparing the ways of getting technical work done.
What staff augmentation means for your team
Staff augmentation means borrowing developers. An outside company supplies people with the skills you ask for, and they join your team for weeks or months.
It works well when you already have someone senior to lead them: a technical manager who sets priorities, reviews the code and makes the decisions. In that case, extra hands are exactly what you need.
It works less well when you don’t. The developers are yours to direct. Someone has to tell them what to build, answer their questions, check their work and decide what happens when something goes wrong. If that someone is the owner, the “extra hands” can quickly become extra work.
To be fair to it: augmentation can be quick to start, and it lets a strong technical team grow for a busy period without permanent hires. It’s the right tool when the leadership is already in place.
What a fractional developer arrangement looks like
A fractional or managed arrangement starts from the problem rather than from people. You describe what the business needs, in plain English. The team works out what has to be built, assigns the right people, makes the technical decisions and delivers the finished work.
With Agapi, that means:
- Agapi’s own senior engineers do the work. Not borrowed staff, and not a different set of people every month.
- We manage them. Priorities, reviews, technical decisions and quality are our job, not yours.
- You set the goal and the priorities. You decide what matters to the business. We decide how to deliver it.
- One consistent point of contact keeps you up to date and answers your questions.
- You own everything we build.
The amount of work can grow or shrink month to month. A quiet quarter doesn’t leave you paying for an idle hire, and a busy one doesn’t mean a recruitment drive.
Hiring in-house: what it takes beyond the salary
A full-time developer in the US typically earns around $100,000 to $140,000 a year in base salary. Benefits and payroll taxes usually add another 25 to 35 percent. A recruitment agency typically charges 15 to 25 percent of the first year’s salary, or you spend weeks of your own time finding someone. Add equipment and software, and one in-house developer realistically costs $150,000 or more a year. Our developer cost calculator works out the figure for your own numbers.
Then there’s everything that isn’t money: getting them up to speed, directing their work, reviewing it, and keeping them busy when the work comes in bursts. One developer is also one set of skills, and the person who’s great at websites may not be right for moving your data or connecting your systems.
Hiring is the right choice when you have years of steady, full-time development work ahead and someone senior to lead it.
Getting the work done without managing developers
Most owners who search for an extra set of hands aren’t really looking for people. They’re looking for finished work: the system connected, the report automated, the website fixed. They don’t want to become a technical manager to get it.
That’s the gap a managed team fills. Here’s how it works with us, step by step, as set out in how it works:
- A free 30-minute call. You describe the problem in plain English. No obligation and no technical specification.
- A written scope and price. What will be delivered, the timeline and the cost. The price is agreed in writing before any work starts.
- The work gets done. Our engineers build it, test it with your real information, and walk your team through it in plain English.
- You come back when something new comes up. The team is already up to speed, so there’s no re-explaining.
Picking the option that fits the work
A few questions usually settle it:
- Do you have a senior technical person who can direct developers? If yes, staff augmentation may be all you need. If no, a managed team is the safer route.
- Is the work steady and full-time for years ahead? If yes, hiring may make sense. If it comes in bursts, a fractional arrangement fits better.
- Do you need different skills for different jobs? A team covers more ground than one hire.
- How much of your own time can you give to managing the work? Be honest. It’s usually less than you think.
To be honest about the limits of our own model: if software is your core product, or you need a developer in the building every day, an in-house team will usually serve you better. We’ll say so on the first call.
The short version
Staff augmentation gives you extra developers to manage. Hiring gives you an employee to recruit, pay and manage. A fractional or managed team gives you finished work, with the developers managed for you.
If you’re not sure which fits, book a free 30-minute call. We’ll talk it through in plain English and tell you honestly what we’d do in your position.