Workflow Automation · AI and custom software
The busywork between your systems, handled.
Most automation breaks the first time real life shows up: an invoice layout changes, an email arrives half-filled. We build and look after workflows that expect the mess, with a person in the loop where judgement matters.
What you hand us, and what comes back.
You hand us
- Emails, PDFs and forms someone re-types today
- Approvals that stall in an inbox
- Two systems that should agree and do not
- A process only one person knows how to run
You get back
- Workflows that run on their own and say when they cannot
- AI that reads the messy inputs and drafts the next step
- A named person for every exception, with the context attached
- Monitoring and upkeep after launch, not a handover and a goodbye
What we have built.
From our own project records, client names removed.
A WhatsApp message becomes a numbered, branded PDF receipt in the same chat.
n8n · WhatsApp Cloud API · Claude · Gotenberg · PostgreSQL
An application becomes a scored recruiter dossier, with nobody advancing it by hand.
Django · SvelteKit · PostgreSQL · Claude · Gotenberg · Brevo
Exam-practice engines that change the numbers in every question, on every attempt: the accountancy alpha covers 843 examinable outcomes.
Cloudflare Workers · Workers KV · Cloudflare Access · Playwright
Quotes, invoices, payment reminders and summaries for small service businesses, over WhatsApp. Full acceptance run in progress.
n8n · PostgreSQL · NocoDB · Brevo · Twilio · Gotenberg
AI reads a sales mailbox and proposes CRM updates; nothing changes until an editor accepts.
n8n · Claude · Cloudflare D1
Read the workflow automation case studies → or see all eight.
Start with something small enough to judge.
Inbox to system
Turn a shared mailbox of orders, invoices or requests into clean records in the system that needs them.
System sync
Keep two or three core tools in agreement, with every exception routed to a named person.
Assisted decisions
Let AI prepare the case and a person approve it, instead of a person doing both.
Straight answers.
Do we have to replace the tools we use now?
No. The work is connecting what you already run. We only suggest a new tool when an existing one cannot be reached any other way.
What happens when a workflow meets something it has not seen?
It stops, says so, and hands the item to a person with the context attached. Silent failure is the thing we design against.
Who owns what gets built?
You do. Workflows are built in your accounts and documented so another team could take them over.
What this runs on
- n8n
- Claude (Anthropic API)
- WhatsApp Cloud API
- Gotenberg
- PostgreSQL
- NocoDB
- Brevo
- Twilio
- Docker
- DigitalOcean
Most engagements end up touching more than one.
Tell us what needs to happen.
Thirty minutes, your agenda. You leave with a first step whether or not we work together.
omari@monosolution.xyz+1 213 556 4010