Hypotheses and Customer Profiles Get Their Own Pages
Tracsio adds dedicated Hypotheses and Customer Profile workspaces inside each project. Founders can now inspect assumptions, manage validation experiments, edit the active ICP, and move between project sections from the sidebar.
This is the day the chat-first project model starts getting supporting rooms around it. Chat remains the place where the agent proposes and updates things, but hypotheses and ICP now have surfaces that are easier to scan and manage.
The important shift is that assumptions are no longer buried in a conversation transcript. A founder can open the Hypotheses page, see what is known, decide what needs validation, and then use chat only when they want the AI to help move the work forward.
Customer Profile follows the same pattern. The ICP is editable as structured product data, but still close enough to chat that a user can ask for help when the profile needs real thinking rather than field edits.
- Hypotheses page: problem and solution hypotheses now have a dedicated project page with type filters, status filters, priority order, and detail views.
- Hypothesis management: users can add, edit, delete, approve, reject, and reorder hypotheses without leaving the project workspace.
- Experiment controls: hypotheses can receive manual validation experiments or route into chat for AI-generated experiment suggestions that go through approval.
- Customer Profile page: each project now has a dedicated ICP page covering target company, buyer, end user, characteristics, and project context.
- ICP editing from the page: users can update the active customer profile directly, while AI improvement still hands off to chat when a more guided rewrite is useful.
- Project navigation in the sidebar: projects, conversations, customer profile, and hypotheses are now reachable from the main sidebar instead of being split across page headers.
- Custom account menu: the Clerk user menu is replaced with an app-styled menu that also keeps credits visible in the same flow.
- Project switching preserves context: changing projects keeps the current section, so a founder reviewing hypotheses or the customer profile does not get dropped into the wrong view.
- Onboarding copy tightened: the first-run project setup copy is adjusted around the newer project and chat workflow.
- New project generation narrowed: fresh projects no longer create solution hypotheses up front before the problem space is clear.
- Hypotheses UI flattened: the page moves toward a quieter hierarchy with breadcrumbs, fewer shadows, and more scannable controls.