A shared workspace for product teams
From customer evidence to reviewable changes.
Connect customer evidence, product decisions and requirements with the code changes your team reviews. Keep customer needs visible through each handoff, and bring that context into your existing coding tools.
Start free
Email is enough. Connect GitHub when you want your AI coding tools to read the persona and journey.
30 free credits · No card · GitHub optional
Example library card
Overextended Solo Counsel
I’m the legal department and the help desk.
- Researched personas cite their sources
- Your library is stored in Sydney
- 30 free credits to start
Why evidence
Your AI builds what you tell it. Tell it who the customer is.
Keep the customer need and its supporting evidence visible as your team moves from research to requirements and code review.
| Handoff challenge | With Persona Journey |
|---|---|
| A request arrives without its supporting evidence | An idea plus market evidence goes in |
| The customer need gets lost between tools | Your AI coding tools read who the customer is |
| Business context lives in someone's head | Business context lives in your repo |
| A reviewer cannot trace a change back to its customer need | Code trace shows where each need lives, and the gaps |
How it works
Research, build with context, trace and improve
Each step builds on the last, so the code is about a real customer, not a template.
- 01
Research
Live market research becomes a persona with pain points, goals and a Sources section you can check, then a customer journey written for that person.
- 02
Build with context
Sync the persona and journey to your GitHub repo. Your AI coding tools read them and tag the code they write with the need it serves.
- 03
Trace and improve
Code trace maps each pain point, goal and journey phase to the features, UX copy and tests that serve it, and shows what is missing. Untagged code? AI can suggest the links.
Plan the campaign
Take the persona into a social campaign
When the persona is ready, plan how to reach that customer. The results become evidence for the persona.
- 1Your persona and customer journey go to SocialCraft™, our social campaign app.
- 2SocialCraft plans posts for each funnel stage, from awareness to advocacy, written for that persona.
- 3Campaign results come back to the persona as cited evidence, so the next round starts from what customers did.
Nothing is shared until you connect the two accounts, and you can disconnect in Privacy settings. Not available for Sovereign accounts, which keep their data in Australia.
Visit SocialCraft(opens in a new tab)Three ways in
Start from wherever you are
You don't have to start from a blank page. Pick the path that matches what you already have.
Start with an idea
One sentence about your product. We research the market and draft the persona for you to shape.
Bring your research
Add interview notes, PDFs, Word documents or screenshots. The persona is grounded in what you already know.
Use what you have
Paste a persona or customer journey you already wrote. Use it as is, or fill the gaps in our format.
For the whole product team
One source of customer evidence, from research to code
Designers
See which journey phases have no flow or UX copy yet, and design for the moments that matter to the customer.
Developers
Know why each feature exists. See which pain points have no tests, and give your AI coding tools context instead of guesses.
Founders and product leads
Check that what ships serves the customers you researched, and share one library of personas and journeys with your team.