moonshinerXwerks LLC is a hands-on lab for learning and applying AI: real products built end to end, from idea to store release, by a team of AI agents with one person making every call.
How the studio runs: one person and a team of AI agents ↓moonshinerXwerks was founded with a straightforward premise: build useful apps for real people, own every pixel, and never cut corners on privacy. Every product in our portfolio started as a personal itch — a problem we encountered, a tool we wished existed, or an idea we couldn't shake.
We're based in Bend, Oregon — a place where people actually go outside, fish real rivers, and meet friends for happy hour. Our apps reflect that. They're built for people who do things, not just scroll through things.
Your data is yours. Our apps default to on-device storage, never sell data, and only transmit information when you explicitly opt in. No ads, no tracking SDKs, no exceptions.
Every app starts with a real need — not a market opportunity deck. If it doesn't solve a problem we've personally felt, we don't build it.
No outsourcing, no templates. Every line of code, every design decision, every user flow is built in-house with intention and care from concept to App Store.
How the studio runs
moonshinerXwerks runs like a small product organization in which every seat but one is filled by an AI agent. I treated the studio itself as a product: I designed the roles, wrote the reporting protocols, built the command center that tracks the work, and set the rules for where a human has to say yes. The agents do the work. The operating model is what makes that work dependable.
AI agents are capable out of the box. What they don’t come with is an org chart, a reporting line or a definition of done. That’s the part I build.Studio Owner
01 · Organization
Every agent has one job description, one reporting line and a short list of things it never does. That is what lets several products move at once without two agents doing the same job, or none of them doing it.
What each product does, what goes in a release, what waits and what it costs.
Anything that ships, publishes, spends money or touches a key.
Inner ring · shared specialistsOuter ring · product pods·every line reports to the Program Manager
RACI
The RACI lives on a page I edit live, and agents read it before they act. Changing who owns something is an edit, not a meeting. Try editing it in the demo below.
| Work | Studio Ownerdecides | Program Managerstudio-wide, your single contact | Product Advisorone per product | Product Engineerone per product | Research Analystany product | Store Consultantboth app stores | Legal Analystlegal + privacy | QA AnalystUX/UI, every product | Marketing Managerall studio marketing | Product Campaign Mgrper product |
|---|---|---|---|---|---|---|---|---|---|---|
| Direction and planning | ||||||||||
| Product vision, scope and prioritiesWhat a product does, what's in a release, what waits | A | C | R | I | I | C | C | C | I | |
| Cross-product sequencingWhich product gets attention when; one release lane at a time | A | R | C | |||||||
| Pricing and paid-tier decisionsPrices, tiers, what's paid vs free | A | C | R | C | C | C | ||||
| Building and shipping | ||||||||||
| Building features and fixesCode, tests and local commits | I | I | A | R | C | |||||
| Quality review before releaseUX/UI audit and release checks | I | I | C | C | A/R | |||||
| Commits, pushes and deploysOnly after the Studio Owner's OK | A | R | C | R | ||||||
| Stores and compliance | ||||||||||
| Store listings and review answersApp Store and Google Play | A | I | C | R | C | C | ||||
Excerpt with sample rows · the full page has every kind of work
02 · Operating cadence
I invented a handful of lightweight protocols so status flows up without anyone chasing it. Each one has a fixed shape, so the Program Manager can roll every message into one picture of the studio.
Whenever work moves (planned, building, checked, blocked), the agent sends the Program Manager a short update in a fixed format: what moved, what’s next, what’s waiting on me.
If I talk to an agent directly instead of through the Program Manager, that agent files a note with the Program Manager. Shortcuts are fine; losing the thread isn’t.
I can ask every Product Advisor for a check-in at once. Each answers the same four questions: done, doing, blocked, needs a decision.
What changed, what’s unsaved, what’s waiting. Nothing gets stranded between one working session and the next.
Releases follow written steps with gates. An agent can’t skip a gate, and the runbook records who cleared each one.
Onboarding redesign moved Plan → Build. Both platforms in this pass. Waiting on Studio Owner: nothing.
Studio Owner asked me directly for a small-phone audit of Product A onboarding. Logging it here so the roadmap stays whole. Finding: spacing fails on the first screen.
Done: crash fix checked on both platforms. Doing: Release 2.4 proposal. Blocked: none. Needs a decision: none.
Gate 5 of 7, quality review, in progress. Next gate: Studio Owner sign-off.
Changed: 3 records. Unsaved: none. Waiting on you: 3 decisions, 3 actions.
03 · Reporting
The Operations Command Center is a local web app I designed to run the studio from. It turns the stream of updates into an executive summary I can act on in minutes, and it shows what every agent is doing right now.
Prioritized decisions with a recommendation, prioritized actions, progress told product by product, roadmap progress for the week, risks, issues and deadline countdowns. Any item opens its context.
Who is waiting on my direction, working, idle or not running; each agent’s model and current task; and what’s waiting on me, ranked by priority.
Context use per agent against a written compaction policy, so no agent compacts mid-change.
Tokens and estimated cost per agent and per day by model, plus how much of each agent’s open time went to real work.
A chat drawer to message the Program Manager without leaving the dashboard.
Everything in the demo is invented sample data and runs entirely in your browser. The real command center runs locally and isn’t public.
04 · Execution
The same path for a new feature or a one-line fix. Every hand-off goes to someone who didn’t do the work before it, and nothing ships until I’ve signed off.
Something I want, or an issue a user reports. The Program Manager routes it.
A brief: the goal, what done looks like, what not to touch.
Both platforms in the same pass, with automated tests on each.
Checked against the actual code, not the Product Engineer’s summary of it.
A UX and UI audit against the studio’s quality bar.
I review the checked, tested work and say yes or send it back.
Store steps follow the runbook and a compliance review; I submit.
05 · Governance
Releases, store submissions, new paid services and anything involving access wait for my explicit yes.
I create, store and rotate every credential myself. No agent reads, writes or prints one.
One agent can’t authorize another by quoting me. Approval comes from me directly, every time.
The Program Manager audits agents against studio rules. Every break goes into a compliance log with its fix, so the rules get sharper over time.
Marketing and campaign agents stay idle until I kick a campaign off, and any budget they propose comes back to me.
Context use and estimated cost are visible for every agent, and a written policy decides when an agent compacts its memory.
Why it matters beyond the studio
None of these ideas are new to enterprise program work. What’s new is designing them for a team of AI agents: a team that starts each session without yesterday’s memory unless the system provides it, and does exactly what the operating model allows.
Co-Founder & Principal — The “human in the loop” at moonshinerXwerks LLC
John is a senior program manager with over 20 years of experience leading enterprise programs across PMO design, process optimization, commercial excellence, and global customer implementation. He spent a decade at Expedia's Egencia division, progressing from reporting and analytics through global implementation management to program leadership — overseeing Fortune 500 client delivery, consolidating regional teams into a unified global PMO, and earning a President's Club Award for onboarding $195M+ in annual new business revenue.
His career spans enterprise transformation and product-driven delivery at every scale: directing cloud migrations and SaaS platform rollouts, leading product development initiatives to improve SaaS usability and drive adoption, spearheading internal commercialization efforts that aligned product capabilities with go-to-market strategy, and managing Salesforce CRM integrations and commercial excellence programs across multiple organizations.
moonshinerXwerks is where all of that converges — an independent software studio applying 20+ years of enterprise discipline to consumer product development. Every app is taken from concept through release with full ownership of product strategy, feature delivery, privacy architecture, and commercial model. The full product lifecycle is managed using agile delivery, structured change analysis, and AI-enabled tooling — while also owning all supporting operations including legal compliance, hosting infrastructure, and CI/CD pipelines.
Based in Bend, Oregon. Usually found on a river when not managing the next product through development and delivery.
Whether it's about one of our apps, a partnership idea, or just to say hello.
Contact Us →