Loading tenant-scoped operating graph and approval evidence.
From idea or prototype to a testable v0, before you spend too much on a full MVP.
You do not always need a full app first. Most early projects need to understand whether they are still at prototype stage, ready for a v0, or actually ready for an MVP. The Autonomous Company Studio helps selected founders and operators clarify the next step, build a small testable version, and learn from real users before investing in a heavier product.
Where are you really?
A lot of projects fail because they jump straight to a full MVP or native app before validating the first user loop. We help you decide what stage you are really at.
A prototype helps people understand the idea. It can be a clickable maquette, simple demo, fake flow, landing page, or early no-code version.
Best question: Do people understand the concept?
Good for
Not for
A v0 is a small usable version that real users can test. It is not the final product. It is built to validate one core loop before adding more features.
Best question: Do people actually use it, come back, or ask for more?
Good for
Possible formats
An MVP is a more stable first product with enough real functionality to validate the product more seriously. It usually comes after a useful prototype or v0, not before.
Best question: Is this ready for broader launch or deeper investment?
Good for
A native App Store version usually comes after enough proof from the v0 or MVP. Otherwise, you risk spending a lot before knowing what users actually need.
Most early projects should not jump straight to a full native app. Start with the smallest version that can answer the riskiest question.
Ways to start
A staged, application-based path. Studio steps are kept separate from CompanyOS Pricing & Deployment.
High-level review
Share your current link, maquette, feature document, or early prototype. We look at the project at a high level and tell you whether the next step looks more like a prototype, a v0, or an MVP.
Free, limited review
Includes
This is not a full written product audit or build plan.
Show us what you haveStructured plan
For founders who want a clearer written plan before building: what to test first, what to remove, what the core feature should be, and what should wait.
Optional paid plan
Includes
4 weeks
For selected projects ready to build a small testable v0 and test it with real users. It builds a testable v0, not a full native App Store app.
From €900-€1,200 for 4 weeks + usage costs
Includes
After validation
If the v0 shows strong enough signals, the next step can be a more complete MVP, a native mobile app, a larger build, or a longer-term studio partnership.
Scoped after validation
Discuss next stepStudio offers are kept separate from the main CompanyOS pricing cards.
What we need to understand first
Before recommending a build path, we need to understand what already exists, what has been tested, and where the current solution breaks.
What have you already built?
Figma, no-code tool, Lovable, Bubble, FlutterFlow, Bolt, v0, Framer, custom code, or something else?
Is it clickable or usable?
Is it only a maquette, or can users actually try something?
Does it store data?
Are there accounts, user actions, profiles, or feedback captured somewhere?
Who tested it?
How many users tried it, and what did they say?
What is the core action?
What is the one thing users should do again and again?
What is the first user loop?
For example: join → choose goal → take action → share proof → get feedback → come back.
What is the monetization hypothesis?
Free, premium, sponsorship, B2B later, events, marketplace, or something else?
Is a web/PWA/mobile-like v0 acceptable first?
A native app can come later if the v0 proves enough.
Confidentiality and NDA
The first application should stay high-level. Please do not submit highly confidential materials, customer personal data, trade secrets, passwords, or sensitive documents in the initial form. Share only enough for us to assess fit.
If there is a fit and deeper review is needed, we can use a lightweight mutual confidentiality agreement before reviewing detailed documents, prototypes, user research, or business plans.
If a paid pilot starts, the scope will include confidentiality, ownership, usage costs, exclusions, and the distinction between your project assets and our builder/platform assets.
Initial application:
No NDA. High-level only.Detailed review:
Optional lightweight mutual confidentiality agreement.Paid plan:
Short terms with confidentiality.Builder Pilot:
Written scope with confidentiality, IP, platform ownership, usage costs, and exclusions.Studio Partnership:
Full agreement covering revenue share, ownership, reporting, confidentiality, and termination.What this is not
The Studio is designed to reduce wasted build cost by testing the smallest useful version first. If the first workflow cannot attract users, feedback, or revenue signals, we stop or rethink before building more.
Ownership
You keep your idea, brand, content, documents, user/customer relationships, and project-specific materials. LSSM keeps its builder, platform, CompanyOS/ContractSpec stack, reusable components, templates, workflows, methods, and generalized learnings. Any project-specific deliverables, licenses, revenue share, or ownership terms are defined in the signed pilot or studio agreement.
Operating company labs
The Studio is connected to the broader Autonomous Companies vision. Some projects may become operating company labs: real domains where CompanyOS patterns are tested before becoming reusable workflows, contracts, and modules.
Field operations and case-file workflows — Axoperf is an early field-operations proof domain around case files, dispatch queues, document checklists, technical handoffs, audit trails, and field progress. It helps validate how governed operating loops behave in a vertical operating context.
Proof domains, not packaged Solutions
Operating company labs are not packaged CompanyOS Solutions. They are proof domains that inform reusable workflows and modules.
Show us what you have
Share your current idea, maquette, prototype, or product link. We will use it to understand whether your next step should be a prototype, a v0, or an MVP.
Please do not submit highly confidential materials, passwords, sensitive personal data, or customer lists in the initial form. Share only enough for us to assess fit. If deeper review is needed, we can use a lightweight confidentiality agreement before going further.
We review projects based on current stage, workflow clarity, user access, and whether a small v0 can test the riskiest assumption.
FAQ
Do I need a prototype, a v0, or an MVP?
That depends on what you already have and what you still need to prove. A prototype helps people understand the idea. A v0 tests one real user loop. An MVP is a more stable version for broader validation. Most early projects should not jump straight to a full native app.
Can you build a full mobile app?
Not as the default first step. For most projects, we recommend testing a web, PWA, or mobile-like v0 first. A native App Store version can make sense later if the v0 or MVP shows enough traction.
Why not build the full MVP immediately?
Because early B2C products often need many iterations before the right user loop is clear. Building too much too early can waste budget on features users may not need.
What is a Builder Pilot?
A Builder Pilot is a 4-week assisted build path to create a small testable v0, collect user feedback, and decide the next step.
Is the first look free?
The first look is a limited high-level review of what you already have. It is not a full written audit or product strategy. If you need a structured plan, we may recommend a paid Cadrage v0.
Do I need an NDA before applying?
No. The initial form should stay high-level. Please do not submit sensitive materials. If deeper review is needed, we can use a lightweight mutual confidentiality agreement.
Who owns my idea?
You keep your idea, brand, content, documents, users, customer relationships, and project-specific materials. LSSM keeps its builder, platform, reusable components, templates, workflows, methods, and generalized learnings. Project-specific deliverables or licenses are defined in the signed pilot or studio agreement.
Is this a technical cofounder replacement?
No. A Builder Pilot can help validate and prototype the project, but it does not create a cofounder, CTO, employment, or equity relationship unless separately agreed.
Can we do revenue share?
Sometimes, after enough fit is established. Revenue share should not replace scope, responsibilities, ownership, or basic cost coverage. Any hybrid model needs a written agreement.
Selective by design
Bring your current idea, maquette, or prototype. We help you decide whether the next step is a prototype, a v0, or an MVP, and build a small testable version if it makes sense.