# Guided first workspace

Hypothetical example: all interview counts, targets, and time limits are invented planning assumptions, not observed results.

## 1. Problem and evidence
Audience: a new workspace owner setting up a small consulting team.
Evidence: Assumption: in 8 of 12 discovery interviews, owners said they stopped after
creating a workspace because they did not know the next useful action.

## 2. Outcome
Eligible cohort: owners who create a workspace during the first 14 days after release.
Completion: within seven days of workspace creation, the owner invites one teammate, the
teammate accepts membership, and both can see one shared task. Planning target: raise this
completion from an assumed 25% to 40%; compare it with owners who created workspaces during
the 14 days before release, using the same seven-day window and eligibility rules, before
calling it a result.

## 3. Scope
In: a three-step checklist after workspace creation, invite by email, and task creation.
Out: importing contacts, team roles beyond owner and member, and automated reminders.

## 4. Constraints and exclusions
Constraints: use the existing email provider; do not show a teammate's email address to
other members; delivery fits one two-week release.
Dependencies: operations approves the invitation email; engineering confirms event names.
Excluded for this release: billing setup and a mobile-native flow.

## 5. Acceptance
- Given a new owner, when they complete the checklist, then one "setup_completed" event
  records the workspace and completion time.
- Given an owner who invites a teammate and creates a shared task, when the teammate accepts
  the invitation, then they become a workspace member and both people can view that task.
- Given an owner who sends an invitation, when the link has expired, then the recipient sees
  that it expired, cannot enter the workspace, and can request a new invitation.
- Given a member, when they open billing, then access is denied without exposing payment data.
- Given a duplicate invitation request, when the owner resends it, then the prior link is
  invalidated and an administrator can see both attempts in the event record.