Work that runs itself.

Yes, and this is the most common way our projects start. In the 20-minute call you describe your week: the tasks you repeat, the tools you use, where things get copied by hand. We come back with a map of what is worth automating, what is not, and roughly what each piece costs.

That is normal for anything beyond one workflow. You get a custom offer with fixed scope, fixed price and a fixed date. The packages exist as anchors, not as limits.

No. At handover we walk you through it in a short call: what each workflow does, how to pause it, and what to check if something looks wrong. Clients with no technical background run these every day. If you want to learn the internals, add a training session.

Yes, all three, plus OpenRouter, Perplexity and local models via Ollama. We recommend a model based on your task and your budget rather than defaulting to the most expensive one, and we build in cost guardrails so a runaway loop cannot bill you thousands overnight.

Yes, and it is a good chunk of our work. Share the workflow JSON or add us to your instance as a read-only user. We audit it, tell you what is actually broken versus what is only fragile, and quote the fix. If a rebuild is genuinely cheaper than a repair, we tell you that instead.

If it has an API, it can be connected. n8n’s HTTP node plus custom code handles anything with a documented endpoint. If the documentation is bad or missing, we reverse-engineer the calls from the web app. The only genuine dead end is software with no API and no web interface at all.

You do, completely. We build on your n8n instance, cloud or self-hosted, using your credentials, and you get the workflow JSON. Nothing runs on infrastructure we control, so there is no switch we could flip and no subscription to us that keeps your business running.

Every workflow we build has an error path that alerts you in Slack or email with what failed and where, so you find out from the system rather than from a customer. Within your support window we fix genuine build faults free.

Yes. Starter and Agentic include 14 days of bug-fix support, the Automation system 30. Beyond that, a monthly care plan covers monitoring, breakage from third-party API changes and small adjustments: Basic care for simple workflows, AI care for agent workflows and systems, where prompts and models need re-tuning over time.

Anything inside the agreed scope is covered, including revisions. Genuinely new work gets a priced extra before we start it, never a surprise on delivery. If the scope changes enough that the original plan no longer makes sense, we redraw the map together before any more building happens.