01
Operational records
Model customers, products, properties, projects, people, and the relationships between them.
Path feature guide
Structure business records and relationships so Apps, workflows, and AI can use the same context.
△ This is live data. Changes affect your Apps and their users.
What this makes possible
01
Model customers, products, properties, projects, people, and the relationships between them.
02
Give each App a durable data foundation with the access boundaries it needs.
03
Bring selected external records into workflows without losing source identity.
How to approach it
The exact implementation depends on your data, permissions, operating model, and connected systems.
Start with the business nouns, their identifiers, and the relationships the workflow depends on.
Choose the source of truth, required fields, access rules, and update responsibility.
Plan imports, validation, history, and how the model evolves as the business does.
Customer proof
After four decades running the floor on a DOS-era POS and inventory system, Waterloo cut over to a modern Path stack, without losing the store DNA.
One operating platform across the portfolio, with Path Scout automating the work that used to live in spreadsheets and email threads.
A B2B wholesale portal and the consumer storefront at manana.co, built on one Path workspace, sharing a single product catalog.
A marketplace mobile app built on Path with buyers, sellers, listings, and payments shipped from one stack to the App Store.
Customer stories are shown only where the published story names a related Path capability.
Keep exploring
Start with one useful workflow, then connect the rest as the system proves itself.