@rubytech/create-maxy-code 0.1.404 → 0.1.405

package/payload/premium-plugins/venture-studio/skills/investor-data-room/templates/prospectus/index.html

@@ -896,19 +896,20 @@
     <div class="hero">
       <div class="stage">
         <div class="eyebrow">Prospectus — {{ DOC_MONTH_YEAR }}</div>
-        <h1>Operating System for <span class="upright">Estate Agents</span></h1>
-        <p class="deck">{{ BRAND_NAME }} is built for the UK self-employed estate agent &mdash; a cohort on track to reach
-          ~10% of the UK property market by 2030. One admin agent runs the business through a chat. Other agents handle
-          the admin no-one wants to do: qualifying enquiries, chasing vendor updates, booking viewings, keeping the
-          chain moving. The agent's day
-          stays in front of customers, not the keyboard. £500 a month &mdash; less than a Virtual Assistant (VA).</p>
+        <h1>{{ ONE_LINE_POSITIONING }}</h1>
+        <p class="deck">Cover deck (≤ 80 words). One paragraph stating what {{ BRAND_NAME }} does, who it is for, and
+          why it is different. Name the target customer cohort and the single structural reason the product wins. State
+          the headline price point. This is the first thing an investor reads; it carries the whole thesis in one
+          breath. Replace this paragraph with the venture's own; carry no figure that is not cited elsewhere in the
+          document.</p>
 
         <div class="chart">
-          <!-- Two-panel chart driven by the operator's financial model worksheet.
-             Recompute SVG coordinates from the new model: cash polyline, MRR bars, burn step-lines.
-             See Stage 4b § "How to apply answers" step 7 for the recomputation formulae. -->
+          <!-- ILLUSTRATIVE EXAMPLE — the geometry and callout figures below are a generic worked
+             example, not any real venture's model. Recompute every SVG coordinate and label from
+             the operator's own financial model worksheet: cash polyline, MRR bars, burn step-lines,
+             break-even marker. See Stage 4b § "How to apply answers" step 7 for the formulae. -->
           <svg viewBox="0 0 520 320" xmlns="http://www.w3.org/2000/svg" role="img"
-            aria-label="Cash balance, monthly MRR and burn">
+            aria-label="Cash balance, monthly revenue and burn (illustrative example)">
             <defs>
               <pattern id="halftone" x="0" y="0" width="6" height="6" patternUnits="userSpaceOnUse">
                 <circle cx="3" cy="3" r="0.55" fill="#000000" opacity="0.22" />
@@ -936,9 +937,9 @@
               <circle cx="500" cy="117" r="2.6" />
             </g>
             <g font-family="Inter, sans-serif" font-size="9.5" fill="#000">
-              <text x="56" y="38">£321k after capex</text>
-              <text x="332" y="132" font-size="8.5">low £34k · M11 (Round 2 closes M10)</text>
-              <text x="450" y="110">£36k · M12</text>
+              <text x="56" y="38">£300k after capex</text>
+              <text x="332" y="132" font-size="8.5">cash low point · M11</text>
+              <text x="450" y="110">£40k · M12</text>
             </g>
 
             <!-- ── PANEL 2: monthly MRR (bars) and burn (dashed) y 170–290 (span 120). Scale £0–£60k. -->
@@ -968,9 +969,9 @@
             <line x1="124" y1="184" x2="424" y2="184" stroke="#000" stroke-width="1.5" stroke-dasharray="5 3" />
             <line x1="424" y1="184" x2="424" y2="174" stroke="#000" stroke-width="1" stroke-dasharray="2 2" />
             <line x1="424" y1="174" x2="500" y2="174" stroke="#000" stroke-width="1.5" stroke-dasharray="5 3" />
-            <text x="56" y="190" font-family="Inter, sans-serif" font-size="9.5" font-weight="600" fill="#000">BURN £48k</text>
-            <text x="120" y="180" font-family="Inter, sans-serif" font-size="9.5" font-weight="600" fill="#000">£53k (i)</text>
-            <text x="420" y="170" font-family="Inter, sans-serif" font-size="9.5" font-weight="600" fill="#000">£58k (ii)</text>
+            <text x="56" y="190" font-family="Inter, sans-serif" font-size="9.5" font-weight="600" fill="#000">BURN £45k</text>
+            <text x="120" y="180" font-family="Inter, sans-serif" font-size="9.5" font-weight="600" fill="#000">£50k (i)</text>
+            <text x="420" y="170" font-family="Inter, sans-serif" font-size="9.5" font-weight="600" fill="#000">£55k (ii)</text>
             <line x1="495" y1="170" x2="495" y2="290" stroke="#999" stroke-width="0.6" stroke-dasharray="2 3" />
             <text x="520" y="150" font-family="Inter, sans-serif" font-size="8.5" fill="#666" text-anchor="end">Break-even · M12</text>
             <g font-family="Inter, sans-serif" font-size="9" fill="#666" text-anchor="middle">
