# FORGE — Checklists

Every checklist from all eight systems.

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

## Validate · Market signal checklist

Five signals that people will pay. Check only what you can prove with a link, screenshot, or a name.

- [ ] People already pay for a worse or more expensive version of this.
- [ ] The problem is asked about repeatedly in a community I can name, in the last 90 days.
- [ ] A competitor shows visible sales, reviews, or a waitlist.
- [ ] At least three people responded with interest to a one-sentence description.
- [ ] At least one person offered to pre-order or asked how to pay.

## Build · Quality checklist

Run before writing a sales page. Every item is a refund prevented.

- [ ] A stranger can find where to start within 30 seconds of opening the product.
- [ ] Every module ends in one specific action, not a summary.
- [ ] Every referenced template, worksheet, or file exists and opens.
- [ ] No lesson is longer than 10 minutes to read or watch.
- [ ] Instructions use the buyer's words from your research, not jargon.
- [ ] There is one worked example for every template.
- [ ] The after state is reachable using only what is inside.
- [ ] You have done every action yourself with a fresh copy.
- [ ] File names and headings are consistent and numbered in order.
- [ ] Nothing inside promises income or results you cannot back up.

## Storefront · Checkout checklist

Test the purchase path yourself before anyone else does.

- [ ] Buy the product with a real card (refund yourself after) and confirm access arrives.
- [ ] Price on the page matches the checkout price.
- [ ] The confirmation page or email says exactly how to access the product.
- [ ] Refund terms on the page match your platform settings.
- [ ] Page loads and reads correctly on a phone.
- [ ] Every link on the page works.
- [ ] Support contact is visible and monitored.
- [ ] No claims of income or guaranteed results anywhere.
- [ ] Testimonials, if any, are real and permitted.
- [ ] Analytics or link tracking, if used, is optional and does not block purchase.

## Launch · Pre-launch checklist

Everything true before day one.

- [ ] Sales page passes the checkout checklist.
- [ ] Product access works from a fresh purchase.
- [ ] Launch calendar copied into your real calendar with dates.
- [ ] Every post and email drafted, at least in outline.
- [ ] Support inbox monitored daily during launch.
- [ ] Refund process written down.
- [ ] Your positioning three lines are memorized.
- [ ] Analytics or link tracking decided (optional) and set up if used.

## Launch · Launch day checklist

The order of operations on the day the page opens.

- [ ] Buy once more from a private window to confirm the path.
- [ ] Send the launch email.
- [ ] Publish the main platform post with the price.
- [ ] Pin the post or update your bio link.
- [ ] Reply to every comment and reply within the day.
- [ ] Record questions asked for tomorrow's content.
- [ ] Check sales and access issues before end of day.
- [ ] Write down one number: visitors, if you have it, or replies if you do not.

## Launch · Analytics checklist

What to record after a launch without any paid analytics tool.

- [ ] Sales per day of the launch (from your platform dashboard).
- [ ] Visitors per day if your platform shows them; otherwise link clicks or replies.
- [ ] Which post or email preceded the most sales.
- [ ] Every question asked, grouped by theme.
- [ ] Refunds and the stated reason.
- [ ] The single change you would make next launch.
- [ ] Your conversion rate (sales ÷ visitors) entered in the conversion calculator in Optimize.

## Distribute · Distribution checklist

Weekly. Ten minutes.

- [ ] Posted on the primary platform every scheduled day.
- [ ] Repurposed at least three posts to the secondary platform.
- [ ] Replied to every comment and DM.
- [ ] Recorded reach and clicks (or saves) per post.
- [ ] Identified the top post of the week and why.
- [ ] Next week's calendar filled.
- [ ] Bio link checked and working.