I run businesses on an operating system I built.

THE OPERATOR METHOD · OPERATOR-IN-THE-LOOP

See what I run
02 / What I run

A small portfolio.
Operated, not advised.

Own products first, then a handful of outside partners. Same engine, different operating context.

  1. 01

    Green Felt Club

    A pool club for serious amateurs. Member ops, venue outreach, content cadence — all run by the engine, all signed off by me.

    Own · Live
  2. 02

    Dream-Travel

    Host enrichment and booking ops for a travel brand. The first outside partner the practice is operating for.

    Partner · Live
  3. 03

    Dog training app

    An agentic coaching loop on mobile. Owner-app, not a content product. In private build.

    Own · In build
  4. 04

    Perseid Echo Creations

    The practice itself, run on the same engine. The page you are reading is one of its outputs.

    Own · Live
03 / The method

The Operator Method.
An operating system, not a services deck.

Most businesses don’t need more advice. They need a way to turn goals into repeatable motion without losing judgment along the way.

The Operator Method is the system I use to run my own portfolio and a small number of outside partners. It captures the offer, proof, voice, constraints, and goals of a business, then turns them into governed execution cycles.

The engine handles the motion. The operator keeps the judgment.

Every run leaves a record: what we tried, why we tried it, what shipped, what worked, and what changed because of it.

i Inputs What the business brings in

Offer, proof, audience, voice, constraints, goals, and current friction. The engine starts with context, not guesses.

ii Rules The boundaries of the run

The system respects the business, the channel, the audience, and the operator’s constraints. No generic automation spray.

iii Runs One operating cycle, end to end

A run turns a goal into strategy, assets, tasks, approvals, and shipped work. Same shape every time.

iv Artifacts The work before it ships

Strategy, copy, research, outreach, decisions, and operating assets are created as reviewable artifacts — not dumped into a feed.

v Approvals Where judgment stays human

Consequential decisions stay operator-in-the-loop. The machine creates leverage; the operator keeps control.

vi Record What the system remembers

Each run leaves behind what happened, why it happened, what worked, and what should change next.

Most operating stacks optimize for output. The Operator Method optimizes for governed execution: clear inputs, fast motion, human judgment, and a record of what actually worked.

Automation creates motion. Judgment decides what deserves to ship.

Bryan Piard, operator of Perseid Echo Creations
04 / The operator

Run by an operator.
Not handed off.

Perseid Echo Creations is run by Bryan Piard. Twenty-one years in customer experience and digital transformation, most recently at T-Mobile, before going independent to build the engine and run businesses on it.

The practice is small on purpose. Each business running on the engine gets the operator who built it, not a handoff to someone learning it.

  • 01 Run by the operator who built the engine.
  • 02 A small portfolio by design. Quality over capacity.
  • 03 Operator-in-the-loop on every consequential decision.
05 / In motion

What this looks like
this week.

Honest, in-flight numbers. No outcomes promised, no case studies fabricated. The list updates as the work moves.

Green Felt Club 43 venue outreach emails sent and counting. Week of 05/26
Dream-Travel 27 host prospects enriched. Week of 05/26
Dog app Coaching loop scaffolded; first private alpha next. In build
PEC You’re reading it. Today

No services menu. No ladder. If you’re curious about the engine or the portfolio, the door below is open.

06 / Get in touch

The door is open.

If you have a business you think the engine could run alongside — or you just want to ask a question about how the practice works — write. I read every message myself.