BA consulting & specs

BA consulting and technical specification for your team or vendor

Developers can't start without clear requirements — and burn your budget on questions and rework. We deliver a complete documentation package any team can work from, and you can compare vendor estimates on the same scope.

See examples
from $500
requirements package for a small project
1–3 wks
to a finished spec
0
rework from misunderstandings

01

Who needs a BA and a spec

If between your idea and the code there's a team that doesn't see your business from inside — someone has to translate.

01

You have your own dev team

They write great code, but the question "how should the discount work?" eats weeks. You need requirements, not guesses.

02

You're choosing a vendor

Without a spec, estimates from three studios differ threefold because each understood the task its own way.

03

A startup before MVP

You need to define the minimum scope that tests the hypothesis and not build the unnecessary.

04

The project is stuck

Development drags for months, the result doesn't match expectations, and no one can say what "done" means.

05

You need an integration between systems

Two teams or two vendors must agree on a data format — you need an API contract.

06

A mobile app

From concept to MVP: screens, scenarios, roles, backend — all described before the designer opens Figma.

02

What the requirements package includes

Artefacts we deliver. Scope depends on the project — for small tasks the first three are enough.

1

Interviews and process map

Stakeholder conversations, AS-IS process, pains, goals, constraints, glossary.

2

User Stories with acceptance criteria

Each feature as a user story with clear "done" conditions, priorities and complexity estimate.

3

BPMN diagrams

TO-BE processes in BPMN notation: roles, steps, decisions, exceptions — clear to business and developers alike.

4

Wireframes and prototype

Screen layouts and a clickable Figma prototype to validate logic before development.

5

Data model

Entities, relationships, references, statuses — the basis for the database schema.

6

API contracts

Endpoints, request and response formats, error codes — for frontend, backend and integrations.

7

Non-functional requirements

Roles and access, security, performance, languages, devices, backups, logging.

8

Development plan and MVP

Breakdown into stages, what goes into the first release, effort estimate, risks.

Don't see your process?

Describe how it works today — we'll propose a module around your logic.

03

Delivered projects

Live systems our clients use every day. Company names are anonymised by agreement.

✓ MVP ready
BA consulting2025

Mobile app — from concept to MVP

Complete BA documentation package for a startup: User Stories, BPMN, wireframes, API contracts, 28-block roadmap.

28-block roadmap0 launch delaysDemo + MVP covered
Read more1 month
System development2026

TMS platform for a freight company

Built a dispatch platform from scratch: weekly board, billing workflow with PDF invoices, payroll module, ApexCharts dashboard, cross-dock management and PRO# autofill.

20 modules4 RBAC roles0 Excel files
Read more5 months
$ npm run build✓ 78 products → 52 pages
Document automation2026

Medical equipment catalog as code — Markdown to PDF

A designer-made PDF catalog of a medical equipment distributor turned into a code build: one product = one Markdown file, the full 52-page PDF is generated with a single command — no layout designer needed.

78 products52 A4 pages1 build command
Read more1 week

04

How we work on a spec

  1. 01

    Kick-off and stakeholders

    1 day

    We identify decision makers, users, budget and time constraints.

  2. 02

    Interviews and analysis

    2–4 days

    A series of conversations with the team, review of current tools, documents, data.

  3. 03

    Processes and data model

    2–3 days

    BPMN TO-BE, entities, statuses, roles. First review with you — we catch inaccuracies early.

  4. 04

    User Stories and wireframes

    3–7 days

    We write stories with acceptance criteria, draw screens, assemble the prototype.

  5. 05

    API and non-functional requirements

    1–3 days

    Contracts for integrations, security, performance, infrastructure.

  6. 06

    Handover and support

    1–2 days

    We present to the team and answer developers' questions during the first sprints.

05

Pricing for your task

Pricing

from $500

A spec for a small module or integration — from $500. A full package for a system or mobile app with a prototype — $1,500–4,000. The spec cost is credited if we do the development.

What's included

  • Stakeholder and user interviews
  • BPMN processes and data model
  • User Stories with Acceptance Criteria and priorities
  • Wireframes or a clickable Figma prototype
  • API contracts and non-functional requirements
  • Stage plan and MVP with effort estimate
  • Team support at the start of development

What affects the final price

  • Number of roles and user scenarios
  • Prototype depth: layouts or clickable Figma
  • Number of integrations and API contracts
  • Stakeholder availability for interviews
  • Need to join the team's sprints after handover

06

What we work with

We pick the stack for the task and your team, not the other way round. Code and data are fully yours.

BPMN 2.0User StoriesAcceptance CriteriaFigmaMiroOpenAPI / SwaggerER diagramsJiraNotionConfluence

07

Frequently asked questions

Yes, it's a separate service. You get the documentation package and are free to give it to any team. If we later do the development — the spec cost is credited.

Deeper dive

Why a business needs a business analyst and what a good spec is

Why projects without requirements cost three times more

Every unresolved "how should it work?" is either a pause or a developer's assumption. Assumptions turn into rework, rework into missed deadlines and budget. A business analyst removes those assumptions before start.

What a good spec contains

Processes (BPMN), roles, entities and their statuses, features as User Stories with acceptance criteria, screens (wireframes), integrations (API contracts), non-functional requirements and a stage plan. Such a document is equally clear to the owner, designer and developer.

User Stories and Acceptance Criteria

"As a manager, I want to see overdue deals on the dashboard so I can react in time." Criteria: overdue counts from the next-step date; the list sorts by age; a click opens the deal. Now the developer knows what to build and the tester what to check.

BA + developer in one team

Our difference: the person writing requirements can implement them. So the spec contains nothing impossible and estimates are realistic. And if you order development from us too — there's no "lost in translation" between document and code.

When a spec isn't needed

For small tasks of a few days a short description and a mock-up are enough. We'll say honestly if your task doesn't need a full package and propose a lighter format.

08

Other services

Let's translate your task into developers' language

Describe what you want to build and who will build it — we'll propose the package composition, timeline and price.

Telegram ↗
Contact

Let's discuss your project

Describe the task — we'll respond within 24 hours