Zoho, HubSpot or a spreadsheet: choosing for a team of eight

For a team of eight, choose by who will keep the system alive and how much of your selling is written down, not by a feature list. Run your own ten live deals through each candidate, Zoho, HubSpot or a well-built spreadsheet, with the person who will own it doing the typing. The one that person can bend to your sales steps without calling for help is the one to pick. A demonstration led by a vendor tells you little about your own deals.

What decides it before any demonstration?

Three questions, asked first.

Can you describe your sales steps on one page? If not, no tool will help. It will record the confusion. Picking a CRM after writing your sales process shows how to write the page.

Who will own it? A CRM drifts from reality within weeks unless one named person adjusts stages, fixes duplicates and trains new joiners. A job shared by eight people tends to be done by none.

What must it connect to? List what you use now: accounts package, website forms, WhatsApp, portal leads, a phone system. A tool that talks to none of them means retyping.

What should the trial be?

Three short afternoons, not "try it for a while". The owner of the system does the work. Everyone else watches the clock, not the screen.

Afternoon 1   Enter ten real deals, including one lost and one stuck.
              Change a stage name to match how you really sell.
Afternoon 2   Capture an enquiry from your website form and one other
              source. Send a quote and log the follow-up.
Afternoon 3   Pull a list: all deals with no next step.
              Move one seller's deals to another.
              Ask each of the eight to update a deal from a phone.

Mark each line yes, no or "with effort", for the person who will maintain it. Three or more "with effort" marks and the tool will not last. Compare scores side by side for the two or three candidates, and include the spreadsheet as a candidate with the same tasks done by hand.

Which rules settle it?

Apply them in order and stop at the first that fits.

1. Fewer than about thirty live deals across the team, one product, and someone checks the sheet daily? Stay on a well-built spreadsheet and revisit when it hurts. Whether a small business really needs a CRM argues that case honestly.
2. Enquiries arrive from a website, email and several portals, and nobody follows up on time? Pick the tool that captures them without retyping. Test both on your actual forms.
3. You already use other products from one vendor? See whether that vendor's CRM is close enough. Fewer systems means fewer places for data to split.
4. You need unusual stages, fields or approvals, such as a drawing-approval step? Lean toward the option you can customise, and pay for someone who can do it.
5. Nobody on the team will configure anything? Take the one with the shorter set-up and accept fewer options.

Plans, prices and features change often. Ask each vendor for current terms in writing, and do not rely on anything printed here or on a comparison page.

How each option tends to fail

Pick the failure your team is least likely to suffer. A spreadsheet breaks when two people edit together: rows get overwritten and versions get lost. A configurable CRM fails by over-configuration, with the owner adding fields until the form is unusable. A simpler CRM fails by being paid for and half used. No tool is free of failure. Choose the one whose failure you can see coming.

A trial that overturned the demo

Imagine an eight-person tour operator in Madurai that sells group pilgrim tours to temple trusts and community associations. This case is invented. Two sellers, two route planners, a bookings coordinator, an accounts person, the owner and an assistant were on one shared sheet. Two people edited it at once and one of them overwrote the status of a confirmed 40-seat booking, and a second coach was nearly hired for ₹28,000 before anyone noticed.

The owner arranged demonstrations of two products. Both looked good. The choice came from a different test. The owner wrote down ten live bookings and asked the coordinator, who would own the system, to enter them in each over an afternoon. The coordinator finished the first in an hour. In the second the coordinator stalled, because the stage names did not match "enquiry, route sent, advance paid, seats held, travelled", and could not tell how to change them.

The owner had nearly chosen on the demo, which the vendor controls, and chose the first tool. It was not a clean win: the first tool cost more per user, and the route planners stayed on a separate sheet for seat counts until the stages settled. The owner fixed a review date after a stated test period. The coordinator now owns the stage list, and any new stage waits for that approval.

When should you not buy yet?

Skip the purchase when you cannot say who owns the system, or when you are changing your product line this quarter. Skip it too if the real problem is that enquiries go unanswered, because a tool will not make a person pick up the phone. Before moving health, finance or other regulated customer data into a cloud product, check with your own adviser, since the rules differ by state and body and change.

What if you change your mind later?

Moving from one system to another is possible, and far easier if your data is tidy and your fields are few. Keep a dated export of your records every quarter from the first day, so that leaving never depends on one vendor's goodwill. Do not let fear of switching keep you on a sheet that is already failing.

Write your ten deals this week

List ten live deals. Write the one-page process. Name the person who will own the tool, and give that person the afternoons. If you want help running the trial, CRM consulting and selection is where we start, part of how you sell. When the list is written, tell us what you need.