@@ -1062,61 +1063,36 @@
     <!-- Executive summary -->
     <section class="block">
       <h2>Executive summary.</h2>
-      <p><strong>The market.</strong> {{ BRAND_NAME }}'s primary target customer is the self-employed UK estate agent. A
-        cohort whose
-        transaction share has grown 7.5&times; since 2019 (TwentyEA), reached ~2.5% of UK property transactions
-        in 2025, and is on track to account for ~10% of the market by 2030 (Worth Recruiting). The wider industry sits
-        behind it: 26,374 estate-agency businesses, ~388,000 workforce (ONS / IBISWorld 2026).</p>
-      <p><strong>The opportunity.</strong> More and more UK estate agents are leaving agencies to run their own book.
-        When
-        they do, all the admin that used to be split across an office lands on one person: enquiries, CRM, vendor
-        reports, chasing sales through to completion, the regulatory paperwork. The current alternatives are to hire a
-        VA, at £500 to £1,500 a month or subscribe to a range of expensive SaaS tools. A new VA
-        starts knowing nothing about the agent's business; every client quirk, every process, every property has to be
-        taught
-        from scratch. When the VA leaves, all of it walks out with them. Saas tools have steep learning curves, with
-        every new feature loading as much burden on the user as benefit, so much of the value, especially in CRMs, is
-        untapped.</p>
-      <p><strong>{{ BRAND_NAME }} value proposition.</strong> {{ BRAND_NAME }} starts at £500 a month for a solo operator. It
-        learns the agent's business once and keeps everything organised. No handover, no slow first month, no knowledge
-        walking out of
-        the door. It is also on the agent's side by design: every minute of admin it takes off their plate is a minute
-        they spend
-        in front of a customer, a vendor or a buyer in the chain. The data stays with them. Customer conversations sit
-        between their customers and the model provider (Anthropic); {{ BRAND_NAME }} is not in the middle holding the data.
-        That is a much lighter compliance footprint than competitors who pass throiugh the AI costs and keep the agent's
-        data on their servers. <em>For information:</em> the model itself is Anthropic's Claude, paid for on the
-        customer's own
-        subscription. That is a build choice, not what makes {{ BRAND_NAME }} different &mdash; any competitor could pick the
-        same model.</p>
+      <p><strong>The market.</strong> State {{ BRAND_NAME }}'s primary target customer cohort, its size, and its growth
+        rate. Every figure here is cited to a named source (industry body, government statistics, a named study) and
+        traces to <code>08-market/sources.md</code>. Name the structural trend that makes this cohort grow, and why the
+        wider industry behind it matters.</p>
+      <p><strong>The opportunity.</strong> Describe what is currently broken or unmet for that customer: the job they
+        struggle to do, the cost and friction of the status-quo alternatives, and the specific way those alternatives
+        fail them. Concrete, not abstract; this is the problem the product exists to solve.</p>
+      <p><strong>{{ BRAND_NAME }} value proposition.</strong> State the price point, what the customer gets for it, and
+        the single structural reason it beats the alternatives. Where the product depends on a third-party model or
+        platform, make clear that is a build choice any competitor could copy, not the differentiator &mdash; the moat
+        is stated in the architecture block below.</p>
     </section>
 
-    <!-- Architecture (intro + subagent fleets) flows on the same A4 page -->
+    <!-- Architecture (intro + capability fleets) flows on the same A4 page -->
     <section class="block">
       <h2>Architecture &amp; differentiation.</h2>
-      <p><strong>The architecture &mdash; every role you play. Amplified.</strong> {{ BRAND_NAME }} is built around one
-        <strong>AI Operations Manager</strong> &mdash; the chief of staff &mdash; that orchestrates the business: runs
-        the workflows, manages the schedule, prepares the briefings, generates the documents. Underneath it sit two
-        fleets of role-specific subagents (see <a href="{{ PRODUCT_URL }}">{{ PRODUCT_URL_LABEL }}</a> for the
-        live articulation):
+      <p><strong>The architecture.</strong> Describe how the product is built at a level an investor grasps in one read:
+        the core components, how they fit together, and the one structural choice that makes it hard to copy. "AI" is
+        not a moat; the moat is in <em>how</em> the technology is applied. If the product exposes distinct capabilities
+        or roles, group them below and name what each does. Link to a live articulation if one exists
+        (<a href="{{ PRODUCT_URL }}">{{ PRODUCT_URL_LABEL }}</a>).
       </p>
       <ul>
