Potent software shelf

Build what is missing. Prove it in the real world. Graduate what earns it.

This is the front door for Potent products, shared capabilities, utilities, labs, and product lineage. Useful software does not need a fake promotion: each piece stays at the maturity it has earned, and capabilities only become separate products when the evidence gives them a reason to exist.

Two labels. Two different truths.

Access tells you how to enter. Maturity tells you what the software has earned.

Open

There is a public entry point you can use now.

Account

The useful experience starts after sign-in or an invited account or household setup.

Preview

You can inspect or try a working build without treating it as a production commitment.

Private

Potent retains the work, evidence, or lineage without exposing a public entry point.

Live

Supported for its intended current use.

Pilot

Real-world use is deliberately bounded and monitored.

Working Build

Interactive proof of a real workflow, still earning production status.

Lab

A hypothesis or prototype still earning its shape.

Vaulted

Useful lineage or IP kept intentionally out of active product work.

Retired

Superseded on purpose rather than left to become zombie software.

Access, maturity, pricing, source availability, and support are separate decisions. The shelf is meant to make the current state clear rather than inflate an experiment into a promise.

Game night

Potent Games

Original party games and social experiments built to get people looking at each other instead of babysitting a host screen.

See the Potent Games shelf →
Open

Potent Games

BLARKUS

Nonsense for modern times.

A phone-first game-night ringmaster for solo play and 2–8 player rooms. Blarkus mixes verdicts, reaction games, scoring, commentary, sound, and unnecessary confidence while nobody has to volunteer as host.

PaceSetter edge

The software performs the host role itself: authored character, room-aware pacing, voice, scoring, and mechanics that change with the people actually playing.

Boundary

Not a generic trivia deck, room-code wrapper, or collection of mini-games with a chatbot pasted on top.

Product · Lab

Open →
Private

Potent Games

Walker MacDanger

Bad decisions required good friends.

The private party-game prototype that proved multiplayer rooms, duels, verdicts, challenge rounds, turn awareness, and produced-character experiments before the strongest ideas moved into Blarkus.

Lineage · Vaulted

No public entry
Private

Potent Games

House Rules

The early live-room engine.

An earlier family party-game direction that helped establish the live-room foundation. It is retained as product lineage rather than offered as a separate public game.

Lineage · Retired

No public entry

PotentONE

Business & Operations

Working capabilities for bookings, staffing, ordering, venue operations, dashboards, and the handoffs between them. A capability only becomes a separate product when the evidence earns it.

PotentONE overview →
Preview

PotentONE

The Fixer

Bookings, clients & follow-up.

A working service-business flow that keeps availability, booking context, reminders, work status, cancellation recovery, and follow-up in one place.

PaceSetter edge

It owns the messy handoff from request to booked work to recovery and follow-up, where small service businesses usually lose context.

Boundary

Not a Booksy-style marketplace or a reason to replace a calendar, payment tool, or CRM that already works.

Capability · Working Build

Open →
Preview

PotentONE · Food & Events

The Kitchen

Orders, menus, queues & ready alerts.

A mobile ordering and kitchen-flow build for food trucks, events, and rush periods, with menu controls, sold-outs, queue state, and customer-ready handoffs.

PaceSetter edge

It keeps the customer promise and the kitchen queue synchronized through rush-state changes, sold-outs, readiness, and pickup handoff.

Boundary

Not a Toast or Square replacement. Payments and POS stay where they belong when a focused ordering handoff solves the actual problem.

Capability · Working Build

Open →
Preview

PotentONE · Venue Operations

The Hideout

Bookings, guests, service & play time.

A venue operations build that connects booking, check-in, active sessions, staffing, food service, and guest activity without pretending every existing vendor system needs replacement.

PaceSetter edge

It makes the guest's active Visit coherent across booking, arrival, play, service, staffing, and the exceptions between those systems.

Boundary

Not a venue-management monolith. It connects the seams and preserves source-of-truth systems instead of rebuilding them by reflex.

Capability · Working Build

Open →
Preview

PotentONE · Venue Operations

The Capo

Staffing, shifts & team communication.

A team-operations build for schedules, clock events, assignments, breaks, callouts, coverage, timecards, and shift handoff.

PaceSetter edge

It focuses on live coverage and shift handoff: who is here, what changed, what is uncovered, and what the next person needs to know.

Boundary

Not HR, payroll, benefits, or workforce compliance software. Those systems remain authoritative when required.

Capability · Lab

Open →
Preview

PotentONE · Venue Operations

Bird's Eye

Operations overview & exceptions.

An owner and manager view designed to surface bookings, staffing, orders, and operating exceptions without forcing somebody to hunt through every underlying system.

PaceSetter edge

It prioritizes exceptions and next actions across systems instead of making an owner interpret a wall of disconnected dashboards.

Boundary

Not another source system or vanity BI dashboard. It should point back to authoritative records and make uncertainty visible.

Capability · Lab

Open →
Private

PotentONE · Venue Operations

Next Round

Service-continuity DNA, folded into stronger workflows.

A vaulted restaurant and bar workflow experiment. Its useful repeat-round, table-context, and human service-handoff patterns are preserved inside The Hideout and The Kitchen instead of carrying a separate roadmap.

PaceSetter edge

Useful DNA remains in preserving service continuity across table, guest, order, and staff handoff without forcing a POS replacement.

Boundary

No standalone roadmap while incumbent hybrid-tab workflows already cover the original thesis. Reopen only when a genuinely new seam is proven.

Capability · Vaulted

No public entry

The shelf will keep moving

Some ideas become products. Some become capabilities. Some get folded into something better.

Potent does not need to pretend every experiment deserves its own subscription. The useful work is finding repeated friction, proving a meaningful advantage, keeping the strongest parts, and knowing when a separate product has earned the right to exist.