Photo: Google Gemini · AI-generated
New to this topic? Start here
Terms used in this piece
- Requirements catalogue
- A numbered list of what the software must do and how well it must do it, written so that someone else can build and test against it.
- Functional requirement
- Something the software must do, such as "a supplier can confirm an order".
- Non-functional requirement
- How well or under which conditions it must do it, such as "works without a network connection" or "hosted on our own servers".
- Integration
- A connection between two systems that exchange data, for example a portal that writes orders back into the ERP.
- Budget range
- A cost estimate given as a band (for example ±40 percent) instead of one number, because early on nobody knows enough for one number.
- Tender
- A formal request to several suppliers to bid for the same described piece of work.
Read first
- Non-functional requirement ↗The clearest short explanation of the difference between what a system does and how well it does it, which is the part most specifications leave out.
- A Second Opinion Before You SignOur earlier piece on reviewing someone else's proposal. This one is about the step before a proposal exists.
A requirements workshop is one day in a meeting room. That day is the least important part of it. What matters is what you hold two weeks later, and whether you could hand it to someone else.
Ours ends with four documents. Below is what each one is for, with two projects we built as examples of what these documents catch.
A process map
A drawing of how the work happens today, step by step, including the parts that live in email and spreadsheets. It is often the first time everyone in the room agrees on what actually happens, because purchasing, the warehouse and finance each describe a slightly different process.
The map is also where the boundaries of the project become visible. Which steps the new software takes over, which stay manual, and which belong to a system that already exists.
A requirements catalogue
A numbered list, in two parts. The functional part says what the software must do. The non-functional part says how well and under which conditions, and in our experience that is the part that decides the architecture.
The construction portal we built for a company with around 500 employees is the clearest example. Subcontractors on site needed current drawings and tasks, and a network connection on a building site cannot be assumed. “Works fully offline and syncs later” is one line in a catalogue. It changed the platform, the data model and the testing. If that line arrives after the first release, much of the app gets built twice.
An integration list
Every system the new software has to exchange data with, in which direction, and who owns each side. It looks like the most boring page in the set. It is often where the money is.
For a manufacturer with 100 to 150 employees, we built a purchasing portal on top of Sage 100. Suppliers confirm orders and report shipments in the portal, and order and delivery data flows back into the ERP. The decision that framed the project is exactly what an integration list records: Sage 100 stays, the portal extends it, and nothing gets typed in twice. A supplier who has not seen that page will quote a different project.
A budget range, and why it is wide
At this stage we give a range of plus or minus 40 percent, with a recommended next step. That sounds imprecise, and it is meant to be. Before anyone has designed anything, a single number is a guess presented as a fact. A range tells you whether the project is the size of a new van or the size of a new building, which is the decision you need to make next.
Why all of it should be yours
Everything in the set belongs to the client and is written so that any supplier can work from it. That includes taking it into a tender, and it includes a tender we lose.
We would rather build it, obviously. But a workshop whose results only make sense if you hire the people who ran it is a sales meeting with a fee attached. The test is simple: if you sent the four documents to a competitor tomorrow, could they quote from them? If not, the workshop did not do its job.
If you have one clearly bounded initiative, such as a portal, an integration or a single process, and nothing written down yet, this is where we would start. Talk to us about it.
Go further
- Technical ConsultingThe Requirements Workshop and the other three fixed-scope packages, with what each one delivers.
- Purchasing Portal case studyThe Sage 100 add-on used as the integration example in this piece.
- Subcontractor Portal case studyThe construction portal whose offline requirement shaped the whole design.
