Chapter 1
About Page — Sharpened
What Shipped
New Hero Section
- Rewrote headline and subhead
- Tighter, more direct product framing
- Removed vague category language
Cleaner Product List
- Products described by what they do
- Removed 'coming soon' placeholders
- Consistent description format across all products
Better Examples
- Replaced category descriptions with dollar-denominated pain
- "Losing $200 every no-show" vs "local business owner"
- Specificity is the sell
Mobile-Responsive
- Layout tested at 375px
- Grid collapses cleanly
- No horizontal overflow
What Worked Well
💰
Dollar-denominated pain beats category descriptions
"Losing $200 every no-show" lands differently than "appointment-based small business." The first is a problem. The second is a demographic. Writing for the problem is what makes copy sellable — not clever phrasing, not brand values. Specificity does the work.
📐
Testing UI locally before deploying
Iterated on layout and copy locally before pushing. Multiple layout passes in one deploy instead of one deploy per change. Dramatically faster feedback loop — no deploy queue, no 100/day limit risk, no waiting on Vercel build.
Chapter 2
The Armory — Built from Scratch
What Shipped
README + TEMPLATE
- docs/armory/README.md — purpose and structure
- docs/armory/TEMPLATE.md — standard schema
- Fields: buyer, pain, outcome, objections, vertical fit
- Demo story section on every card
8 Modules
- Missed Call Follow-Up
- Estimate Reminder Sequence
- Jobs Pipeline
- Review Request
- Lead Intake
- Photo AI Caption
- Document Q&A
- Session Recap
4 Engines
- Guided Workflow Engine (PilotLight)
- Local History Engine (Flyback)
- Inngest Sequence Engine (Forge)
- Vertical Config System (Armory)
4 Packs
- Contractor Pack (Gino's Electric — live)
- Local Service Pack (cleaners, detailers)
- Auto Shop Pack
- Salon & Spa Pack
What Worked Well
📂
Two armory layers — both are needed
The existing docs/armory.md and the new docs/armory/ folder cover different layers: armory.md is a sales-facing config catalog (what to show a client), while the folder is an engineering and business catalog (how things are structured and what they cost to build). Neither replaces the other. Both stay.
🗂️
A schema forces you to answer the hard questions
Writing every module and pack through a fixed schema (buyer, pain, outcome, objections, demo story, pricing) means you can't write a card unless you actually know who buys it and why. Several cards revealed gaps in the product story — objections we hadn't thought through, outcomes that were too vague. The schema is a quality gate.
🔁
Modules compose into packs — packs compose into clients
The Contractor Pack is just: Lead Intake + Missed Call Follow-Up + Estimate Reminder + Jobs Pipeline + Review Request. Each module already existed. The pack is just a named configuration of them. This is the ForgeKit model in practice — build once, combine differently, deliver to any vertical.
Chapter 3
The Discovery — ShowUp Named
What Shipped
ShowUp — Named & Committed
- Tagline: "ShowUp. No more no-shows."
- Target: salons, barbershops, groomers, massage, med spa
- Core flow: book → remind → confirm/reschedule → no-show rebook
- Pricing hypothesis: $99–$149/mo (lighter than Forge)
- Standalone product, not a Forge module
Core SMS Flow
- Day-before reminder: confirm or reschedule?
- 2-hour reminder: see you soon
- No-show: automatic follow-up to rebook
- Simple reply-to-respond — no app needed for the customer
Armory Home
- Local Service Pack — updated to include appointment confirmation
- Salon & Spa Pack — written with ShowUp in mind
- ShowUp-specific pack card: to create next session
Why Standalone?
- Forge requires contacts, pipeline, Clerk orgs, DB migrations
- A salon owner needs: phone number, appointment time, SMS out
- ShowUp can be set up in 30 minutes
- Lower price = faster yes = faster first revenue
What Worked Well
🎯
Pain mapping found a gap Forge doesn't fill
Forge is powerful. That's also why it's the wrong tool for a salon owner who just wants fewer no-shows. The discovery session forced the question: "what does this business actually need?" Answer: not a CRM. A text reminder. ShowUp is the result of being willing to say Forge is too much for this buyer.
⚡
Product decisions are faster when the Armory exists
Because the Salon & Spa Pack already had the buyer profile, pain, sequences, and pricing written out, the ShowUp decision took minutes — not a whiteboard session. The catalog did the thinking. This is the point of the Armory.
Rules Added to Playbook
1
Test UI locally before deploying — always
Deploy-and-check is one deploy per guess. Local iteration is instant. The only time you deploy is when the thing is ready. Layout bugs, opacity, copy changes — all of that happens locally.
2
Write dollar-denominated pain, not category descriptions
"Losing $200 every no-show" is copy. "Appointment-based small business owner" is a marketing brief. Copy closes. Briefs don't. Every product card, every pitch, every About page section should lead with the loss, not the label.
3
Two Armory layers — don't collapse them
docs/armory.md is the sales catalog (what to configure for a client). docs/armory/ is the engineering catalog (how modules are structured, what they cost to build). Both have a job. Keep them separate.
4
When Forge is the wrong tool, build a lighter one
Not every pain needs a full CRM. Before defaulting to "that's a Forge feature," ask: could this be a standalone product? ShowUp exists because the answer was yes. A lighter product with a lower price point can reach buyers Forge never will.
"Losing $200 every no-show." That's a product. A demographic isn't.
Discovery session · ForgeKit · Medina OH · 2026-06-18
Next Session — Start Here
Open Items
New Product
ShowUp — product definition + stack — Product is named and committed. Next session: define the data model (appointments, businesses, contacts), pick the stack (Forge patterns or lighter?), and build the first screen. The goal is a working SMS reminder loop by end of session.
Feature
ShowUp pack card — Write the ShowUp-specific Armory pack card (docs/armory/packs/showup-pack.md). Buyer, pain, sequences, objections, demo story, pricing. This should be done before the first line of code.
Blocker
A2P 10DLC for Forge SMS — Still pending. Check Twilio console for brand registration status. This gate applies to ShowUp too — plan for 2–4 week lead time on any new number.
Deploy
About page + PWA manifest — Still staged from June 17 (hit Vercel 100/day limit). Run vercel --prod from forgekit-website/ to push the pending commits.