Specialist work. A clear scope.
Work we take on as standalone projects, and software we sell on its own, for companies whose day-to-day IT belongs to someone else entirely. Each one is scoped and priced in writing before it starts, and the findings are yours to keep.
A defined project, with your team in charge
These are defined jobs with a beginning and an end. We agree the scope, quote it flat, do the work, and hand you the result. You keep your provider and your internal team, and the report is written so you can hand it straight to them, or to your insurer, your auditor or your attorney, without translation.
The review work is read-only by design and cannot change a setting even by accident. The build work is quoted before a line of it exists, and comes with documentation and an off switch.
Workflow automation
The job someone does by hand because two programs won't talk.
We sit with the person actually doing the work for an hour, find the step worth automating, quote it flat, and build it on the software you already own. We use existing platforms where practical, and identify hosting, licensing, API usage, and support costs in the proposal. The work is documented and handed over with operating instructions.
Examples of work we have shipped, including paperwork read on arrival and a monthly spreadsheet that assembles itself, are on the automation page, anonymised and thin on purpose: what each one does is the client's business.
What should we automate?
The question everybody gets stuck on, answered from evidence.
Building the automation is the easy half now. The hard half is knowing what is worth building, and a meeting where people describe their work from memory surfaces what is annoying, which is not the same as what is expensive.
So we go and find it. Three ways in, and you only need whichever one you have:
- 01
A year of your requests, read and grouped
Every support request your company filed over twelve months, read one by one and grouped by what was actually being asked for. Repetition is the signal: something that arrives every week with the same shape is a candidate, and a hard problem that happened once is not. It works on your current provider's ticket history too, exported, which is usually a spreadsheet nobody has ever looked at sideways.
- 02
Your written processes, against what actually happens
The onboarding checklist, the month-end close, the SOP written two years ago and never opened since. We walk the written version next to the real one. The gap between them is where the manual work hides, and it is also, usually, where the mistakes come from.
- 03
An hour beside the person doing the job
The mundane work nobody logs because it is just the job: retyping what is already on another screen, checking the same thing twice, the Friday spreadsheet, the folder of scans somebody keys in by hand. This is the richest of the three and the one nobody thinks to ask for.
What comes back is a ranked list, we ran it on our own service desk first. Each item carries how often it happens, roughly what it costs you now, what it would take to automate, and how confident we are. It also names what to leave alone, because some work is cheaper by hand. You can take that list and build from it yourself, or hand it to whoever you like.
Most of the list will be ordinary, and two or three items on it will be things you did not think were possible: reading messy scanned paperwork, drafting from a template and holding the draft for a human, watching a stream of text for a pattern. That ground moved recently and most people have not been told. Judgment stays with your people; the typing does not have to.
Email discovery and search
When somebody needs every message about one thing.
A lawyer asks for the correspondence. An insurer wants the thread. A records request lands, or a dispute turns on what was actually said in March. Searching that by hand means one person clicking through folders and hoping, and it misses the attachments entirely.
We read the mailboxes you name, every folder including deleted items, and we open the attachments too, including the text inside scanned PDFs and photographed documents. What comes back is the set of records that answer the question, each item fingerprinted, with a sealed manifest so what you hand over is verifiably what we found.
Microsoft 365 cleanup and audit
Who still has the keys, and what is still tied to people who left.
A one-time review of your tenant: the accounts of people who left that are still enabled and still billing, who holds administrative rights and how they got them, the forwarding rules and app permissions and guest accounts nobody remembers approving, the security work that was agreed to and never finished.
We also read the tenant's own audit record directly, going back roughly six months rather than the week a console shows, for the events that matter. If you want a smaller starting point, name your recent departures and we will run only those.
The findings are rarely dramatic and almost always worth knowing. The kind of thing it turns up: a website contact form somebody set up years ago, still sending its alerts to a mailbox nobody reads. A domain renewal notice bouncing off a closed account. A shared login whose security code goes to a phone that left with its owner. More of what that looks like.
Email fraud review
A quieter service, for owners with a suspicion.
For an owner who suspects something is wrong inside their own company email: altered documents, redirected payments, paperwork reused under another name. The review reads all of it rather than a sample, and looks for the patterns a skimming eye misses.
It runs under the direction of you and your attorney, with a named scope agreed up front rather than a dragnet, and every finding is argued against internally before it reaches you. A review that turns up nothing is reported as exactly that: we looked hard in the agreed places and found nothing, with the scope and our confidence stated, which is a different claim from nothing having happened.
EnlightenDLP, our redaction software
Black bars that are actually black bars.
Firms redact documents in the worst possible way: a black rectangle drawn over the text in a PDF editor, with the words still sitting underneath where anyone can select and copy them. We built EnlightenDLP because we kept seeing it, and it is available on its own, whether or not we do anything else for you.
- The document never leaves the machine. Redaction runs entirely in your own browser. The file is never uploaded or queued on a server, and nothing goes to anyone's AI. That is a property of how it is built; no privacy policy has to promise it.
- You decide what gets redacted. The terms are yours: names, account numbers, addresses, whatever the matter requires, plus patterns for the common ones. Nothing is guessed at and nothing is redacted because software thought it should be.
- The text is removed, not covered. Redacted pages are rebuilt so the words are gone from the file rather than hidden behind a shape. Copy and paste from the result and there is nothing underneath to recover.
- Scanned paper is read too. Documents that are photographs of pages get read on the spot, so a term buried in a scan still gets covered. That includes files that mix typed pages and scanned ones.
- It tells you where it is unsure. Pages it could not read cleanly, pages at an angle, and comments or sticky notes it stripped out are all reported before you export, with a confidence figure. You get to decide, rather than finding out later.
- One shared term list for the whole firm. Your team works from the same list, so the same client name is redacted the same way by everyone, on their own accounts, with an audit log of who did what.
Couldn't you just ask an AI to do this?
Partly, yes. The tools sit on everyone's desk, and a capable person can attempt most of what is described above in an afternoon. What has become scarce is not the doing.
Point something clever at a year of company email and it will hand you a long list of things that look wrong. Almost none of them are. Learning which signals are noise took us real matters, run repeatedly, and that part does not fit in a prompt; the failed version of this work accuses people who did nothing. And when the answer is going to an insurer, an auditor or an attorney, somebody has to put their name on it, including when the answer is that nothing turned up.
So the honest position: if a job here is one you can do yourself, do it. What you are paying for is the idea and the willingness to stand behind it. The typing is the cheap part now, and we are not going to pretend it isn't.
Describe the job in two sentences
Tell us what needs doing and who it's for. You'll get a straight answer on whether it's worth doing, what it would cost, and whether we're the right people for it. Sometimes the answer is that you don't need us.