Service
Business process automation for small teams
Business process automation takes the repetitive steps your team does by hand and turns them into workflows that run on their own: copying data between systems, chasing approvals, sending the same email again. I start by finding where your hours actually go. Then I automate the costliest jobs first, inside the tools you already pay for.
Sound familiar?
The signs this is your problem
If two or more of these are true, there is almost certainly a worthwhile automation hiding in it.
- The same information gets typed into three different systems
- Onboarding a client takes a checklist and half a day of someone's time
- Invoices, receipts and purchase orders are processed by hand
- Approvals stall because nobody knows whose turn it is
- A spreadsheet has quietly become mission-critical infrastructure
What gets built
What a process automation build includes
Four things, in roughly this order. The proportions shift by project — the shape does not.
What you get
Handed over, documented, yours.
- A documented process map of every workflow reviewed, with hours-per-month attached
- Working automations running in accounts you own
- Plain-English documentation — no jargon, written for whoever inherits it
- A short screen-recorded walkthrough for your team
- 30 days of post-launch support included
Typically built with
Chosen per project, not by habit. Everything runs in accounts registered to you — you hold the keys and see the bills directly.
When this is not the right service
How we'd work
From audit to autopilot in weeks.
Fixed scope. One fixed price. Working software every week. You always know what ships next and what it saves.
- Week 0 · Free
Audit
Thirty minutes on where your hours actually go. I map the repetitive workflows, time them, and score each one by what automating it would return. You keep that map either way — including the honest note on which processes to leave alone.
- Week 1
Blueprint
A written proposal: what gets built, which systems it touches, what it costs to run each month, the timeline, and one fixed price for the whole engagement. Nothing starts until you approve it. The price does not move unless you change the scope.
- Weeks 2–4
Build
I design, build and test inside your own accounts, with evaluations and guardrails on anything using a language model. You see working software every week rather than a status update — which means you can redirect early, while redirecting is still cheap.
- Ongoing
Run & improve
Launch, monitor, iterate. Thirty days of support included with every build. After that: take a care plan, hand it to your own team using the documentation, or run it yourself. All three are genuinely fine.
Questions
Business process automation — the usual questions
Most single workflows are live within two to four weeks of the blueprint being approved. The audit that precedes it takes about one week. Larger multi-process projects are phased deliberately so that something is saving you time by week three rather than everything landing at the end.
No. Automation is built around your existing tools, not instead of them. The whole point is to connect what you already pay for — your inbox, spreadsheets, CRM, accounting software — so information moves between them without a person in the middle.
You keep everything. Workflows are built inside accounts you own and control, documentation is handed over in plain English, and there is no proprietary Lytheo platform you would need to keep paying for. You can maintain it yourself, hand it to an in-house developer, or bring in anyone else.
Every engagement is quoted as a single fixed price after a free 30-minute call, so you know the total before anything starts. There is no hourly billing. Cost depends on how many systems are involved and how much exception handling a process needs — a single well-defined workflow is a very different project from an eight-step process spanning four systems.
Related
Often paired with
Ready to get the hours back?
A free 30-minute audit call. You leave with a written map of your automatable workflows and what each one is worth — whether we end up working together or not.
Replies within 24 hours · No sales team — you talk to the builder