Practical AI workflow automation for small businesses
You did not start a company to become a courier between your own apps.
If your week contains moving information between your tools by hand — retyping an enquiry into the CRM, copying orders into accounting, forwarding the same email to three people — that work can run itself. We build n8n workflows that connect the tools you already use, configure AI agents that take over routine steps, and do the integration work that makes your systems agree with each other.
Everything is assembled from templates and components that already run in our own operations, documented in plain language, and handed over to you. Fixed scope, fixed price, quoted without a call. No theatre. Useful systems, explained in human language.
- No calls — A human replies within one business hour.
- Fixed scope, fixed price — A written quote, before any work starts.
- You own it — The workflows, the documentation and the connections.
- Never alone. Hand work back to us anytime, in credits.
What is n8n, and why do we build on it?
n8n is a workflow automation tool. A workflow is a chain of steps: when a new enquiry arrives, log it, classify it, draft a reply, notify the right person. n8n connects the tools those steps happen in — email, calendars, spreadsheets, CRMs, online shops, booking systems, forms, messaging — through ready-made connectors, and we build custom connections where no ready one exists.
n8n can be self-hosted, so your workflows run on infrastructure that we or you control. Hosted automation tools such as Zapier and Make meter their price by the task or the operation; on your own instance the workflows simply run, and the running cost is the server. The workflows themselves are exportable files you own — the same ownership rule we apply to website code.
We also use it ourselves. The enquiries, follow-ups and mechanical steps behind DevPowers are n8n workflows, and nothing becomes a service we sell before it runs in our own operations first.
No proprietary platform. No DevPowers licence fee. No lock-in.
What routine work can be automated?
The work that automates best is work you can describe as a rule: when X happens, do Y. Examples of what we take over:
Where a step reaches your customers, you decide whether it runs on its own or waits for your click. Those approval points are set with you during setup and written into the scope, not left to chance.
Do you need a developer to keep it running?
No. The workflows are built modularly with clear error handling, and they run without you watching them. You receive visual documentation in plain language and a live walkthrough, so you can see what each step does, turn workflows on and off, and make simple adjustments yourself.
Nothing is hidden. You own everything we built, and any competent developer can open, read and modify it. If an external service changes its API and a workflow needs updating, that is ordinary larger work: change credits or a quoted project.
What you receive at handover
- The workflows, running and tested against realistic examples of your data.
- AI agents configured for the routines that need reading and drafting, with the approval points you set.
- Visual documentation in plain language.
- Error handling, and failure notifications to a channel you choose.
- Connections made with your accounts; the credentials live inside your automation setup, and you keep ownership of every account.
- A live walkthrough for you and whoever will work with the automations.
What is included and what is explicitly excluded
Whatever the scope turns out to be, the commercial shape of the work is always the same.
What is included
- Fixed scope, fixed price and a written quote, without a call.
- Workflows assembled from templates and components that already run in our own operations, configured to your tools and your rules.
- Testing against realistic examples of your data before you see anything.
- The full handover: workflows, configured agents, documentation, approval points, failure notifications and a live walkthrough.
What is explicitly excluded
- Voice and chat agents that talk to your customers. That is a separate service: conversational AI voice agents for your website and phone line.
- Your AI subscriptions. If a workflow uses an AI tool, you pay that provider directly. We configure whichever tools you choose, and we are not a reseller of AI tools.
- The subscriptions and running costs of the tools we connect — your CRM, your shop system, the hosting the workflows run on. They are not part of our price.
- Ongoing monitoring and maintenance. There is no retainer, and there are no open-ended automation programmes here. You own documented workflows that keep running on their own.
After handover, the support boundary, stated literally: simple adjustments you make yourself are free. Larger work — new workflows, new integrations, changes to existing automations — and repairs of damage you cause yourself are bought as change credits or quoted as a project. Credit packs cost less as a short subscription than bought one-off, and unused credits expire after two months. If something breaks because of our work, the repair is free and costs no credits.
Flying solo does not mean flying alone.
You can do it yourself - or hand it to us. Both stay open, permanently.
When a change is bigger than a prompt, or the hour is better spent on your own work, hand it to us by email or chat, the same way you reached us during the build. The work is bought as change credits: you receive an estimate in credits before anything starts, and you accept or decline it. Failures caused by DevPowers are repaired free of charge and consume no credits.
Every change is estimated in credits, and you accept or decline the estimate before work starts. Credit pack prices are being set with the first clients and published once they are measured, not guessed.
How the work runs, in writing
Everything important stays in writing.
-
1
You write
Describe the routine in your own words; one email is enough. We send one structured set of questions you answer in a single sitting. We acknowledge your email instantly and a human replies within one business hour.
-
2
Scope and pay
The offer arrives as soon as discovery is complete, with a way to pay attached: deliverables, explicit exclusions, timeline and payment stages, at a fixed price. Work starts when the deposit is paid.
-
3
Built and tested
We assemble from tested templates and reusable components, connect your tools, and test each workflow against realistic examples of your data.
-
4
Handover
You receive the workflows, the documentation and a walkthrough in plain language. You own everything we built.
Payment has three stages: deposit before work, payment on first-draft acceptance, and final payment on handover.
The full written process — how we work and deliver, from discovery to the support boundary — is on the how we work page.
DevPowers is part of Edukey Sp. z o.o., operating since 2010, based in Porto with a presence in Poland, working internationally in English.
Automation FAQ: API keys, failure alerts, privacy, and maintenance
Which tools can you connect?
The ones small businesses actually use: email, calendars, spreadsheets, CRMs, online shops, booking systems, website forms, messaging apps, accounting tools. n8n ships ready connectors for most of these, and we build custom ones where needed. If you are unsure whether your tool is covered, that is a one-line email and the answer comes within one business hour.
Do I need API keys for all my tools?
Where a tool requires an account or a key, the connection is made with your account, and the credentials live inside your automation setup. You keep ownership of every account and can revoke access at any time.
What happens when a workflow fails?
Each workflow is built with error handling: failed steps are retried where retrying makes sense, and when something still fails, you are notified in a channel you choose. The workflows are documented and owned by you, so any competent developer can repair them, including us.
How do you handle data privacy when AI is in the loop?
The workflows run on infrastructure we or you control, and every step is visible in the workflow itself and named in the documentation. Where a step sends data to an external AI service, you decide what it may see, and approval points can hold any outbound message for your review before it is sent. There is no hidden processing.
Can automation be part of a website project?
Yes. Automation can be bundled into a website build or bought as a standalone project — including after launch, as change credits or a quoted project.
What does it cost?
Every engagement is fixed scope and fixed price, quoted in writing without a call. Keep two cost groups apart: our one-time price for building, which is in your offer, and the running costs of the tools themselves — your AI subscription, your CRM, the hosting the workflows run on — which you pay to those providers directly.
Am I left without help after handover?
No. Doing it yourself is the default after handover - it is not a duty. Any change you would rather not make yourself, from a small edit to a new feature, you can hand to DevPowers by email or chat: the option stays open, it is simply not the default. The work is bought as change credits, and you receive an estimate in credits before any work starts; you accept or decline it. Failures caused by DevPowers are repaired free of charge and consume no credits.
What is a change credit?
A change credit is a unit of paid work you buy in advance and spend whenever DevPowers does work on your site. You buy a credit pack; packs cost less as a short subscription than bought one-off. Each change consumes credits by its complexity, not by the time it takes. Credits carry an expiry date and unused credits expire after two months. Credits cover new work and repairs of damage you caused yourself. Failures caused by DevPowers are repaired free of charge and consume no credits. Credit pack prices are being set with the first clients and published once they are measured.
What if I break the site myself?
A change that fails the automated gates cannot reach your live site, and rollback to the previous deployment is always available - most accidents stop before they happen. If you override a stop-and-warn and the site is damaged, DevPowers repairs it and the repair is paid in credits: you receive an estimate first and accept or decline it. Failures caused by DevPowers are repaired free of charge and consume no credits.
What if I just want DevPowers to do it?
Then we do it. Doing it yourself is the default because it is cheaper and faster for you, not because we stop working with you at handover. Send the change by email or chat, you receive an estimate in credits, and you accept or decline before anything starts. Nothing about the handover closes that door.
What about an agent that talks to my customers?
That is a separate service: conversational AI voice agents for your website and phone line — answering questions, booking and triage in real time. This page is the work behind the scenes.
Your move, hero.
Tell us what the site needs to do. We acknowledge your email instantly and answer within one business hour - no call, form or booking calendar.