What SkipOps does — and exactly where we are

The objective: before SkipOps can run anyone's day, it has to learn how that firm works. The boss fills in a quick 5-step setup wizard + a review — (1) Van & crew, (2) Waste types, (3) Sites, (4) Ops, (5) Checklist — tap and type, then Next. Each step shows only the one thing it's asking, so it never feels busy. We started at 5/6 steps, collapsed to 3, then split back out to 5 because the honest shape is one clear question per screen: who works here → what waste you handle → where each one ends up → how each one gets there → the job checklist. No AI, no guessing in setup: each step is a plain form our own code checks before you can advance, and the firm is saved at the end. Hours aren't asked — they flex day to day, so the day's window comes from the crew sharing live location to sign in (gaffer's "kick off the day", stage ②).

flowchart LR
  S1["① Van & crew"] --> S2["② Waste types"]
  S2 --> S3["③ Sites
(map per waste)"]
  S3 --> S4["④ Ops
(how it moves)"]
  S4 --> S5["⑤ Checklist"]
  S3 --> R["Smart routes +
full-van trips"]
  S4 --> R

The objective: the original wizard makes the boss type in everything — crew, waste types, checklists — before the firm exists. v2 flips that: it asks only what a boss can answer in a minute, and everything else arrives later, in Telegram, where his crew already are. (1) Your firm — the name and how many vans. (2) Your base — one pin on the map. (3) Where does it go? — a card for each place he gets rid of waste: he searches a tip by name (the way he actually knows them), ticks which waste goes there, and the yard is simply the first card — anything ticked on it says whether it's stored then taken on or disposed of right there. (4) Checklist — the same job + yard checklists the original wizard builds (what the crew must tick, photograph or measure on every job), pre-filled so most bosses just glance and carry on — and the firm's Google review link is required here (Alex's call: the "ask for a review" step must always point somewhere real). Nobody types a crew list, ever: when the firm's saved, a share-able link makes whoever opens it the boss's account — so Alex can fill the whole thing in on a sales call and just send the link. If something's blocking the Next button, the screen now says exactly why, right next to the thing to fix (added after Alex's walk caught it staying silent).

flowchart LR
  A["① Your firm
(name + vans)"] --> B["② Your base
(one pin)"]
  B --> C["③ Where does it go?
(tip cards + waste ticks)"]
  C --> CL["④ Checklist +
review link"]
  CL --> D["Save — the
firm exists"]
  D --> E["Send the link →
the boss takes over"]

The objective: for each waste type, capture the disposal site(s) the firm itself uses — the places it actually has access to and an account with. That list is what routing trusts. Why not just auto-find sites for them? Because no data can tell us whether a site will take a crew that turns up unannounced — many require a trade account; some (like Robins) don't. Sending a van somewhere it gets turned away is unacceptable. So the firm names its own (it only ever uses 4–5) — and our whole job is to make that entry effortless: we suggest the real sites near their yard and let them tap to add, instead of making them type everything from scratch.

flowchart LR
  A["Yard postcode"] --> B["Suggest real sites
near you, by material
(from EA data)"]
  B --> C["Firm taps to add
· or types its own"]
  C --> D["The firm's sites,
per material"]
  D --> E["Routing only ever
uses these"]

The objective: given the day's jobs, work out the most efficient round for every van — fewest miles, fullest loads — including nipping back to the yard to empty when a van fills up, then carrying on. This saving (fuel, time, wages) is the whole pitch.

flowchart LR
  A["The day's jobs"] --> C["The planner"]
  B["The vans + capacity"] --> C
  C --> D["Most-efficient
route per van"]
  D -. "van full →" .-> E["empty at the yard,
then carry on"]
  E -.-> D

The objective: jobs change all day — a new one comes in, one's cancelled, a van finishes early. When that happens the system quietly re-plans the rest of the day and re-sends the routes, without anyone asking.

flowchart LR
  A["New / cancelled job,
or van free early"] --> B["Re-plan the
rest of the day"]
  B --> C["Re-send the
updated routes"]