-        <li><strong>Admin specialist subagents</strong> (private, ring-fenced &mdash; one per role the human estate
-          agent
-          plays in their day): <em>Negotiator</em> logs call notes from a voice message with no CRM typing;
-          <em>Chain Progressor</em> monitors every open transaction and flags when a milestone is overdue;
-          <em>Valuer</em> assembles pre-built valuation packs, ranked call lists and automated vendor reports;
-          <em>Branch Manager</em> delivers morning pipeline briefings, automated progression tracking, team activity
-          digests; <em>Prospector</em> runs ranked call lists, farming letters, market triggers and database follow-up
-          sequences; <em>Compliance</em> handles legislation, listing audit, AML and citations (internal only).
+        <li><strong>Internal capabilities</strong> (private, access-controlled): the functions the product performs on
+          the operator's behalf. One line each &mdash; what it does and for whom. Scope and access-control each like a
+          junior member of staff: one clear job, one identity, only the data needed to do it.
         </li>
-        <li><strong>Public specialist subagents</strong> (customer-facing): <em>Buyer Enquiry Agent</em> onboards new
-          buyers through natural conversation &mdash; not inconvenient forms &mdash; 24/7; <em>Viewing Booking
-            Agent</em>
-          schedules, sends confirmations, groups viewings for efficiency; <em>Sales Progression Agent</em> (one per
-          transaction, gated to buyer, seller and solicitors, knows the full chain); <em>Vendor Update Agent</em> (gated
-          to a specific vendor, real-time status on their property); and the on-platform <em>{{ BRAND_NAME }} Sales</em> agent
-          that qualifies leads for {{ BRAND_NAME }} itself 24/7.</li>
+        <li><strong>Customer-facing capabilities</strong>: the functions that face the operator's own customers, each
+          with its own identity and access boundary. One line each &mdash; what it does and which customer it is gated
+          to.</li>
       </ul>
     </section>
 
@@ -1135,45 +1111,25 @@
 
     <section class="block">
       <h2>Architecture &amp; differentiation (cont.).</h2>
-      <p>Every subagent is briefed, scoped and access-controlled like a junior member of staff &mdash; given one clear
-        job, one identity, and the data needed to do it, nothing more. The agent <em>delegates</em> rather than
-        operates;
-        the subagents carry the load; the agent's time and judgement go to the relationships that win instructions and
-        close transactions. This is the architectural reason an estate agent can hit the ground running on day one:
-        nothing needs to be learned beyond the chat &mdash; the platform is run the same way the agent already runs a
-        team of people. {{ BRAND_NAME }} handles the admin that fills the gaps between, and gives the agent back the work
-        that only they can do, in every role they play. <strong>The public agents are the interface. Not the
-          product.</strong></p>
-      <p><strong>What we do that nobody else does.</strong> Most software, and most AI tools, work the same way: they
-        pull the customer's data onto the supplier's server, then make the customer learn a dashboard to get any value
-        out of it. {{ BRAND_NAME }} does the opposite. The data stays with the agent. The AI does the work that frees the
-        agent up, instead of sitting between the agent and their own customer. The whole platform runs through a natural
-        language chat interface,
-        not a dashboard. The chat can be text or voice driven, according to the working pattern of the user. The real
-        defence, however, is the structure
-        underneath, where the human is in the middle and not the platform. That is also why 60% of agents using current
-        AI tools say they don't really understand them &mdash; those tools are still built the old way, not intuitively.
-      </p>
-      <p><strong>Cross-CRM AI &mdash; the structural differentiator.</strong> Every CRM in UK estate agency is now
-        bolting AI onto its own product &mdash; AI features that only work inside that one CRM, with that one vendor's
-        roadmap, locking the customer in. {{ BRAND_NAME }} is built the opposite way: it integrates every CRM through its open
-        API, so the agent keeps their CRM choice and {{ BRAND_NAME }} makes whichever one they use materially more powerful.
-        Every agent on every CRM is therefore addressable. This is the structural funnel driver as the AI-in-CRM trend
-        accelerates.</p>
-      <p><strong>Wedge &middot; beachhead &middot; blitzscale.</strong> Our entry into the market has already begun with
-        a brochure flywheel strategy, designed to hook agents into the utility of the product without having to make a
-        firm commitment. We then leverage this to generate early revenue and upsell to pre-val presentations. The
-        brochure flywheel and pre-val
-        product are
-        <em>the wedge</em> &mdash; narrow entry, fast proof, low-friction adoption into the agent's day. The Loop
-        integration into eXp UK (3,000+ agents on a mandated CRM) is <em>the beachhead</em> &mdash; one decisively
-        winnable segment chosen to gather repeatable wins. The Round 2 raise at month 9 (£500k&ndash;£1m on hit
-        milestones) funds <em>the blitzscale</em>: integrate every property CRM in the UK, market into the whole UK
-        estate-agency workforce, and {{ BRAND_NAME }} becomes the operating system for UK estate agency &mdash; not
-        aspirationally, concretely. At that point, <strong>an agent cannot compete effectively with an agent who has
-          {{ BRAND_NAME }} operating their CRM &mdash; whichever CRM either of them happens to use.</strong> The race is to
-        that establishing position.
-      </p>
+      <p><strong>Why the structure wins.</strong> Explain the consequence of the architecture for the customer: what
+        they no longer have to do, what they get on day one, and why a competitor cannot match it without abandoning
+        their own model. Keep it to the structural argument, not adjectives. State plainly what is the interface and
+        what is the product.</p>
+      <p><strong>What we do that nobody else does.</strong> State the one thing the product does that incumbents
+        structurally cannot &mdash; the inversion of how everyone else in the category is built. Name the default
+        approach the market takes (for example: pull the customer's data onto the supplier's server and make them learn
+        a dashboard), then state how {{ BRAND_NAME }} does the opposite and why that is defensible rather than merely
+        different.</p>
+      <p><strong>The structural differentiator.</strong> If the product is agnostic to the incumbent system-of-record
+        (integrating with whatever the customer already uses rather than forcing a migration), state it here: how that
+        makes every customer in the category addressable, and why it is a funnel driver as the category's dominant
+        trend accelerates.</p>
+      <p><strong>Wedge &middot; beachhead &middot; blitzscale.</strong> The staged go-to-market. <em>The wedge</em>:
+        the narrow entry product with fast proof and low-friction adoption into the customer's day. <em>The
+        beachhead</em>: one decisively winnable segment, funded by Round 1, chosen to gather repeatable wins.
+        <em>The blitzscale</em>: the market expansion funded by Round 2. State the concrete milestone at each stage and
+        the establishing position the venture is racing to reach &mdash; the point at which a competitor without the
+        product cannot compete with one that has it.</p>
     </section>
 
     <div class="page-num">Page 3 / 7</div>
