Feature mindmap
See the whole product at a glance — every module, sub-feature and integration, and how they connect.
The mindmap is Ideon's answer to the question every project faces: what actually needs to be built? Instead of a flat feature list, you get a tree that shows the shape of the product.
A root node represents the product itself. Each top-level feature branches from it, and each feature owns its own sub-features. External services — authentication providers, payments, third-party APIs — are called out as their own nodes so you can see the seams of your system.
Because it is generated from your questionnaire answers rather than from a generic template, the tree reflects your product's vocabulary and your stated scope. Regenerate it whenever your thinking changes; the previous nodes are replaced with the new structure.
How the tree is actually built
Ideon sends your validated context to the model and asks for a structured response: nodes with an id, label, description, type and canvas position, plus the edges between them. That structure is stored per project, which is why the mindmap survives a reload and why regenerating replaces the tree cleanly instead of appending to it.
Reading the node types
The root node is the product itself. Feature nodes are the modules someone would recognise as separate parts of the product. Sub-feature nodes are the granular pieces of work inside a module. Integration nodes mark the places where you depend on something you do not own — auth providers, payments, third-party APIs.
Why a tree and not a list
A flat list puts everything on the same level, which hides the fact that some features contain others. A tree preserves that hierarchy, so when you scope an MVP you can cut an entire branch instead of unpicking a list.
What you get
A real hierarchy
Root, feature, sub-feature and integration node types, connected by edges that show what belongs to what.
Integrations surfaced early
Third-party dependencies get their own nodes, which is usually where estimates go wrong.
Interactive canvas
Pan and zoom the canvas to explore the tree. The layout is generated so the shape of the product stays readable.
Cheap to iterate
One credit per generation. Regenerate as many times as your understanding evolves.
How it works
- 1
Complete the questionnaire
The mindmap is only as good as the answers it is built from.
- 2
Generate the mindmap
Ideon sends your validated context to the model and turns the response into nodes and edges.
- 3
Explore the tree
Pan, zoom and follow connectors to understand how features depend on each other.
- 4
Regenerate when it changes
Update your answers and regenerate — the tree is rebuilt from your latest thinking.
Good for
- Scoping an MVP without missing a module
- Spotting third-party integrations before they become surprises
- Aligning a team on what the product actually contains