How we work
Small first. Written down. Then run.
A first project is small enough to judge in weeks, scoped on one page, and looked after once it is live.
A 30-minute call
You describe what is slow, manual or unanswered. We ask what it costs you, and whether it is worth fixing first.
A one-page scope
What we take on, what you will see, how we will both know it worked, and what we will measure.
One piece of work
One workflow, one dashboard or one queue. Built in your accounts, documented so someone else could take it over.
Run it, then report
We operate it, keep it working, and report against the measures in the scope.
What stays human.
Decisions
Hiring, money, approvals and anything consequential stay with a named person. AI prepares the case.
Arithmetic
Totals, billing and financial figures are calculated in code, never by a language model.
Exceptions
When something does not fit, it goes to a person with the context attached, instead of failing silently.
Your data
It stays in your systems, behind your logins, and names are kept out of anything that gets published.
After launch.
Tests before release
Automated checks, including tests written to prove a permission can fail.
A login in front of every dashboard
Each audience sees its own edition, and access lists are reviewed.
Backups with restore drills
Encrypted offsite backups, and restores actually rehearsed.
Written change control
Shared servers run under a written contract of who may change what, and when.
The toolbox we run on
- n8n
- Cloudflare Workers
- Cloudflare Pages
- Cloudflare D1
- Cloudflare Access
- PostgreSQL
- Docker
- DigitalOcean
- Claude (Anthropic API)
- WhatsApp Cloud API
- Twilio
- Brevo
- Gotenberg
- Django
- SvelteKit
- Playwright
- GitHub
- Microsoft 365
- Google Workspace
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