Skip to main content

Featured

The Docstring Coverage Gate Is the Product: What I Verified in AI Doc Generator

The Docstring Coverage Gate Is the Product: What I Verified in AI Doc Generator Documentation debt never announces itself. It shows up as the three hours you lose reading a function called process_data2 , or as the README that documents an argument the code stopped accepting two refactors ago. Every team knows the number that matters is documentation coverage, and almost nobody has a cheap way to measure it, let alone gate a merge on it. That is the specific pain I went looking for a tool to solve, and it is how I ended up testing AI Doc Generator — a $49 single-file Python CLI that scans a codebase for undocumented functions and classes. This post is what I actually measured in the bundle, on my machine, from a clean copy. Including the parts that don't work. Yes, it is a product I sell, and this article says so plainly rather than dressing up as a neutral review. The real problem: coverage is invisible until it is a crisis Ask a team what fraction of its public functions...

Mobile Detailing Client Intake Form: What Your Vehicle Inspection Sheet Has to Record

Mobile Detailing Client Intake Form: What Your Vehicle Inspection Sheet Has to Record

Most mobile detailing paperwork problems do not present as paperwork problems. They present as a client saying the scratch was already there, or forwarding a text from three weeks ago where a number got mentioned and never written down. By the time the disagreement arrives, the only record is memory, and memory is the least reliable document in the business.

We built a small kit around that gap: ten working files plus four that support them, all plain Markdown and CSV, no app and no login. This article is about the intake-and-inspection half, because that is where the expensive arguments begin. The amounts inside the kit are fictional planning inputs, not market rates.

Why the client intake form decides the job before the wash starts

Intake usually gets treated as an address-collection step: a name, a phone number, a vehicle, a time slot. That is enough to schedule and not nearly enough to deliver. What you actually need on site — how large the vehicle is, what condition it is in, where the water comes from, whether the owner will be present — gets discovered on arrival, with the clock already running.

Water and power are the standard example. A third-floor apartment with no hose access changes the entire job, and learning that after the equipment is unloaded is a bad conversation to have while someone watches. The intake in the kit is one page of grouped prompts rather than a database: client and contact block, vehicle block, service expectations block, and a consent checklist. Each field exists because its absence causes a specific problem later.

What a vehicle inspection sheet has to capture, and what it should not

The vehicle block is short by design: year, make, model, colour, size or layout, where it will be serviced, and a note on contents if relevant. Plate is optional — store it only if you need it, because it is personal data you have to protect for no operational benefit in most cases.

Condition is where the sheet earns its keep. The prompts ask for known stains, odours, pet hair, sand, spills, plus which areas the client wants prioritised and — the part most operators skip — which conditions they understand may need extra time or may not fully change.

That last prompt is not legal protection. It is expectation setting, in writing, before anyone touches the vehicle. A pet-hair job that runs ninety minutes long goes far more smoothly if the intake says pet hair was noted and the client acknowledged it. What the sheet should not do is promise outcomes: never promise removal or restoration of a condition you have not inspected.

The condition log: photo references you can actually find again

The condition log is a flat CSV with nine columns: log identifier, quote identifier, job identifier, stage, panel or area, condition, file reference, customer acknowledgement, notes. The file reference column holds a filename, not an image. The kit does not upload, host or store photographs. You take the photo on your phone, name it job-001-before-front-seats.jpg, and write that name in the row.

The images then live in a folder you control, which is better for client privacy than scattering them across a messaging app. The acknowledgement column matters: a photo the client agreed to is evidence, a photo they did not agree to is an argument about consent.

The quote worksheet and arithmetic you can audit

The quote worksheet is a CSV because a quote is a row, not a paragraph. Each row carries the quote identifier, client and vehicle identifiers, the service, the observed condition, add-ons, travel adjustment, time adjustment, quoted total, deposit, balance, status, and a notes field.

The kit ships one frozen fictional example, and the numbers are invented. Maintenance Detail at 120.00, a pet-hair add-on at 25.00, a travel adjustment at 15.00, a time adjustment at 0.00, giving a quoted total of 160.00. A 50.00 deposit leaves a balance of 110.00. Every figure is buyer-editable. None of it is a market rate, an expected earning, or evidence that any detailer charges these amounts.

The structure gives you auditability. Travel and time sit in their own columns on purpose, because they are the two things operators quietly absorb and then resent; if you drove forty minutes each way, it belongs in the row where the client can see it.

The service agreement template and the review boundary

The agreement is a fill-in document covering parties and job identifiers, scope and exclusions, access and preparation, payment and cancellation, condition acknowledgement, and signatures. It is not a legal form, it is not legal advice, and it needs review by a qualified local professional before you use it with a paying customer. A template that has not been checked against your jurisdiction's consumer-contract rules is a document that can hurt you.

Two clauses are worth getting right early. Exclusion language should say what is not included in plain words — repair, restoration, paint correction, part replacement, biohazard handling — rather than relying on a general disclaimer. And any add-on or scope change needs written customer approval before the work is performed, not a verbal yes in a driveway. If access fails, the operator pauses and records why instead of improvising.

Running the day, and the add-on nobody approved

The job checklist is sequenced rather than thematic. Arrival and access confirmations first — date, window, contact, vehicle, water and power, weather, approved package and payment status. Then a pre-service walkaround: pre-existing damage, fragile surfaces, contents, before-service photo references, acknowledged exclusions. Service execution follows the selected package scope and needs an approved add-on recorded beforehand. Closeout records payment, balance, receipt or outstanding status, plus any rework request. Follow-up is the last block, and it is the one that gets skipped when the day runs long.

