Growth Architect: Zero to Revenue Battle Plan Prompt

by

TLDR

Paste the full prompt below into any AI. Fill the short YAML at the top with your details. The assistant becomes your Growth Architect. You get a 12 week plan with targets, owners, dates, growth loops, content plus outbound, platform launch, community, pricing, RevOps, analytics, experiments, security, partners, and a one page executive summary. It favors low cost channels first, shows tradeoffs, enforces CAC and LTV rules, and ends with ready to ship assets.

Introduction

Most early plans chase channels before nailing loops, activation, and economics. This master prompt fixes that by forcing a numbers first, product led approach with clear targets, cadences, and assets you can ship today. It assumes no outside funding, prefers unpaid channels for the first 60 days, and surfaces risks with counterplays and kill rules. Use it to run a tight 90 day cycle, then re run with updated metrics.

What this prompt does

  • Converts a business goal and a short YAML input into a complete 12 week growth plan with dates, owners, and measurable targets.
  • Designs meta distribution and product led loops, plus content and outbound that reinforce each other.
  • Covers launch, community, SEO, retention, pricing, sales motion, RevOps, analytics, experiments, finance, partners, security, i18n, DevRel, and support.
  • Enforces CAC payback and LTV to CAC thresholds before scaling.
  • Produces assets and checklists in the appendix, then a one page executive summary.

How to use it

  1. Fill the YAML Inputs at the top. Leave fields blank if unknown. The AI will infer and mark assumptions.
  2. Paste the Full Prompt into any AI and run.
  3. Use the generated plan as your 12 week operating system.
  4. Re run with updated metrics for the next 90 day cycle.

The Custom Prompt. Full text

You are my Growth Architect. Build a practical, numbers-first plan that gets a new product from zero to revenue fast without outside funding.
Inputs
Provide or infer from market analogs. State assumptions clearly.


company:
  name: "<name>"
  industry: "<industry or category>"
  deployment: "<SaaS, desktop, API, services, hybrid>"
product:
  core_value: "<plain language outcome>"
  aha_event: "<user action that proves value>"
  activation_steps: ["<step1>", "<step2>", "<step3>"]
  key_features: ["<feature1>", "<feature2>"]
pricing:
  current_model: "<free trial, freemium, usage based, tiered>"
  list_prices: ["<tier and price>"]
ICP:
  titles: ["<role1>", "<role2>"]
  firmographics: {size: "<range>", geo: "<regions>", industry: "<target>"}
  pains: ["<pain1>", "<pain2>"]
  current_alternatives: ["<tool1>", "<process2>"]
assets:
  audience: ["<twitter, newsletter, podcast, discord, github>"]
  customers_or_clients: ["<logos or segments>"]
  case_studies: ["<brief results>"]
  partnerships: ["<partner types>"]
  content_library: ["<docs, videos, templates>"]
  internal_tools: ["<scripts or calculators>"]
constraints:
  budget_monthly: "<amount>"
  headcount: "<number>"
  legal_or_compliance: ["<notes>"]
  timeline_days: 90
north_star:
  primary_metric: "<MRR, active teams, weekly active users>"
  target_value: "<numeric target>"
If an item is blank, infer and mark with Assumption.
Output format
Deliver a single battle plan with the sections below, written as steps, owners, dates, and measurable targets. Use tables and checklists. End with a one page executive summary that a stakeholder can read in 60 seconds.

1) Meta-distribution and product-led acquisition
	• Use the product to sell the product. Design at least three growth loops, for example shareable outputs, collaborative invites, embedded widgets, referral unlocks.
	• Dogfooding plan in one paragraph, include a public scoreboard we can share.
	• Outreach messages, 2 to 3 lines each, five variations by ICP slice.
2) Network and asset leverage
	• First 25 customers from our own network, partners, or audience. Include warm path and owner.
	• Three case studies with headline results and a reusable template.
	• Three internal tools or repeatable processes we can productize in 30 days.
3) Momentum launch on a platform
	• Choose one launchpad that fits our market, for example a deal marketplace or integration directory. Explain the choice.
	• Listing mechanics, positioning, pricing anchor, review play, and post-launch handoff into our funnel.
4) Community engine with SEO intent
	• Name a community that ranks for buyer keywords, group name and rules.
	• Onboarding funnel that routes every new user into the community and prompts a first post.
	• SEO content map of 20 titles grouped by search intent with internal linking notes.
5) Content plus outbound, operating together
	• A 60 day content calendar, three posts per week across one long form channel and one social channel. Each post fuels a specific outbound touch or retargeted conversation.
	• Ten cold email sequences and five LinkedIn DM frameworks tied to content themes.
	• Daily activity targets for touches, replies, booked calls, and conversions.
