# FORGE — 30-Day Mission Calendar

Print it. One objective, one action, one tool per day.

_Part of NIGHT//SHIFT OS. Planning material only — nothing here promises income or results._

## Day 1 — Build your skill inventory

- **Lesson:** Products come from problems you have already solved for someone. Today is not about ideas; it is about evidence of what people already come to you for.
- **Action:** Fill all three columns of the skill inventory with at least five rows each, then circle two rows that appear twice.
- **Tool:** Skill inventory (System: find)
- **Next:** Tomorrow you turn circled rows into problems in the buyer's words.
- [ ] Done

## Day 2 — Mine ten real problem quotes

- **Lesson:** A product sentence written in your words sells worse than one written in theirs. Communities and reviews are full of the exact phrases.
- **Action:** Using the problem mining system, collect ten exact quotes for one circled row from at least three sources.
- **Tool:** Problem mining system (System: find)
- **Next:** Tomorrow you shape the first product from those quotes.
- [ ] Done

## Day 3 — Write a desire statement

- **Lesson:** The desire is the outcome the buyer wants, not the feature you would build. Start there and the product shape follows.
- **Action:** Complete the market desire worksheet for your strongest row.
- **Tool:** Market desire worksheet (System: find)
- **Next:** Tomorrow you compare it to two alternatives.
- [ ] Done

## Day 4 — Compare three ideas

- **Lesson:** Ideas look strong alone and weak side by side. The matrix makes the gaps visible before you commit.
- **Action:** Fill the product idea matrix with three ideas and pick a winner.
- **Tool:** Product idea matrix (System: find)
- **Next:** Tomorrow you score the winner.
- [ ] Done

## Day 5 — Score the opportunity

- **Lesson:** A score is a forced honesty exercise. A low number today saves weeks.
- **Action:** Run the opportunity score. If RED, pick the next circled row and re-score tomorrow instead of continuing.
- **Tool:** Opportunity score (System: find)
- **Next:** Tomorrow you get a second opinion from your AI account.
- [ ] Done

## Day 6 — Get an AI second opinion

- **Lesson:** You have context; the model has breadth. The generated command carries your real inputs, so the answer is specific.
- **Action:** Generate the opportunity research command, paste it into your own AI account, and save the shortlist to your notes.
- **Tool:** AI opportunity research builder (System: find)
- **Next:** Week two is validation. Tomorrow you study the alternatives.
- [ ] Done

## Day 7 — Map three competitors

- **Lesson:** Competitors are proof of demand. Their one-star reviews are your positioning.
- **Action:** Fill the competitor workspace for three alternatives, including free ones.
- **Tool:** Competitor workspace (System: validate)
- **Next:** Tomorrow you collect the buyer's exact language.
- [ ] Done

## Day 8 — Collect customer language

- **Lesson:** Ten phrases for the problem, five for the outcome. These become your headline, hooks, and FAQ.
- **Action:** Complete the customer language research worksheet and rewrite your product sentence in their words.
- **Tool:** Customer language research (System: validate)
- **Next:** Tomorrow you book conversations.
- [ ] Done

## Day 9 — Book five conversations

- **Lesson:** People will tell you what they paid for last month. They will not accurately predict what they will buy next month.
- **Action:** Message ten people who match the buyer and ask for 15 minutes this week. Read the interview questions before each call.
- **Tool:** Interview questions (System: validate)
- **Next:** Hold the first two conversations tomorrow.
- [ ] Done

## Day 10 — Hold conversations 1-2

- **Lesson:** Record phrases, not summaries. The emotion in the story tells you how painful the problem is.
- **Action:** Hold two conversations. Paste the exact phrases into your notes on the customer language worksheet.
- **Tool:** Interview questions (System: validate)
- **Next:** Three more tomorrow.
- [ ] Done

## Day 11 — Hold conversations 3-5

- **Lesson:** By the fifth conversation you will hear the same phrase twice. That phrase is your headline.
- **Action:** Hold three conversations. Update your product sentence if the words changed.
- **Tool:** Customer language research (System: validate)
- **Next:** Tomorrow you ask for money.
- [ ] Done

## Day 12 — Send the pre-sell

- **Lesson:** Asking for money before the product exists is honest when you say it is not built yet and when it ships. Any payment is the strongest signal you can get.
- **Action:** Write the pre-sell message with the framework and send it to 10-20 qualified people.
- **Tool:** Pre-sell framework (System: validate)
- **Next:** Tomorrow you decide.
- [ ] Done

## Day 13 — Decide: RED, YELLOW, GREEN

- **Lesson:** A decision made with evidence, even a RED one, is progress. A YELLOW means rewrite and re-ask; it rarely means quit.
- **Action:** Run the market signal checklist and the validation score. Record the result in your notes.
- **Tool:** Validation score (System: validate)
- **Next:** GREEN: tomorrow you design the transformation. YELLOW: repeat days 8-12 for three days. RED: return to day 4 with the next row.
- [ ] Done

## Day 14 — Design the transformation

- **Lesson:** Buyers purchase the gap between before and after. Every module must be a required step across that gap.
- **Action:** Complete the transformation designer, including the steps you removed.
- **Tool:** Transformation designer (System: build)
- **Next:** Tomorrow you group steps into modules.
- [ ] Done

## Day 15 — Architect the modules

- **Lesson:** Three to six modules, each ending in one action. More modules is more places to quit.
- **Action:** Fill the module architect for every module.
- **Tool:** Module architect (System: build)
- **Next:** Tomorrow you list every asset.
- [ ] Done

