Office Studio
Building the studio as its own first operating system
- Entrance and website
- Qualification flow
- CRM structure
- Prospect research
- Enquiry triage
- Proposal workflow
- Content loop
Work
Products and the systems behind them
These are products and systems PJ Roch designed and built before and alongside Office Studio. They are not client commissions. The product demonstrations show the customer experience; the systems below show the work behind it.
Product demonstrations
driftspeak
A spoken-audio product, with a repeatable production system behind it.
Nemolines
A line-learning interaction built around first-letter recall.
zinepic
Three photographs become a page of a zine; pages collect into issues.
Todext
A private memory of the people you keep: one typed sentence becomes a reminder, a plan or a date.
AMES Pool
One table, one red eight, one marked pocket: aim, pull and release in one motion.
Team tools and operating methods
These are systems PJ Roch designed, built and operates himself. They show the method: founder judgment encoded into workflows, tools and bounded AI systems that keep operating without constant founder involvement.
A governed content system
A governed content system that lets a part-time operator create on-brand output without constant founder review
- Closed format schema
- Brand refusals enforced as the operator types
- Templates the operator cannot rewrite
- A month of briefs seeded
- Publishing loop verified in production
A decision-led operating system
An open-source decision ledger, memnant, built to keep product decisions, constraints and supersessions intact across long-running AI-directed work
- Decisions persist across sessions
- Supersessions are explicit rather than silently overwritten
- Current canon stays distinguishable from historical decisions
- Humans and AI agents can work from the same current decision state
- Built and used across the studio’s own product estate
Implementation notes and other formats
These are production systems and live formats rather than software a team logs into. They are here for how they were built: the constraints, the checks and the repeatability.
Driftspeak
An automated production system for atmospheric language audio
- Structured content generation
- Text-to-speech production
- Evaluation loops
- Quality control
- Repeatability
- Low production cost
Zinepic
Turning three photographs into a constrained publishing system
- Fixed input structure
- Deterministic layout
- Mobile publishing
- Taste through constraint
Todext
Turning a typed sentence into a reminder, a plan or a date, with no server behind it
- A rules interpreter reads each entry as it is typed
- Dates, reminders and follow-ups extracted on the phone
- A ranker suggests at most one person a day, or stays quiet
- No account, no analytics, no Contacts permission
- Sync through the owner's own iCloud, end-to-end encrypted
- Every word exportable as a readable file
AMES Pool
Turning a pool night's format into a one-frame-a-day game, with every frame proven before it ships
- Deterministic physics, a run is a pure function of its seed
- Every published frame proven to clear across a full degree of aim
- Golden fixtures written by one tool and checked in CI
- Six colours and two typefaces, carried from print to screen
- A ball sheet as law, ball 13 looks like ball 13 forever
- Two-shot visits, one per partner
LINECONIC
Turning a game mechanic into a repeatable live operating format
- Rules
- Participant flow
- Scoring
- Repeatable event operations
- Physical and digital assets
Every one of these began as something done by hand, and ended as something that runs.