Renton, Washington
I'm Bryan Piard, I run Perseid Echo out of Renton, and I make the systems that take repetitive back-office work off owner-led businesses here, things like quotes nobody chases, the job-to-invoice handoff and intake for clinics. You can start with a free 60-second Fit Check, and a first conversation can be in person if you'd rather.
I live and work here. If you run a business in Renton and the same job keeps eating an afternoon a week, that is the kind of thing I take off your plate — carefully, one workflow at a time.
Written by Bryan Piard · Published · Updated
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
Renton is not one economy, it is three sitting on top of each other. There is the Boeing supply chain and the machine shops and fabricators that feed it. There is a deep bench of owner-led trades — electrical, HVAC, auto, landscaping, remodels — a lot of them running two vans and a whiteboard. And there is the Highlands and downtown service layer: clinics, dental practices, restaurants, studios.
What those three have in common is that the back office never got built. The work got bigger, the paperwork got bigger with it, and nobody ever stopped to design the part where information moves from one place to another. That gap is where I do most of my work.
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.
The single most common one I find in Renton trades. The quote gets sent, the owner means to follow up, the week happens. A system that chases every quote on a schedule you set is usually the cheapest thing on the list and the fastest to pay for itself.
Work gets done in the field, then somebody retypes it in the office at night. Photos in one place, hours in another, the invoice built from memory. This is normally a plumbing problem, not an AI problem, and it fixes cleanly.
New patient or new client turns into a stack of forms somebody keys in by hand, and the same details get asked for three times. Worth mapping when it happens often enough, and worth leaving alone if it does not.
How it goes
Start with one recurring problem in your Renton business. The first two steps are free; the Map gives you a plan to act on before any implementation is scoped.
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 customer or operational workflow: the steps, ownership, likely causes, and a practical first improvement. Procedures, communication, and team guidance come before tools where that is the better fix. Credited toward a build signed within 30 days. What is in a Map
When software is the right fix, most builds land between $3,500 and $9,000. Process guidance and team enablement are scoped separately. For systems, take the keys, choose maintenance, or ask me to run it.
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 Renton, 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
My experience includes improving service journeys, preparing frontline teams for new products, and creating tools that remove repetitive work. My own AI-assisted projects show the implementation side: approvals, reporting, content preparation, and workflow controls. The examples distinguish prior internal work, prototypes, and historical project results. They are evidence of the work, not a forecast for your business.
What I will not do is show you a number from a business in Renton that I have not worked with. If I have not done it, it does not go on the page.
Straight answers
I am in Renton. That is where the business is registered and where I work from, so a first conversation here can be in person if you would rather do it that way. I have deliberately not written pages for cities I could not get to.
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 with one recurring problem
No account, no calendar, no waiting for a reply. Run the Fit Check and you get the read on your own screen. If the workflow looks worth exploring, the next step is a free 20-minute call about the problem, its impact, and whether I can help. The result is a starting point, not a diagnosis or a build quote.
Or just write to me: bryan@perseidechocreations.com · or call 425-243-3473