Delight before a form.
Start a game as a guest. Let a satisfying first session explain why someone might want to save more later.
The product plan / September 30, 2026
A small controller.
A whole place
to go.
Make the object on your desk a reason to play, a way to say something, and a little part of your day.
An independent PointCast product. A living plan, with evidence before expansion.
01 / THE DIRECTIONA focused starting point
Become the place
owners actually use.
Our first customer is a Codex Micro owner who likes the hardware and wants more satisfying things to do with it.
The job: “Give me something worthwhile to do in a few minutes, make my controls work, and remember where I left off.” Ordinary keyboard and touch players can join immediately. Other controller owners are a next audience, with compatibility earned through testing.
Our ambition is to become the most useful independent destination for this community. We have not established market leadership, an owner count, or product-market fit.
A reason for every control.
Tune with the dial. Navigate with directions. Make rhythm with pads. Design around a physical action people enjoy.
Trust is a feature.
Say which setup was tested. Label local progress honestly. Make sound, sharing, and physical signals deliberate choices.
The competitive opening. Work Louder already covers configuration; Elgato and Logitech have plugin ecosystems. Playdate and PICO-8 show the value of a recognizable creative format. Our strategic inference: combine edited short-form play, reliable owner support, and expressive signals around one shared control vocabulary. Read the dated evidence →
02 / WHAT WORKS TODAYThis release / October 2026
A real destination.
A clear starting line.
Explore the club without registration. Keep the distinction between browser-local features and shared services visible.
New adventure
Lantern Route
Three night deliveries. Gather parcels, work the gates, find the way through, and light the final beacon. Seeded routes and progress saved in this browser.
In this releaseThe game library
Six games in one searchable, filterable place. Find a mood, revisit a favorite, or pick up a recent game.
In this releaseToday’s circuit
A daily three-game V2 circuit. A small, finite invitation to return, with progress kept in this browser.
Browser-localYour Passport
A personal record of play and discovery. Favorites and progress belong to this browser; this is not a public account or verified rank.
Shared serviceSignal Rooms
People and agents can exchange messages and visual signals through a private invite. Computer sound and speech are opt-in.
Setup & supportMake it work
Understand key mappings, test inputs, and find the optional macOS light bridge. Physical lighting needs its guided visual check.
Downloadable researchThe owner field guide
A sourced market report, the original V2 PRD, and a transparent product roadmap you can inspect.
Still ahead: cloud accounts and sync, public profiles, moderated contributions, verified competitive rankings, vendor plugins, and paid plans. Signal Rooms are invite-based rooms, not a public social network. No manufacturer partnership or hardware ownership verification is implied.
03 / WHY COME BACKLoops to validate, not engagement claims
Build a habit
worth having.
A good return visit offers a clear choice, a satisfying finish, and permission to leave. More time on site is not the goal.
- A
The first-minute loop
Choose a game → try a control → get a clear response → finish a short round.
We learnCan a newcomer reach the fun without help? - B
The daily loop
Open Today → complete a three-game circuit → see personal progress → return for another set.
We learnDoes the invitation still matter after the novelty? - C
The together loop
Share a seeded challenge or private room → receive a response → create a small shared ritual.
We learnDoes a second person make the experience better? - D
The owner-to-maker loop Next
Solve a setup problem → save a tested recipe → contribute a tiny experience → earn visible credit.
We learnCan contributors add quality with a small support burden?
04 / THE NEXT 90 DAYSOutcome gates, not feature promises
Earn the next
level of ambition.
Work in small releases. Each release needs a working result, a test, and a decision about what the evidence changes.
01
FIRST 30 DAYSTarget review: October 30, 2026
Prove the first visitMake the club easy to start and worth returning to.
Polish discovery, the daily circuit, personal progress, and setup. Establish a privacy-respecting measurement plan and observe real first-time sessions.
Acceptance to move forward
- All six games are reachable by keyboard and touch; pause, sound, and storage failure paths remain usable at 320 px.
- Observe 10 first-time sessions: at least 8 reach a completed short round within three minutes without moderator help.
- Publish a dated support matrix with exact device, OS, connection, and firmware evidence. Mark untested combinations clearly.
- Define events and consent before collecting pilot behavior. Record a baseline and report the sample, exclusions, and uncertainty.
If it misses: fix the dominant activation failure before adding another destination or account requirement.
02
DAYS 31–60Target review: November 29, 2026
Prove the returnAdd depth, then make a shared ritual.
Ship an edited mini-season or adventure path with meaningful variation. Test private challenge rituals, collect reasons to return, and prepare a bounded sponsor offer.
Acceptance to move forward
- Run a consented 20-person pilot. At least 6 return for a completed game in days 7–13 after activation; publish the exact denominator.
- Release one replayable adventure or weekly collection with saved progress, a satisfying end, and reduced-motion support.
- At least 4 of 10 participating pairs use a Signal Room or shared challenge on two different days.
- Prepare one clearly labeled sponsored-circuit concept, placement rules, measured audience summary, and a delivery-cost model.
If it misses: interview returners and non-returners; revise the content promise before increasing acquisition or building billing.
03
DAYS 61–90Target review: December 29, 2026
Prove a small businessTest one offer people can understand.
Select a sponsor pilot or a paid owner collection based on observed demand. Pilot a small creator contribution format and investigate optional sync through existing PointCast identity.
Acceptance to move forward
- For a commercial pilot, document the exact deliverable, price, fulfillment, disclosure, support, and refund terms before any sale.
- Report revenue received separately from interest, proposals, and booked revenue. Report direct costs and contribution per delivered pilot.
- Three invited maker prototypes meet the same input, accessibility, licensing, and performance checks as first-party games.
- Only ship accounts if repeat users need portable progress; reuse PointCast identity and prove authorization, export, and deletion.
If it misses: keep the core free and useful. Rework the offer; do not add subscriptions to compensate for weak retention.
05 / A BUSINESS WORTH BUILDINGCommercial hypotheses / no paid offer is live
Revenue follows
a useful relationship.
The scalable asset is an engaged audience with a recognizable play format, useful setup knowledge, and trusted distribution. We need to prove each part.
Make house inventory work.
The existing PointCast campaign introduces the club. Test destinations and creative against completed first play, not just clicks.
Decision gate Measure referred starts and completions with an explained, minimal data policy. No paid acquisition until activation works and delivery costs are understood.
A sponsor can fund a good week.
Offer one edited challenge or mini-season with visible sponsor credit and a useful owner takeaway. The sponsor buys a defined experience; reach must come from measured data.
Decision gate Validate the offer in five qualified partner conversations and seek two nonbinding expressions of interest before building a repeatable sales package. Outreach is a separate, deliberate activity.
Sell a collection worth keeping.
Test a finite premium collection or advanced owner utility after people return to the free club. A one-time collection may fit better than a subscription.
Decision gate Interview 10 repeat users about specific paid benefits. Then run one transparent offer test with real fulfillment and support. Interest is not revenue; renewal requires recurring value.
SPONSOR PILOT / PROPOSAL ONLY
Count the work before pricing the week.
A $500 sponsor pilot and a $9 owner collection remain research hypotheses, not quotes or agreed prices.
The seven-day pilot brief now has a playable, clearly labeled PointCast house sample. Actual audience, delivery costs and contribution are unavailable. The cost planner requires explicit estimates instead of filling unknown costs with zero. Modeled contribution includes valued internal time; it is not cash received or profit.
HYPOTHESIS / NO PAID OFFER$500Planning fee only.
Scope and price need agreement.
Scope and price need agreement.
Unknownactual delivery cost
Unknownactual contribution
Scale only what works. Expand to adjacent controllers after support costs and compatibility are known. Expand the catalog after repeat use. Add recurring plans after recurring value. No revenue forecast, sales commitment, paid subscriber count, or sponsor relationship is claimed here.
06 / THE SCORECARDProposed targets / baseline not established
Measure a
worthwhile return.
The north star is a person who comes back and completes something satisfying on another day.
Track weekly returning players in an explicitly consented pilot: participants who complete a game on at least two distinct days within a seven-day window. Pair behavior with “Was that worth your time?” No target below is an observed result or an industry benchmark.
The current Passport is browser-local. It is not a sitewide analytics system, an account identity, or a reliable way to count people across devices.
The optional play pilot now measures consented visits, starts, engaged finishes, daily circuits, and return in days 7–13. It is off by default, excludes QA, and withholds small samples. A working collector is not an audience baseline. The proposed weekly north star and moderated setup targets still require separate evaluation.
A satisfying first session
Observed newcomers finish a short round within three minutes, without moderator help. Start the clock at the club landing page.
A reason to return
Activated pilot participants complete a game in days 7–13 after their first completion. Keep non-returners in the denominator.
A circuit worth finishing
Consented participants who start Today complete its three games that day. Record interruption and setup failure reasons.
A shared ritual
Participating pairs exchange a response or replay a shared challenge on two separate days. Count pairs, not messages sent.
These are small-sample learning gates, not statistically proven demand. Report counts with percentages, cohort dates, recruitment source, device mix, and exclusions. Pause interpretation if event loss or selection bias makes the result unreliable.
07 / REPLACE THE BIGGEST UNKNOWNSResearch plan / recruitment not completed
Watch the first press.
Ask about the second visit.
Begin with real behavior. A small, explicit research program is more useful than a large set of untested features.
16 short setup sessions
Recruit eight Micro owners, four owners of adjacent controllers, and four ordinary keyboard or touch players. Record exact device and software versions with consent.
- Ask them to find a game, start a round, pause, change sound, and recover from one mapping issue.
- Time the first meaningful response and first completed round.
- Ask what they expected the physical controls to do before explaining the design.
A 20-person diary pilot
Recruit a separate or clearly identified overlapping cohort for 14 days. Use voluntary short check-ins and an explained event plan.
- Ask what brought them back, what interrupted play, and which experience they would miss.
- Interview both returning and non-returning participants.
- Separate content fatigue, setup friction, and lack of a useful daily context.
Test a concrete offer
Show a finished sample, its proposed price, and exactly what is included. Compare sponsor interest with owner willingness to pay.
- Do not turn positive feedback into a sales forecast.
- Document the alternatives people use today and the work they expect us to replace.
- Choose one commercial experiment; keep the core product open while learning.
Open decisions that research should settle
- Depth or variety: do returning owners want mastery in three games or a wider changing collection?
- The useful signal: is the strongest message a friend’s hello, an agent finishing work, or a shared play moment?
- Portable identity: does cloud sync solve an observed problem, and what do people actually want saved?
- The business customer: who values the audience and experience enough to pay for a concrete, repeatable offer?
- Support burden: which controller/OS combinations can we support consistently at a sensible cost?
08 / EVIDENCE & READINGSource snapshot / September 29, 2026
Built on research.
Open to being wrong.
The observations below come from the dated market report. They are not a fresh audit of current offers, prices, stock, or platform policies. The product choices drawn from them are PointCast hypotheses.
Configuration already has a home.
Work Louder documents Input setup and layers. Elgato and Logitech document developer routes. The implication is to add owner experiences and tested support, rather than compete solely on remapping.
A recognizable creative format helps.
Playdate combines development tools with edited game releases. PICO-8 connects a constrained creation format with playable carts. The inference for Micro Club is to create a common input vocabulary and an edited release rhythm.
Adjacent demand is not our demand.
Playdate’s historical Catalog report describes its own ecosystem. It cannot establish Micro’s installed base, retention, or spending. Those remain questions for this product’s research.
Playdate Catalog report · May 2, 2024Market report interpretation
THE SEPTEMBER FIELD GUIDEThe small controller market Read online / PDF availableTHE ORIGINAL REQUIREMENTSMicro Club V2 PRD September 29 baseline / PDF available
This October 1 operating plan updates product priorities and shipped/planned boundaries. The original PRD remains a dated record and may describe features that have since shipped. This page contains no visitor analytics or data collection.
THE NEXT GOOD THING STARTS WITH A PRESS.