StartupOS — Decision-First Architecture¶

New design based on the ARCH Framework — 2026-07-17

The Problem With the Old Model¶

The old StartupOS had 26 canvases. That is not a product — that is a spreadsheet collection.

It is like handing a 19-year-old 26 Excel sheets and saying "Build a startup."

Every framework-first app has the same problem: - User opens BMC first → immediately overwhelmed → quits - User sees TAM, VPC, SWOT, PESTEL in a menu → thinks "I'm not ready for this" - User fills in 3 canvases, forgets about the rest → has an incomplete business with no clear story

The root issue: Frameworks are inputs, not outcomes. They make the builder do extra work so the investor can read a standard format.

The New Principle: Decisions Over Frameworks¶

Don't build an app around frameworks. Build an app around decisions.

Every real startup is built on ~15 key decisions: 1. Who is my customer? 2. What problem do they have? 3. How do they solve it today? 4. Why is that solution painful? 5. Where in the value chain does that pain live? 6. Can I remove that step? 7. What is the simplest version of my solution? 8. How will I make money? 9. How will customers find me? 10. What do I build next? 11. Are customers actually using it? 12. How fast is it growing? 13. What do I need to raise funding? 14. Who is my competition? 15. What makes me different?

Every framework (BMC, JTBD, CVC, AARRR) is just a structured output of those decisions.

The app should ask the questions. The frameworks should be generated from the answers — silently, behind the scenes.

The Invisible Engine: Customer Value Chain¶

The Customer Value Chain (CVC) — based on Thales Teixeira's decoupling theory — is the backbone of the new model.

Customer Wants Something
        │
        ▼
  Discover  ← "How do customers find solutions?"
        │
        ▼
  Evaluate  ← "How do they compare options?"
        │
        ▼
  Purchase  ← "How do they buy?"
        │
        ▼
  Receive   ← "How do they get the product?"
        │
        ▼
  Use       ← "How do they get value?"
        │
        ▼
  Share     ← "How do they tell others?"

Every startup problem maps to exactly one of these six steps. Every framework in the old model maps to one of these steps too.

Why this works: Founders don't think in frameworks. They think in stories like: - "Customers can't discover my product" → Discover problem - "They try my competitor instead" → Evaluate problem - "They drop off at checkout" → Purchase problem - "They don't come back" → Use problem

The ARCH Framework — Archetiq's Signature Method¶

Rather than exposing all academic models, Archetiq has one proprietary framework founders can actually remember:

A — Assess     (Where is the friction?)
R — Rethink    (How can the value chain be improved?)
C — Create     (Build the smallest solution)
H — Hone       (Validate and prepare to scale)

This aligns with how architects think: survey the site → rethink the design → build → refine.

ARCH in Practice¶

A – Assess - Map the customer's value chain (6 steps) - Identify which step has the most friction - Identify who has this problem (customer segment)

R – Rethink - Apply decoupling: can you remove a step? - Apply simplification: can you make a step faster/cheaper? - Apply substitution: can you use a better alternative?

C – Create - Define the simplest solution (MVP) - Define the business model (how you make money) - Define the customer acquisition channel

H – Hone - Run the validation loop: Build → Measure → Learn - Track AARRR metrics: Acquisition → Activation → Retention → Referral → Revenue - Prepare the growth engine

The 5 Workspaces¶

Instead of 26 disconnected canvases, founders move through 5 workspaces. Each workspace is a set of guided questions. Each answer feeds the next workspace.

┌─────────────────────────────────────────────────────────────┐
│  WORKSPACE 1                                                │
│  Discover          ← "Who has this problem?"                │
│                                                             │
│  Customer Profile  │  Problem Statement  │  Pain Score      │
│  Current Solution   │  Market Size       │  Alternatives     │
└─────────────────────────────────────────────────────────────┘
                          │
                          ▼
┌─────────────────────────────────────────────────────────────┐
│  WORKSPACE 2                                                │
│  Opportunity       ← "Where is the value chain broken?"    │
│                                                             │
│  Value Chain Map   │  Decoupling Canvas │  Opportunity Score│
└─────────────────────────────────────────────────────────────┘
                          │
                          ▼
┌─────────────────────────────────────────────────────────────┐
│  WORKSPACE 3                                                │
│  Build             ← "What do I build?"                     │
│                                                             │
│  Solution Canvas  │  Business Blueprint │  Pricing Model   │
└─────────────────────────────────────────────────────────────┘
                          │
                          ▼
