# Business Analyst vs Project Manager: Which Comes First?

> Business analyst vs project manager: what each role owns at a Shopify agency, which gap shows up first, and how to cover both before a full-time hire.

_Published: 2026-10-12 · CommerceCopilot_

## The short answer

In the business analyst vs project manager question, the split is simple: a business analyst decides what to build, a project manager keeps already-decided work moving. The BA runs requirements gathering, resolves ambiguity, and turns a client's ask into scoped tickets a developer can build from. The PM sequences those tickets, tracks progress, and flags blockers before they cost days. At most Shopify agencies, the business analyst gap opens first, because every project starts with a brief that has to become scope, and no amount of sequencing can rescue work that was scoped wrong.

That ordering is the useful part of the comparison. Plenty of articles define the two roles; few answer the question an agency founder is actually asking, which is "we can afford one of these functions right now, so which one?"

## Business analyst vs project manager: what each role owns

The two roles sit at different points in the same pipeline, and the handoff between them is exactly where the confusion starts.

### The business analyst: deciding what to build

A business analyst owns everything between "the client said a thing" and "a developer can start." That means running discovery and requirements gathering, asking the follow-up questions the client didn't think to answer, documenting what's confirmed versus assumed, and writing the result as [tickets with acceptance criteria](/blog/how-to-write-development-tickets) rather than a narrative summary. On a Shopify project, it also means knowing enough about the platform to scope realistically: whether that loyalty feature is a metafield pattern or a custom app, whether the checkout ask is even possible on the client's plan.

The BA's output is a backlog that's actually buildable. If you want the longer treatment of the role, including the signs an agency has outgrown doing this informally, we cover it in [does your Shopify agency need a business analyst](/blog/business-analyst-digital-agency).

### The project manager: keeping decided work moving

A project manager picks up where the BA stops. Given a scoped backlog, the PM decides what gets built first based on dependencies, tracks progress across workstreams, notices when a ticket has sat untouched past its expected window, and keeps handoffs clean: development to QA, QA to client review. The PM also owns the calendar reality of a project, which tickets have to ship before others can be tested, and where the risk is concentrated.

What a PM cannot do is fix bad scope. A project manager handed an ambiguous backlog can only sequence the ambiguity. We go deeper on what this function looks like, and what the AI version of it does differently, in [what is AI project management for a Shopify agency](/blog/what-is-ai-project-management-shopify-agencies).

## Why agencies blur the two roles

At most small and mid-size Shopify agencies, nobody holds either title. One person, usually the founder or a senior producer called "the PM," does both jobs: they sit in the sales calls, translate the brief into tasks, then chase those tasks to done. That works at one or two concurrent projects. Past that, the two jobs start competing for the same hours, and the failure modes get misattributed.

The misattribution matters because the two gaps produce different symptoms, and agencies routinely treat one as the other. A project that feels "constantly blocked" looks like a project management problem. But if the blockers are mostly unanswered questions ("what should happen for logged-out customers?", "which markets does this apply to?"), those are scoping failures surfacing late. Hiring a PM, or buying PM software, does nothing for that project except document the stalls more neatly.

## Which gap shows up first, and how to tell them apart

Run your last three projects through this split.

Signs the gap is on the business analyst side:

- Tickets come back from developers with "actually, what did the client mean by..." questions that should have been settled before the quote went out.
- Change requests are mostly clarifications in disguise: the client isn't changing their mind, they're answering a question nobody asked in week one.
- A senior developer spends real hours translating client emails and call notes into buildable tasks, at senior developer rates.

Signs the gap is on the project manager side:

- Scope is solid, but blockers get discovered at the weekly status meeting instead of the day they appeared.
- Work stalls at handoffs: a build sits finished for days before QA knows it's ready, or QA findings sit unread.
- Nobody re-sequences the backlog when a dependency shifts, so developers pick tickets in whatever order they notice them.

Most agencies that honestly run this exercise find the first list more familiar. That's not surprising: scoping failures happen on every project, because every project starts unscoped, while coordination failures only compound once there are enough parallel workstreams to coordinate. It's why the practical answer to "which role first" is usually the business analyst, even though PM tooling is the thing agencies buy first.

The exception is real: an agency running mostly retainers made of small, well-understood tasks (swap this section, fix that app conflict, monthly theme updates) has trivial scoping and heavy coordination. If that's your book of business, the PM gap genuinely comes first.

## What each hire costs

If the answer is a full-time hire, the salary data is worth having before you budget. Across current US figures from Built In, Salary.com, and other salary aggregators, average business analyst salaries cluster between roughly $84,000 and $111,000 a year. For project managers, ZipRecruiter puts the US average at about $102,700, with the middle half of roles between roughly $78,500 and $123,000, and Glassdoor's average sits near $104,000.

So the two roles cost about the same, and neither bills hours directly. For an agency running four to six concurrent projects, carrying one of these salaries is defensible when it frees up enough senior time; carrying both rarely is. That's the real constraint behind the "which first" question: most agencies at this size can justify at most one non-billable delivery role, and many can't justify a full-time version of either.

## Covering both functions without two salaries

This is the gap CommerceCopilot is built for, and it starts on the business analyst side because that's where projects start. The Business Analyst agent listens where requirements actually form (client calls, connected Slack channels, meeting notes), maintains a living model of what's confirmed, what's assumed, and what's still open, and raises questions instead of guessing. Once discovery findings are accepted, it writes them up as sequenced, dev-ready tickets with acceptance criteria.

The Project Manager agent then picks up exactly where a human PM would: it sequences that backlog by dependency, tracks progress across every active project, and flags blockers the day they appear rather than at the next check-in, working inside the tracker your team already uses through the [Jira](/docs/jira) or [Notion](/docs/notion) integration. Because the same system runs both functions, the handoff between them, the exact place where single-person agencies drop context, doesn't depend on anyone's memory. The [getting started guide](/docs/getting-started) walks through the full pipeline from brief or discovery to a sequenced project workspace.

Neither agent replaces the judgment a senior human applies to messy client relationships or unusual constraints. What they replace is the version of both roles that most agencies actually have today: one overloaded person doing each job in the gaps around their real one.

## FAQ

### Is a business analyst the same as a project manager?

No. The business analyst decides what to build: requirements, ambiguity resolution, scope written as buildable tickets. The project manager keeps decided work moving: sequencing, progress tracking, blocker detection. They're adjacent stages of one pipeline, not interchangeable titles, even though small agencies often staff both with one person.

### Which should a Shopify agency hire first?

Usually the business analyst function, because scoping failures appear on every project while coordination failures only compound at higher project counts. The exception is retainer-heavy agencies with small, well-understood tasks, where scope is trivial and coordination across many clients is the actual bottleneck.

### Can one person do both jobs?

At one or two concurrent projects, yes, and most agencies run that way. The problem isn't capability, it's hours: both jobs peak at the same moments (project kickoff, mid-build scope changes), so the same person ends up doing one job well and the other one late. That's the point where agencies either hire or put tooling under one of the two functions.

---
Canonical page: https://www.commercecopilot.ai/fr/blog/business-analyst-vs-project-manager-shopify-agency