Product catalogue — our services as products

Young, 2026-10-17: "work on which products we should offer based on Vercel Example — they give us a platform to showcase our services."

The insight that shapes this list: we are already running the Vercel Docus template (docs-site/package.json: docus: latest, nuxt: ^4.4.8). The template library is not aspirational for us — it is the catalogue of what we can already deploy, priced and packaged.

1. The product ladder

Each product is a named, priced bundle on the template that delivers it. All verified live or from the catalogue today.

2. The two pilot customers, mapped

2.1 Young Le — youngle.au

Services: Docs + Pulse websites.

So P1 + P6 are already delivered for this customer. The one gap is the apex youngle.au — it serves nothing. A landing page at the apex is the missing piece and would be the showcase Young is asking for (P5).

2.2 YukonIT — yukonit.com.au

Services: KB Website + EVE + Medusa + StoreFront.

This is the important finding. YukonIT is already a trading hosting business. That changes the shape of the engagement: we are not building a shop for a blank slate, we are adding KB + EVE + Medusa + storefront to an existing operator — who will judge us by whether our stack is better than what they already sell.

The delivery set for YukonIT = P1 (KB) + P2 (storefront) + P4 (EVE) + hosting. Exactly the bundle in business-plan-v2, and the pilot that proves the A$119 tier.

3. Why this catalogue and not the other 200 templates

The Vercel library has ~200 entries. I selected on three rules:

1. Licence-clean and self-hostable. Docus (MIT), Medusa (MIT), EVE (Apache-2.0). Excluded: Shopify/Hydrogen (platform lock), Saleor Paper (FSL — not resellable).
2. We already run it or have a verified study. P1 is live; P2–P4 have Tam's measured studies behind them. Nothing here is a new bet.
3. It maps to a price we can defend. Each product has a number in business-plan-v2-aud-allowance.md or services-pricing-model-aud.md.

Deliberately excluded: the 14 eve Slack/iMessage agent templates (they sell Slack agents, a different product), and all Shopify/Salesforce/Wix storefronts (platform lock — the customer would own nothing).

4. The showcase angle — what "platform to showcase our services" should mean

Young's framing is right, and it suggests a concrete build: a public services site that is itself the demonstration.

• It runs Docus (P1) — the same stack we sell.
• It hosts live demos of P2/P3/P4 rather than screenshots.
• It lists the prices from the business plan.
• It is the apex youngle.au landing that is currently missing.

That is one build that closes a measured gap and creates the shopfront. Nova's lane for the frontend, Tam's for the content port, Sol's for the tenant wiring.

5. What I need decided (not mine to rule)

1. Apex youngle.au — build the showcase landing there? (Currently serves nothing.)
2. YukonIT scope — KB + EVE + Medusa + storefront as one pilot bundle, or phased?
3. P7 managed hosting — do we sell raw hosting to tenants, or only the full bundle?

Honest limits

• Product prices live in the two plan docs; this doc names the products, not new prices.
• youngle.au returning 000 could be DNS, not hosting — I measured the HTTP response, not the DNS record.
• YukonIT's existing site means the Medusa work may need to coexist with their current platform; that is an integration question for Sol, not a pricing one.