Every firm has a bottleneck. Yours is findable.

I find the process quietly costing your team the most time, then build the automation that removes it. Discovery first, and then something working. Not a transformation program.

Find my bottleneck See a finding

Reveal the bottleneck.
Unlock the efficiency.
Uncover what it makes possible.

Bottlenecks rarely announce themselves. They look like normal work.

Documents come in. Someone manually pulls the information out.
document processing
A meeting ends. Someone spends the next half hour updating three systems.
post-meeting admin
Every Friday, someone rebuilds the same report from the same four places.
recurring reporting
The answer exists, in a PDF, an email thread, or a folder nobody can find.
internal knowledge

None of these feel like problems from inside the firm. They feel like the job, which is exactly why they survive for years. Finding the one that costs the most is worth more than any tool you could buy first.

Uncover, then build, then hand it over.

I find it

I walk the workflow as it actually runs: who touches it, which systems it crosses, where it stalls, and what it costs in attention. You get the finding in writing either way.

I remove it

No transformation project. The specific bottleneck gets removed with the right combination of software, AI and integrations: the simplest useful version, and nothing more.

It becomes yours

I test against real cases, deploy into the way your team already works, and adjust once people have lived with it for a week.

The bottleneck was reading. The opportunity was the dashboard.

independent financial advisory practice

An independent advisor thought her problem was speed. Walking the workflow showed something narrower: for every household, the reading, extraction and modelling happened by hand before any advice could begin. That was the constraint on how many clients she could serve.

I built a custom web application that takes the documents in, pulls out the relevant figures, structures them, applies the practice’s own financial logic, and presents the result as a branded dashboard the advisor can walk a client through.

Removing the bottleneck uncovered a second thing worth having: the dashboard itself. It has kept evolving through paid follow-on work, and the advisor has since asked about making it available to other advisors.

finding Statements, tax documents and account PDFs, read and re-keyed by hand

system Upload → extraction → structured data → the practice’s financial model

output A branded snapshot of where the client stands and where they’re heading

result 5 to 10 hours a week back across document processing, manual updates and client decks

screenshot: document upload
and extraction review

screenshot: client snapshot
dashboard

portrait: founder,
plain background

Technical enough to build it. Business-minded enough not to over-engineer it.

I have spent over a decade working inside technology companies. I am not a career software engineer, and I do not pretend to be one. But I have been close enough to how software actually gets built, for long enough, to hold my own in a technical conversation, read a system, and know what a build really takes before anyone commits to it.

AI coding tools changed what I could do with that. What used to end at a recommendation now ends at a working system. I do the discovery, design the automation, build it, and hand it over, usually in the time a larger firm would spend scoping.

You work with me directly. The person who maps your workflow is the person who writes the code and the person who hands it over. Nothing gets passed down to a junior team, and nothing is lost between the diagnosis and the build.

The advantage isn’t deep machine learning research. It’s knowing which problem is worth solving and stopping at the point where it’s solved.

What working together costs.

Start with an assessment. It tells you where the bottleneck actually is and whether a build is worth doing at all, before anyone commits to one. If you go ahead, the fee comes off the implementation.

assessmentstart here

$2,500

A discovery process with the people who actually run the work, to find where the bottleneck really is. You get a full written report that walks the workflow, shows where the time goes and what it costs you, and says whether a build is warranted at all.

No build. Credited in full against implementation if you move forward.

implementationthe usual next step

$9,500

Everything in the assessment, plus the bottleneck removed. Built, tested, and handed over to your team.

Custom implementation: tool, script or internal app
Integrations with the systems you already pay for
Tested against your real cases, not demo data
Deployment and a handoff your team can maintain
First 30 days of Standard support included

One to two weeks from kickoff to something your team is using.

Larger or multi-workflow engagements are quoted individually.

after the build

essential

$500 / month

I monitor what’s running and resolve anything that stops working.

standardrecommended

$1,300 / month

Essential, plus unlimited changes to what I’ve already built, one at a time.

pro

$2,500 / month

Standard, plus a quarterly review of how your team is working, to find the next bottleneck before it costs you.

Included: any change to something I have already built for you.

Not included: anything I haven’t built yet. That is new work, quoted on its own.

Book a free call support is always available · you can cancel a plan at any time

What people ask before they hire me.

What access do you need to our systems?

As little as will do the job. I scope access to the one workflow being automated, read-only wherever that is enough, and I tell you exactly what I need and why before I ask for anything. Nothing gets connected that isn’t required for the thing you hired me to remove.

What happens to our data?

You own every account involved. Where a build needs an AI service to read your documents, you create that account and hold the key. I use it while building and testing, and at handover you change it, which locks me out completely. I don’t keep copies of your data afterwards, and nothing from your business is used for anything but the work you asked for. I’m glad to sign an NDA before we start.

You’re one person. What happens if you’re unavailable?

Everything I build runs on your accounts, using standard tools, and it is documented at handoff. Nothing sits on a platform of mine that you would lose access to. If I disappeared tomorrow, another developer could pick it up and keep going. That is deliberate.

Do we own what you build?

Yes, outright. It runs on your accounts and the code is yours. There is no licence to renew and nothing to keep paying me for unless you want ongoing support.

How long does it take?

One to two weeks after the assessment, from kickoff to something your team is using.

Show me the process your team loses the most time to.

I’ll go through how it works today, where the time actually goes, and whether removing it is worth doing. No deck, no pitch. And if the finding is that software shouldn’t touch it, I’ll tell you that instead.

Free, 30 minutes. No preparation required. You’ll leave knowing whether the process is worth automating.

Book a discovery call

prefer email? hello@revelationlab.io

or send it ahead

I’ll reply within twelve hours.

Name required Company required Email required Team size

Which process do you suspect is the bottleneck? required

I’ll only use this to reply to you. Nothing else.