How we work: four stages, and you know what you get from each
We start by understanding how the business works, and only then choose tools and build. At every stage you know what is happening, what you’ll get at the end, and what we need from you.
15 minutes. You talk, we mostly ask questions.
Four stages, from the first call to a system that runs
Each one ends with something concrete in your hands.
An intro call, then we map the process. Lots of questions, including ones nobody has asked you yet.
You walk away withProcess map
We write down what we’ll build, in which tool, how long it will take and what it will cost. Before we build anything.
You walk away withA specification document and a fixed quote
We build in stages and test every scenario before your customers run into it.
You walk away withA working system
We train your team and provide a warranty period after go-live. After that, you can keep us on for support and maintenance.
You walk away withTraining, documentation and a warranty period
After stage one: a process map
This is what it looks like: what triggers each step, what happens when the answer is no, and where a person steps in. This is a sample map.
After stage two: a specification and a fixed quote
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 is with you at each stage
You are not passed to a junior team after the intro call.
- Intro call15 minutes, with one of the partners.
- SpecificationMichael leads every specification, from the side of information systems and technology. Eran joins from the side of product, marketing and user experience. Shir joins at this stage too, to learn the project.
- Build and testingThe team that specified is the team that builds. Shir manages the project and makes sure things happen on time.
- After go-liveTeam training, documentation and a warranty period. After it you can continue with our support and maintenance.
What we need from you
- One person who decidesSomeone on your side who knows the process and can approve decisions.
- Access to what existsThe systems, the files and the people who do the work.
- Time for reviewsEvery stage is handed to you for review. Quick feedback saves late fixes.
What stays with you at the end
- The system itself, in your accounts.
- The specification document and the technical documentation.
- Training for the team, and recordings of it.
- A warranty period after go-live, and after it optional support and maintenance.
Frequently asked questions
We start by understanding how the business works, and from there we choose tools and build. The stages are an intro call, specification, build and testing, and support with a warranty period. At each stage it is clear what you get and what we expect from you.
After you approve the specification and the quote in writing. We do not start building before we agree on the process, the scope of work and what counts as done.
You get a working system, documentation of every process, and training for the team that uses it. We always set everything up under the client’s ownership, so the accounts and access are yours from day one.
There is a warranty period after go-live, during which we handle fixes. After it you can choose to continue with our support and maintenance services.
It depends on the scope. A focused automation takes less time than a broad system. You get an exact schedule in writing after the specification.
Want to start with the first stage?
A 15-minute intro call. You talk, we mostly ask questions.



