Specification: first understand how the business is built. Then build.
In the specification we map how work gets done, ask why it looks that way, and put in writing what needs to be built. The result is one document that any development team can build from.
15 minutes. You talk, we mostly ask questions.
What happens during the specification
Five stages, from a pile of files and messages to one document. The demo runs by itself, and you can move between the stages.
- We collect everythingFiles, screenshots, recordings, and conversations with the people who do the work. Including what looks unimportant.
- We draw the processUsually a process map, a data structure and a customer journey. Some processes need several diagrams of each kind and some need fewer. It depends on the type of process.
- We ask why it is done this wayWe do not copy what exists. Some steps are there only because they have always been done, and those get removed or changed.
- We choose a solutionBy requirements, costs, language support and security. Sometimes it is an off-the-shelf tool, sometimes code, sometimes a mix.
- We define the scopeWhat goes into the first stage, what waits, how long it takes and what it costs. In writing.
- We hand over a documentIt is yours. You can build from it with us, with an in-house team, or with another vendor.
What a typical specification contains
Every specification starts from the project’s goal and objectives, and they set its scope, diagrams, structure and size. These are the chapters of a typical document.
- BackgroundWho is the business, and what are the project’s goal and objectives?
- The process today, as it isHow does the work get done today, and where does it get stuck?
- Functional requirementsWhat must the system do, and what is only nice to have?
- Map of the proposed processHow will the process run after the change?
- Data structure: entities and fieldsWhich information is stored, and how is it linked?
- Customer journey and touchpointsWhat does your customer go through, and on which channel?
- Interfaces and integrationsWhich systems connect, and how?
- Schedule and costHow long does it take, and what does it cost?
Who leads the specification
Michael leads every specification. You are not passed to a junior team after the intro call.
- Michael MaorCo-founder and CTO. Leads every specification, from the side of information systems and technology.
- Eran BraunsteinCo-founder and product lead. Joins from the side of product, marketing and user experience.
How we work with you
- We askYou leave with a process map.
- We specifyYou leave with a specification document and a fixed proposal.
- We build and testYou leave with a working system.
- We supportYou leave with training, documentation and a warranty period.
Frequently asked questions
The specification does more than record what exists. We map the process, ask why it works that way, and simplify where we can. At the end you get a written specification and a fixed quote, before any building starts.
Someone who knows the day-to-day work, not only the view from the top. Useful things to bring: a description of the process, the tools in use, and an example of a lead or an order that goes through by hand today.
A good specification describes the business goal, the process including exceptions, roles and permissions, the systems to connect and the direction information flows, and what goes into the first version and what waits for the next stage. It also says how you know the work is done, with clear acceptance scenarios. Without this document it is hard to compare quotes or measure success.
The intro call is short. The specification takes a few focused conversations with whoever knows the process, so we do not specify by guessing. The build itself happens on our side, with checkpoints for your approval.
Want to know what a specification of your business would look like?
In a 15-minute call we work out the scope and what is worth mapping first.
