Pomio Insights
Articles on how a CRM is set up: the multi-tenant model, permissions, MFA and data export. Answer-first, from Pomio CRM.
No. "On hold" is a status, not a step in the buying process. Keep a paused deal in the stage it really reached, mark it with an on-hold label, set a realistic close date and a dated check-in, keep it out of the committed forecast, and agree a maximum hold period. Pomio CRM supports this with labels, tasks and stages.
Yes. Clean up before you migrate, not afterwards: decide what moves, merge duplicates, give every record an owner, map old stages to new ones and archive what nobody needs. A migration copies mistakes as faithfully as good data. Pomio CRM imports leads, deals and companies via CSV.
Yes. A short monthly check of what the CRM forecast said against what was actually won shows whether stages, probabilities and close dates can be trusted. It takes half an hour, needs no extra software and makes the next forecast better. Pomio CRM keeps amount, stage, probability, close date and owner on every deal.
Most SMEs should start with one shared CRM pipeline and only add a second one when a sales process really has different stages, such as a recurring contract versus a one-off project. Separate pipelines per salesperson or per region make reporting harder. Pomio CRM keeps one shared pipeline with roles, teams and scope.
CRM notes should record what the next colleague needs: what was agreed, what happens next and why. Never write passwords, card or bank details, health or other sensitive personal data, or private opinions about people. Pomio CRM keeps notes on the timeline, protected by roles, scope and an audit log.
Colleagues outside sales who regularly need customer information, such as finance, support or delivery, should get their own login with a read-only role and a limited scope, not edit rights, a shared account or exports by email. Pomio CRM has a viewer role with own, team or organisation scope.
Follow the way you sell: build CRM teams around the people who share a pipeline and answer to one sales manager, not around departments on the org chart. Keep offices, regions and segments as locations or labels. Pomio CRM links teams to scope, targets and the scoreboard.
Not everyone: let salespeople merge obvious duplicates they own, send merges across owners or teams to the sales manager, give organisation-wide clean-ups to one named person and agree which record survives. Pomio CRM gives every record an owner, a server-enforced scope and an audit log.
Usually yes, but not edit them: let salespeople see the deals of their own team, let only the owner change a deal, and keep organisation-wide access and earnings for a small group. Pomio CRM gives every permission an own, team or organisation scope, enforced on the server.
Yes. An audit trail that records who did what and when lets an SME reconstruct changes to deals, contacts and access without guesswork. It needs personal logins, should never store passwords or MFA secrets, and works best with clear review moments. Pomio CRM keeps an audit trail.
Yes. A short monthly check on missing owners, duplicates, stale records and unlinked contacts keeps a shared CRM trustworthy. Use a fixed list, one person who runs it and fixes made at the source. Pomio CRM keeps owners and links on every record.
Not forever. Pick a fixed retention period for leads with no deal and no recent contact, write it down, and review that group on a schedule: delete or anonymise what has no purpose left. Pomio CRM keeps lead source, owner, activity history and privacy requests in the same environment.
Start a 14-day trial or request a demo. This preview site has no purchase flow.
