PRODUCT MODELLING
Why model my product?
- Capture the initial vision of a product
- Reconcile your vision with user flows
- Gain critical early feedback from your team


Rapidly map out your customers journey
- Takes only minutes to map
- Whole team access to the Journey
- Attach user stories directly to your customer Journey’s
Let it flow, fast
- Model your first Flow in minutes
- Drag and drop Flow steps for easy iteration
- Iterate 2, 10, 50 times at pace with logic and Elements to create reusable Interfaces, Data, Forms, and Resources.

Build your first Flow out fast and free now!

Gain feedback and iterate, cheaply.
- Friction free web based platform for any team members to give feedback - no account required.
- Storytelling format makes it easy to interpet for technical and non technical people.
- Find gaps and opportunities you couldn’t see before with versatile team perspectives
Ready for Handoff
- Pitfalls and opportunities ironed out pre $100 phase, limiting expensive late changes.
- No double handling of documentation, minimising missed notes and queries.
- Sprint team can execute independently, at pace with better information.

What else can I do with Primary?
Handoff Documentation for happy engineers.
Clearer, cleaner, better documents for your build team, no double handling (yes it’s possible)!
Frequently asked questions
No, you can use the Free level of Primary without a credit card.
No, Primary is purely online, but it works like a local software package.
Pro subscriptions are for a single user, they allow sharing models in view-only mode. Team subscriptions are for multiple users. Primary allows fine-grained access management to projects, SSO sign on and centralised billing for teams.
The best way to get started is to dive in and start working. This will raise some questions, and give you and understanding of the challenges and opportunities of modelling in Primary. Be prepared to throw away or at least heavily refactor your first attempts. The good news is that all these activities are quick to implement, and so don’t be afraid of the time commitment.
Flows should have a short, strong verb statement. Some example names are “Make a Comment” and “Edit My Profile”. Don’t use wishy-washy terms that can be confused. “Manage things in the admin panel” is an example of a poor name.
A flow should achieve just one real-world result for the user. “Clicking a button”, for example, is unlikely on its own to achieve such a goal, and so is unlikely to be an entire flow. At the other end of that spectrum, “Find a product, specify its options and buy it” is likely to be quite a few different flows, as many real-world goals are achieved.
What our customers are saying
Take a read of what our customers are saying on Capterra