The checklist philosophy
Shipping weekly is less about heroics and more about relentless checklists. Every launch at Thingg.co runs through this exact template—no matter the product surface. It shortens debates, keeps AI co-builders aligned, and lets us handoff work mid-sprint without losing context.
Monday — Frame the bet
By noon we need a single-page brief that names the user, the problem, and the success metric. The doc includes:
- Pull signals: the insight that triggered the sprint and the evidence it’s worth chasing.
- Blocking assumptions: the three things we must prove true by Thursday.
- Launch surface: the artifact we’ll ship publicly—demo, waitlist, paid beta, or teardown.
Once the brief ships, we record a Loom so everyone—including AI copilots—can re-sync async.
Tuesday — Prototype the story
We co-design with AI tools (Midjourney, Galileo, v0) to express the product narrative fast. Checklist items:
- Create a visual north star and landing page wireframe.
- Draft the product onboarding flow with at least two critical edge cases covered.
- List the data we must capture from day one—no silent analytics debt.
Before logging off we host a 20-minute async critique in Slack so everyone can react to the artifacts.
Wednesday — Build the loop
We implement the smallest version of the user loop. For software that typically means:
- Instrument the core user action (e.g., submit a mission brief, join a room).
- Automate the follow-up or response so the user feels momentum.
- Log every state change to a shared dashboard so Friday’s story writes itself.
By the end of the day we run a red-team session to break the flow. Bugs get tickets. Crashes get fixed on the spot.
Thursday — Polish the promise
This is where the copy, the brand, and the onboarding moments get tightened. The non-negotiables:
- Ship-ready landing page with tracking links.
- Launch checklist that spells out the Friday script, timing, and owner for every channel.
- FAQ doc covering pricing, roadmap, and how to request access.
We also record a dry run of the launch demo and push it to our internal archive.
Friday — Launch and learn
Launch day is a routine, not chaos. The checklist:
- AM standup to confirm the launch window.
- Publish the landing page and toggle acquisition automations.
- Write the public changelog entry and send the Friday dispatch.
After the launch we perform a 20-minute retro. Wins, blockers, and bets for next week go straight into Notion along with metrics from the shared dashboard.
Copy the template
We keep the checklist in Notion so each new sprint starts with a duplicate. Grab it here and adapt it to your velocity. If you need more structure around research, read how we stack AI agents to run research sprints.