Product UX and seeded data
Navigation, mapping, template structure, preview diff, generated workspace, run log, replay model, settings expectations, and failure states.
Seeded demo workspace
Review ClientFlow with the Northstar Studio sample workspace: a Won client becomes an SEO Retainer project with tasks, owners, due dates, recurring reviews, preview, and a replay-ready run log.
Navigation, mapping, template structure, preview diff, generated workspace, run log, replay model, settings expectations, and failure states.
Account creation, email verification, OAuth authorization, live workspace discovery, real database writes, disconnect and reconnect behavior.
This workspace is seeded with the Northstar Studio scenario. It is designed for product review and sales proof without touching a real workspace.
Review path
The demo uses the same scenario as the homepage, but lays it out like a product audit: account gate, Notion authorization, discovery, mapping, templates, preview, execution, logs, replay, and the expected failure paths.
31tasks generated
6owners and queues
2recurring deliverables
90 daystarget log retention
Password rules, confirmation, email verification copy, Notion-after-account sequence.
Permission explanation, cancel paths, plan limit messaging, reconnect expectations.
Workspace and database selection states for populated, empty, and unavailable data.
Clients, Projects, Tasks, Services roles and required property validation.
Versioned SEO Retainer pack with owners, relative dates, and recurring deliverables.
Visual diff before writing projects, tasks, relations, dates, and recurring rows.
Run progress, partial success, warnings, and plain-language recovery.
Action status, generated Notion links, filtering model, and failed-action replay.
Seeded workspace
These product views are intentionally concrete: the reviewer can see the mapped databases, service template, visual diff, generated workspace, and run history.
Workspace status
31tasks
6owners
2recurring reviews
Task pack
New Project+ SEO Retainer - Northstar Studio
New Tasks+ 31 generated tasks
New Relations+ Client -> Project -> Tasks
Owners+ Sarah, Analytics, Content
Dates+ Kickoff Jul 22, Audit Jul 28
Recurring+ Weekly report, Monthly review
Kickoff MeetingSarahJul 22Ready
GA4 ConnectedAnalyticsJul 24Ready
Search ConsoleAnalyticsJul 24Ready
Technical AuditSarahJul 28Queued
Monthly ReportContentAug 01Recurring
10:42:11Project createdSEO Retainer - Northstar Studiosuccess
10:42:1831 tasks generatedTask pack linked to projectsuccess
10:42:23Owner relation warningSarah matched, Analytics queue needs reviewreview
10:42:31Recurring top-up scheduledWeekly report and monthly reviewsuccess
Settings and controls
A mature product audit needs more than a happy path. This section documents the settings surface the authenticated app needs to expose around workspace control, ownership, notifications, and data handling.
Northstar Studio Demo, connected state, pause rules, disconnect path.
Sarah owner, Analytics queue, Content queue, role handoff warnings.
Execution success, warning, failed replay, monthly top-up alerts.
Stored IDs, encrypted tokens, log retention, export/delete request path.
Failure testing
These are the cases a Notion power user will test first. The demo frames the expected product behavior so QA can compare real authenticated screens against it.
Block activation until Clients -> Projects and Projects -> Tasks relations are valid.
Pause dependent rules and show the database role that needs remapping.
Create safe warning when Sarah exists but Analytics queue needs review.
Respect Retry-After, continue queued actions, keep run visible.
Replay failed actions only so completed Notion pages are not duplicated.
Require validation when status, date, owner, or relation properties change.
Power user audit