@@ -1192,37 +1148,22 @@
     <!-- Body block 2: Funnel -->
     <section class="block">
       <h2>Business development.</h2>
-      <p>{{ BRAND_NAME }} acquires customers by producing the artefacts agents already need, at a fraction of the time and
-        cost
-        the agent would otherwise spend, and at better quality too. This is the revolutionary outcome that only AI can
-        achieve in the right hands. Each artefact demonstrates the platform's capability and earns revenue in its
-        own right, before the agent commits to their own subscription. There are two such products today and a third
-        strategic channel that opens at scale.</p>
+      <p>Describe how {{ BRAND_NAME }} acquires customers: the specific channels producing customers in the first
+        months, and any product that earns revenue in its own right before the customer commits to a subscription.
+        Each channel is concrete &mdash; a named integration, a named partner, a demonstrable artefact with numbers to
+        date &mdash; not an aspiration. Typically there is a live wedge, a higher-value upsell, and a distribution
+        channel that opens at scale.</p>
       <ul>
-        <li><strong>The brochure flywheel (live).</strong> A property brochure is the standard sales document an estate
-          agent prepares for every listing &mdash; photography, floorplan, room descriptions, EPC, location narrative.
-          Producing one well, in regulatory compliance, takes hours. {{ BRAND_NAME }} produces a brochure from the listing URL
-          and a short brief in
-          minutes, and only a few seconds of the operator's time. A free LinkedIn campaign has delivered five brochures
-          to date. The brochures themselves are
-          discoverable artefacts &mdash; agents publish them to win the instruction, other agents see them, demand
-          compounds. The next step is to convert delivery into a low-cost monthly service or pay-per-brochure, with
-          gross margin near 100%.</li>
-        <li><strong>The pre-valuation product (next).</strong> A pre-val presentation is the higher-value private
-          document an agent walks into a homeowner's kitchen with to win a listing instruction: comparable sales,
-          marketing plan, recommended price, the agent's pitch. It is high-stakes, time-consuming and currently done by
-          hand. Same architecture as the brochure flywheel, much higher willingness-to-pay. Because the data is
-          sovereign, this is what will drive {{ BRAND_NAME }} conversion from the service-based brochure production.</li>
-        <li><strong>The Loop CRM integration &mdash; the first of many (Q3 2026).</strong> Loop is the only CRM
-          integration today and it is the right place to start: Loop is the CRM every eXp UK agent has to use &mdash;
-          3,000+ agents &mdash; and is releasing an open API to which we have early access. {{ BRAND_NAME }} already
-          integrates
-          natively with email, Outlook, WhatsApp and Telegram, so agents and their customers communicate on the channel
-          they already use. CRM vendors are racing to bolt AI onto their own products, locked to their stack. {{ BRAND_NAME }}
-          does the opposite: AI that will work with whichever CRM the agent already uses (Reapit, Alto, Street,
-          GoHighLevel and any other open-API CRM under Round 2). The whole UK estate-agency CRM base becomes
-          addressable,
-          not just one vendor's.</li>
+        <li><strong>Wedge channel (live).</strong> The low-commitment product or artefact that demonstrates the
+          platform's capability and hooks the customer without a firm commitment. State what it is, how fast it
+          delivers versus the manual alternative, what it has delivered so far (with numbers), why it is discoverable
+          so demand compounds, and how it converts to paid.</li>
+        <li><strong>Higher-value upsell (next).</strong> The higher-willingness-to-pay product the wedge converts into.
+          Same architecture, greater value and stakes; state why the customer pays materially more for it and what
+          structural property of the product drives the conversion.</li>
+        <li><strong>Distribution partnership / integration (dated).</strong> The named integration or channel partner
+          that opens a whole segment at scale. State who, how many customers it reaches, and what access or agreement
+          is in place. Name the integrations and channels already live, and the ones Round 2 funds.</li>
       </ul>
     </section>
 