┌─────────────────────────────────────────────────────────────┐
│  WORKSPACE 4                                                │
│  Validate          ← "Do customers actually want it?"      │
│                                                             │
│  MVP Canvas        │  Experiment Board  │  Weekly Learnings│
│  AARRR Metrics     │  Validation Score  │  Retention Check │
└─────────────────────────────────────────────────────────────┘
                          │
                          ▼
┌─────────────────────────────────────────────────────────────┐
│  WORKSPACE 5                                                │
│  Scale             ← "How do I grow?"                       │
│                                                             │
│  Growth Engine    │  Funding Readiness │  Pitch Deck        │
│  AI Strategy      │  Risk Assessment  │  ESG Scorecard      │
└─────────────────────────────────────────────────────────────┘

Cards, Not Canvases¶

The UI paradigm shifts from "fill this canvas" to "answer this card."

Old Canvas	New Card
Business Model Canvas	Revenue Card
Value Proposition Canvas	Customer Value Card
TAM	Market Card
Competitor Analysis	Alternatives Card
MVP Canvas	Prototype Card
AARRR Metrics	Growth Card

The app asks: "How will you make money?" — not "Fill in the Revenue Streams box."

AI as the Canvas¶

The biggest UX shift: the AI interview replaces the canvas filling.

Example Conversation¶

Archetiq AI: What are you building?
User: An app that helps final-year students find internships.

Archetiq AI: Who struggles with this the most?
User: Final-year students at universities.

Archetiq AI: How do they solve it today?
User: LinkedIn, WhatsApp groups, university career fairs.

Archetiq AI: What frustrates them about those options?
User: Too many irrelevant listings. Career fairs are once a semester.

Behind the scenes, the AI generates: - Customer Journey (CVC) - Problem Statement - Customer Segment (JTBD) - Competitor Analysis (Alternatives Card) - Lean Opportunity Canvas - Business Blueprint - Business Model Canvas - Pitch Draft

The user never sees a framework being filled. They have a conversation.

Frameworks: What Stays, What Goes¶

Keep (Hidden or Lightweight)¶

Framework	Why	How Used
Customer Value Chain ⭐⭐⭐⭐⭐	Core backbone	Drives every question
JTBD ⭐⭐⭐⭐⭐	Excellent for understanding why customers buy	Hidden in conversation
Lean Startup ⭐⭐⭐⭐⭐	Validation mindset	Weekly check-ins
Design Thinking ⭐⭐⭐⭐	Ideation and empathy	Stage 3 prompts
AARRR ⭐⭐⭐⭐	Growth measurement	Hidden metrics engine

Remove (Or Bury Behind Scenes)¶

Framework	Reason
Business Model Canvas	Too heavy for beginners; generated from answers
Value Proposition Canvas	Too abstract; embedded in conversation
SWOT	Mostly redundant for early startups
PESTEL	Too academic for most founders
Porter's 5 Forces	Better for established companies
Fishbone	Optional; only for retrospectives
Lean Waste	More relevant to ops than early-stage
Blue Ocean	Selected ideas only; not a starting point

Old Model vs New Model¶

Dimension	Old (Framework-First)	New (Decision-First)
Entry point	BMC or canvas menu	"What problem are you solving?"
UX paradigm	Fill in a template	Answer questions + get cards
Core engine	26 separate canvases	Customer Value Chain
Signature framework	None (all are visible)	ARCH Framework
AI role	None	The primary interface
Output	Completed canvases	Generated frameworks from conversation
Mental model	"I need to learn all these frameworks"	"I'm having a conversation about my startup"
Retention risk	High (overwhelm → drop off)	Low (progressive, conversational)
Gen Z fit	Poor	Strong

The Backend Data Model¶

The database stores decisions, not canvases.

// Old model: store the filled canvas
{ type: "businessModelCanvas", data: { ...all 9 boxes... } }

// New model: store atomic decisions
{ decision: "customer_segment", value: "Final-year university students" }
{ decision: "problem", value: "Can't find relevant internships" }
{ decision: "current_alternative", value: "LinkedIn, WhatsApp, career fairs" }
{ decision: "pain_point", value: "Too many irrelevant listings" }
{ decision: "value_chain_step", value: "discover" }
{ decision: "revenue_model", value: "subscription" }
{ decision: "pricing", value: "49/month student, 199/month employer" }
// ... etc

Frameworks are generated on demand:

GET /api/generate/business-model-canvas
→ reads all decisions for startupId
→ assembles BMC shape from stored answers
→ returns completed canvas

GET /api/generate/pitch-deck
→ reads decisions
→ generates 10-slide investor deck
→ returns slides

This means: 1. The user only enters data once 2. Every framework is always up to date 3. Investor-ready outputs can be regenerated any time

5-Workspace UX Flow¶

