The Orbit story
The operating system every Averian company runs on.
Orbit is Averian's internal operating platform. Structured workflows, reusable capabilities, and institutional memory that compound across every venture the studio builds. Not for sale — the value to other builders is the methodology, which we share openly.
What Orbit is.
Orbit is the studio's working memory. Every observation a product surfaces, every decision a founder makes, every outcome a venture measures — Orbit captures the shape of it so the next decision, the next product, and the next founder conversation start with more context than the last.
It uses structured workflows to keep observation, decision, and measurement connected. It uses AI where AI genuinely helps: structured retrieval, drafts and recommendations, pattern-matching across ventures. The strategy, the customer conversations, and the final call stay with the founders.
Orbit is not autonomous. It doesn't run the company. It makes founder judgment observable, portable, and reusable — which is what compounds.
The loop
Observation to reuse, on repeat.
Orbit runs a continuous seven-step loop. Each stage feeds the next; the last one feeds the first.
01
Observe
Signals from customers, markets, product analytics, and the studio's own operating data.
02
Capture
Observations become structured records, not scattered notes. Retrievable across ventures.
03
Decide
Recommendations and drafts assist. Founders make the call and record the reasoning.
04
Build
Execution runs through reusable capabilities: content, workflows, growth loops, integrations.
05
Measure
Outcomes tie back to the decision that produced them. No blind experiments.
06
Learn
Signals from measurement update the institutional memory the next decision draws from.
07
Reuse
Proven capabilities harden into templates the next venture starts with.
The loop makes the studio's knowledge cumulative. What one product learns doesn't stay inside that product; it becomes structure the next venture can pull from on day one.
What compounds
Reusable capabilities.
Four things carry across every venture the studio operates. Each one starts as a product need, hardens through use, and becomes a template the next venture starts with.
Institutional memory
Structured records of every meaningful decision, its context, and its outcome — retrievable across every product the studio operates.
Reusable capabilities
Content systems, growth measurement, workflow automation, recommendation logic, and integration patterns built once and reused across ventures.
Decision documentation
Recommendations, evidence, and outcomes captured together so founder judgment is legible and revisitable.
Cross-venture pattern-matching
Signals from one venture inform decisions in the next. What worked for one audience becomes a hypothesis for another.
Products don't just consume Orbit.
They improve it. A growth pattern proven inside First Year Credit — structured content that performs well against AI search and traditional search alike — becomes a capability the next venture can adopt on day one. An operator workflow refined inside Laudvi — a review-response drafting-approval loop that actually gets used by a business owner — becomes a template every studio company can reach for.
This is the point of the studio model. Each venture is its own business, but the capabilities compound across all of them.
What founders still do.
The promise is not that AI replaces founders. The promise is that AI and structured workflows replace enough of the day-to-day execution that founders can spend their time on the choices that only humans should make.
Things Orbit handles.
- Structured retrieval of prior decisions and outcomes.
- Drafts and recommendations for founder review.
- Workflow orchestration across the venture lifecycle.
- Pattern-matching across ventures.
- Documentation of what shipped, when, and why.
Things founders still do.
- Strategic decisions (which product, which audience, which positioning).
- Approval at every meaningful gate.
- Pricing calls.
- Positioning and brand voice.
- Customer empathy and product-market fit judgment.
- Trust commitments — which promises, which partnerships.
Methodology, shared
The patterns we use.
Eight institutional patterns Orbit has codified through real shipping. Useful to any team building on similar terrain.
01
Schema discovery first
Every slice queries information_schema before writing migrations. Never invent column names.
02
Append-only history
Recommendations and outcomes get new rows, never UPDATE. You can audit what the system suggested last Tuesday.
03
Strict false plus Zod
Anthropic strict mode rejects integer bounds; Zod is the actual validation gate at the runtime boundary.
04
ASCII-only commits
No smart quotes, em-dashes, ellipses. PowerShell and git compatibility, every time.
05
Founder-gated invocation
Every automated recommendation surfaces to a founder before it acts. Multiple checkpoints prevent accidents.
06
RLS three-policy pattern
SELECT via current_site_ids(); INSERT/UPDATE via has_site_role(site_id, ...). Consistent across every site-scoped table.
07
Service-role client for runner and admin paths only
Never the SSR cookie client for privileged work — it silently forwards user JWT and breaks service-role intent.
08
One site per product
Each venture is a site_id in Orbit's DB. RLS scopes everything. The site selector switches context.
Watch the studio build.
Orbit is not for sale. Its value to the studio is operational; its value to other builders is the methodology — which is why we share it. Updates capture selected decisions, milestones, and lessons as they happen.