Kit

Vehicle

MOT, tax, insurance and what each vehicle really costs — one glance, not four reminder apps.

MOT or inspection, tax, insurance, servicing, and what each vehicle is actually costing you a month — one glance instead of four reminder apps and a glovebox. Tell Flint about each vehicle once and the dates you know go on the register; say "filled up, £62" or "serviced today, £180" in passing and the cost log grows, asking which vehicle when there is more than one and you haven't said. Every Monday the sweep reads your email for what the insurer, the garage and the licensing office have sent, files the costs, moves the dates forward from the evidence, and warns you thirty days out. Two cars, or three, without a second anything — the next one is a row, not a setup.

Try it free

1 agent, 1 routine, 1 dashboard, 2 records, 2 skills. Installing ends with Meet Flint — a short conversation sets it up, and everything can be retimed or paused after.

The logbookExample data
Next datesevery vehicle you still own
The hatchbackMOT or inspection · in 6 days48,210 mi
The vanMOT or inspection · in 15 days112,640 mi
The vanInsurance renews · in 23 daysAurora Insurance
The hatchbackTax or registration · in 41 days
Last servicefrom the cost log

The hatchback

74 days ago at 48,210 miles — Marlow Motors, £240

The van

201 days ago at 112,640 miles — Marlow Motors, £164
Running costmonth by month, every vehicle
£533

all logged · £298 the hatchback · £235 the van

May
Jun
Jul
Aug
Sep

The crew

Flint

Keeps the dates that would otherwise slip, and the slow story of each machine.

Steady, unhurried, patient with rough answers; keeps a logbook the way a good garage does.

What else it installs

Vehicle recordrecord

One row per vehicle — its dates, its mileage, and whether you still have it.

Vehicle costsrecord

Every fill-up, service, repair, renewal and fine — one row each, against its vehicle.

Vehicle registerskill

"The van's MOT is due in March" — and the register moves.

Cost captureskill

"Filled up, £62" — that is the whole interaction.

The logbookdashboard

Every vehicle's dates on one table, what is due soon, and what each one is costing.

Vehicle sweeproutine

Mondays — reads the insurer, the garage and the licensing office; files the costs; warns thirty days out.

Runs mondays · 7am

How it works

The mechanics of this kit, plainly — what runs and when, where the data lands, and what you look at.

  • Vehicle sweep runs mondays · 7am and keeps the The logbook dashboard fresh. Mondays — reads the insurer, the garage and the licensing office; files the costs; warns thirty days out.
  • What is captured lands in the Vehicle record, which lives at Data/Vehicle Record in your vault — yours to open, search, and edit like any other file.
  • What is captured lands in the Vehicle costs record, which lives at Data/Vehicle Costs in your vault — yours to open, search, and edit like any other file.
  • The The logbook dashboard reads from the record and shows, at a glance: next dates · due in the next 60 days · on the register · running cost, all logged · cost by vehicle · cost month by month, every vehicle · last service · the register · the cost log · how this board works.

The wiring, in one breath: Vehicle register writes to Vehicle record · Cost capture writes to Vehicle costs · Vehicle record shown by The logbook · Vehicle costs shown by The logbook · The logbook kept fresh by Vehicle sweep · Vehicle sweep run by Flint · Flint holds Vehicle register · Flint holds Cost capture.

Getting the most from it

A kit earns its place when it changes what you look at and what you say, not when it is installed. This is the rhythm that makes it pay.

  • Give each vehicle the dates you know the day you add it — a rough month is fine — and Next dates is worth a glance from that moment. The blanks are honest; fill them as the letters arrive.
  • Say a cost the way you'd say it to a passenger — "filled up, £62", "serviced today, £180 at the garage" — and Cost capture files it against the right vehicle. With two on the register, name which; if you don't, Flint asks rather than guessing.
  • Read Due in the next 60 days on Monday morning, after the Vehicle sweep has been through your email. Amber at thirty days is the honest signal — it is drawn from the register, so a date nobody stated is never on it.
  • Forward the renewal email, the MOT certificate or the garage invoice to Flint and the date on the register moves from the document, not from memory. That is the correction that keeps the table true.
  • Look at Cost by vehicle once a month, not once a week: it answers which one is costing more, and the line beside it whether the total is growing. Neither reads a bank — they add up only what you and your email have said.
  • When a vehicle goes, say so — "sold the van" — and it drops off the table keeping its history. The next one is a row, not a setup.

Make it yours

Nothing here is fixed. The pieces are ordinary agents, routines, records and dashboards, so anything you know about shaping those applies. Retire whatever earns nothing.

Things people usually change first

Say any of these in chat, or edit them on the kit’s page in the app.

  • What you call each vehicle — the name on the register is the word Flint uses back.
  • When the Monday sweep runs, or turning it off and keeping the register by hand.
  • The garage and the insurer you use, so the sweep searches for them by name.
  • Whether the log keeps fuel at all, or only the big things — services, tyres, renewals.

Your first run

Installing starts a short setup conversation — not a form. Answer roughly, correct later.

  1. Installing ends with "Meet Flint" — a short conversation, not a form. The first question is the one that shapes everything: how many vehicles to keep track of. Then each one in turn — what you call it, the registration if you know it, and the dates you know off the top of your head: MOT or inspection, tax or registration, insurance renewal, last service, rough mileage. Each row lands as you say it; a blank stays blank.
  2. Nothing in that conversation touches your email. The Vehicle sweep is what reads it — every Monday, for what the insurer, the garage and the licensing office have sent about each vehicle — and it asks for email access the first time it runs, from its own screen, where the ask makes sense.
  3. Skip the conversation and the door quietly stays open: until a vehicle is on the register, the kit page, the board and Flint's chat keep the offer ready, and the Monday sweep leaves one card inviting you in rather than searching for nothing. The first vehicle, however it arrives, closes it.
  4. The first sweep with a vehicle on the register looks back a year — filing the costs it can be sure of against the right vehicle, moving a date only when a document states the new one, and drawing Due in the next 60 days and Last service. After that it scans only what is new, and says something only when a date is within thirty days, a document moved one, or an email could not be matched.

Watch the first pass, then tell it what you would have done differently — that correction teaches it more than any setup could.

The essentials

Learning, preferences and run costs work the same in every kit — so they are covered once, in the Kits guide.

Living with a Kit — the Kits guide →

← All kits

Put the Vehicle kit to work.

Install it, run it once against something that already happened, and see whether what comes back sounds like you.

Try it free

Everything it installs can be retimed, paused, or removed.