Day 1:
  → Workspace 1 (Discover)
    → 5 questions
    → Customer Profile card generated
    → Progress: 1/5

Week 1:
  → Workspace 2 (Opportunity)
    → 4 questions
    → Decoupling Canvas auto-generated from Day 1 answers
    → Opportunity Score calculated

Week 2-3:
  → Workspace 3 (Build)
    → 6 questions
    → Business Blueprint generated

Week 3-6:
  → Workspace 4 (Validate)
    → Weekly check-ins
    → Experiment Board auto-populated
    → AARRR metrics tracked

Month 3+:
  → Workspace 5 (Scale)
    → Pitch Deck generated
    → Funding Readiness score
    → Growth Engine visible

Migration Path¶

For existing users with filled canvases:

Import canvas data → parse into atomic decisions
Map decisions to workspaces → auto-populate workspaces 1-5
Show "Your previous work" → let user see which canvas each answer came from
Gradually retire old canvas pages → archive after migration

"Your Business Model Canvas has been converted to a Business Blueprint. You can still view it under Advanced."

Implementation Priority¶

Phase	What	Why
Phase 1	AI Interview module (Workspace 1 questions)	Fastest path to value
Phase 2	Decision store (atomic decisions vs canvas store)	Foundation for framework generation
Phase 3	Workspace 1-3 full cards + CVC backbone	Core founder journey
Phase 4	Framework generation engine (BMC, Pitch from decisions)	"Frameworks as outputs"
Phase 5	Workspace 4-5 + AARRR metrics	Validation + Scale
Phase 6	Retire old canvas pages	Cleanup

Comparison: What the User Sees¶

Old StartupOS¶

Menu: BMC | VPC | SWOT | TAM | JTBD | Lean Canvas | 20 more...
↓
User picks TAM
↓
TAM canvas appears with 9 empty boxes
↓
User thinks "What is ASM?"
↓
User closes tab

New StartupOS¶

Screen: "What problem are you solving?"
↓
User types one sentence
↓
Next: "Who has this problem?"
↓
Next: "How do they solve it today?"
↓
Done. BMC auto-generated. JTBD auto-generated. 
Pitch deck ready in 10 minutes.

Live deployment setup¶

Item	Value
Production frontend root	`/opt/personality-app/public`
Demo frontend root	`/opt/personality-app-demo/public`
Production backend port	`5002`
Demo backend port	`5006`
Nginx	serves SPA routes and proxies `/api/` to Express
Domain	Startup Playbook production: `startup.archetiq.com`; demo: `demo-startup.archetiq.com`

What is currently implemented¶

StartupOS is available through the live route tree under /startup/*.

Live StartupOS routes¶

/startup/dashboard
/startup/persona
/startup/problem-validation
/startup/design-thinking
/startup/vpc
/startup/competitor
/startup/blue-ocean
/startup/bmc
/startup/market
/startup/financial-model
/startup/pricing-strategy
/startup/gtm
/startup/mvp
/startup/experiment-board
/startup/product-roadmap
/startup/metrics
/startup/okrs
/startup/value-stream
/startup/seven-wastes
/startup/fishbone
/startup/speedboat
/startup/team
/startup/risk-assessment
/startup/esg
/startup/ai-strategy
/startup/funding-readiness
/startup/pitch
/startup/decision-lab
/startup/onboarding
/startup/settings
/startup/institution
/startup/lecturer

Live access rules¶

StartupOS visibility is controlled by hasStartupOS() in client/src/utils/journeyGates.ts and the route guards in client/src/components/ProtectedRoute.tsx.

Who gets StartupOS¶

Users with StartupOS access in the live gate model
Users with startupId
Users in an institution workspace
Organisation users with the StartupOS add-on
Admins

What StartupOS replaces¶

Decision Lab is part of StartupOS
StartupOS is the owner of the founder journey
Institution Hub and Lecturer Dashboard are treated as StartupOS support surfaces

The live sidebar groups StartupOS into:

Start Here
Institution Ops
Decision Tools
Stage 1 to Stage 5 founder sections

That structure is implemented in client/src/components/Layout.tsx.

Current role model inside StartupOS¶

Member / founder group member
Lecturer
Institution Admin
Coach

What the live app currently does¶

/startup redirects to /startup/dashboard
StartupOS is hidden unless the gate opens or the user is already on a /startup/* route
Institution members can be given StartupOS by default
Organisation users can be given StartupOS as an add-on
Admin can edit organisation/institution records and toggle the add-on state from the Organisations admin screen

User-facing summary¶

StartupOS is the institution workspace for founder journeys, canvas work, lecturer feedback, and startup management. It is now part of the unified live server rather than a separate legacy application.