Method
How we work
The detail of how we work: what happens in the diagnostic, what we need from your team, how often we meet and what happens when the project ends.
The two weeks of the diagnostic
Before building or automating anything, two weeks to understand your operation. This is what happens in each one and what you receive.
Diagnostic
-
Week 1 · Watching how the work is done
- We talk to the people who do the work, not only to whoever runs it.
- We review the tools, spreadsheets and systems they use today.
- We note what is done by hand and which system does not talk to which.
-
Week 2 · Deciding what goes first
- We look at where lost time really costs you money.
- We choose what is worth building or automating first.
- We put together the proposal with scope, timeline and price.
-
What you receive
- A map of your processes: what is done by hand and where time is lost.
- A recommendation of what to solve first.
- A proposal with a defined scope, timeline and price.
- All of it is yours even if you decide not to continue with us. If you continue, the cost of the diagnostic is deducted from the project.
What we need from your team
Your team does not need to know technology. We do need three things from you.
Your team
-
A responsible person
- Someone who knows the process and can decide for the team when a choice has to be made.
-
Access
- To the people who do the work and to the tools, spreadsheets and data they use today.
-
Time to weigh in
- To see each increment and say what works and what does not. Without that feedback in time, the project drifts.
Meetings and demos
You do not wait three months to see something working.
Progress
-
Every one or two weeks
- We show you what already works, not slides.
- You try it, weigh in and we adjust course in the next cycle.
-
The first delivery
- In Build, the first working delivery arrives in about 6 weeks.
- In Flow, the first automation reaches production in 3 to 6 weeks.
-
Between one demo and the next
- If something blocks progress or a priority changes, we tell you as soon as it appears, without waiting for the next demo.
If the scope changes
Course changes are normal: you learn while you build. What must not happen is a change you did not know about.
Changes
-
How we handle it
- We record the change and what prompted it.
- We tell you what effect it has on the timeline and the price.
- It is agreed in writing before it is done.
- If it does not fit now, it is noted for a later cycle.
-
What does not change
- Nothing is added to the project without your approval.
- The agreed price does not go up for work you were not consulted on.
After the handoff
The project ends when your team can run it. That does not mean we disappear.
Afterwards
-
What stays with you
- All the code and the documentation.
- A handoff session with your team.
-
If you need help
- We stay available, but never as a mandatory dependency.
- If you want us to keep supporting you, or to add the next piece, it is agreed separately.
Should we start with a diagnostic?
Two weeks to know exactly what to build or automate first.