How pure and base bont go together
pure bont and base bont share one CRM. Edit a deal in pure bont and base bont sees it instantly. Same for contacts, companies and activities.
pure bont and base bont are two views on one shared dataset. base bont's job is to store the CRM (contacts, accounts, deals, activities); pure bont's job is to act on it (prioritisation, scoring, forecasting, reporting). Anything you change in one app, the other sees in real time — there is no sync delay, no separate database.
Where to do what
- Add or edit raw records — both apps can. The Contacts, Companies, Activities and Deals lists are the same UI rendered under each app's left nav.
- Daily prioritised work — pure bont's Activities and Inbox, scored deal list, and recommendations are designed for "what should I work next?"
- Configure the CRM model — base bont's CRM configuration pages own pipelines, fields, products and so on. pure bont reads them.
- Run forecasting and reporting — pure bont owns the Reporting and Forecasting tabs.
Switching between them
The workspace switcher in the top-left of the app lists every enabled app for the org. Click pure bont or base bont to jump between them; your current selection persists across sessions.
What happens if base bont isn't enabled?
Workspaces can have pure bont without base bont — in that case pure bont still exposes the Contacts/Companies/Deals/Activities lists itself, sourced from the CRM via the integrations layer. base bont is most useful when your team primarily edits the CRM data; pure bont is enough on its own if you mostly read it.