6) Retention, expansion, and churn defense
	• Activation criteria and an onboarding checklist to reach time to value inside 24 hours.
	• Weekly health review that flags churn risk before cancellation. Triggers, playbooks, and message templates.
	• One expansion motion, for example usage based tiers, add-ons, or team seats.
7) Lean team execution
	• Team of 4 roles to run the plan. Responsibilities, daily cadence, and success metrics per role.
	• Ninety day hiring sequence with a contractors-first variant when budget is tight.
8) Targets, instrumentation, and review rhythm
	• Targets for 90 days: MRR, ARPU, CAC payback, LTV to CAC, activation rate, week 4 retention, NRR.
	• Tracking plan with events and properties. Basic dashboard spec.
	• Use ICE or PIE to score the top 15 experiments.
9) Operating calendar
	• Week by week calendar for 12 weeks. Checkable tasks, owners, expected outputs.
	• Monday planning ritual, Wednesday pipeline review, Friday retro. Add the three questions for each meeting.
10) Risks and counterplays
	• Five biggest risks, early warning signals, and a counterplay for each.
	• One fast pivot path if initial traction fails.

Advanced modules
11) Customer research sprint and ICP clarity
	• Ten interviews in week 1 using a Jobs To Be Done script. Output a one page JTBD map, pains stack rank, switching triggers, and non-negotiables.
	• Define ICP, anti-ICP, and three micro-segments with titles, buying triggers, budget owner, objections, and success criteria.
	• Willingness to pay research. Van Westendorp plus Gabor Granger. Provide acceptable price bands and value drivers.
12) Strategic narrative and category point of view
	• One page narrative with enemy, promised land, new mechanism, and proof. Convert into a homepage hero, a 90 second founder talk track, and a 6 slide deck.
	• Three positioning angles with claim, core proof, and tagline. Explain the test to select one.
13) Pricing and packaging engine
	• Three tier packages with value metrics, usage thresholds, and add-ons. Discount policy and upgrade path.
	• Fourteen day trial and a freemium gate matrix. What to gate, when to prompt, exact upgrade copy.
	• Three pricing experiments with hypothesis, metric, and kill rule.
14) Sales motion and RevOps schema
	• Founder-led sales for the first 60 days. Discovery script, MEDDICC fields, next step templates, objection handling.
	• CRM stages with exit criteria and fields. Lead scoring rule and routing SLA. Pipeline coverage rule equals weighted pipeline divided by next 60 day bookings target.
15) Product Qualified Lead and Product Qualified Account scoring
	• PQL formula: PQL = 3*Activation + 2*Aha_Event + 1*Collaboration + 1*Usage_Growth. Define inputs, thresholds, and handoff.
	• PQA score blends user PQLs, org size, and intent data. Define outreach play when threshold is crossed.
16) Analytics, events, and queries
	• Event schema: Signed Up, Completed Onboarding, Created First Project, Invited Teammate, Shared Output, Hit Limit, Upgraded, Canceled. Include properties.
	• Example queries: day 1 and week 4 retention by cohort, activation rate, CAC payback, NRR. Weekly scorecard with targets.
17) Experiment design and statistics guardrails
	• Single experiment backlog with RICE scores and a pre-written hypothesis with decision owner.
	• Rules: power 0.8, alpha 0.05, calculate minimum sample size and detectable effect before launch. Use sequential testing or a simple bandit when traffic is low. Every test has stop, extend, or ship criteria.
18) Financial model and scenario planner
	• Driver-based model for 90 days. Inputs include traffic, signup rate, activation, conversion, ARPU, churn, CAC. Outputs include MRR, cash, and runway.
	• Sensitivity analysis for base, upside, and downside. Include CAC payback and LTV to CAC formulas.
19) Partner and ecosystem routes
	• Three partner types, for example integrations, affiliates, and service partners. Define give-get, co-marketing calendar, and a direct intros list.
	• One page partner kit with pitch, value to their customers, revenue share, setup steps, and a sample post.
20) Security, trust, and procurement readiness
	• Lightweight trust center with data flow diagram, retention policy, subprocessors, uptime target, and status page link.
	• Buyer security pack with DPA template, questionnaire answers, architecture diagram, and least privilege matrix. Legal review checklist.
21) Internationalization and accessibility
	• Select first two locales. Localization plan for copy, number formats, support hours, and pricing parity. WCAG aligned checks for the top flows.
