Who this is for#
Finance, operations, compliance, reporting — any team where smart people spend a large chunk of the week moving data between systems, reformatting documents, or writing the same class of narrative again and again.
If you are sensitive about data leaving your network, say so up front. On-premises and local LLM setups are in scope.
How it works#
1. Observe (about 2–3 days)#
I sit with your team (in person when it makes sense, remotely when it does not). I watch the actual workflow — not the process diagram from five years ago. We map where time goes and what breaks.
2. Design (about 1–2 days)#
I come back with two or three concrete opportunities ranked by impact and feasibility. You approve what we build before I write serious code. No surprises.
3. Deploy (about 1–2 weeks)#
I build using tools you already have permission to use: Microsoft 365, Python, vendor APIs, KNIME, whatever fits. I am not selling you a black-box platform you cannot keep.
4. Transfer (about 2–3 days)#
Documentation, walkthroughs, and a clean handover. You should be able to run and extend what we built without me on retainer. I am happy to stay involved — I am not trying to create dependency.
What actually gets deployed#
Every engagement is different, but typical outputs include:
- Report and memo drafts from structured data or notes — humans stay in the loop for judgment and sign-off.
- Document formatting and brand compliance — especially alongside DocMark when you need machine-checkable rules.
- Extraction from PDFs, emails, scans — into sheets, databases, or downstream workflows.
- Workflow automation that replaces repetitive data entry or copy-paste between systems.
- Summarisation and research assist where the risk profile allows — always with clear boundaries on what the model is allowed to do.
On-premises and local LLMs#
If your InfoSec team says no to cloud inference, we plan for models and orchestration inside your perimeter. The goal is the same: less manual slog, same audit posture you need.
Pricing#
Scope-based, tied to outcomes and time on site. Most engagements land in a two- to four-week shape; we scope explicitly in the design phase. The 30-minute discovery call is free.
FAQ#
Do we need new software?
Not necessarily. I start from what you already license and approve. We add components only when there is a clear gap.
What about data sensitivity?
We design around your classification and residency rules. That can mean local models, VPC deployments, or no model at all — just deterministic automation where that is the right answer.
How is this different from a big consultancy?
You get me — not a pyramid. I am in the workflow with you, building and handing over. If you want a 40-slide strategy, I am the wrong fit.
What happens after you leave?
You own the artifacts. I document and train so your team can operate and extend. Ongoing support is optional, not mandatory.