Custom build
Workflow automation
Software that does a repeating job on a schedule. Quotes into the CRM, invoices raised, reports sent, follow-ups chased. Written to be idempotent, so a retry after a half-finished run does not raise the invoice twice, which is the failure that makes people stop trusting an automation and go back to doing it by hand. Every run is logged in your portal with its inputs and its result, a failure opens a ticket instead of going quiet, and the job is priced against the hours the audit actually counted. The code is documented and handed over.
Price
On enquiry
How it works
Step 01
Scope comes from the audit, not from a conversation
We build against the hours the Operations audit measured, so the business case exists before the first line of code.
Step 02
It is built and tested against your real cases
Including the awkward ones. Every process has the exception that breaks a naive automation, and finding it in testing is much cheaper than finding it in production.
Step 03
Handover is a session and a runbook
How it works, how to change it, and what to do if it stops, written for somebody who is not us. Without it, nobody but us can change it.
Step 04
Thirty days of post-launch support, then you choose
A month of real use with us watching it. After that you either host it on FourWinds Automation and we keep running it, or you take it in-house with the runbook.
What is included
- Scoped from the audit
- Documented handover
- 30 days post-launch support
Questions
- How is this different from an integration or the bank feed?
- An integration moves data between two systems. This does a job on a schedule, which usually needs one or more integrations underneath it and is quoted with them. The bank feed is a pre-scoped version of exactly this shape, for transactions and receipts, so if that is your job take that one and skip the scoping.
- Is this the same thing as FourWinds Automation?
- They are two halves of one thing. This is the build: the software that does your particular job. FourWinds Automation is what it runs on, and it is where you watch it: the schedule, the log of every run, and the ticket that opens when something fails. You can take the code in-house instead and run it yourself, and then the runbook and the on-call are yours.
- We already had the audit. Can you just build it?
- That is the normal case and the cheaper one. The audit is the scope, so the build starts from a number.
- Who owns the code?
- You do. It is documented and handed over so another developer can pick it up. Hosting it on FourWinds Automation afterwards is a choice, not a condition of the build.
- What happens if it breaks in month four?
- On FourWinds Automation, a failure opens a ticket and is handled under your SLA. If you took it in-house, it is your runbook and your on-call, which is why the runbook is part of the handover.
- How do you arrive at a number?
- Scope varies here more than anywhere else in the catalogue. The audit turns it into a fixed figure before you commit to anything.
Talk to us
Tell us what the work looks like now. We will say whether Workflow automation is the right line for you, and what it would cost.
Send us the detail