Order intake off email and PDFs
Orders arrive as attachments and somebody retypes them into the system. High frequency, real cost when a digit moves. Usually the first thing I look at in a Kent Valley business.
Kent, Washington
The Kent Valley runs on order paperwork, and most of it still moves by hand. I build and run the systems that carry it, from a shop fifteen minutes up the hill.
Free, no account, and it will tell you to leave the work alone if that is the right answer.
What the work looks like here
Kent has one of the densest concentrations of warehousing, distribution and light manufacturing on the West Coast. That produces a very particular kind of repetitive work: order intake off email and PDFs, purchase orders matched against invoices, inventory counts reconciled between a spreadsheet and whatever the system says, driver and dispatch paperwork chased down after the fact.
It is high-volume, low-judgement work, and it is almost always being done by somebody who is too senior to be doing it. That combination — frequent, tedious, and expensive when it goes wrong — is the clearest case for building something. It is also the case where I am most likely to tell you the fix is a better process rather than a bigger tool.
Where I would look first
These are the patterns I see most often in this part of the county. Not a promise that yours is one of them — that is what the Fit Check and the Map are for.
Orders arrive as attachments and somebody retypes them into the system. High frequency, real cost when a digit moves. Usually the first thing I look at in a Kent Valley business.
Three documents that should agree, checked by eye. This is where the money quietly leaks, and it is well-suited to a system that flags the exceptions and leaves the judgement calls to a person.
Proof of delivery, hours, damage notes — captured on paper or in a phone, then chased at the end of the week. Getting it captured once, at the point it happens, is often the whole fix.
How it goes
Nobody in Kent needs to commit to a build to find out whether one is worth doing. The first two steps are free and the third is bounded.
Five questions on your own screen. You read the answer before I ask you for anything, and one of the possible answers is that you should not automate this yet.
A conversation about whether this is a fit, not a free solution design. If it is not, you will hear that on the call.
One workflow, taken apart properly: what it costs you now, what should stay human, and what a build would actually involve. Credited toward a build signed within 30 days.
Most land between $3,500 and $9,000 depending on how many systems have to agree. Then I hand you the keys, maintain it, or run it — your call.
I will not quote a build price off a web form. Ranges point at the Map, and the Map is where a real number comes from.
Before you hire anyone
For the workflows that come up most in Kent, I have written out the honest version of that decision — including when the right answer is an off-the-shelf product and you should keep your money.
The part most people worry about
Every workflow I build has a setting for how much it is allowed to do on its own, and you pick it per workflow rather than once for the whole business.
The system does the assembling and the remembering. A person reads it and presses the button. Where most work should start, and where a lot of it should stay.
It acts on the rules you agreed and reports what it did. Suitable once a workflow has proven itself and the cost of a wrong move is small.
Fully hands-off with a switch you own and a record of every action. Appropriate for high-volume, low-judgement work, and not much else.
Whether I can actually build
I am one operator, not an agency with a case-study deck. So rather than show you somebody else's results, I will show you the machinery I built for my own business and still run daily — content production, outreach, lead handling, approvals, monitoring. It is the same kind of work I would build for you, and it is the honest version of proof: you can ask me how any part of it works and I will know, because I am the one who fixes it when it breaks.
What I will not do is show you a number from a business in Kent that I have not worked with. If I have not done it, it does not go on the page.
Straight answers
Usually the opposite. The expensive work is almost never inside the system of record, it is in the gaps around it — the email that has to become a record, the spreadsheet that reconciles two systems, the report somebody rebuilds every Monday. I would rather connect what you already pay for than sell you something new.
Then that is the answer, and you get it for free in about a minute. The Fit Check genuinely returns “do not automate this yet” when the work is infrequent or a miss costs nothing, and I have not tuned that away to win more business. A build on the wrong workflow is worse than no build: you pay for it, then you maintain it, then you work around it.
That is not what this work is for and it is not usually where the money is. The jobs worth building are the ones nobody's title covers — the retyping, the chasing, the reconciling that gets done at seven in the evening by whoever is still there. Taking that off a person's plate is the point.
A Map takes about a week from the call. A first build is usually two to four weeks after that, depending on how many systems have to agree and how quickly I can get access to them. I would rather ship one workflow that works than four that half-work.
Nearby
Same work, different local shape. Every one of these is close enough that a first meeting can happen in person.
Start at the bottom of the staircase
No account, no calendar, no waiting for a reply. Run the Fit Check and you get the read on your own screen. If it says the work is worth mapping, the next step is a free 20-minute call. If it says leave it alone, you have lost a minute and I have lost a customer I should not have had.
Or just write to me: bryan@perseidechocreations.com · or call 425-243-3473