Q1 How long does implementation take? ↓
Simple automations usually take one to two weeks. Larger systems take longer, because testing, commissioning and handover matter. You get a written timeline before we start.
Q2 Will automation replace our staff? ↓
No — it replaces the parts of their job they’d gladly hand over. The humans stay; the drudgery goes.
Q3 Do you only do AI and automation? ↓
No. We also build focused software — small workflow tools, secure client portals, registers and dashboards — when off-the-shelf products do not fit. If an existing product will do the job, we will say so.
Q4 What do you mean by a business agent? ↓
An AI agent set up around a role in your business, not a one-task chatbot. It runs inside a harness: the working environment and controls around the AI, not the AI model itself. The harness holds approved company knowledge, memory, skills, tools, schedules and the rule that a person approves anything that leaves. We work with frameworks such as Hermes and OpenClaw, and build on pi when a job needs more engineering. Where a framework lacks a control the job needs, we build and test it. Every assistant starts with business context, everyday conversation and a named owner. Connected systems and action permissions are scoped and tested separately; another conversation topic is not another chargeable job.
Q5 Our systems are old. Is that a problem? ↓
Rarely. We integrate with legacy systems more often than we replace them — and we’ll tell you honestly when replacement is cheaper.
Q6 Do you provide training? ↓
Yes. We train teams online, on request.
Q7 What happens if something breaks? ↓
Every build includes a support period of 30 to 90 days, depending on complexity, set out in the scope before work starts. After that, ongoing care is available if the system needs it.