A design the whole team understands.
Describe your product once: four catalogs — actors, features, objects, rules — and the needs that connect them. Every need has its own diagram, generated for you.
Four catalogs
Actors, features, objects and rules: each item is written once and reused everywhere.
Needs that connect
“As [actors], I want to [feature], so as to [benefit]”: a sentence anyone can read.
A diagram per need
Generated from the need itself: nothing to draw, nothing to arrange.
Markdown export
One need, or your entire design, in a single .md file.
Catalogs, not pages
An actor can inherit from another. An object has fields; a field can reference another object, and an object can inherit from another while overriding its fields. Rules form a single catalog: an object or a field picks the ones it carries.
- Inheritance for actors and objects
- Fields that reference another object
- A rule written once, picked wherever it applies
Readable by humans and by Claude
Every item has a stable identifier. Exported to Markdown or read through the MCP connector, a need keeps its full context: actors, feature, objects, fields and rules.
- Tickets linked to the needs they fulfill
- Live presence and updates
- get_conception and get_need tools for Claude
Frequently asked questions
Another question? Read the FAQ or write to us.
Do I need modeling skills?
No. Four catalogs and one sentence per need are enough to describe most products.
Can I start from an existing document?
Yes, with the MCP connector: Claude can read your document and write the actors, features, objects, rules and needs for you. Markdown export, for its part, is available at any time.
Which plan do I need?
Up to 30 items on the Free plan, unlimited from Pro upward.
Explore more
All features →
Try Grepo with your team.
The Free plan has no time limit. Move to Pro when your team grows.