A complete operating model slice for a premium pizza delivery startup — generated from a two-page pitch deck in a single Claude Cowork session using the PlausibleBA skills library.
This is the only input provided to the skills — a two-page startup pitch. No capability framework knowledge required. No prior architecture work. Just paste and run.
Draft Pitch: Dough-To-Door Pizzeria Page 1: The Vision & The Problem Company Name: Dough-To-Door Pizzeria Tagline: "Farm-to-table speed, neighborhood soul." The Problem: Current delivery options in the [Target Neighborhood] are either low-quality fast food or high-end sit-down restaurants with 60+ minute wait times. There is a "quality gap" for busy families and professionals who want premium, organic ingredients delivered fast. The Solution: A Fast-Casual Hybrid Model that combines artisanal wood-fired quality with a tech-driven delivery engine. We use locally sourced, organic ingredients and a proprietary "Dough-Sync" logistics app to ensure every pizza is delivered within 25 minutes of being pulled from the oven. Target Market: Young professionals and families (ages 25-45) in high-density urban areas. Local market opportunity: $1.2M in annual revenue. Page 2: The Strategy & The Ask Traction: 3-month pop-up pilot. $15,000 in revenue. 4.8-star average rating. Team: Head Chef (10 years Michelin-rated kitchens) + CTO (logistics software). Financials: Break-even in 10 months. Year 2 target: $540,000/year. The Ask: $250,000 seed — equipment (30%), ghost kitchen lease (40%), marketing and app launch (30%). Revenue streams: Direct sales 40% · Branded app delivery 50% · Meal kits 10% Cost structure: Ghost-kitchen hybrid. Organic COGS 14%. Tech-driven ops. Customer acquisition: Hyper-local social media, community events, Dough-Points loyalty programme.
Click any L3 capability tile to inspect it.
Select a concept node to see its definition and lifecycle states.
The entire operating model above was generated in a single Claude Cowork session. The only input was the pitch deck text above — no prior architecture knowledge, no reference models, no configuration.
Each skill guided the session through structured elicitation with two validation checkpoints before rendering. The outputs are BIZBOK-grounded, MECE-validated, and schema-validated for VCC import.