Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Minimal Toolchain, Max Push

Overcomplicated tool stacks are energy sinks. Endless apps, countless clicks, and buried templates turn momentum into frustration. The more you juggle, the less you ship. Strip the noise. Focus on what moves you forward.

The Minimal Stack

Tools should remove friction, not add it. The minimal stack for momentum is boring on purpose: a timer, a notes doc, and a way to capture proof. Everything else is optional. The more clicks between you and a ship, the less you will ship. Keep the stack light and the templates handy. If you want to start fast, copy these and begin:

Daily Proof

Use this single entry per session. Keep it short and visible.

Date: YYYY‑MM‑DD

Artifact: <what changed>

Link/Screenshot: <url or path>

Why It Matters: <one sentence>

Ask Sent?: Y/N — To: <name/channel> — Question: <one line>

First Reply Time: <e.g., 6h> — Latency: <hours>

Next Move (staged): <first line you’ll type tomorrow>

Example

Date: 2025‑09‑16

Artifact: Added welcome line + primary CTA on onboarding screen

Link/Screenshot: https://staging.example.com/onboarding; clip: loom.com/…

Why It Matters: clarifies next step for first‑time users

Ask Sent?: Y — To: Ana (DM) — Question: “Does this welcome make sense in under 10 seconds?”

First Reply Time: 6h — Latency: 6

Next Move (staged): Replace button copy with user phrasing

Ask3 Outreach Script

Three messages, one clear question, easy reply.

# Context

I’m working on <product/feature> for <audience>. I shipped a tiny slice today and want to sanity‑check one thing.

# Script (DM or Email)

Hi <name> — quick one?

Could you <action: “try this first screen” / “scan this headline” / “watch this 20s clip”> and tell me <one question: “where you paused” / “if the promise is clear” / “if you’d click”>?

Link: <url>

A one‑line reply (even 👍/👎) is perfect. Thank you!

# Variants

- Comprehension: “Does this make sense in under 10 seconds?”
- Friction: “Where did you hesitate?”
- Value: “If this solved <pain>, would $<price>/mo feel fair?”

# Log (copy into proof entry)

- Sent: <date/time> — To: <name/channel> — Q: <question>
- First Reply: <time> — Latency: <hours>

One‑Page PRD

# One‑Page PRD

## Problem

Describe the user’s pain in their words (1–3 sentences).

## Audience

Who is this for (be specific) and where you can reach them.

## Outcome

The single action you want (e.g., “first‑run success,” “reply,” “trial started”).

## Scope (Thin Slice)

The smallest version that teaches you something true (one screen, one task, one CTA).

## Risks / Unknowns

Top 2–3 things you’re testing (e.g., comprehension, friction, value).

## Measure

One signal you’ll track this week (proof day, finish rate, latency, or a specific event).

## Demo Plan

How you’ll show it in 20–30 seconds (clip/screenshot), plus the ask you’ll make.

## Notes

Links, references, quotes from users that shape copy or flow.

Weekly Note

# Week: YYYY‑MM‑DD → YYYY‑MM‑DD

## Scoreboard

- Proof Days: <x/7>
- Finish Rate: <slices/sessions = %>
- Avg Feedback Latency: <hours>

## Lever + Theme

- Lever: <Starts / Finish Rate / Feedback Speed / Evidence Strength>
- Theme: <Discovery / Activation / Revenue / Retention>
- Stack (2–3 moves): <e.g., Slice‑Box‑Button>

## Commitments

- Ask: <specific ask you will make this week>
- Demo: <day/time + audience>
- Monday Staged: <link to file + “Ship:” line>

## Friday Highlight (fill at end of week)

- Artifact 1: <what + link> — Why it mattered
- Artifact 2: <what + link> — Why it mattered
- Next: <one change you’ll try next week>

Timers and Proof Capture

A timer can be an app or a kitchen timer. You need start, stop, and a chime you cannot ignore. A notes doc or sheet holds your three numbers, your weekly note, and your museum of proof. Keep it in a place you can open in one click. A screenshot and screen‑record tool captures before/after and short clips. Set hotkeys you will remember.

Templates That Speed You Up

Templates save time on decisions. The Daily Proof entry (../templates/daily-proof.md) gives you a one‑minute close. The Ask3 script (../templates/ask3.md) has blanks you can fill and send. The One‑Page PRD (../templates/one-page-prd.md) clarifies a slice before you build. The Weekly Note (../templates/weekly-note.md) sets the Sunday scoreboard, lever, theme, and demo.

Do You Need Project Management?

You do not need project management software to run this system. If you already have one, use it to store slices written as outcomes and to tag discovery, activation, and revenue. If you don’t, a single doc works. The proof is the progress. The doc is the map.

Add Tools Only for Bottlenecks

When you add a tool, add it because a bottleneck hurts. If you spend fifteen minutes every day stitching screenshots into a post, create a tiny script or a shortcut that does it in two. If you lose track of asks, set up a canned email template and a label to collect replies. Advanced automations can wait — focus first on tools that keep reflection visible and habits intact.

Keep Tools Visible

Keep the stack visible. Put the proof log in your dock. Pin the outreach template to your clipboard manager. Leave the PRD template where you can duplicate it without thinking. Friction hides in clicks and searches. Expose what you need and you will use it.

Match Your Style

Tools should fit your style. If you love paper, a notebook with a weekly page for numbers and a daily line for proof works. If you love spreadsheets, a sheet with formulas for finish rate and average latency works. The method is the same. The best tool is the one you will open when you are tired.

With your stack lean and your tools tuned, you’re ready to build momentum that lasts. Next, we’ll explore how to sustain cadence and unlock advanced strategies to keep the push going strong.

Indie10k Shortcut

All the templates in this chapter are designed to be copied and used independently—no dependencies, just fast starts. If you prefer to keep full control and zero reliance on outside tools, you can copy these templates into your own docs, sheets, or notes and begin immediately.

However, Indie10k (https://indie10k.com) also provides structured path to track all these records, reducing setup friction and making it even easier to get started.

You can choose either approach: use the manual templates for a fully independent process, or let Indie10k handle the setup so you can focus on shipping. Both paths are valid—the best system is the one you’ll actually use.