Workflow automation · Custom systems · AI-assisted processes
You shouldn’t be
the connection.
Most repetitive work exists because information has to travel between systems that were never introduced to each other — so a person carries it. We build the workflow that carries it instead: emails, documents, spreadsheets, databases and APIs joined into one process that runs, checks itself, and asks for a decision only when a decision is needed.
- Accounts inbox
- PDF attachment
- Shared drive
- 01Read the inboxtrigger
- 02Open the attachmentauto
- 03Extract supplier, number, amountAI
- 04Match supplier recordrule
- 05Check against purchase orderrule
- Approve for paymenthuman
- 07Post to the ledgerauto
- 08Archive and notifyauto
Illustrative workflow — the shape of a build, not a client engagement.
The premise
Automation is not
about connecting two apps.
Real processes cross a dozen systems and a few people. What makes them worth automating is simpler than the tooling suggests: information is being moved, checked or re-entered by hand, repeatedly, in a shape that barely changes.
Where that is true, the process can usually be automated, partly automated or meaningfully shortened. Which of those applies is a question about the process, not about enthusiasm for automation.
Worth a look when someone keeps
- copying
- checking
- sorting
- sending
- downloading
- uploading
- reconciling
- notifying
- chasing
- re-entering
- filing
- re-formatting
Not everything can be automated, and not everything should be. Judgement, relationships and craft are the reason people are still in the process — the point is to stop spending them on moving information.
Solutions
What can be
automated.
Eight groups of work where automation reliably pays for itself. Most engagements touch two or three of them, because the process does not stop at a department boundary.
Business Operations
The internal rituals a team runs on: things being approved, chased, updated and reported on.
- Approval and sign-off routing
- Task creation triggered by an event
- Status updates pushed between systems
- Recurring reporting packs
- Data moved between tools that do not talk
- Operational alerts when something changes
- Document handling, filing and retrieval
- Checklists that complete themselves as work is done
Small task, large shadow
Eight handoffs.
One decision.
Automation does not always replace the person. It removes the unnecessary steps around the person.
- An attachment arrives in someone’s inbox.
- It is downloaded and renamed by hand.
- Three figures are copied into a spreadsheet.
- A colleague is emailed the file.
- The CRM record is updated manually.
- A reminder is created in a calendar.
- The same figures are checked again the next day.
- A month later, nobody is certain which version is current.
- The workflow collects the file and reads the figures.Pickup, extraction and validation — the file is never touched by hand.
- Every system that needs the information is updated.The spreadsheet, the CRM, and a record of what changed and when.
- One step stays with a person: the decision that needs one.Everything around that decision has already been done.
The column on the left does not disappear because the work stopped existing. It disappears because the workflow carries it.
Human in the loop
Automation that asks
before it acts.
Some steps carry consequence: money leaves, a document becomes official, a customer hears something. Those steps stop and wait for a person — then carry on by themselves.
If nobody approves, the workflow waits, reminds or escalates. It does not decide on someone’s behalf.
Decisions worth keeping
- Payment approval
- Sending an important email
- Publishing a report
- Approving a generated document
- Reviewing an exception
- Escalating a customer
Where an approval can reach someone
- Slack or Teams
- An approval link
- A review screen in an internal dashboard
An approval is a message with a clear yes or no, not a login to another system.
Examples
Five workflows,
end to end.
Illustrative builds. These show the shapes of systems we can put together — they are not descriptions of existing clients. Pick one to follow it from the first trigger to the last notification.
Invoice intake
An invoice arrives by email and reaches the ledger already coded, checked and approved.
- Invoice arrives by emailTriggered by a message to the accounts inbox, or a file landing in a shared folder.
- Attachment detected and opened
- Details extractedSupplier, invoice number, date, amount, currency and line items.
- Supplier and purchase order checkedThe invoice is matched against the record and the approved order.
- Coding applied from your rules
- Record created or matched in the accounting system
- Approval requested from the responsible personhumanBy WhatsApp, email or an approval link. Approve, amend or reject with a reason.
- Approved invoice posted and archived
- Anything that does not match goes to an exception queueWith the reason attached, so it can be resolved rather than guessed at.
- Accounts inbox
- Shared drive
- Accounting software
- WhatsApp or email
Where a person decidesStep 07 — nothing is posted until a person approves it.
What changesReading, matching, coding and filing stop being manual. Finance spends its time on the exceptions and the decisions.
Integrations
Connect what you
already use.
Nothing here requires replacing your systems. Most workflows connect tools you already pay for, through access they already provide.
How a connection is made
- A documented API
- A webhook the system already sends
- Direct database access
- A scheduled import or export file
- A shared folder
- A spreadsheet used as the interface
- A purpose-built connector
Older or in-house software with no API is often still automatable: a database, an export file, a watched folder or an email address is frequently enough to work with.
Email & messaging
- Gmail
- Outlook
- Microsoft 365
- Slack
- Microsoft Teams
- WhatsApp Business
Documents & files
- Google Drive
- OneDrive
- SharePoint
- Dropbox
- Word
- Excel
Data & databases
- Google Sheets
- Airtable
- Notion
- PostgreSQL
- MySQL
- Supabase
- CSV
Business systems
- HubSpot
- Salesforce
- Shopify
- Stripe
- Xero
- QuickBooks
- Zoho Books
Development & cloud
- REST APIs
- Webhooks
- AWS
- Google Cloud
- Azure
- Scheduled jobs
- SFTP
These are realistic connection targets, not certified partnerships, and the route for each one is confirmed during scoping before anything is built. There is no “500+ integrations” badge on this site — you only pay to connect what the workflow actually needs.
Custom builds
The workflow
decides the tools.
Off-the-shelf automation platforms are genuinely useful — right up to the point where a process stops being ordinary. When that happens we build the missing part, wherever in the process it belongs.
Sometimes that means a small script and a scheduled job. Sometimes it means a database, an interface for staff, and an AI model doing the parts that rules cannot describe.
What that means in practice
- You are not buying a platform licence. You are buying a process that works.
- If a drag-and-drop tool genuinely solves it, we will say so and use it.
- Anything we build is documented and handed over — not held hostage.
What a build can be made of
- Custom software
- Python services and scripts
- API integrations
- Serverless functions
- Databases and data models
- AI models and APIs
- Scheduled jobs and queues
- Webhook endpoints
- Workflow automation platforms
- Internal dashboards
- Custom interfaces for staff
- Automated document generation
Chosen to fit the process — not to fit a product.
How we work
Six steps, and a
process that survives contact.
Scoped in conversation, built in stages, tested against the awkward cases before it is trusted with anything real.
Understand
We start with what people actually do, not with the process document that says what they should do.
Map
The current steps, the handoffs, and the ones that exist only because two systems do not talk.
Design
Which steps are automated, which stay manual, and where a person must approve before anything moves.
Build
Systems connected, the missing pieces written, the workflow assembled and put in front of real cases.
Test
Normal cases, messy cases, failures and edge cases — including what happens when a system is unavailable.
Monitor
For running systems, workflows are watched and adjusted as the business changes around them.
Reliability
Automation should
fail safely.
A workflow that quietly makes a bad decision is worse than no workflow at all. Every build is designed around that sentence, which is why the boring parts get as much attention as the clever ones.
Can this be processed confidently?
The step completes, the next one starts, and the run is recorded.
The item goes to a person with the reason attached. Nothing is dropped and nothing is invented.
- ValidationValues are checked against expected formats and ranges before they are used.
- RetriesTemporary failures are retried with backoff instead of abandoning the item.
- Error handlingA failure at one step does not silently stop the rest of the process.
- Approval gatesSensitive actions wait for a named person to approve them.
- Audit trailWhat arrived, what was done, what changed and who approved it.
- NotificationsThe right person hears about a problem while it is still small.
- MonitoringRuns are watched, so a workflow that stops working is noticed.
- Exception handlingUnusual items are separated out rather than forced through.
- Fallback processWhen the workflow cannot proceed, there is a manual route that still works.
Scale
Twenty minutes a day,
or an operating system.
Useful automation does not have to be an enterprise programme. The smaller builds are often the fastest way to find out how we work.
Worth doing anyway
Something that saves twenty minutes a day is worth automating — and worth automating well, because it runs three hundred times a year.
- Rename and file incoming documents
- Turn form submissions into a structured report
- Send the reminders people currently send by memory
- Keep two spreadsheets genuinely in sync
- Prepare the weekly report overnight
- Organise attachments into the right folders
- Notify someone when a value changes
- Generate documents from spreadsheet rows
- Chase documents that have not arrived
A small workflow is usually the cheapest way to test whether we are a good fit.
Several systems, one process
When the process spans departments, the build grows: several triggers, checks, a database of record, approval stages and reporting on top of the same data.
- Trigger
- Validate
- Process
- AI
- Database
- Approval
- Notify
- Report
- Triggers
- Emails, files, forms, schedules, webhooks and database events.
- Processing
- Extraction, cleaning, validation and business rules.
- AI
- Understanding, classification, drafting and summarisation where judgement is fuzzy.
- Database
- A single record of what came in and what happened to it.
- Approvals
- Human decisions at the points that carry consequence.
- Notifications
- The right people told at the right moment, through the channel they use.
- Reporting
- Dashboards and scheduled packs built on the same data the workflow writes.
Who it is for
Teams who do the
same thing every week.
Automation is not tied to an industry. It tends to land first where volume meets repetition — and where somebody has already noticed the pattern themselves.
If the work is mostly judgement, you probably do not need us. If a large part of the week is spent moving, checking or re-entering information, you probably do.
Where it usually starts
- Small businesses
- Growing companies
- Finance teams
- Accountants
- Auditors
- Operations teams
- Consultants
- Sales teams
- Founders
- Professional services firms
- Teams buried in spreadsheets and email
Worth examining
What do you do every week
that you wish you didn’t?
You do not need to know what an API is to answer these. Describing the process is the whole job at this stage — working out the mechanism is ours.
0processes flagged so far
Nothing flagged yet. If one of those questions is closer to home than you would like, that is usually where to start.
Answering this is not a commitment, and nothing is submitted anywhere — the list stays in your browser.
Next step
Describe the repetitive part.
We’ll work out the rest.
You do not need to know which system should talk to which, or what ought to be an API. Tell us what you do today, how often, and which part takes the longest — we will tell you honestly what is worth automating and what is not.