The timeline above is an illustration of a small automation pilot. Larger builds take longer; you get a schedule with the quote, before anything starts.
How we work
Start small, prove it, then grow
We would rather put one useful thing into daily use than plan a year of work up front. Every project follows the same three stages.
A project, start to finish
- CallFree process analysisYou show us the work as it is done today
- SummaryWritten recommendationWhat to change first, and why
- PPilotOne fixed-scope buildAgreed result, agreed price
- LLaunchIn daily useTested with the people who use it
- CareMonitoring and next steps
The three stages
What happens, in order
- 01
Free process analysis
On a call, you walk us through one process as it runs today. We map each step, who does it and in which tool, and send you a written summary of what we would change first.
- 02
Fixed-scope pilot
We agree what the pilot does, what done means and what it costs before work starts. Then we build it, test it with your team and put it into daily use.
- 03
Care and next steps
We watch the runs, fix what breaks and work through your list of improvements month by month. Each next project is scoped the same way as the first.
Inside a build
From an agreed scope to a system people use
Larger builds, such as a CRM or ERP rollout or custom software, follow the same steps in more detail. You see working software early and often, not a big reveal at the end.
- Discovery and planning: goals, users, data and the scope in writing
- Design: screens and flows you can click through before we build
- Development: short iterations with a demo at the end of each
- Testing: with real data and the people who will use it
- Launch: migration, training and a watched first week
- After launch: monitoring, fixes and improvements under care
Pilot progress
- Scope and access agreedAccounts, sample data, who approvesDone
- First version demoedRunning on your real dataDone
- Tested with the teamEdge cases and error alertsDone
- In daily useDocumentation handed overDone
What each side brings
What you get from us
- A written scope and a fixed price before any work starts
- One contact person who also builds
- A demo at every step, on your own data
- Documentation another team could take over from
- Everything in your accounts and your repository
What we need from you
- One person who knows the process and can decide
- Access to the tools involved, or a test copy of them
- A few real examples: emails, documents, exports
- Feedback on each demo within a few days
- Time for the team to try it before launch
The rules we work by
One process at a time
A finished thing in daily use beats five started ones.
You own it
Accounts, code and documentation are yours from day one.
A person in the loop
Where a mistake would be costly, a person approves.
Agreed data boundaries
We decide together which data may leave your systems.
Questions about working with us
How long does a pilot take?
It depends on the scope, which is why we agree it first. A single automation is a matter of weeks; a CRM or ERP rollout or custom software takes longer. The schedule is part of the quote.
What if the pilot shows the idea does not work?
Then you found out with one small project instead of a large one. We say so plainly and suggest what we would try instead, if anything.
Can we stop after the pilot?
Yes. The pilot is a complete piece of work that runs in your accounts with its documentation. Care and further projects are optional.
Do you work on site?
Most work is remote, with calls and shared screens. For larger rollouts and training we can come to you by agreement.
In which languages do you work?
English and Croatian, for the calls, the documentation and the software itself.
Show us one process. We will show you what it could look like.
The analysis is free, takes about an hour of your time, and ends with a written summary you keep.
Prefer to read first? See examples