Do we need this if we already know what we want?

You probably know much of it - and the gaps only show up mid-build, where they are expensive. What feels clear in one head is rarely identical across five. The write-up is how you find out.

Can you write requirements for a tender?

Yes. We write specifications precise enough to compare bids against fairly, and to hold the winner to afterwards.

Who needs to be involved?

The outcome owners and the day-to-day users, in focused sessions. We do the writing in between, so the demand on their time stays small.

Does this lead into a build with you?

It can, but it does not have to. The document is deliberately self-contained, so any competent team can build from it.

Business analysis & requirements gathering

Ask why a project hurt and the answer is usually upstream: nobody pinned down what “done” meant. We sit between the business and the delivery team, draw out what is needed, and write it up so both sides recognise the same scope.

Service details

At a glance

Stakeholder interviews and workshops
Requirements that are specific and testable
Process and data flows mapped
One scope document everyone signs

The expensive part is the part nobody wrote down

Mid-build change requests, arguments about scope, features that technically match the spec but miss the point - nearly all of it traces back to requirements that were vague when everyone signed them. A short analysis phase makes the implicit explicit while it is still cheap to fix.

Translation in both directions

We interview the people who own the outcome and the people who will use the system daily, map the processes and data flows underneath, then turn what we hear into requirements an engineer can build and a tester can verify. Engineering constraints travel the other way, translated into choices the business can make. Nothing is signed off until the people who will live with it have read it.

Interviews and workshops with owners and everyday users
Edge cases and exceptions surfaced early
Acceptance criteria attached to every requirement

A scope that holds

The result is a specification solid enough to estimate against, tender against, or hold a supplier to. It stands alone: bring it back to us for the build or take it anywhere else, and it reads the same.

Frequently asked questions

Do we need this if we already know what we want?: You probably know much of it - and the gaps only show up mid-build, where they are expensive. What feels clear in one head is rarely identical across five. The write-up is how you find out.
Can you write requirements for a tender?: Yes. We write specifications precise enough to compare bids against fairly, and to hold the winner to afterwards.
Who needs to be involved?: The outcome owners and the day-to-day users, in focused sessions. We do the writing in between, so the demand on their time stays small.
Does this lead into a build with you?: It can, but it does not have to. The document is deliberately self-contained, so any competent team can build from it.

Ready to talk through Business analysis & requirements gathering?

Book a free 30-minute consultation with a senior engineer to see how we can help.

Book a consultation

Business analysis & requirements gathering

Service details

At a glance

The expensive part is the part nobody wrote down

Translation in both directions

A scope that holds

Frequently asked questions

Ready to talk through Business analysis & requirements gathering?

Other services

Product discovery & ideation

Strategy & roadmapping

Custom software