# Cloud-based CRM for a sales team of five: five questions to ask before you sign

https://salesbond.app/blog/cloud-based-crm-small-sales-team-five-questions-before-you-sign/
Published: 2026-10-22 · Updated: 2026-10-22

A cloud-based CRM is hosted by the vendor, so for a five-person sales team the questions that matter are about your data, not the servers: export, admins, a rep’s last day, restores and change history. Ask them before you sign, get the answers in writing, and ask the same five again every quarter.

Most teams already ask the first two in a demo. Three to five are the ones nobody asks until a rep has left, a contact list has been overwritten, or a close date has moved and nobody knows who moved it.

## What “cloud-based” does and does not decide for a five-person team

“Cloud-based” decides one thing: you rent access to software the vendor runs. Nothing to install, no server to keep alive at night. For a team of five with no IT person that is the right trade, and the CRMs SalesBond connects to (Pipedrive, HubSpot, Salesforce, Zoho CRM) are all vendor-hosted anyway. So cloud or not is not really the decision you are making.

What it doesn’t decide is anything about your data. Who can get it out, and in what shape. Who holds the admin login. What is left behind when a rep is deactivated, what the vendor restores after a mistake, and whether anyone can see who changed the amount on the deal that just fell out of the forecast. None of that is a property of the cloud. It is a property of the contract, the plan and the settings, and a vendor answers it only if you ask.

