Onboarding and first snapshot
Onboarding gives TOW its first structured understanding of your company. The first snapshot turns that understanding into a trusted baseline after human review.
Complete onboarding before depending on AI answers, operating guidance, or generated plans.
When onboarding appears
TOW opens the company onboarding dialog when the active organisation does not yet have an active onboarding snapshot for the current user and organisation.
The dialog cannot be dismissed while onboarding is required. If onboarding has already been submitted but not activated, TOW asks you to open Snapshots and review the pending company snapshot.
Choose the workflow
The first step asks for the workflow mode.
| Workflow | Expected use |
|---|---|
| Founder | Direct focus, strategy, technical judgment, and execution coaching for a founder or small leadership group. |
| Organization | Team coordination, project work, access control, accountability, docs, tasks, decisions, and risks. |
The selected mode is saved to organisation settings and used by AI prompts and operating guidance.
Hidden gotcha: Workflow mode can be changed later, but changing it does not rewrite previous memory or snapshots. If the company grows from founder-led to team-led, review existing priorities and decisions after switching to Organization mode.
Capture the company baseline
Move through each onboarding section and enter the most current information you have.
| Section | What to include |
|---|---|
| Company | Name, one-liner, mission, stage, location or timezone, website, legal notes. |
| Product | Product description, users, core use cases, differentiators, current product status. |
| Market | ICP, segments, pain, alternatives, competitors, channels. |
| Strategy | Current strategy, priorities, milestones, open decisions, non-goals, things to ignore. |
| Technical | Stack, architecture, integrations, data sources, dataset strategy, model strategy, evaluation strategy. |
| Operations | Team, roles, fundraising, metrics, constraints, risks, blockers, operating cadence. |
Company name and one-liner are required. List fields expect one item per line.
Write for future use
Onboarding is not a pitch deck. It is the source material TOW will use to form memory and initial tasks.
Good onboarding answers are:
- Specific enough to be checked later.
- Current as of today.
- Clear about uncertainty.
- Honest about constraints and risks.
- Explicit about what should not be pursued.
Avoid putting confidential information in onboarding unless your organisation is ready for that information to become workspace memory.
Finish onboarding
At the end of onboarding, select Finish onboarding.
TOW then creates:
- Initial memory items from the submitted facts.
- Initial task seeds from priorities and blockers.
The browser keeps your in-progress answers locally while the dialog is open. TOW clears that draft after onboarding finishes.
Role availability
| User type | Availability |
|---|---|
| First registered user | Can complete onboarding and becomes organisation owner and server admin. |
| Organisation member | Can use the workspace after onboarding is complete, subject to access rules. |
| Organisation admin or owner | Can manage workflow mode, invites, members, groups, and organisation settings. |
| Project lead or admin | Can manage project-level setup for projects they control. |
Onboarding is tied to the active organisation. If you switch organisations, the onboarding status may be different.
Hidden gotchas
- Empty fields become missing context. TOW will not know facts you did not provide or capture elsewhere.
- Priorities and blockers may create initial task seeds. Review Tickets after onboarding.
- If generated results seem delayed, Agent Runs may still be queued or running.
Job queues: Related AI work can run in the background. Wait for active Agent Runs to finish before assuming downstream proposals are complete.