FAQ
The things people usually ask
If your question is not here, just ask — we usually reply the same day.
14
Getting started
What is the first meeting like, and does it cost anything?
The first session is free and runs about 45 minutes. There is no sales deck; we ask about your business and end by telling you honestly whether automation makes sense for you right now. Sometimes our answer is that it is too early.
We are a small business — is it too soon for us?
Not necessarily. For smaller teams we usually start with a small, low-cost slice that proves its value immediately. What is genuinely too soon is buying heavy systems before the process is clear.
What do we need to prepare for the first meeting?
Nothing in particular. Process diagrams or reports help if you have them, but most organisations do not, and that is fine.
Process and timing
How long does a project usually take?
Process analysis takes one to three weeks, and a first delivery phase usually three to eight. We prefer several short phases that each produce something usable over one large six-month project.
How much of our team’s time does this take?
The heaviest demand is during analysis: a few short sessions with the people doing the work. During delivery, a weekly meeting and access to one person for questions is usually enough.
What if our needs change mid-project?
That is normal, and it is why we work in phases. At the end of each phase we revisit priorities; changing scope between phases costs very little.
Technical
Do we have to replace our current tools?
Usually not. We prefer to keep what your team knows and what already works, and to build bridges between systems. Replacing a tool is only proposed when it is genuinely in the way.
Where is our data stored?
We decide during design where data lives and what must never leave your organisation. If you have specific constraints, the architecture is built around them.
What if something breaks after handover?
Every flow has logs, an error path and alerting, so failures do not stay silent. There is also a support period after handover, and your team gets the troubleshooting documentation.
Do we own the code and the system?
Yes. Flows, documentation and configuration are built in your own accounts and handed over in full. The aim is that you do not depend on us.
Working together
How is pricing structured?
By the scope of each phase, not hourly. After the analysis stage we give a defined scope and price for phase one. If a project is unclear to us, we do not quote it — we clear up the ambiguity first.
Do you work remotely or on site?
Most of the work is remote. Process analysis gives better results in person when that is possible, because seeing the real working environment reveals things an online session does not.
Academy
Who are the courses for?
The foundations course is for people starting out, the assistants course for those who know the basics, and the systems workshop for managers who will not build but must evaluate.
Do the courses require programming experience?
Not for the foundations course or the managers’ workshop. For the AI assistants course, basic programming familiarity helps considerably.
Still have a question?
Still have a question?
A few short questions so we know the subject before the call. The first session is free and runs about 45 minutes.