Public package structure. Sales-level scope.
Nestory keeps the pricing story public and legible: a strong core product first, then role-based add-ons for owner visibility, vendor execution, and platform controls.
Package ladder
Core package
Nestory Core
Operations and records
Work orders, reviews, vendor coordination, routing controls, and verified maintenance history for the day-to-day operating team.
Add-on
Owner Intelligence
Institutional oversight
Owner dashboards, inspection workflows, accountability views, and property history reporting built for asset managers and ownership groups.
Add-on
Vendor Network
Execution quality
Vendor onboarding, completion documentation, response quality, and payment visibility for private vendor ecosystems.
Enterprise
Platform Controls
Scale and governance
Advanced roles, integrations, routing policies, audit views, and rollout support for larger organizations.
What shapes pricing
The first conversation should be about scope, not a login wall.
Platform map
Core
Operations + records
Owners
Oversight view
Vendors
Completion + payments
Controls
Roles + integrations
What packages unlock
Nestory Core
Daily work orders, review steps, vendor coordination, and the verified maintenance record.
Owner Intelligence
Portfolio visibility, inspection follow-through, and property history reporting for asset owners.
Vendor Network
Field documentation, completion reports, response quality, and payment status.
Platform Controls
Advanced roles, integration rollout, routing rules, and audit visibility at scale.
Buying motion
Start with the workflow. Add the visibility each role needs.
See what the package map unlocks
The buying conversation gets easier when the product structure is visible before pricing.
Buyers should be able to see how the operating workflow, owner visibility, vendor execution, and platform controls relate to one another before anyone asks them to talk in abstraction.
Scoping worksheet
Core workflow baseline selected
Operations dashboard, reviews, routing, and property history are the foundation.
Owner layer added for institutional oversight
Scope grows when asset managers need inspection and reporting visibility.
Integration and control depth defined by rollout
Pricing changes with system complexity, access mix, and governance needs.
Properties
48 in scope
Roles
Ops + owners + vendors
Rollout
3 phased launches
How teams typically buy
The right package depends on role mix, property count, and rollout scope.
Nestory is easier to understand when buyers can separate the product structure from the pricing conversation. These are the steps most organizations follow.
Start with the daily operating workflow
Most teams begin with Nestory Core so operators can run maintenance work and build the verified record first.
Add the visibility layer your stakeholders need
Owner, vendor, and platform-control workflows are added when the organization needs a different view or operating standard.
Scope rollout around real properties and real systems
Pricing is then shaped by property count, integration scope, role mix, and implementation support.
Next step
Bring your property count, team structure, and workflow questions into the first conversation.
The best demo or pricing discussion starts with real context: how many properties you manage, who needs access, what systems you already run, and which reporting requirements matter most.