Software analysis and specification
A specification is a document a team can build from without guessing: it describes processes, features, screens and scope. You get material you can use to compare quotes or brief another supplier. It is ready in 1—2 weeks.
- Typical first deliverable
- a specification and user stories another team could build from
- Delivery
- 1—2 weeks
- Entry price
- from €800
- Stack
- Wireframy · BPMN · Jira
What you get
Process analysis
A map of how things really run, including exceptions. In BPMN where useful.
Functional and technical specification
What the system should do, for whom and with which connections.
Wireframes and user stories
Screens and requirements in a form that can be built directly.
Scope and risk estimate
An estimate before the first line of code, with the uncertainties named.
When you need it
- You have supplier quotes that cannot be compared.
- The project is running and the scope keeps changing.
- You want to know the price before signing a contract.
- You are taking over a system from another supplier and documentation is missing.
When you do not need it
- A small site or one automation. A call and a fixed quote are enough.
- Nobody in the company has time to talk about how the process works.
What is included
- Process analysis of how things actually run
- Functional and technical specification, wireframes, user stories
- A document you could take to a supplier other than us
- An estimate of scope and risk before the first line of code
How it works
- Interviews
We talk to the people who do the process and those who decide about it.
- Mapping
We write down the current state, exceptions and where people wait or errors appear.
- Specification
We prepare features, screens and user stories and go through them with you.
- Estimate and handover
You get the document and an estimate of scope and risks.
How much analysis costs
Analysis and specification start from €800 excluding VAT. The price depends on the number of processes and roles to map. For a larger system we start with one area and you decide whether to continue based on the result.
Frequently asked questions
Do we then have to build with you?
No. You get a specification that another team can work from. It is material for briefing any supplier.
What is in a specification?
Processes, functional requirements, wireframes, user stories and an estimate of scope and risks. We fit the exact content to the size of the project.
Why not go straight to development?
On a small project that makes sense. On a larger system a change on paper is cheaper than a change in finished code.
Related
- Process automationSystems hand data to each other — no retyping
- Websites and e-commerceOne measurable goal, a fast site, a clear CTA
- Custom applicationsInternal systems and portals from prototype to production
- AI solutionsDocuments, enquiries, classification — with error checking
- QA and test automationCritical flows tested before every deployment
- Excel replacement for business: when to build a custom appBlog