Upsell disputes are almost never about the money. They are about the sequence: an operator notices the floor mats need work, does them because it seems obvious, and mentions it at closeout. The upsell and rework log records offers, decisions, approval, rework status, feedback and follow-up date. "Customer approved before service" is a record. "Customer seemed fine with it" is not. The same file handles rework, which is the other direction of the same problem.

Mobile detailing repeat customers and the eight-week gap

Retention in this trade is not a marketing problem. It is a calendar problem. A Maintenance Detail client on an eight-week cadence is due again in about two months, and if no date exists anywhere, the client drifts until they notice the car looks bad again and book whoever answers first.

The recurring tracker is one CSV row per client: recurring identifier, client, originating job, cadence, last service, next service, package, status, follow-up note, cancellation reason. Status values are plain words — proposed, confirmed, paused, cancelled — and the follow-up column exists so the renewal conversation has an owner and a date. The kit does not send reminders. What it gives you is a list you can scan once a week.

Route-day handoff and the monthly review

A route sheet gets carried around, photographed, texted to a helper, and left open in a van, which makes it the worst possible place for gate codes. The handoff CSV holds date, route order, a client-job alias, service window, access status, a location alias, equipment notes and completion state. The sheet says North-Client-001, and the mapping to a real address lives in a private record you control. Keys, codes, passwords and tokens are excluded from the bundle entirely — a deliberate omission, not an oversight.

The last working file summarises a month: job count, revenue, variable costs, fixed costs, refunds, notes. It is an organiser, not accounting software and not tax advice, and its example row is marked fictional. The useful discipline is the variable-cost column, because consumables are the cost most often forgotten.

What actually ships in the bundle

Fourteen files, one ZIP, 13,033 bytes. Ten are working documents, four support them.

FileWhat it holds
01_Service_Menu_and_Pricing.mdPackages, add-ons, scope and editable inputs
02_Quote_Worksheet.csvQuote rows: service, condition, adjustments, deposit, balance, status
03_Customer_Vehicle_Intake.mdContact, vehicle, expectations, consent checklist, privacy reminder
04_Condition_Photo_Log.csvStage, area, condition, local file reference, acknowledgement
05_Service_Agreement_Template.mdScope, exclusions, access, payment, condition, review boundary
06_Appointment_Job_Checklist.mdArrival through closeout and follow-up
07_Upsell_Rework_Feedback_Log.csvOffers, decisions, approval, rework, follow-up
08_Recurring_Service_Tracker.csvCadence, last and next service, status
09_Route_Day_Handoff.csvOrder, window, access status, location alias, completion
10_Monthly_Revenue_Cost_Tracker.csvJob count, revenue, costs, refunds, notes
README.md, START-HERE.mdQuickstart and a single-job walkthrough
LICENSE.txt, self_qos.pyPersonal-use licence; offline bundle checks

Running python3 self_qos.py from the folder prints SELF-QOS PASS: 14 manifest files, 6 CSV example rows, quote total 160.00, balance 110.00 and exits zero. It checks that every manifest file is present, that CSV headers match the documented contract, and that the example arithmetic adds up. It is read-only and makes no network calls. It also fails cleanly, which we tested: delete a required file and it reports the missing filename and exits one, with no traceback.

Plain files versus a CRM subscription

There are two shapes for an operations tool. One is a service you log into that holds your data, charges monthly, and gradually becomes the place your business lives. The other is a set of files you own, which cost once and work offline. The first gives you automation and takes a fee plus a dependency. The second gives you portability and takes discipline.

This kit is the second. There is no CRM, no dispatch, no GPS tracking, no route optimisation, no automated reminders, no invoicing, and no payment processing. Nothing in it connects to anything, including any AI service. If two people need to edit the same record at once, a folder of CSVs is the wrong tool and you will feel it within a week. If you are one person or a small crew running a repeatable sequence, the discipline cost is small.

The kit, the price, and who should skip it

Mobile DetailOps Client Kit — Quotes, Vehicle Intake, Condition Logs & Repeat-Service Tracking is available at the Mobile DetailOps Client Kit listing on Gumroad. The current intro price is $1.00, verified live on 21 November 2026. It is an intro price on a ladder that can move, not a permanent promise — re-check it before you buy.

Disclosure: This post links to a product we made. If you buy through it, we may earn a commission at no extra cost to you.

On evidence: what sits behind this article is a visible supply gap on Gumroad for a plain-file operations kit in mobile detailing, plus indicative search intent around intake forms, inspection sheets and repeat-client retention. That is intent density — not search volume, not a demand forecast, and not purchase proof. There is no review, rating, testimonial or sales figure we could cite, so none is cited here.

Who should skip it: anyone who wants software. No dashboard, no sync, no mobile app, no client portal, no automation of any kind. Skip it if you want someone to tell you what to charge — the amounts are placeholders. Skip it if you want a detailing course; there is no wash technique, no paint-correction method and no safety certification here, only paperwork. And skip it if you will not adapt the agreement to your jurisdiction with a local professional.

Keep reading

If the cost structure here was useful, how to price a recurring pet waste route walks the same logic for a stop-based service. Our breakdown of how to price a plumbing job builds a job from labour and materials, and the tree removal quoting guide covers the version where equipment and risk dominate.

Corrections and questions are welcome. If we got a fact wrong, write to nandminc2020@gmail.com and we will fix it.

Comments