TechnologyCategory 02 of 10

Software Development Agencies

Definition

A software development agency builds custom applications for companies that do not have, or do not want to grow, an internal engineering team. Clients range from funded startups outsourcing their first product to established businesses replacing spreadsheets and legacy systems with purpose built tools.

10,000 to 20,000
US entities
100 to 250 dollars
US hourly rate
3 to 9 months
Typical build timeline
We estimate 10,000 to 20,000 US entities in this category. Directional estimate, not a census figure.
01

How they make money

Most work is billed time and materials: an hourly or weekly rate per person on the team. US based senior engineers typically bill 100 to 250 dollars per hour through an agency, while firms with offshore delivery teams and US project management commonly blend down to 40 to 90 dollars. Fixed price bids exist but only make sense when the scope is genuinely nailed down; on vague requirements, a fixed price quote just means the padding is hidden.

The typical engagement starts with a paid discovery phase, usually a few weeks, that produces specs, designs, and an estimate. Treat that as a cheap way to test the firm before committing to a six figure build. After launch, most agencies sell a monthly maintenance retainer covering bug fixes, dependency updates, and small features. Budget for it: software that nobody maintains decays, and a common rule of thumb puts annual upkeep at 15 to 25 percent of the original build cost.

02

What good ones have in common

The people in the sales call are the people on the project. Good firms name the actual team, with resumes, before you sign. If seniors sell and juniors deliver, you will find out three sprints in, at your expense.
Code lives in your repository from day one. Your accounts, your source control, your cloud. A firm that keeps the code on its own infrastructure until final payment is building a hostage, not a product.
They push back on your spec. A strong agency cuts scope in the first meeting and proposes a smaller version one. Firms that agree to everything are pricing the work, not thinking about it.
Working software every two weeks. Demos of running features on a schedule, not slide decks about progress. This is the single most reliable early signal of how the whole project will go.
References at your scale and stack. Ask for two clients whose project resembled yours in size and technology, and actually call them. Ask what went wrong and how the firm handled it.
03

Red flags

A fixed price for a vague idea. If they quoted your two paragraph description without a discovery phase, the number is fiction. Either the price balloons through change orders or the product ships hollow.
The agency owns the IP until final payment, or forever. Read the assignment clause. You want full ownership of the code you paid for, transferred as work is delivered, not held as leverage.
No engineers you can talk to. If every conversation routes through an account manager and you never meet a developer, you cannot judge the team, and questions decay into a game of telephone.
A portfolio of logos with no live products. Ask for links to shipped software you can actually use. Screenshots and NDA excuses across the entire portfolio usually mean projects that never launched.
They say yes to every technology. A shop claiming equal depth in mobile, web, embedded, blockchain, and machine learning has depth in none. Good firms name what they do not do.
04

How the category is changing

AI coding assistants have genuinely changed the economics of this category. Boilerplate, tests, and routine features now take a fraction of the hours they did, so well run agencies deliver more per billed week, and buyers increasingly know it. That is compressing prices for commodity builds while raising the premium on the judgment work AI does not do: architecture, integration with messy legacy systems, security, and knowing what not to build. Expect smaller teams on the same scope than you would have seen a few years ago, and be suspicious of any firm still staffing armies of juniors.

The other shift is the collapse of the pure body shop. Buyers burned by offshore teams with no product judgment are consolidating toward firms that take outcome responsibility: fewer people, closer to the business problem, often on retainer as a fractional product team rather than a one time project vendor.

05

Frequently asked questions

How much does it cost to hire a software development agency?
US agencies typically bill 100 to 250 dollars per hour per person; firms with offshore delivery commonly blend down to 40 to 90. A modest custom application usually lands in the tens of thousands, and a serious multi month build runs well into six figures.
Should I hire an agency or my own developers?
An agency wins when you need a product built faster than you can hire, or when software is not your core business. Internal hires win for long lived products that need constant iteration. Many companies use an agency to ship version one, then hire a team to take it over.
How long does a custom software project take?
Most real builds run three to nine months from discovery to launch. A few weeks of discovery, then two week development sprints. Anyone promising a custom system in a month is either reusing an existing product or cutting corners you will pay for later.
Who owns the code the agency writes?
You should, in full, through a written IP assignment. The standard arrangement transfers ownership as work is paid for. Watch for clauses that let the agency reuse your code for other clients or that hold ownership until the final invoice clears.
What happens after the software launches?
Plan on a maintenance retainer for bug fixes, security patches, and small improvements. A common budgeting rule is 15 to 25 percent of the build cost per year. Also insist on documentation and a handover path so a future team can take over without the original agency.
Want the full directory of software development agencies?We are publishing full listings category by category. Leave an email and we will send this one when it goes live. Requests decide what publishes next.
One email per category. No newsletter.

Dev shops live and die on referrals, so they lean on marketing agencies to keep the pipeline warmer than word of mouth alone, and they flex bench size through staffing agencies between big builds.