12
years of experience
What I do
reducto
A document intelligence platform.
Founding Product Designer · Sept 2025 – July 2026
What do they do?
reducto is a document processing company. Simply put, many companies have heaps of documents. They are looking for a way to take that content out of them. Frontier models aren't really great at getting this content out cheaply, so they turn to reducto. It's the largest company in the space and trusted by many big names.
Redesign Outcome
From a fresh component set to a shared system the whole team could build on.
Evaluate
Getting the most accurate, cost effective results from reducto
Millions
of docs
Customers run thousands, sometimes millions, of documents at a time. A single job can take the entire weekend, so nobody wants to get it wrong.
Example of health document
Before the big run, they rehearse in Studio
A visual tool on top of our API, where teams iterate on a handful of documents before committing to the whole batch.
But what does happy{{ smileSvg }} mean?
Evaluate v1
We created an evaluate feature where we would grade the results of each file. It would give suggestions for improvements and an overall score. The score was developed by a pricer, more accurate model. You can't run those on the larger runs but it's great for testing.
People loved the suggestions but didn't really trust the numbers.
Evaluate v2
So we stripped out the grading aspect, and added the suggestions to the editing experience. Most people didn't need all the nitty gritty grading details.
Evaluate v3
The score on its own wasn't enough to earn trust. Eventually we'll give people the support to go in and see the grading on a field by field level, so every number can be traced back to the exact value it came from.
Evaluate Outcome
What shipped, what got cut, and what came next.
Runbook
AI agents for physical operations.
Founding Product Designer · So far a 1.5 month contract
The AI workforce for field services
Runbook builds long-running AI agents for field services and transportation companies: fire and security inspectors, building controls providers, freight carriers. Runbook handles the busy work around a work order, from first call to final invoice.
We reach any system a person can, through APIs, browsers, Virtual Machines, phone, text, etc. This is done by simulating their workflows within Runbook.
Runbook · The last six weeks
What I worked on
Setting up a new customer
During onboarding, we breakdown their workflows like this. The general workflow is easy to distill from something called backtesting . This is where we analyze previous work orders and find common solutions between each thing.
However there's a TON of niche situations that can only be attained by follow up engagement with the customer.
Getting the knowledge out
That knowledge typically comes from huge Zoom meetings with numerous heads at the company. They're hours long and can be quite draining.
Our ops people can't keep track of all the special situations.
Problem statement
How might we capture a customer's entire workflow without hours of draining calls?
New Issues Experience
I created an issues experience. Similar to Linear, our customers could create "issue tickets" that would be assigned to our internal ops. Anytime there was a problem with an existing workflow, our customers could flag it to our ops.
However, there was a problem, no one used it.
Why no adoption?
- The experience was overwhelming
- Did not fit into current ops people's workflow
- Very little to no notifications
Training & notifications
Slack channel integration where our ops and our customers both got Slack notifications.
We also trained our ops people to train our customers on the new Issues experience.
Issues Outcome
Issues filed per day
On averageTime to adopt a new workflow
Down from 4 weeks