Route Star - office platform Screen 3 of 13 · ask in plain English {{ icoSparkles13 }} Concept preview All screens
AI-native throughout

Ask your business a question

Answers from your own data in seconds, faster decisions, nothing guessed, nothing leaves your business.

No report builder, no filters, no export to a spreadsheet. Type the question the way you'd say it out loud and get an answer you can act on - grounded in your own route, your own customers, your own payments.

Ask Route Star

Plain-English questions about your own data
{{ icoSearch16 }} Search jobs, customers… ⌘K
{{ icoBell18 }} {{ icoPlus16 }} Add job
{{ icoInfo16 }}
Ask Route Star is in build
The question and answer below are an illustration of where the platform is heading, not a live feature. Answers will always cite the records they came from.
TB
Compare churn for instalment customers against pay-as-you-go, and tell me what to do about it.
{{ icoSparkles16 }}

Customers paying by Direct Debit instalments stay far longer than pay-as-you-go customers on AutoPay. Over the last 12 months you lost 6.4% of instalment customers against 14.1% of pay-as-you-go - and the gap widens after the second winter, when pay-as-you-go customers tend to skip the autumn visit and never restart.

Instalment churn
6.4%
412 customers · 26 lost
Pay-as-you-go churn
14.1%
188 customers · 27 lost
Visits per year
4.6 vs 2.9
instalment vs pay-as-you-go
Customers lost by month
Instalment Pay as you go
AugSepOctNovDecJanFebMarAprMayJunJul
What I'd do
  • {{ icoCheckBold13 }} Offer instalments to the 63 pay-as-you-go customers who have had three or more visits - they're the ones most likely to switch.
  • {{ icoCheckBold13 }} Protect the autumn visit - that's where pay-as-you-go customers drop out. A reminder three weeks before, with the Lawn Health Check attached, is the obvious lever.
  • {{ icoCheckBold13 }} Nine customers cancelled within a fortnight of a missed visit. Worth watching that pattern rather than the payment method alone.
Answered from 600 customer records 2,847 visits 12 months of payments 53 cancellations {{ icoLock14 }} Your data only - never used to train anything
TB
Which visits are at risk this week?
{{ icoSparkles16 }}

Four of this week's 68 visits look shaky. Rain is forecast Thursday afternoon on the Winchcombe route, and three customers have something outstanding.

Weather Winchcombe route, Thursday PM - 8 mm forecast. Move 6 visits to Friday?
Access 4 Meadow Court - no gate code on file, technician turned away twice.
Payment 2 customers have a failed Direct Debit from 1 July, both due a visit Wednesday.
TB
What’s my revenue year to date against budget?
{{ icoSparkles16 }}

You’re £14,600 ahead of budget with nine months gone - but all of the upside is in recurring programmes. One-off renovation work is running £9,200 behind, which is the gap worth closing before the autumn window shuts.

Revenue to date
£412,600
{{ icoTrendUp14 }} 3.7% ahead
Budget to date
£398,000
Apr–Dec plan, set in March
Full-year outlook
£548,000
if renewals hold at 94%
Against budget, by line
Recurring programmes £344,200 +£23,800
One-off renovation work £47,900 −£9,200
Extras added from condition codes £20,500 no budget
TB
Which routes lost the most drive time last month?
{{ icoSparkles16 }}

The Winchcombe route is the one to fix. Crews spent 18.4 hours driving it in June - 29% of paid time, against 17% across the rest of the book. Two customers sit well outside the cluster and pull the whole day out of shape.

RouteDrive% of dayWhat’s causing it
Winchcombe · Thu 18.4 h 29% Two outliers 11 km past the cluster
Cheltenham north · Mon 12.1 h 19% School-run traffic before 09:30
Bishop’s Cleeve · Tue 8.6 h 14% Tight cluster - nothing to fix
Tewkesbury · Wed 9.8 h 16% Spare capacity on the return leg
{{ icoMap16 }} Move 4 Meadow Court and 22 Stanley Road onto the Tewkesbury Wednesday route and Winchcombe drops to 13.2 hours - about 42 km and 1.4 hours a week back.
TB
Which customers are due a re-quote?
{{ icoSparkles16 }}

34 customers are worth re-quoting. Nineteen have a bigger lawn than the one you priced - the satellite outline has grown since they signed up. Eleven have had the same price for three seasons. Four keep buying extras every visit and would be better off on a bigger programme.

19 · lawn has grown 11 · price unchanged 3 seasons 4 · buying extras every visit
CustomerPriced atMeasures nowReason
Bramley House, Woodmancote 640 m² 910 m² Rear lawn extended
7 Sandy Lane, Prestbury 310 m² 395 m² Patio lifted, turf laid
Meadow Farm, Gotherington 1,820 m² 1,820 m² Same price since 2023
Re-measure suggestions · concept - exploring
{{ icoSparkles18 }}
{{ icoSparkles14 }} Try one of these tap a question to see the answer
What you can ask about
{{ icoUsers16 }} Customers, churn and retention
{{ icoPound16 }} Payments, VAT and cash coming in
{{ icoNavMap }} Routes, drive time and capacity
{{ icoLeaf16 }} Treatments, condition codes and stock
{{ icoNavQuotes }} Quotes, conversion and follow-ups
Recent questions
Saved by Tom Bright
Which customers are due a re-quote?
Which routes lost the most drive time last month?
Saved queries are personal to the signed-in staff member.
Which customers are still on paper invoices?
Yesterday
What did we spend on fertiliser this quarter?
Monday
Which crew has the tightest route on Tuesdays?
Last week
{{ icoSparkles16 }}
Where else AI shows up
In the field In build
Photo lawn diagnosis and grass identification to back up the technician's own judgement.
On the inbox In build
Routine enquiries answered from your own route data, with anything unusual handed to the office.
On quotes In build
Follow-up timing and re-quote suggestions when a lawn has grown or a season has turned.
{{ icoShield16 }} Where answers come from

Your data stays in your Route Star account. Nothing is shared with other businesses and nothing is used to train a general model. Only your own records - customers, visits, quotes, payments and stock. Every answer shows what it counted so you can check it.

Concept preview for discussion. All customers, figures and answers are fictional. AI capability shown here is in build, not a launch feature list - nothing on this screen is a committed specification.

 ← Back to demo menu