I. The Blueprint · II. The Install · III. The Brain
Quarter to quarter. A record of every key decision, reviewed each month.
The brain keeps a current record of your key decisions: what was decided, the reasoning behind it and the outcome. Once a month we review how those decisions were made and what to change across the operating system.
Built alongside your COO or ops lead, inside the cadence you already run.
One decision, start to finish
[[decision-record]]
A weekly launch meeting approves a new packaging run. The brain records who owns the decision, the information they had and what they assumed about supplier lead time. When the run lands late, the outcome comes back to the monthly review beside the original decision.
Illustrative workflow. The sources, dependencies and decision owners are agreed during the Install and tested before the Brain goes live.
What the monthly review looks at
A good outcome alone doesn't establish a good decision. Each month we review the key decisions against five things:
- The information available. What the owner knew when they decided, and what was missing.
- The assumptions. What they took as given, and whether it held.
- Ownership. Whether the right role made the call, and who was left waiting on it.
- Timing. When it was made, against when it was needed.
- The result. What happened next, and how much of it the decision explains.
From that, the review recommends changes across the operating system: a meeting to add or cut, an owner to change, a number to start measuring.
TAO · THE BRAIN'S THREE STANDARDS
Trusted
Your records stay in your own GitHub. Each person sees only what their clearance allows, and the brain touches only what your admin approves. Your data never trains public models.
Accurate
Every answer names the meeting or number it came from. Numbers are pulled from the system that holds them, and the brain is checked against questions with known answers.
Open to any model
Run it on the AI model you choose. When a better one arrives, switch without rebuilding.
Built on your existing software, the brain reads everything against your two blueprints, so it knows how work moves today, how it should move, who owns each decision and where friction builds. It chases status, drafts replies and preps meetings, so your people spend their time on the work only they can do.
BEFORE IT GOES LIVE.The brain needs the operating system underneath it. It is built during the install and proven on a silent run and a backfill before anyone relies on it.
How we think about AI
AI on top of a messy workflow scales the mess. The Parallax Process fixes how information moves first, then installs an AI brain to close the gap between ideal and actual ops. Your people keep the decisions.
Signs you need one
- Your calendar is a list of people's blockers
- A week away costs two weeks of prep
- The team is strong, but you're still necessary for delivery
What it does
- The decision record. Every key decision with its owner, the information it was made on, the assumptions and the result.
- Ask it anything. Any question about your department, answered from its own files with the sources named.
- Dashboards. One per person: messages sorted, replies drafted, and what is waiting on them.
- The executive view. One view of the whole company. Correlations between departments show up here and nowhere else.
- The monthly review. The month's key decisions: how they were made, what happened next, and what we'd change across the operating system.
- Flags. A decision that stalls, a number that goes missing, a meeting that repeats.
Kept current as your company grows
Your subscription includes the upkeep of the brain we installed, alongside your ops lead:
- The sources. We maintain the agreed connections to your approved tools and the records coming into the brain.
- The operating context. We update its standing files as your goals, decision owners and operating rhythms change.
- The workflows. We check sourced answers, meeting preparation and status follow-ups against known examples, and maintain the agreed workflows as your tools change.
Your monthly review shows how decisions were made, where work is drifting from the ideal state and what to change next. We agree the connections and workflows before the brain goes live. New departments, integrations or workflows are scoped separately.
What it reads
Meta Ads, Google Ads, TikTok Ads, Amazon Ads, Shopify, Northbeam and Klaviyo on the demand side, Cin7 and NetSuite on the supply side, plus your meetings and Slack. Each department's brain connects only the sources that department uses.
What it measures against
THE IDEAL STATE, DRAWN IN THE BLUEPRINT.Your ideal state is one of the two blueprints we draw from your team's interviews. It sits beside your actual state, your strategy and your current OKRs as a standing file, and once a month the brain measures the work against it and reports how much of the gap has closed.
The monthly review
It surfaces the decisions that are hard to see from inside the week. From a sample report, month three against the day of the install:
FROM THE DECISION REVIEW
DECISIONS ESCALATED TO THE FOUNDER
12 → 5
AT INSTALL → MONTH 3
DECISIONS WAITING ON SIGN-OFF
9 → 4
AT INSTALL → MONTH 3
DECISIONS WITH NO OWNER
3 → 0
AT INSTALL → MONTH 3
Illustrative numbers from a sample report.
Terms
Quarter to quarter. Stop at the end of any quarter. The brain is installed one department at a time, so you can start with one and add the rest. Each month you get a decision review with our advice on what to change next, which keeps the company accountable to its ideal state.
What stays yours
Both blueprints. The files, in plain markdown in your own repository. The record of every decision and commitment with its date, owner and outcome. Stop the subscription and everything captured stays with you. The dashboards, the monthly review and our advice stop, and you can restart any time.