Security and compliance (encryption, single sign-on, where the data is stored, the data processing agreement) is a separate list, and it belongs to whoever signs the contract. The questions here are the sales manager’s, because the manager lives with the the answers: the Friday forecast, the call from the customer whose rep left, the hunt for the lost note. If you are still deciding what kind of CRM the team needs at all, start with [what an operational CRM records and where the manager’s questions get answered](https://salesbond.app/blog/operational-crm-vs-analytical-crm/).

## Question 1: can you export everything, in a format you can read

The demo version of this question is already in [the seven questions to ask in every CRM demo](https://salesbond.app/blog/how-to-choose-a-crm-sales-team-of-five/). What the contract adds is time: ask the vendor to state in writing whether export still works for a period after you cancel, or whether the last day of the subscription is the last day you can get your own data. And ask for a sample export file before you sign, then open it; if notes arrive as one long cell per deal, you have just priced your next migration.

## Question 2: who is admin, and who else can become one

Name two admins before you sign, one of them the sales manager, and ask whether an existing admin can promote another user without the vendor’s help and whether the admin role is tied to the billing contact. Ask which rights sit apart from admin. In HubSpot, for example, delete, bulk delete, import and export are separate permissions, and we went through them in [HubSpot permissions for a sales team: who sees which deals, and who can delete them](https://salesbond.app/blog/hubspot-user-permissions-sales-manager-deal-visibility/).

## Question 3: what happens to a rep’s deals and access on their last day

A rep gives notice on a Friday. The manager’s first thought is the deals; the second, a week later, is the login.

A cloud CRM makes the second one harder than it used to be, because there is no laptop to hand back. The rep has the mobile app on their phone, a personal calendar connected, maybe an automation tool authorised under their own user, and an email sync that has been copying their inbox into the CRM for a year. So the question before you sign is not “can we remove a user”. It’s a short list, and we suggest asking for a demonstration rather than a yes:

- Deactivate a user without deleting anything they created. Deals, notes, activities and files stay, with the old owner’s name still on the history. If deactivate and delete are the same button, the history of every deal that rep touched goes with it.
- Reassign their open deals in one operation, by filter. A handful by hand is fine; a whole book of, say, eighty deals is a lost afternoon and a few missed ones.
- What happens to the synced mail and the connected calendar? Does the mail stay on the deals, and does the connection close by itself or keep syncing a mailbox that now belongs to nobody?
- Where are connected apps and API keys created by that user listed, and can an admin revoke them without the user’s password?
- Is a deactivated seat still billed, and until when?

The hand-over itself (freezing the book, who gets which deal, why the forecast is rebuilt rather than carried) is in [A rep just quit: how to reassign their Pipedrive deals without wrecking the forecast](https://salesbond.app/blog/rep-leaves-reassign-pipedrive-deals/). That article assumes the CRM lets you do all of the above. This is where you make sure it does, while the vendor still wants your signature.

## Question 4: what the vendor backs up and what stays your job

The vendor backs up the platform against the vendor’s own failures. That’s what “cloud” buys you, and it is not nothing. It is also not what hurts a five-person team. What hurts is a rep bulk-deleting dozens of contacts while trying to delete a few, an import mapped to the wrong column that overwrites every phone number, or a well-meant clean-up that merges two companies that were never the same. The vendors backup restores their system, not your Tuesday.

So ask about your mistakes, not theirs. Can an admin restore a deleted deal or contact, and for how long after deletion? Is restore per record or a whole-account rollback that also undoes a week of real work? Can a bulk update or an import be undone, or does “undo” mean re-importing your own file? Get the retention window in writing. If the honest answer is “contact support”, decide now whether you can live with that at five o’clock on the day it happens.

The part that stays yours whatever the vendor says is a copy of the list. Export deals, contacts and activities on a schedule (monthly if the team imports or bulk-edits, quarterly if not) and keep the file somewhere that is not the CRM. That export doubles as the test for Question 1, because an export you run every month is one you know works.

A copy is only worth as much as the data in it, though. A pipeline where many deals have no next activity and close dates in the past is faithfully backed up and still not trusted. Our monthly clean-up is in [CRM data cleansing for a sales team of five: a 60-minute monthly routine](https://salesbond.app/blog/crm-data-cleansing-monthly-routine-small-team/). And since this is where the product fits: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. It reads the CRM and shows the manager where the data has holes, like deals with no next step, missing fields and dates that keep moving. It backs nothing up and isn’t a security product. If you want those holes listed without building the filters, [check your CRM with SalesBond](https://salesbond.app/).

## Question 5: where changes are logged

The forecast was one number on Monday and a smaller one on Friday, and three deals have a new close date. Who moved them, and when? A CRM that cannot answer that is a shared spreadsheet with a login page.

“Is there a history?” gets a yes from every vendor. The real questions are which fields, from when, and who can read it. Ask whether field-level history is included in the tier you are being quoted and whether it is switched on per field or per object. In Salesforce, Field History Tracking is enabled per object and records only the fields you select, up to 20 per object; the opportunity fields we think are worth it are in [Salesforce Field History Tracking: which opportunity fields to track](https://salesbond.app/blog/salesforce-field-history-tracking-opportunity-audit/). Whatever CRM you end up with, assume history starts the day you switch it on. So decide on day one which fields drive the forecast, usually close date, amount, stage and owner, and turn tracking on for those before the first deal is entered.

Then widen the question. Are deletions logged with the user who deleted? Are exports logged? The week you most want to know who ran a full contact export is the week a rep hands in thier notice, and that’s Question 3 arriving early. Are logins and connected apps logged? Don’t expect a yes to all of it. Expect a clear list of what is and isn’t recorded, and treat a vague answer as a no.

One honest limit: a change log tells you what changed, not whether the change was right. Whether a deal is slipping or the buyer really re-planned is still a conversation for the manager.

## The same five questions every quarter

The answers drift. A plan changes, a second admin leaves, the export that worked in January has a new format in June. So every quarter the manager asks the five again, this time of the CRM itself. Aim for about an hour.

![Quarterly checklist card with five rows to tick: export, admins, leavers, restore and change log](https://salesbond.app/wp-content/uploads/2026/10/cloud-based-crm-small-sales-team-five-questions-before-you-s-2.png)

1. Export. Run the full export and open the file. Look for notes and activities, not only deals and contacts; if the file is smaller than last quarter’s, find out why.
2. Admins. Two named admins, both still with the company, both able to log in today.
3. Leavers. For every user deactivated this quarter: open deals reassigned, email sync and calendar disconnected, connected apps revoked, seat off the invoice.
4. Restore. The retention window for deleted records is written down where you can find it, and the latest export sits outside the CRM where someone other than you knows to look.
5. Change log. History is recording on close date, amount, stage and owner. Pick one deal whose close date moved this quarter and trace it to the person who moved it.

Most quarters the one that fails is the leaver check, because the seat was deactivated and the calendar was not. Or the admin check, because the second admin was the founder’s co-founder and nobody updated it after the reshuffle. That’s fine. You found it in an hour in March, not at five o’clock on the day it matters.