01
Operations workspaces
Give teams one place to manage records, owners, status, and exceptions.
Build
Path feature guide
Turn a business process into a shared app.
Build a browser-based system around your records, roles, approvals, and daily work.
Product screenExample data
properties.your-domain.com
Property OperationsPortfolio
Work orders
Search…
New
| Work order | Property | Status | Due |
|---|---|---|---|
| WO-2184 | Riverside | In progress | Today |
| WO-2183 | Westfield Place | Scheduled | Sep 18 |
| WO-2182 | Northline Center | Needs review | Sep 19 |
| WO-2181 | Harbor Point | Complete | Sep 20 |
| WO-2180 | Elmwood Square | Scheduled | Sep 22 |
What this makes possible
Start with the work, then shape the system.
02
Customer systems
Shape CRM, service, ordering, and account workflows around your business.
03
Admin tools
Replace spreadsheet handoffs with focused tools for the people who run the work.
How to approach it
A practical starting path.
The exact implementation depends on your data, permissions, operating model, and connected systems.
- 01
Choose one workflow
Start with a recurring process that has a clear owner and a visible result.
- 02
Model the work
Define the records, relationships, roles, states, and approvals the app needs.
- 03
Build and adapt
Create the interface, connect the right systems, and refine it with real use.
Customer proof
See it in a real business.
Waterloo Records
Waterloo Records moved off MS-DOS and onto Path.
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.
Base
Base runs a portfolio of brands on Path.
One operating platform across the portfolio, with Path Scout automating the work that used to live in spreadsheets and email threads.
Mañana
Mañana runs wholesale and direct on the same Path stack.
A B2B wholesale portal and the consumer storefront at manana.co, built on one Path workspace, sharing a single product catalog.
Customer stories are shown only where the published story names a related Path capability.
Keep exploring
Related systems and capabilities.
Build your version.
Start with one useful workflow, then connect the rest as the system proves itself.