CalMov Lite vs Plus vs Pro: a plan comparison

What is the main difference between CalMov plans?

The central difference is how driving time enters availability. Lite uses a gap selected by the business. Plus estimates driving time between customer postcodes. Pro checks roads and expected traffic for the planned appointment time and checks the journey again before the booking is confirmed. Each level suits a different degree of geographic variation.

Plan limits also matter. Lite currently includes one staff member and up to two services. Plus and Pro include unlimited services and online payments. During the founder launch, one active staff member can take bookings per business; multi-staff controls are marked as coming soon, so they should not drive a purchase today.

When is CalMov Lite enough?

Lite is a practical starting point for a solo operator with a compact area, a short service menu and journeys that take roughly similar amounts of time. You choose the standard gap, which makes the rule easy to understand. It also lets a new business test online booking before committing to a paid travel calculation.

The limitation is deliberate: the same chosen gap applies whether customers are close together or far apart. Set it too short and long journeys become unreliable; set it for the longest journey and nearby appointments inherit unnecessary dead time. Lite works best when geography is controlled enough that this compromise is acceptable.

• One staff member included
• Up to two bookable services
• A travel gap set by the business
• An online booking page
• Working-hours and time-off controls

When does CalMov Plus make more sense?

Plus suits a solo business whose customer postcodes create meaningfully different journeys. Instead of reserving the same manual gap every time, the system estimates driving time from one customer postcode to the next and adds it automatically. That can protect long journeys without forcing their allowance onto every nearby pair.

Plus also adds unlimited services, online payments and a booking-and-payment overview. It is therefore a stronger fit when the service catalogue has outgrown Lite or payment collection is part of the desired booking flow. It does not include Pro’s road-and-expected-traffic check or final pre-confirmation journey recheck.

When is CalMov Pro worth considering?

Pro is designed for a tighter or more traffic-sensitive diary where postcode estimates alone do not give enough route context. It checks available roads and expected traffic for the planned appointment time, examines driving before and after the proposed job and checks the journey again before booking confirmation.

Expected traffic is not a promise about every incident, closure or access delay. You still need service durations, parking allowances and a sensible margin. Pro is most useful when better journey context changes which slots can safely be offered; it is unnecessary complexity if a fixed gap already keeps a lightly booked local diary reliable.

How do the plans handle the same diary example?

Imagine a 60-minute service between a previous customer and a later confirmed visit. Nearby postcode pairs usually take fifteen minutes, while cross-area pairs take forty. Lite applies the chosen standard gap to both. A fifteen-minute setting risks the long route; a forty-minute setting blocks extra time for nearby routes.

Plus estimates the postcode pair so the two journeys can reserve different amounts of time. Pro adds road and expected-traffic context for the planned time and a final journey check before confirmation. None of the plans should be used to hide an unrealistic service duration or eliminate the margin needed for parking and setup.

Which costs and constraints should you compare?

Compare the current monthly price with the operational problem it solves. Estimate how often a manual gap blocks a usable nearby slot or fails to protect a long journey. Also count the time spent checking postcodes, collecting payment and correcting unsuitable bookings. Use your own figures rather than assuming a paid plan automatically creates more profit.

Check current limits on staff, services, payments, support and travel features before purchase because product details and introductory pricing can change. If one person takes bookings and the route is simple, start smaller. If a missing feature creates repeated manual work or unreliable availability, test the plan that directly addresses it.

• How many customer-bookable services do you need?
• Do journey times vary substantially by postcode pair?
• Will customers pay during the online booking flow?
• How often do you manually reject or move a booking?
• Does expected traffic materially change appointment reachability?

How should you choose and review a plan?

Take a representative week and run three cases: the shortest regular journey, the longest regular journey and a proposed booking between two confirmed visits. Identify whether a fixed gap is safe, whether postcode variation changes usable slots and whether time-sensitive road conditions create the remaining problem. Choose from evidence, not the plan name.

Review after the first month and after changes to coverage or service mix. Track late arrivals, manual interventions and unusable gaps. Upgrade when a higher calculation level solves a repeated, measured issue. Downgrade when the extra feature no longer changes decisions. The pricing page is the source of truth for what each plan currently includes.

How do you run a one-week plan decision test?

Take one representative week and mark the shortest, typical and longest transition between customer postcodes. Note every time you manually check an address, reject a requested slot or leave a large fixed gap for a nearby journey. This shows whether the constraint is service count, payment handling, postcode variation or time-sensitive roads.

Match the evidence to the plan rather than starting with price. Lite is the control case for a consistent manual gap. Compare Plus only where postcode variation changes availability, and compare Pro where road and expected-traffic context would change the decision again. Use the current pricing page for the final cost.

• Record the shortest, typical and longest regular journey.
• Count manual postcode checks and moved bookings.
• Identify whether time of day changes the route decision.
• Test the same three diary cases at each relevant level.
• Choose the lowest plan that fixes the measured constraint.