Execution Seasons
Plan weekly commitments with proof standards, attach evidence, and build a track record that cannot be backfilled.
An Execution Season is a structured operating window — an eight-week template or a custom range — in which your startup calls concrete weekly commitments, attaches a proof standard before the work begins, and closes each commitment against what actually happened.
Seasons extend the Verified Execution Record: every commitment, outcome, miss, reset, and review accumulates on your startup profile with the original commitment visible relative to the result. Anyone can reconstruct a favorable history after the fact; a season preserves proof of when each claim was made.
Sureshake never computes a universal founder, velocity, or fundability score. Your record keeps its underlying dimensions so each investor applies their own thesis.
Before your first season: the baseline
A season starts from a baseline — the founder-confirmed snapshot of where the company actually is before the work begins.
- Baseline fields carry their own evidence and are confirmed by the founder.
- A locked baseline is immutable. Mistakes are fixed through corrections, which preserve the original entry and its timestamp.
- The baseline records constraints and assumptions so later outcomes are read in context.
Running a season
Choose the eight-week template or a custom duration, set the primary outcome, link your baseline, and pick a cadence (weekly, biweekly, or monthly). Phases and milestone events give the season its shape.
Each commitment states the outcome, what "done" means, and the proof standard — the evidence you will show — before the week starts. Commitment quality warnings flag vague or unfalsifiable phrasing, and optional AI rewrite proposals stay pending drafts until you explicitly accept them.
Evidence can come from multiple sources, including connected systems. Missing evidence is an explicit state — a commitment without proof is never silently treated as complete.
Close each commitment against its original text. Commitments are versioned: edits after the week starts are guarded and preserved in the version history. A missed commitment can be reset — the reset links back to the miss instead of erasing it.
Structured weekly reviews summarize planned versus observed work, with configurable prompts and editable AI drafts. When the season completes, a Season Review consolidates the record.
The execution calendar
The calendar shows your season the way a training plan shows a program:
- Views. Today, week, month, and season views — each request names its view, time zone, and anchor date explicitly.
- Rescheduling history. Moving an item preserves where it was; the calendar never rewrites the past.
- Private details, shared outcomes. Day-to-day calendar detail stays private to the team. What followers see is the outcome record, not your working calendar.
Who can see a season
Season visibility uses the startup profile's audience tiers — public,
follower, capital, diligence, or custom. Public visitors see public
called shots and closed outcomes; approved followers see the current season's
target, progress, and approved weekly updates. See
Startup Capital Marketplace for how
tiers, follow requests, and investor access work together.
API
Seasons, commitments, evidence, reviews, and the calendar are fully API-accessible — see the Execution API reference.