@@ -1246,44 +1187,38 @@
     </div>
 
     <section class="block asset-block">
-      <p>{{ BRAND_NAME }} is not a slide-ware concept. The platform is in production today, built over months of senior
-        engineering by Joel Smalley before incorporation. <strong>At closing it transfers outright to {{ BRAND_NAME }}
-          Systems Ltd</strong> &mdash; with no licence-back, no royalty, and no encumbrance. The {{ ROUND_SIZE }} raise funds
-        go-to-market and
-        product hardening, not greenfield engineering. The difficult architectural choices have already been made and
-        the core components are already working in production.</p>
+      <p>{{ BRAND_NAME }} is not a slide-ware concept. State the current build status: what is in production today, and
+        that it was built by the founding team before incorporation. <strong>At closing it transfers outright to
+        {{ COMPANY_LEGAL_NAME }}</strong> &mdash; with no licence-back, no royalty, and no encumbrance. The
+        {{ ROUND_SIZE }} raise funds go-to-market and product hardening, not greenfield engineering. The difficult
+        architectural choices are already made and the core components already work in production.</p>
       <div class="asset-grid">
         <div class="asset-col">
           <div class="asset-head">Working today</div>
           <ul>
-            <li><strong>Admin agent.</strong> One conversation runs the whole business &mdash; briefings, CRM updates,
-              document generation, follow-ups, scheduling.</li>
-            <li><strong>Unlimited specialist public agents.</strong> Lead qualifiers, vendor-update agents, viewing
-              bookers, sales-progression chasers &mdash; each with its own identity, knowledge, and access control.</li>
-            <li><strong>Workflow orchestration.</strong> Continuous, AI-initiated &mdash; the platform monitors business
-              state and acts without being asked.</li>
-            <li><strong>CRM integration.</strong> Loop is the live CRM integration today; every other open-API CRM
-              follows under Round 2.</li>
-            <li><strong>Communication channels (live).</strong> Native email, Outlook, WhatsApp and Telegram &mdash;
-              agents and their customers reach {{ BRAND_NAME }} on the channel they already use, with no new app to install.
-            </li>
-            <li><strong>Customer-owned model subscription.</strong> Customers hold their own Claude subscription &mdash;
-              zero AI compute on {{ BRAND_NAME }}'s P&amp;L, customer data stays with the customer.</li>
-
+            <li><strong>Core capability.</strong> One line: the central function the product performs in production.</li>
+            <li><strong>Specialist capabilities.</strong> The customer-facing and internal functions live today, each
+              with its own identity, knowledge and access control.</li>
+            <li><strong>Orchestration.</strong> How the product monitors business state and acts without being asked.</li>
+            <li><strong>Integrations (live).</strong> The systems-of-record and communication channels the product
+              already connects to; name what follows under Round 2.</li>
+            <li><strong>Cost structure.</strong> Any structural cost advantage &mdash; for example, the customer holds
+              their own model subscription, so third-party compute stays off {{ BRAND_NAME }}'s P&amp;L and customer
+              data stays with the customer.</li>
           </ul>
         </div>
         <div class="asset-col">
           <div class="asset-head">Implications for this round</div>
           <ul>
-            <li><strong>The hard engineering risk is mitigated.</strong> The architecture, agent orchestration, and the
-              admin/public split are designed and shipped.</li>
-            <li><strong>£350k goes to commercial work, not R&amp;D.</strong> Hardening, the Loop API integration,
-              marketing, training, legal &mdash; not greenfield build.</li>
-            <li><strong>Replacement cost exceeds the raise.</strong> Building this from a blank canvas at UK
-              senior-engineering rates would cost more than {{ ROUND_SIZE }} and take 9&ndash;12 months.</li>
-            <li><strong>Time-to-revenue is short.</strong> Two pilots run from week 1 because the platform exists:
-              Muvin (Adam &amp; Jamie's agency) and Beacons (Alex's agency). Both are founder-operated &mdash; the
-              people promoting {{ BRAND_NAME }} are active users of it.</li>
+            <li><strong>The hard engineering risk is mitigated.</strong> The architecture and core build are designed
+              and shipped, not speculative.</li>
+            <li><strong>The raise goes to commercial work, not R&amp;D.</strong> Hardening, integrations, marketing,
+              training, legal &mdash; not greenfield build.</li>
+            <li><strong>Replacement cost exceeds the raise.</strong> State the cost and time to rebuild this from a
+              blank canvas at market engineering rates &mdash; more than {{ ROUND_SIZE }}.</li>
+            <li><strong>Time-to-revenue is short.</strong> Name any pilots or paying customers running from week 1
+              because the platform already exists &mdash; ideally operated by the people promoting it, so they are
+              active users of the product.</li>
           </ul>
         </div>
       </div>
