What it does
Features and requirements
Invoicing, user management, reporting. The features your product offers people, and the requirements that make each one complete.
Invoicing SMS reminders
See your product from every angle.
VPM, the Visual Product Manager, is like Google Maps for your product: one living map of what it does, how it’s built and when it changes. Zoom in on a module, slide through releases, and edit right where you look. Built for the people who steer the product, not for tickets.
How it’s built
Modules
Backend, mobile app, admin portal. The parts your teams build and ship, linked to the features they carry.
BackendMobile app
When it changes
Releases and versions
Releases as slices through time: which requirements were delivered, what is planned, and which version of every module went out.
3.13.23.3
Turn the product
One model, many views.
Every view is a different angle on the same data. Select something in one view and it stays selected in the next. Filter, focus, and change it in place.
Product map
Features and modules as regions, requirements inside. Click anything to see what it touches.
Feature × module matrix
Where is functionality built? Direct links and inherited links, side by side.
Roadmap timeline
Releases with their target and actual dates, dependencies drawn as arrows.
The 3D product cube
Turn the whole product in your hands. Front, top and side are the three angles.
Inform, never plan
The facts, on the item itself.
VPM tells you when dates don’t fit, a dependency slipped or a release waits on something that is on hold. It never moves your plan for you. You stay at manager altitude: features, requirements, modules and releases, while the tickets stay in Jira, GitHub or Linear and the specs stay where your team writes them.
Invoicing v23.2
PlannedWarning
Invoicing v2 targets 15 Mar, but it depends on Payment migration, which slipped.
InvoicingMobile appBackend