Concept build, sample business

A landscaping week, run from one screen.

A Concept build: software for a made-up landscaper, Marrowstone Landscape Co. in Vacaville. Everything in it is sample data.

Pick a time to talk

The problem

  • The week lives on a whiteboard in the garage.
  • The phone rings out while you’re on a mower, and the caller tries the next company.
  • The quote gets written that night, if it gets written at all.
  • Rain means a phone call for every yard on the route.
  • You chase payment for work done weeks ago.
  • Some yards take far longer than you priced them for, and nothing shows you which.

What the software does

  • Answers the calls you miss and books a free estimate at a time you’re really open.
  • Sends good, better and best options from the yard, before you leave.
  • Takes the approval and the deposit, and books the job into your first open day.
  • Moves a rained-out day to open times on the next dry one, and confirms each new time.
  • Sends the invoice when a visit is marked done.
  • Shows you the yards that take longer than you priced them for.

Step by step

  1. The week

    Each crew’s stops for the week, in route order and grouped by street.

    Sample data: the Route Desk sample app at step 01, The week
    Sample data · the sample app, at phone width

  2. The missed call, answered

    Tom calls while Ray’s on a mower. The line picks up, says it’s automated and the call is recorded, and books a free estimate at a time Ray is really open.

    Sample data: the Route Desk sample app at step 02, The missed call, answered
    Sample data · the sample app, at phone width

  3. Confirmed on both sides

    Tom sees it confirmed right away. Ray sees it on his Thursday, with the job card.

    Sample data: the Route Desk sample app at step 03, Confirmed on both sides
    Sample data · the sample app, at phone width

  4. The quote, at the yard

    Ray picks a template, types what he measured, and sends three options before he leaves.

    Sample data: the Route Desk sample app at step 04, The quote, at the yard
    Sample data · the sample app, at phone width

  5. Approved, deposit paid

    Tom picks one, types his name to approve it and pays the deposit. The job books into the first open day, confirmed for both of them.

    Sample data: the Route Desk sample app at step 05, Approved, deposit paid
    Sample data · the sample app, at phone width

  6. Onto a plan

    When the job’s done, Tom is offered the weekly plan. Yes puts him on the Tuesday route, in order with the stops already there.

    Sample data: the Route Desk sample app at step 06, Onto a plan
    Sample data · the sample app, at phone width

  7. Rain on Thursday

    That’s Ray’s call. One tap moves the yards to open times on Friday, and every customer sees the new time confirmed. Any yard that doesn’t fit comes to Ray.

    Sample data: the Route Desk sample app at step 07, Rain on Thursday
    Sample data · the sample app, at phone width

  8. Invoiced when it’s done

    The crew marks the visit done, and the invoice goes out. Nobody chases it. A card that’s declined becomes a reminder for Ray.

    Sample data: the Route Desk sample app at step 08, Invoiced when it’s done
    Sample data · the sample app, at phone width

  9. The review request

    After the visit, every customer gets the same review request, not just the happy ones.

    Sample data: the Route Desk sample app at step 09, The review request
    Sample data · the sample app, at phone width

  10. The yard that loses money

    A yard priced for a short visit that takes much longer every week stands out, so Ray can see it and fix the price.

    Sample data: the Route Desk sample app at step 10, The yard that loses money
    Sample data · the sample app, at phone width

What this isn’t. No client. No results. A made-up business and sample data, built to show the idea.

Concept build, sample businessDetailingSoftware for a mobile detailer: bookings by vehicle size, the photos and the payment.