@@ -1309,9 +1244,11 @@
 
     <div class="traj">
       <div class="visual">
-        <!-- MRR by month — exponential ramp to £60k by M12. Three-step burn line. -->
+        <!-- ILLUSTRATIVE EXAMPLE — a generic monthly-revenue ramp with a three-step burn line.
+             Not any real venture's model. Recompute every bar, label and burn step from the
+             operator's own financial model worksheet. -->
         <svg viewBox="0 0 480 320" xmlns="http://www.w3.org/2000/svg" role="img"
-          aria-label="MRR by month with monthly burn line">
+          aria-label="Monthly revenue by month with monthly burn line (illustrative example)">
           <line x1="40" y1="40" x2="40" y2="280" stroke="#000000" stroke-width="0.8" />
           <line x1="40" y1="280" x2="464" y2="280" stroke="#000000" stroke-width="0.8" />
           <!-- Y ticks: £0, £20k, £40k, £60k. Scale 0→60k mapped 280→40, span 240. -->
@@ -1329,7 +1266,8 @@
             <text x="358" y="296">M9</text>
             <text x="464" y="296">M12</text>
           </g>
-          <!-- MRR bars M1-M12: 6,7,9,13,18,24,31,38,44,50,56,60 (£k). y = 280-(m/60)*240. -->
+          <!-- MRR bars M1-M12 (illustrative ramp). Recompute each bar from the operator's model:
+               y = 280 - (mrr_k / axis_max_k) * 240, height = 280 - y. -->
           <g fill="#000000">
             <rect x="75"  y="256" width="22" height="24"  /> <!-- M1:  6k -->
             <rect x="110" y="252" width="22" height="28"  /> <!-- M2:  7k -->
@@ -1344,15 +1282,15 @@
             <rect x="425" y="56"  width="22" height="224" /> <!-- M11: 56k -->
             <rect x="460" y="40"  width="22" height="240" /> <!-- M12: 60k -->
           </g>
-          <!-- Three-step burn line: M1–M2 £48k (y=88), M3–M9 £53k (y=68), M10–M12 £58k (y=48). -->
+          <!-- Three-step burn line (illustrative): M1–M2 £45k (y=88), M3–M9 £50k (y=68), M10–M12 £55k (y=48). -->
           <line x1="40" y1="88" x2="132" y2="88" stroke="#000000" stroke-width="1.6" stroke-dasharray="5 3" />
           <line x1="132" y1="88" x2="132" y2="68" stroke="#000" stroke-width="1" stroke-dasharray="2 2" />
           <line x1="132" y1="68" x2="412" y2="68" stroke="#000000" stroke-width="1.6" stroke-dasharray="5 3" />
           <line x1="412" y1="68" x2="412" y2="48" stroke="#000" stroke-width="1" stroke-dasharray="2 2" />
           <line x1="412" y1="48" x2="482" y2="48" stroke="#000000" stroke-width="1.6" stroke-dasharray="5 3" />
-          <text x="46" y="84" font-family="Inter, sans-serif" font-size="10" font-weight="600" fill="#000">BURN £48k</text>
-          <text x="138" y="64" font-family="Inter, sans-serif" font-size="10" font-weight="600" fill="#000">£53k (i)</text>
-          <text x="418" y="44" font-family="Inter, sans-serif" font-size="10" font-weight="600" fill="#000">£58k (ii)</text>
+          <text x="46" y="84" font-family="Inter, sans-serif" font-size="10" font-weight="600" fill="#000">BURN £45k</text>
+          <text x="138" y="64" font-family="Inter, sans-serif" font-size="10" font-weight="600" fill="#000">£50k (i)</text>
+          <text x="418" y="44" font-family="Inter, sans-serif" font-size="10" font-weight="600" fill="#000">£55k (ii)</text>
           <!-- Break-even marker at M12 -->
           <line x1="471" y1="40" x2="471" y2="280" stroke="#999" stroke-width="0.6" stroke-dasharray="2 3" />
           <text x="475" y="30" font-family="Inter, sans-serif" font-size="9" fill="#666" text-anchor="end">Break-even · M12</text>
@@ -1360,22 +1298,22 @@
         <div class="visual-caption">Monthly MRR (bars) vs. monthly burn (dashed line)</div>
       </div>
       <div class="meta">