## Day 16 — Plan resources and the MVP

- **Lesson:** The MVP is what delivers the after state in 14 days. Everything else is version two, with no guilt.
- **Action:** Complete the resource planner and the MVP planner. Set the build stop date.
- **Tool:** MVP planner (System: build)
- **Next:** Tomorrow you generate the full build plan.
- [ ] Done

## Day 17 — Generate the build plan

- **Lesson:** The product builder prompt turns your architecture into a lesson-by-lesson plan you can execute without thinking about structure again.
- **Action:** Run the product builder prompt in your AI account. Then run the curriculum prompt for module 1.
- **Tool:** Product builder prompt (System: build)
- **Next:** Build days begin tomorrow.
- [ ] Done

## Day 18 — Build module 1

- **Lesson:** Build in the order buyers will use it. Module 1 gets the most attention because it decides whether they continue.
- **Action:** Write or record module 1 and produce its worksheet with the worksheet prompt.
- **Tool:** Worksheet prompt (System: build)
- **Next:** Module 2 tomorrow.
- [ ] Done

## Day 19 — Build module 2

- **Lesson:** Keep each lesson under ten minutes. If it runs long, it is two lessons.
- **Action:** Build module 2 and its asset.
- **Tool:** Curriculum prompt (System: build)
- **Next:** Module 3 tomorrow.
- [ ] Done

## Day 20 — Build module 3 and the rest of the MVP

- **Lesson:** Finishing beats polishing. A complete rough product can be sold; a beautiful half product cannot.
- **Action:** Build remaining MVP modules and assets. Stop at the build stop date regardless.
- **Tool:** Resource planner (System: build)
- **Next:** Tomorrow you quality-check.
- [ ] Done

## Day 21 — Run the quality checklist

- **Lesson:** Every item on the checklist is a refund prevented. Do every action yourself with a fresh copy.
- **Action:** Complete the quality checklist. Fix anything unchecked before moving on.
- **Tool:** Quality checklist (System: build)
- **Next:** Packaging starts tomorrow.
- [ ] Done

## Day 22 — Stack the value and price it

- **Lesson:** Price against the cost of the problem, then check the number against three real alternatives.
- **Action:** Fill the value stack, then run the pricing lab. Write your price and its reason sentence.
- **Tool:** Pricing lab (System: package)
- **Next:** Tomorrow you name and position.
- [ ] Done

## Day 23 — Name, position, score the offer

- **Lesson:** An offer that explains itself in ten seconds outsells a better product that does not.
- **Action:** Use the naming framework, fill the positioning worksheet, then run the offer score. Fix the lowest item.
- **Tool:** Offer score (System: package)
- **Next:** Tomorrow you write the page.
- [ ] Done

## Day 24 — Write the sales page

- **Lesson:** Sections in order: promise, problem, transformation, inside, for whom, proof, FAQ, CTA. Use the buyer's words throughout.
- **Action:** Run the AI sales page builder with your real inputs. Pick a headline with the headline framework.
- **Tool:** AI sales page builder (System: storefront)
- **Next:** Tomorrow: FAQ, mockups, and the checkout test.
- [ ] Done

## Day 25 — FAQ, mockups, checkout

- **Lesson:** Buy your own product. If anything in the path confuses you, it will confuse buyers.
- **Action:** Fill the FAQ builder, make mockups with the mockup guide, publish the page, and complete the checkout checklist.
- **Tool:** Checkout checklist (System: storefront)
- **Next:** Tomorrow you plan the launch.
- [ ] Done

## Day 26 — Choose and schedule the launch

- **Lesson:** A launch is a calendar. Pick 7, 14, or 30 days based on audience size and put real dates on it.
- **Action:** Choose a launch calendar and copy it into your own calendar. Run the pre-launch checklist.
- **Tool:** Pre-launch checklist (System: launch)
- **Next:** Pre-launch content starts tomorrow.
- [ ] Done

## Day 27 — Pre-launch day 1

- **Lesson:** Tell people what you are making and why, and ask one question. Replies are your first launch content.
- **Action:** Publish the day-1 pre-launch post and email. Reply to everyone.
- **Tool:** Email copy templates (System: launch)
- **Next:** Tomorrow you show a piece of the product.
- [ ] Done

## Day 28 — Pre-launch day 2-3

- **Lesson:** Showing beats telling. One screenshot of a real worksheet answers 'what do I actually get'.
- **Action:** Publish a research-quote post and a product-preview post using the launch content plan.
- **Tool:** Launch content plan (System: launch)
- **Next:** Tomorrow the page opens.
- [ ] Done

## Day 29 — Launch day

- **Lesson:** Announce once to your list and once on your main platform, with the price stated plainly. Then spend the day replying.
- **Action:** Run the launch day checklist top to bottom.
- **Tool:** Launch day checklist (System: launch)
- **Next:** Tomorrow you set up the machine that improves this.
- [ ] Done

## Day 30 — Set up your weekly review

- **Lesson:** The launch is a spike. The weekly review is the system. One logged experiment per week compounds.
- **Action:** Fill the analytics dashboard with launch numbers, run the conversion calculator, and log your first experiment in the tracker.
- **Tool:** Experiment tracker (System: optimize)
- **Next:** Mission complete. Run the weekly review every week; continue the launch calendar you chose.
- [ ] Done