Skip to content

Evaluate GrowthOS in one week

A fair week: pick Path A (idea) or Path B (existing SaaS), stay Native, generate a real backlog, start a Pro sprint, confirm one agent claim. Do not evaluate time tracking, automations, SSO, burndown, or executive dashboards — they are coming soon. Do not evaluate Connected unless you are an Enterprise design partner.

  • Who: Evaluator, design partner, or founder doing a one-week trial
  • Time: Five working days
  • Plan: Use Pro if you will start a sprint (recommended for eval). Free cannot show sprints.
  • Run a script you can repeat in a live demo.
  • Score Idea Lab + Native execution + MCP — not a tracker you do not have.
  • Procurement or a cofounder asked “does this replace our planning stack?”
  • A Pro trial if sprints are in scope. A gos_ key for the claim day.
  • Start at Choose your path, then this catalog.
  1. Day 1: Pick Path A or B. Create the project. Do not invite the whole company yet.
  2. Day 2: Finalize PRD (or living PRD). Approve phases. Skip or approve UX Spec.
  3. Day 3: Backlog + DoD. Confirm Native (no Jira on Team).
  4. Day 4: Pro sprint ACTIVE. Today + My Tasks. Optional first invite.
  5. Day 5: Mint gos_, one confirmed agent claim, ## Agent handoff. Stop. Write the eval notes.
  • You can say yes/no on planning + Native + one agent ticket — without blaming coming-soon modules.
  • If you only have 15 minutes on day 5, use Founder to Cursor — not the whole week’s path.
  • Spending the week clicking coming-soon nav items.
  • Evaluating Connected on a Team workspace.
  • Calling the week a failure because Idea Lab → backlog did not fit in 15 minutes.