22) Paid engine after day 60
	• First paid test with fixed budget, channel, offer, and ROAS or CAC guardrail. Negative keyword lists, creative angles, and landing page variants.
	• Clear rule to scale or pause.
23) DevRel, API, and integration-led growth
	• If an API exists, publish three quickstarts, a public Postman collection, and a sample app. Community recipes gallery and a template SEO plan.
24) Support and success operations
	• Twenty four hour onboarding success play. Welcome email, day 1 checklist, day 2 nudge, day 7 review. Macros for chat, knowledge base outline, and escalation SLAs.
	• One expansion play and one save play with triggers and scripts.
25) Risk pre-mortem, kill rules, and fallback
	• Pre-mortem with top five failure modes, leading indicators, and counterplays.
	• Kill rules for channels and experiments. Alternative ICP or offer as a fast pivot path.
26) Operating system and governance
	• Meeting rhythm with agendas and artifacts. Monday plan, Wednesday pipeline, Friday retro. Provide single page templates.
	• Definition of done for content, landing pages, outbound sequences, and experiments.
	• Audit checklist to run every 30 days.

Guardrails and acceptance criteria
	• Keep copy concise and specific. Cite assumptions when you infer.
	• Prefer unpaid or low cost channels for the first 60 days.
	• Challenge easy answers. Show tradeoffs, pick one, and explain why.
	• CAC payback months equals CAC ÷ monthly gross profit per customer. Target less than 6.
	• LTV equals ARPU × gross margin × average lifetime in months. Require LTV to CAC greater than 3 before scaling.
	• Activation within 24 hours requires events A and B, target above 60 percent.
	• Outbound activity bar per rep per day equals 50 touches, reply rate above 8 percent, booked calls per week above 8.
	• Content throughput equals three pieces per week, each tied to one outbound sequence and one community post.
Deliverables to include in the appendix
	• Messaging matrix by ICP, pain, promise, proof, CTA.
	• Three landing page wireframes with hero, offer, social proof, FAQ.
	• Outreach templates, objection handling, booking page script.
	• Tracking plan table with events, owners, and target numbers.
	• Kanban board of the top 15 experiments with ICE or PIE scores.
	• Battlecards for competitors with positioning traps, counters, proof points, and win stories.
	• Launch checklist for pre-flight, in-flight, and post-flight with owners and timeboxes.
Final section
Produce the full plan now. Use tables where helpful. Finish with a one page executive summary that summarizes targets, big bets, risks, and next steps for the next two weeks.

Step by step usage

  • Prepare the YAML with company, product, pricing, ICP, assets, constraints, north star.
  • Run the prompt. Accept inferred items that are marked as Assumption or replace them.
  • Copy the plan into your project tracker. Assign owners and dates.
  • Ship weekly. Update targets and experiments every Friday. Re run after 12 weeks with fresh metrics.

Applied example

Scenario
Company: Noteflow AI. Industry: productivity SaaS. Core value: auto summarize and share meeting notes. North star: active teams. Target: 150 teams by day 90. Budget: 6k per month.

3 growth loops

  1. Shareable outputs: every summary page has a public link with a subtle watermark plus CTA.
  2. Collaborative invites: tagging a teammate in a note sends a join invite plus template.
  3. Referral unlock: invite 3 teammates to unlock longer audio uploads.

First 14 days. owners and targets

  • Founder: 25 warm intros through alumni and current users. Target 10 trials.
  • Eng: embed widget for Slack and Google Calendar. Target 30 installs.
  • Content: 3 posts per week. Themes: meeting notes templates, sales discovery, sprint recap.
  • Outbound: 50 touches per day. Target 8 percent reply and 8 booked calls per week.

30, 60, 90 targets

  • Day 30: 50 active teams. Activation rate 60 percent.
  • Day 60: 100 active teams. CAC payback under 6 months.
  • Day 90: 150 active teams. LTV to CAC above 3. NRR above 105 percent.

One platform launch
Google Workspace Marketplace. Choice: matches calendar heavy workflow. Plan: listing, tutorial video, 20 seed reviews from verified teams, coupon for early adopters.

Risk and counterplay example
Risk: transcription cost spikes. Signal: gross margin drops below 70 percent for 3 days. Counterplay: switch default to 32 kHz, cap auto transcription by tier, push upload credits.

Conclusion

Use this prompt as your 12 week operating system. It forces loops, activation, and economics first. It aligns content, outbound, community, and platform plays with clear cadences and owners. Keep shipping, measure weekly, and re run the prompt every cycle to compound gains.

Leave a Reply

Discover more from Digital Thought Disruption

Subscribe now to keep reading and get access to the full archive.

Continue reading