Instructions:

1. Duplicate this document to your workspace.
2. Update the entry date and fill out your first Check-In Interval.

<aside>

Examples

Check-in Intervals | Simulations

</aside>

Check-in Intervals

Focus: Bridging the gap between initial conviction and market proof.

1. STAGE + CONSTRAINT

Identify the bottleneck. You can have many problems, but only one constraint.

<aside>

Which one is preventing the Direct Flight Path?

• [ ] Distribution
• [ ] Activation
• [ ] Retention
• [ ] Monetization
• [ ] Positioning
• [ ] Build Speed
• [ ] Capital </aside>

2. UVP NORTH STAR ANCHOR

The Fixed Point. Do not change this unless the entire strategy has shifted.

<aside>

• The Unique Mechanism: We help [Audience] achieve [Outcome] by [Specific Technical/Process Unlock].
• The Anchor Metric: (Single metric that proves the mechanism is working) ____________________
• The Dependency: What is the one technical milestone required to unlock the next $1M in value? ____________________ </aside>

Capital Diligence (if raising)

<aside>

• Raise Amount: $____________________
• Primary Objective: To move the Anchor Metric from [Current] to [Goal].
• Runway/Burn Logic: This capital removes the [Constraint] and provides [X] months of runway. </aside>

3. 🔁 THE TEST (Pressure-Test)

Did you test for confirmation (blind-spot), or did you use Critical Logic to attack your riskiest assumption?

<aside>

• Constraint Being Attacked: _________________________________________________

• The Effort (Input): (How many times did you force the mechanism to run?)

  ---

• The Signal (Output): (The specific metric that proves the constraint was bypassed.)

  ---

• The Failure Gate: (The specific result that proves your hypothesis is wrong.) </aside>

• The 1-Line Focus: "If you had to bet your entire remaining runway on one data point that proves your Unique Mechanism isn't just a theory, what is that point?"
• Proof vs. Noise: Don't look for "likes" or "interest"; look for the moment behavior changed. Isolate the one step where your logic usually fails and run real-world interactions against it.
• Setting a Failure Gate: Be aggressive. If your mechanism is a "Must-Have," it should survive friction. (Example: "If <10% of users complete this high-friction upload, our mechanism isn't strong enough.")