Perseid Echo Creations · Renton, WA
Answer five quick questions about the repetitive work eating your team's time. You will see whether it looks worth investigating, what should stay human, and where I would look first.
No signup. You see the result before I ask you for anything.
The workbench
This is not a quote form and it does not email you a PDF three days later. Five questions, an honest read at the end, and one of the possible answers is "do not automate this yet."
How this goes
Nobody sensible hands a stranger access to their business on day one. So the first two steps cost nothing, the third is a small fixed fee that produces something you keep, and only the fourth is a real commitment.
Best fit: established owner-led businesses with recurring workflows, where a missed follow-up, an hour of manual administration, or a day of delayed information has a cost you can actually put a number on.
Five questions, right here on this page. You get a read on whether the work you are describing is a sensible candidate, what should stay human, and whether it is worth going further.
We work out whether the problem is expensive enough to be worth solving, whether it repeats often enough and follows clear enough rules, and whether I am actually the right person for it. If the answer is no, I will say so on the call.
A paid working engagement on one recurring process. We document how the work happens today, where it breaks, what can safely be automated, what decisions stay yours, and what building it would actually involve. You keep the map either way.
One scoped system, built around the tools you already use, tested and documented. Afterwards you take the keys, keep me on to maintain it, or hand the day-to-day running to me. The build price is the same whichever you pick.
Proof from the floor
Systems built for clients stay private unless they give me permission to share them. These examples come from systems I own and operate myself, with the real numbers attached, including the unflattering ones. Every one of them is running right now.
534emails sent, 15 replies, 2 qualified opportunities
Built for my own venue brand: list sourcing, the sequence, the sending schedule, deliverability monitoring, reply handling. It watches its own bounce rate and pauses before a sending domain gets burned, which is the part most people find out about too late.
Green Felt Club · my brand, my list, my numbers
216automated tests, all green, enforced on every commit
A live email platform with configurable state-specific sending windows, a circuit breaker that pauses everything at a 2% bounce rate and refuses to re-arm itself, one-click unsubscribe, and per-recipient suppression that survives a provider swap. This is the standard I build to when the thing has to hold up.
Live at heartwood-crm.vercel.app
4brands published from one pipeline, every post human-approved
Drafts the copy, generates the imagery, tailors each post to the platform it is going to, then holds everything at an approval gate until a person says yes. Nothing publishes on its own. It runs daily across several brands, including this one.
Running today · operator approval on every send
Ask on the call and I will tell you what I can about the client work.
The entry product
Most people in this business will happily spend two unpaid hours designing your system, because it is really a sales meeting wearing a hard hat. I would rather charge a small fixed fee and give you something genuinely useful, including the parts that argue against building anything.
You keep the map whether I build the system or not. If you take it to someone else, or build it in-house, or decide the honest answer is to fix the process before automating it, the document still does its job.
Automation with boundaries
The fear is not really the technology. It is sending something embarrassing to a customer, or depending on a machine you cannot see inside. So before anything gets built, we agree exactly what the system is allowed to do. Every meaningful action receives one of these three control settings, and you can change them later.
The system prepares the quote, the reply, the report, the schedule. It stops there. You make the final call and you send it.
The system does the whole job and then holds it at the gate, finished, waiting for your yes. One tap and it goes.
Routine cases go automatically inside limits you set. Anything unusual stops and comes to you instead of guessing.
The point is not that nothing is automatic. It is that nothing gets authority by accident. Whichever settings you choose, the system keeps a visible activity log, tells someone when a run fails, and has a pause switch that you control.
What it costs
Two separate things: a one-time build, then your choice of how involved I stay afterwards. The build costs the same either way, so you are never paying extra just to keep your options open. Real numbers get scoped from the map, not guessed from a form.
$750
One workflow. One recommended first build. One decision-ready plan. Credited toward a build signed within 30 days.
from $2,500 most land $3,500 to $9,000
Mapped, built, tested, documented, handed over with training and a post-launch bug-fix window.
$0 / from $750 / from $2,000 a month
Take the keys and run it yourself, keep me on to maintain it, or hand me the day-to-day running of it. Month to month, change or cancel whenever.
Need to start smaller? When the workflow supports it, the build can be phased around one measurable first win.
Tool subscriptions, AI usage, hosting, and third-party platform costs are billed separately unless included in your proposal.
Who you are dealing with
I am Bryan. I spent 21 years in corporate customer experience and digital operations before going independent, which means I have been on the other side of the table watching an agency bill for a discovery phase that produced a slide deck. The person on your first call is the person who builds your system and the person maintaining it a year later.
Coaches, consultants, and fractional operators
Refer it, work alongside me, or bring implementation into your own offer. Nothing is quoted to your client until I have reviewed the workflow.
Straight answers
Then that is what the map says, and I will tell you on the call before you spend the $750 if it is already obvious. Some work is not frequent enough to be worth building around. Some of it needs the process fixed before a machine is pointed at it. Some of it is genuinely a judgement call that should stay with a person. Selling you a build in those cases produces a system nobody trusts and a client who never comes back.
I will not tell you "it is completely safe," because no honest systems person can promise that in one word. What I can do is tell you exactly where it goes.
Before anything gets built, you get it in writing: which data the system touches, which third-party services process it (hosting, AI providers, whatever tools you already use), what is stored and for how long, who has access, what is deliberately excluded, and what happens to the connection when we stop working together. If a piece of that is not acceptable to you, we design around it or we do not build it.
You own and control the project-specific system built for your business. You get the credentials, the configuration, the documentation, and a plain-English owner's guide: everything needed to run it or hand it to someone else. The build price is the same whether you take the keys the day it launches or keep me on for years.
Two honest caveats. Third-party tools keep their existing licenses, so you hold those accounts directly. And the reusable frameworks I build every client's system on top of stay part of my toolkit unless your proposal says otherwise. Making it easy to leave is deliberate; it is the only version of this business I would want to buy from.
Fair question, and the answer is not to pretend it cannot happen. Every system is documented well enough for another competent technical person to pick it up, monitored so failures announce themselves instead of going quiet, and built on tools you can access without me. You are never holding a black box whose only key is my phone number.
It will happen eventually. Software vendors change things. That is exactly what the monthly maintenance option is for: I watch for it, fix it, and adjust the system as your tools and workflows change. If you have taken the keys instead, you can call me and pay for the fix, or handle it yourself with the documentation.
No. You do not touch code or settings. You tell me what keeps repeating and what it costs you when it slips, I build it, and you go back to running your business. The part you do stay involved in is deciding what the system is allowed to do on its own, and that conversation is in plain English.
Yes. I work directly with a client's trusted advisor, join an existing coaching or consulting engagement, or contract separately as the implementation specialist. Your advisor does not need to design or manage the technical system. Responsibilities get agreed before the project starts, and nothing is quoted until I have reviewed the workflow.
If you are the advisor rather than the owner, here is how partnering works.
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