-        <h3>Subscriptions only.</h3>
-        <p class="lead">Solo £500 a month, Office £2,000 a month from month four, Annual £6,000 a year. A free tier
-          capped at 50 stays in place for early evangelists and KOLs. £60k closing MRR is the M12 target: <strong>100
-            Solo + 5 Office customer relationships, 105 Pi devices to support.</strong></p>
+        <h3>Revenue model.</h3>
+        <p class="lead">State the pricing tiers, any free tier, the closing-revenue target for the plan period, and the
+          customer mix that produces it. The figures in this panel are an <em>illustrative example</em> &mdash; replace
+          every value from the operator's financial model worksheet.</p>
         <div class="grid">
           <div class="row"><span class="k">Cash at incorporation</span><span class="v">£5,000</span></div>
-          <div class="row"><span class="k">Cash after raise</span><span class="v">£355,000</span></div>
-          <div class="row"><span class="k">Capex at M0</span><span class="v">£34,000</span></div>
-          <div class="row"><span class="k">Cash after capex</span><span class="v">£321,000</span></div>
-          <div class="row"><span class="k">Burn (M1–M2 / M3–M9 / M10+)</span><span class="v">£48k / £53k / £58k</span>
+          <div class="row"><span class="k">Cash after raise</span><span class="v">£330,000</span></div>
+          <div class="row"><span class="k">Capex at M0</span><span class="v">£30,000</span></div>
+          <div class="row"><span class="k">Cash after capex</span><span class="v">£300,000</span></div>
+          <div class="row"><span class="k">Burn (M1–M2 / M3–M9 / M10+)</span><span class="v">£45k / £50k / £55k</span>
           </div>
-          <div class="row"><span class="k">MRR · Month 6</span><span class="v">£24,000</span></div>
-          <div class="row"><span class="k">MRR · Month 12</span><span class="v">£60,000</span></div>
-          <div class="row"><span class="k">Customers · M12 (Solo / Office)</span><span class="v">100 / 5</span></div>
+          <div class="row"><span class="k">Revenue · Month 6</span><span class="v">£24,000</span></div>
+          <div class="row"><span class="k">Revenue · Month 12</span><span class="v">£60,000</span></div>
+          <div class="row"><span class="k">Customers · M12</span><span class="v">~100</span></div>
           <div class="row"><span class="k">Break-even month</span><span class="v">M12</span></div>
-          <div class="row"><span class="k">Cash · Month 12</span><span class="v">£36,000</span></div>
+          <div class="row"><span class="k">Cash · Month 12</span><span class="v">£40,000</span></div>
         </div>
       </div>
     </div>
@@ -1397,27 +1335,26 @@
           <tr>
             <td class="l">Y1 close (M12)</td>
             <td class="l">Round 1 deployed</td>
-            <td>105 (100 Solo + 5 Office)</td>
-            <td>£0.72m (£60k MRR)</td>
-            <td class="l">Loop integration proven; Muvin (Adam &amp; Jamie) and Beacons (Alex) both running as
-              founder-operated pilots; 100+ production systems live across the customer base.</td>
+            <td>~100</td>
+            <td>~£0.7m (£60k MRR)</td>
+            <td class="l">Wedge and beachhead proven; founder-operated or lighthouse customers live; production systems
+              running across the customer base.</td>
           </tr>
           <tr>
             <td class="l">Y2 close (M24)</td>
-            <td class="l">Round 2 (M9, £1m) deployed</td>
+            <td class="l">Round 2 (M9) deployed</td>
             <td>~500</td>
             <td>£3m</td>
-            <td class="l">Every UK property CRM integrated; marketing into the full UK estate-agency workforce; senior
-              hires added on top of the Y1 junior engineer (senior platform engineer, head of customer success, head of
-              growth); {{ BRAND_NAME }} established as the operating layer.</td>
+            <td class="l">Category integrations complete; marketing into the full target segment; senior hires added on
+              top of the Y1 team; {{ BRAND_NAME }} established as the operating layer.</td>
           </tr>
           <tr>
             <td class="l">Y3 (M25+)</td>
             <td class="l">Internationalisation round</td>
             <td>&mdash;</td>
             <td>&mdash;</td>
-            <td class="l">International expansion. Primary candidate: North America. Same conversational architecture;
-              different CRM landscape; the playbook is replicable.</td>
+            <td class="l">International expansion into the first overseas territory. Same architecture; different local
+              landscape; the playbook is replicable.</td>
           </tr>
         </tbody>
       </table>
@@ -1452,22 +1389,22 @@
             <tr>
               <td class="l">Product &amp; engineering</td>
               <td>40%</td>
-              <td>£140,000</td>
+              <td>£160,000</td>
             </tr>
             <tr>
               <td class="l">Business development &amp; GTM (events, training delivery, travel)</td>
               <td>30%</td>
-              <td>£105,000</td>
+              <td>£120,000</td>
             </tr>
             <tr>
-              <td class="l">Infrastructure &amp; operations (hosting, compute, Pi inventory)</td>
+              <td class="l">Infrastructure &amp; operations (hosting, compute, device inventory)</td>
               <td>15%</td>
