Launch Kit v0¶
Updated: 2026-06-06
Internal launch work round for turning AI Company from an operating system into a sellable offer.
Round Record¶
| Field | Value |
|---|---|
| Objective | Create the minimum commercial front door before soft launch. |
| Owner | Terry |
| Supporting agents | Sales, Consultant, Planner, Scout |
| Estimate band | M |
| Proposed token budget | Up to 30k tokens |
| Gate | Spec review before polishing assets; release approval before soft launch. |
| Exit criteria | Terry can explain who the company serves, what it sells, what it costs, how delivery works, and what proof asset supports the first conversation. |
How To Use This Page¶
Work top to bottom. Do not polish copy before the offer is clear.
- Fill the ICP hypothesis.
- Choose 2-3 service packages.
- Add pricing bands and minimum project size.
- Draft the website/intro page outline.
- Draft FAQ and objection responses.
- Draft proposal/SOW terms.
- Create the internal proof case study.
- Run the launch-readiness gate.
ICP Hypothesis¶
Initial target customer: small teams, founders, consultants, and professional-service firms that need useful AI-enabled tools, websites, research, or client-facing deliverables but do not have enough internal product/design/automation capacity.
Likely buyer: owner, founder, partner, director, or project lead with authority to approve a small fixed-scope project.
Pain points:
- They have ideas or manual workflows but no fast builder.
- They need a usable internal tool, website, deck, or research output quickly.
- They cannot justify a large agency or long software project.
- They want AI leverage but need human judgment and quality control.
Why AI Company can win:
- Human-led, agent-assisted workflow keeps work fast and reviewable.
- Wiki memory preserves decisions and reduces repeated explanation.
- Fixed-scope packages reduce ambiguity.
- The company can combine research, product thinking, build, test, and sales assets in one workflow.
Not ICP for v0:
- Enterprise buyers requiring formal compliance, procurement, or security review.
- Large custom platforms.
- Work requiring production support beyond a small agreed window.
- Clients who need agents to act autonomously without human review.
Service Packages¶
| Package | Buyer problem | Output | Scope boundary | Good first price band |
|---|---|---|---|---|
| Internal Tool Sprint | "We need a simple app/workflow to reduce manual work." | Small web app, automation, dashboard, or internal workflow tool | One primary workflow, simple auth/data model, deployed prototype | TBD |
| Website / Launch Page Sprint | "We need a credible web presence or offer page." | Website, landing page, copy, basic visual system, deployment | 1-3 pages, one audience, one offer | TBD |
| Research-to-Deck Sprint | "We need a clear market/client/storyline deliverable." | Brief, research summary, insights, deck outline or deck | One question, one audience, one decision/use case | TBD |
Pricing Bands¶
Use bands for internal quoting before publishing exact pricing.
| Package | Starter | Standard |
|---|---|---|
| Internal Tool Sprint (1 wk) | ¥80,000 | ¥200,000 |
| Website / Launch Page Sprint | ¥50,000 | ¥150,000 |
| Research-to-Deck Sprint | ¥30,000 | ¥100,000 |
| Band | Use | Internal guidance |
|---|---|---|
| Starter | Small, low-risk, one clear output | Simple tool, landing page, or narrow brief |
| Standard | Most first projects | Full web app, 2-3 page site, or full brief + deck |
| Custom | Larger, ambiguous, or client-facing production work | Scope first; quote after review |
Minimum acceptable project size: ¥30,000 (soft launch — no hard floor, but decline below this).
Turn-down rule: decline if estimated AI API spend exceeds $10, or if scope clearly exceeds 1 week.
Soft-launch option: ¥0 (case study trade) — client gets the work free in exchange for a testimonial and proof case. Use for first 1-2 internal/consultant clients.
Default payment terms: 50% upfront / 50% on delivery.
Website / Intro Page Outline¶
Purpose: give a warm lead enough confidence to take a call.
- Hero: AI Company builds small apps, websites, research decks, and AI-enabled workflows with human review at every gate.
- Who it helps: small teams and professional-service operators who need useful tools and deliverables quickly.
- Packages: Internal Tool Sprint, Website / Launch Page Sprint, Research-to-Deck Sprint.
- How it works: intake, plan, build, test, deliver, review.
- Proof: internal Launch Kit v0 case study.
- Quality: secure coding basics, UI review, human approval gates.
- Call to action: send a project idea or book a short scoping call.
FAQ And Objection Bank¶
| Question / Objection | Draft answer |
|---|---|
| Is this just AI-generated work? | No. AI agents help research, draft, plan, build, and test, but humans approve scope, quality, delivery, outreach, and invoices. |
| What kinds of projects are a fit? | Small tools, websites, simple games, research/deck sprints, and AI workflow automation with clear scope. |
| What is not a fit? | Enterprise platforms, highly regulated systems, large ongoing support needs, or work requiring formal compliance on day one. |
| How do you control quality? | Every project has gates: intake, spec, build, test, release, and retro. Testing includes acceptance checks and basic security checks. |
| How do you protect client data? | Keep client data minimal, use approved storage, avoid secrets in code or logs, and apply access controls for private materials. |
| How fast can you deliver? | Depends on scope. v0 offer should focus on short fixed-scope sprints rather than open-ended builds. |
| Do you provide ongoing support? | Only if agreed in the scope. Default support should be a short handoff/fix window. |
Proposal / SOW Outline¶
Use Proposal/SOW Template for the working template.
Minimum sections:
- Client and project name
- Problem / objective
- Scope and deliverables
- Out of scope
- Timeline and review gates
- Acceptance criteria
- Pricing and payment terms
- Client responsibilities
- Change request rule
- Security/privacy assumptions
- Handoff and support window
Internal Proof Case Study¶
Use Case Study Template.
Working proof:
Title: Building AI Company's Launch Kit v0 with the AI Company workflow.
Situation: The company had operating rules and agents, but no clear commercial front door.
Action: Used the internal launch workflow to define ICP, packages, pricing bands, intro-page copy, FAQ, proposal/SOW, and proof asset.
Result: TBD after completion.
Launch Readiness Gate¶
Before soft launch, Terry must mark each item:
| Item | Status |
|---|---|
| ICP hypothesis is clear enough to test | Missing |
| 2-3 service packages selected | Missing |
| Internal pricing bands and minimum project size set | Ready |
| Website/intro page draft exists | Missing |
| FAQ/objection bank draft exists | Missing |
| Proposal/SOW template exists | Partial |
| Internal proof case study draft exists | Partial |
| Payment/invoice flow is usable | Partial |
| Security/privacy basics are documented | Ready |
| Human gates are documented | Ready |
Next Slack Prompts¶
Run these in order: