Requirements · Specs · Process · Acceptance criteria
A business analyst who turns vague ideas into buildable specs.
A senior e-commerce business analyst who sits between you and the developers — capturing what the business actually needs and translating it into clear requirements, process maps, and acceptance criteria. Retainers from 0.25 FTE.
Sound familiar?
You explain it twice. They build it wrong anyway.
The problem usually isn't the developers — it's that nobody turned the idea into a clear, complete, agreed specification before work started.
spec:missing Features built from a Slack message
Requirements live in chat threads and your head. Developers fill the gaps with guesses — and guess wrong.
rework:constant Endless rework
"That's not what I meant" after it's already built. You pay twice — once to build it, once to fix it.
edge:unhandled Edge cases hit production
Refunds, partial shipments, tax corner cases — nobody thought them through, so customers find them first.
process:unmapped Nobody knows how it actually works
Your order, fulfilment, and returns processes live in tribal knowledge. New tools and people can't plug in cleanly.
integration:unclear Integrations underspecified
ERP, PIM, CRM connections start before the data mapping is agreed — and stall halfway through.
estimate:unreliable Estimates you can't trust
Without clear scope, every estimate is a finger in the air — and every project runs over.
What they own
The bridge between business intent and working software.
An embedded e-commerce BA who makes sure what gets built is what the business actually needs.
Requirements & user stories
Turns goals and ideas into clear, prioritized requirements with acceptance criteria developers can build against.
- Stakeholder interviews & workshops
- User stories with acceptance criteria
- Prioritized, testable backlog
- Definition of done
Process & flow mapping
Documents how your store actually operates — order, fulfilment, returns — so you can improve and automate it.
- As-is / to-be process maps
- Order, fulfilment & returns flows
- Bottleneck & automation analysis
- Edge-case & exception handling
Data & integration specs
Defines exactly what flows between systems before development starts, so integrations don't stall mid-build.
- ERP / PIM / CRM data mapping
- Field-level specifications
- API & sync requirements
- Migration data rules
UAT & acceptance
Defines and runs the tests that confirm what was built matches what was agreed — before it reaches customers.
- Test scenarios & UAT scripts
- Acceptance sign-off
- Defect triage & clarification
- Release readiness checks
How it works
From fuzzy idea to buildable spec in four steps.
Intro call
We learn your business, systems, and the projects where requirements keep slipping. You meet your BA.
45 min · freeDiscovery
The BA interviews stakeholders, maps current processes, and identifies the biggest clarity gaps.
3–5 daysSpec & cadence
We agree the FTE level and a working cadence, and the BA delivers the first specs developers can build from.
1 workshopThey take ownership
Your BA owns requirements end to end — fewer surprises, less rework, estimates you can trust.
ongoingPricing
Simple hourly rates. Retainers from 0.25 FTE.
Start with as little as a quarter of a full-time BA and scale in 0.25 FTE steps. No project minimums, no hidden management fees.
| Role | Hourly rate | Est. monthly (0.25 FTE) |
|---|---|---|
| Business AnalystRequirements, specs & process mapping | €45 / hour | €1,800 |
| Senior Business AnalystComplex flows, integrations & data | €60 / hour | €2,400 |
| Lead BA / Solution AnalystCross-system design & stakeholder alignment | €75 / hour | €3,000 |
Monthly estimates assume 1 FTE = 160 h/month. Capacity scales in 0.25 FTE steps. Billing is hourly against actual tracked time.
Why trust us
Analysts who know e-commerce, not just BPMN.
Our analysts have specified real e-commerce systems — checkout, fulfilment, ERP and marketplace integrations. They know the edge cases that trip up generic analysts, because they've shipped through them before.
Start here
Get a free 45-minute intro call.
Tell us about the project that keeps getting built wrong. You'll leave with a clear view of what tighter requirements would change.