CRM tools
CRM in Gmail, extension, or full suite: which model to pick?
Compare CRM architectures — inbox-native, Chrome extension, Workspace add-on, SaaS — for commercial teams.
Where does your CRM tool live? In a separate tab, in Gmail’s sidebar, or in an extension that turns the inbox into a cockpit? The technical model drives adoption, cost, and iteration speed.
Four common CRM architectures
SaaS suite (Salesforce, HubSpot, Pipedrive)
- Strengths: reporting, ecosystem, scale
- Limits: price, learning curve, double entry with Gmail
Google Workspace add-on
- Strengths: Marketplace distribution, admin trust
- Limits: Google review cycles, constrained UI, Store billing
Chrome extension (MV3)
- Strengths: rich UI injected in Gmail, fast iteration, extension OAuth
- Limits: per-user install, Chrome dependency
Spreadsheet + scripts (Sheets, Notion)
- Strengths: free, flexible
- Limits: no thread link, no pipeline rituals
Choice criteria for a sales team
| Criterion | CRM suite | Inbox extension |
|---|---|---|
| Time in Gmail | Low | High |
| Team size | > 10 | 1–10 |
| Budget | €€€ | € |
| Data | Vendor cloud | Sheets / export |
For a Google-native SMB, extension + Sheets combines lightness and data ownership — without a second hub.
Security and governance
Questions for any vendor:
- Where are metadata stored (threads, notes)?
- OAuth: which scopes exactly?
- Export and deletion?
- Billing: Store vs external Stripe?
Colossales stores threads, comments, and reminders in your Google Sheets; Pro subscription runs through Stripe, outside the Chrome Web Store.
Bottom line
There is no universal “best CRM” — only the model aligned with where work happens. If Gmail is the gravitational center, a pipeline CRM extension beats a suite in a forgotten tab.