A business analyst (BA) turns what a business wants into work a development team can build and test. In a software project that means user stories with acceptance criteria, user flows, a list of rules the product must follow, and a record of every change to scope with its effect on time and cost. Developers write the code. The BA makes sure it is the right code.
Founders who outsource a build often aren’t sure they need one. The work a BA does gets done either way. Without a BA, it falls on the founder, the developers or nobody, and “nobody” is the expensive option.
The International Institute of Business Analysis surveys the profession every year. Its 2025 Global State of Business Analysis report, with responses from more than 2,380 professionals in 171 countries, found the same top three roles as the year before: enabling change by defining needs and recommending solutions (23%), collecting, synthesizing and analyzing information (20%), and evaluating and improving business processes (19%).
Most people in the field see AI as good for their careers so far. In the 2026 report, based on 2,120 professionals in 122 countries, 69% reported a positive impact from AI on their careers, and negative sentiment was 5%.
The need shows up on the developers’ side too. In the Stack Overflow Developer Survey 2026, unclear priorities or requirements was the top answer when 18,214 developers named the factor that most made their job harder in the past six months, at 16.6%. Poor documentation or knowledge sharing was named by 7.1%. Both are what a BA is there to fix.
Everything a good BA does comes back to requirements: finding them, writing them down, keeping them current and checking the product against them.
A BA starts by collecting what the product has to do and why: interviews with you and your users, your current process and data, competitors, rules your industry imposes. Then they turn it into user stories with acceptance criteria that a developer can build and a tester can check.
This matters most where the business rules are hard. On Koncierge, a payment platform for Japan, the hard part was the data: matching each bank deposit in a shared agent account to the right customer and merchant, under strict anti-money-laundering rules. Our team there included a business analyst, and the stories, acceptance criteria and API reference lived in Jira and Confluence.
Here is a common case. A client asks for “a website just like our competitor’s.” A developer needs a spec; the client keeps pointing at the competitor. A closer conversation shows the client doesn’t want the “Compare” button or separate payment and delivery pages at all. “The same website” meant something different to each side.
A BA closes that gap in both directions. They translate your goals into terms the team can build, and they explain technical trade-offs back to you in plain words, so you can decide.
In agile work, documentation is lighter than the long specifications of waterfall projects, but it still exists. A BA usually keeps:
When a stakeholder asks in March why a feature works the way it does, the answer is in writing, not in someone’s memory. Big stories need splitting before a team can plan them; our guide to user story splitting shows how a BA and a product owner do it.
Testers check that the software works. A BA checks that it does what the business needed. That means user acceptance testing: using the product the way a real customer would, confirming every acceptance criterion and spotting where the business logic went wrong. It doesn’t replace QA, which our post on quality assurance vs quality control covers. It catches a different kind of mistake: software that works perfectly and solves the wrong problem.
A BA learns a new domain fast and holds the full picture: the users, the business process, the data, the people building it. That view lets them spot a conflict between two requirements before a developer builds both, or a cheaper way to reach the same goal. On Everytale, an online events platform, eleven of our specialists joined the client’s 25-person core team, and one of them was a business analyst.
Not every project needs a full-time BA.
| Your situation | BA needed? |
|---|---|
| A narrow first version, and you can write and order the stories yourself | Not full-time; a short discovery may be enough |
| Complex business rules: payments, compliance, logistics, roles and permissions | Yes |
| Several stakeholders who disagree about what the product should do | Yes |
| A live product with a long backlog and a dedicated team | Yes, usually as part of the team |
| Integrating with an existing business process or legacy system | Yes |
| A one-person internal tool with a clear owner | No |
If you are the product owner and have the time, you can do much of the BA work yourself; our checklist of product owner responsibilities shows where the two roles split. A one-week discovery up front also does a lot of BA work in one go; see the discovery phase.
In-house, you pay a salary. IIBA’s 2025 report put the salary of business analysis professionals with 11 to 16 years of experience at $94,913, across all the countries surveyed, so local rates vary widely.
From an outside team, you have two options with us. In our dedicated teams, a business analyst is part of the usual set of roles, next to the developers and a Scrum Master, and turns your goals into clear tasks while helping the product owner keep the backlog in order. Through staff augmentation, a business analyst can join your own team at $39-55 an hour, with a $5,000 minimum, starting in 3-5 days or within 2 weeks if we hire someone new.
An estimate is a first pass at business analysis. Our project estimate turns your brief into user stories. You confirm what is in scope, and every hour in the budget traces back to a story you kept. We check the hours the model suggests against what our team actually books on finished projects, then multiply by our published rate of $39-55 an hour.
It’s a planning range, not a fixed quote. It won’t replace a BA on a complex product, but the confirmed stories give a BA, or you, a starting backlog instead of a blank page. You can get a free project estimate in about four minutes.
A business analyst collects and writes the requirements, usually as user stories with acceptance criteria, keeps business rules and flows documented, logs changes with their effect on time and cost, and checks the finished product against what the business needed.
Not always full-time. For a narrow first version where the founder can write and order the stories, a short discovery may be enough. If the product has complex rules, such as payments or compliance, or several stakeholders who disagree, a BA saves rework.
The product owner decides what gets built and in what order and is accountable for the product’s value. The business analyst helps by collecting requirements, writing stories and checking the work, but doesn’t own the priorities.
IIBA’s 2025 survey put the salary of business analysis professionals with 11 to 16 years of experience at $94,913 across all countries surveyed. Through our staff augmentation, a business analyst costs $39-55 an hour, with a $5,000 minimum.
Not according to the people in the role. IIBA’s 2026 survey found that 69% of business analysis professionals reported a positive impact from AI on their careers, and negative sentiment was 5%. The same survey lists AI adoption among the trends the profession is adapting to.
Carefully curated content for resourceful Devs, CTOs, and PMs. No spam.