-              <td>£52,500</td>
+              <td>£60,000</td>
             </tr>
             <tr>
               <td class="l">Working capital, legal &amp; compliance (corporate, data, AI regs, SEIS/EIS)</td>
               <td>15%</td>
-              <td>£52,500</td>
+              <td>£60,000</td>
             </tr>
             <tr class="total">
               <td class="l">Total raise</td>
@@ -1488,30 +1425,22 @@
             </tr>
           </thead>
           <tbody>
+            <!-- One row per founder. Replace these example rows with the actual holders,
+                 roles and post-dilution percentages; keep the Founders / New investors rows. -->
             <tr>
-              <td class="l">Joel Smalley</td>
-              <td>Product, CTO</td>
-              <td>24.95%</td>
-            </tr>
-            <tr>
-              <td class="l">Adam Mackay</td>
-              <td>BD, CEO &middot; Muvin</td>
-              <td>24.95%</td>
-            </tr>
-            <tr>
-              <td class="l">Alex Pelosi-Buchanan</td>
-              <td>Distribution</td>
-              <td>16.00%</td>
+              <td class="l">Founder name</td>
+              <td>Role</td>
+              <td>00.00%</td>
             </tr>
             <tr>
-              <td class="l">Jamie Fisher</td>
-              <td>Pilot &middot; Muvin</td>
-              <td>7.10%</td>
+              <td class="l">Founder name</td>
+              <td>Role</td>
+              <td>00.00%</td>
             </tr>
             <tr>
-              <td class="l">Roger Black / Steve Backley</td>
-              <td>BackelyBlack Distribution</td>
-              <td>7.00%</td>
+              <td class="l">Founder name</td>
+              <td>Role</td>
+              <td>00.00%</td>
             </tr>
             <tr class="total">
               <td class="l">Founders</td>
@@ -1530,30 +1459,23 @@
 
     <section class="block">
       <h2>The team.</h2>
-      <p class="no-dropcap"><strong>Joel Smalley</strong> runs product and engineering. He built the underlying architecture of the
-        platform from the ground up and assigns the {{ BRAND_NAME }} version to {{ COMPANY_LEGAL_NAME }} at incorporation, with
-        full, exclusive rights. Joel also runs <em>The Maxy
-          Institute</em>, where he teaches professionals &mdash; solicitors, accountants, architects, recruiters, estate
-        agents, etc. &mdash; how to use
-        AI effectively in their day-to-day work.</p>
-      <p><strong>Adam Mackay</strong> runs sales and business development. He is a working estate agent and co-founder
-        of <em>Muvin</em> with Jamie Fisher. Adam, Jamie, Alex Pelosi-Buchanan, Roger Black and Steve Backley work
-        together informally as <em>Real Agency</em>, an estate agency network, offering elite coaching and access to
-        network products, like {{ BRAND_NAME }}.</p>
-      <p><strong>Two founder-operated pilots run concurrently from week 1: Muvin and Beacons.</strong>
-        <em>Muvin</em> (Adam &amp; Jamie Fisher) is the first agency on the platform. <em>Beacons</em> (Alex
-        Pelosi-Buchanan's own agency) is the second, running in parallel. Both are real, paying estate-agency businesses
-        operated by {{ BRAND_NAME }} founders &mdash; demonstrating that the people promoting the product are active users
-        of it. They generate the first case studies; they are not the funnel itself.
+      <p class="no-dropcap">One paragraph per foregrounded founder: name, the function they run, and the one credential
+        that makes them the right person for it. Where a founder built the platform, state that they assign their work
+        to {{ COMPANY_LEGAL_NAME }} at incorporation with full, exclusive rights.</p>
+      <p>For each commercial or domain founder, state their role and the operating experience that gives the venture
+        distribution or credibility in its market. If the founders operate a network or prior venture that seeds early
+        customers, name the relationship in one line.</p>
+      <p><strong>Name any founder-operated or lighthouse pilots running from week 1.</strong> State who runs each, what
+        they pay, and that the people promoting the product are active users of it. These generate the first case
+        studies; they are not the funnel itself.
       </p>
     </section>
 
     <section class="block">
       <h2>Headcount cover.</h2>
-      <p>The plan above is Joel and Adam only at start. Two founders can comfortably serve 10 paying users. Past that,
-        a product engineer (i) joins around month 3 (forward deployment, support, training, dev support); a customer success
-        hire (ii) joins around month 10, coinciding with Round 2 close. Each hire fires when the paying-user count justifies
-        it.</p>
+      <p>State who is on the team at start and how many paying customers that team can serve. Then the first hires and
+        their trigger conditions: the role, roughly which month it joins, and the paying-customer count that justifies
+        it. Each hire fires when the count justifies it, not on a calendar.</p>
     </section>
 
     <div class="page-num">Page 7 / 7</div>