Run your architecture offline in a workbook you own, or build it web-based in the platform where it keeps living. The structure underneath is the same either way.
The Workbook
Offline, yours, no login. An Excel file you can open today, fill in on your own terms, and keep on your own drive.
- Level framework and leveling criteria built in
- Job catalog and mapping sheet with data validations
- Works alongside your existing comp data
- No account required
Excel (.xlsx) — no account, no email required.
The Studio
The same architecture, living in the platform. Your framework, catalog, and mappings stay put between sessions and feed the rest of the work.
- Pick up where you left off — everything saves to your account
- AI-assisted mapping and leveling
- Outputs structured for org design and comp work
- Market benchmarking connection coming
Requires a free account — you can create one on the same screen.
One architecture, either way.
The workbook and the studio use the same columns, the same level definitions, and the same family and sub-family taxonomy. That parity is deliberate: it is what lets work started in one place move to the other without being re-keyed.
Two things are on the roadmap rather than in the product today — moving a filled workbook into the studio and back out again, and connecting the Market Benchmarking Module to the mapping grid so a mapped role becomes a market lookup. Neither is live yet, and nothing here shows a benchmark figure until your own data is loaded.