Start with the job you need the software to do.
A customer directory, a booking calendar, a payment workflow and a marketplace solve related but different problems. Write down where the work currently gets lost: a missed message, a service that reserves too little time, a repeat booking that needs an exception, or a team calendar that ignores equipment limits.
A feature name is a starting question. Ask for a fictional end-to-end booking and retain the product version, account role and commercial terms used in the review. Apply the same standard to Detailr.
On a small screen, scroll the table to read every column.
| Role | Useful question | Evidence to retain |
|---|---|---|
| Customer relationship management | Can the right customer, vehicle and conversation be found? | A fictional record and handoff; access and export terms. |
| Booking and team calendar | Does the reserved time reflect services, extras and people? | Observed adjacent bookings, employee rules and exceptions. |
| Marketplace and discovery | Can customers find and compare the business? | Actual profile and service presentation; no assumed lead volume. |
| Payment and recurring plan | Who is charged, when, and under which terms? | Current fee, renewal, cancellation, completion and payout rules. |
AN ORIGINAL EVIDENCE FRAMEWORK
24 questions. Keep the evidence beside the answer.
Decide which requirements are essential for your business before the demonstration. For each question, retain the relevant written terms or observe the behavior in the tested version. A vendor description and a completed demonstration are different evidence states. No universal passing score is implied.
This worksheet runs in this tab. It does not send entries to Detailr or save them after reload. Export before closing. Use fictional examples; do not enter customer, payment or confidential business information.
All 24 questions are readable below. Download the blank CSV or PDF to record a review without JavaScript.
01 / Services that describe the actual work
A bookable package needs a clear scope, price basis and time allowance.
Can you define a package by vehicle and included work?
Build a fictional sedan service with named inclusions, exclusions, price basis and expected duration. Check what the customer sees before confirming.
Evidence needed for this exercise: observed demonstration.
Does an add-on change the appointment duration?
Add a 30-minute fictional extra to a 90-minute package. Confirm both the displayed total and the reserved time change; inspect an appointment immediately after it.
Evidence needed for this exercise: observed demonstration.
Can condition-dependent work require assessment?
Show how a heavy-soiling, stain or specialist task is described and approved without promising a result or silently expanding a fixed package.
Evidence needed for this exercise: observed demonstration.
Are memberships, packages and subscriptions distinguishable?
Review the actual charge, included visits or credits, renewal, unused-service and cancellation terms. Confirm the customer can tell a recurring appointment from a recurring charge.
Evidence needed for this exercise: reviewed written evidence.
02 / Capacity, employees and repeat bookings
An empty slot only matters if the people, equipment and location can support it.
Does the schedule respect employee availability?
Create two fictional employees with different hours and skills. Check who can receive a job, whether simultaneous appointments are possible, and what happens when one person is unavailable.
Evidence needed for this exercise: observed demonstration.
Can travel and turnaround time be protected?
Reserve time for the actual mobile route or shop reset, not just the cleaning task. Test whether a neighboring booking can consume that time.
Evidence needed for this exercise: observed demonstration.
What happens when a repeat visit meets an exception?
Create a repeat series, then change one visit for a closure or absence. Observe which later visits, charges and messages change. Retain the stated rule.
Evidence needed for this exercise: observed demonstration.
Can you identify the constrained resource?
Check employee, bay, vehicle or equipment limits relevant to your operation. A multi-employee calendar alone does not prove a shared bay or machine is protected.
Evidence needed for this exercise: observed demonstration.
03 / The customer decision and booking
Review the complete experience from the customer's side, including exceptions.
Is the complete customer total visible before confirmation?
Record the service amount, selected extras and disclosed customer/platform charges for a fictional booking. Check taxes, travel or condition charges where applicable.
Evidence needed for this exercise: observed demonstration.
Can mobile and shop instructions be made unambiguous?
Check the actual service address, access, work-space requirements, arrival directions and who supplies any required utilities. Do not rely on the business's mailing address.
Evidence needed for this exercise: observed demonstration.
Are rescheduling and cancellation expectations clear?
Read the current written rules and test a fictional permitted change. Identify cutoffs, any charge, who handles an exception and the customer support route.
Evidence needed for this exercise: reviewed written evidence.
Can a new customer understand the service without calling?
Ask a person unfamiliar with the setup to explain the selected work, location, duration, total and next step. Record misunderstandings, not just whether the screen looked attractive.
Evidence needed for this exercise: observed demonstration.
04 / Messages and the work record
The appointment and its conversation should remain usable through a handoff.
Can the conversation be found from the relevant job?
Send a fictional vehicle-condition question and locate the reply from the appointment and customer context. Check notification settings and responsibility for answering.
Evidence needed for this exercise: observed demonstration.
Does a team member receive the information they need?
Assign or reassign a fictional job. Check vehicle, service, access notes and customer instructions. Review what that role can see and change.
Evidence needed for this exercise: observed demonstration.
Is job completion a defined event?
Observe how completion is recorded, what the customer sees and which payment or review steps follow. A status button is not evidence that a quality dispute has been resolved.
Evidence needed for this exercise: observed demonstration.
Are photos and customer information handled under clear rules?
Review the supported media, consent, access, retention and deletion arrangements. Do not assume a work photo may be reused for public marketing.
Evidence needed for this exercise: reviewed written evidence.
05 / Charges, payouts and service exceptions
Separate the software's commercial model from payment processing and service obligations.
Can every charge be assigned to its payer?
Request current written subscription, commission, usage, processing and customer fee terms. Distinguish a Detailr fee from an unrelated operating cost or a payment-provider charge.
Evidence needed for this exercise: reviewed written evidence.
Are payment timing and payout timing explained separately?
Review authorization, collection, job completion, release and bank arrival under current terms. A completion-dependent release does not guarantee instant bank funds or a particular service result.
Evidence needed for this exercise: reviewed written evidence.
Can a service concern be escalated with the right context?
Use a fictional incomplete-service case. Identify the provider contact, platform support route, relevant record and current dispute/refund rules without promising a refund.
Evidence needed for this exercise: reviewed written evidence.
Can you reconcile one job to the money record?
Follow a fictional service, approved extra and any applicable adjustment through the supported payment/reporting workflow. Identify what must be exported or reconciled elsewhere.
Evidence needed for this exercise: observed demonstration.
06 / Operating cost, adoption and exit
Choose a workflow you can operate today and leave with a usable record later.
Have you recorded first-year and ongoing costs?
Separate setup, recurring subscriptions, variable fees and your own staff time. Include any retained accounting, communications or other tools rather than assuming every outside service disappears.
Evidence needed for this exercise: reviewed written evidence.
Can the team complete a task without the presenter?
Have a staff member configure or run a fictional booking without the salesperson directing each step. Record training and support actually needed.
Evidence needed for this exercise: observed demonstration.
Can you explain export, account access and leaving?
Read the current account, role, export and termination arrangements. Inspect the actual export format and identify information that must be retained elsewhere.
Evidence needed for this exercise: reviewed written evidence.
Does the decision name unresolved gaps and an owner?
Choose proceed, narrow, retest or stop for the stated use. Record the tested version, evidence accepted, open questions, responsible role and what would change the decision.
Evidence needed for this exercise: reviewed written evidence.
BROWSER-ONLY PLANNING EXERCISE
An add-on changes the calendar, too.
Try one repeated job type with equal working time per employee. This deliberately simple model reserves service, add-on, reset and travel time for every job. It shows the arithmetic behind a duration-aware schedule; it is not a live calendar or a prediction of demand.
Formula: available minutes = workday − unavailable time. Job block = service + add-on + reset + travel. Jobs per employee = floor(available minutes ÷ job block). Multiply only by the number of genuinely interchangeable employees.
This does not schedule shared bays, equipment, skills, two-person tasks, route order, drying space, customer windows or series exceptions. If one of those limits the work, reduce the estimate and use the actual operating calendar. A positive result is not permission to overbook.
Test the handoffs that a polished demo can miss.
These four original tabletop exercises use fictional bookings. They are proposals for a review, not measured Detailr results or a comparison of competing products. Use an approved test environment and never initiate a real customer charge to run them.
SCENARIO 01
An add-on meets the next appointment
A fictional 90-minute service gains a 30-minute pet-hair assessment/cleaning extra. Another customer has the next slot.
- Review the approved work and price change with the fictional customer.
- Check whether the extra reserves time and affects the following appointment.
- Record the responsible employee and the customer message if the original plan no longer fits.
Decision check. The test preserves an explainable duration and a workable handoff. A price change alone is insufficient.
SCENARIO 02
Two employees, one resource
Two fictional team members can work at the same time, but the business has one usable bay or one specialist machine.
- Define which jobs need the shared resource and which do not.
- Try the conflicting bookings in a test setup.
- Record the restriction the software enforces and any manual control still required.
Decision check. Team calendars do not automatically establish equipment or bay capacity. Make the remaining operating rule explicit.
SCENARIO 03
A repeating visit needs one exception
A fictional customer has a repeat maintenance series. A closure affects one date.
- Read the difference between recurring appointments and any recurring payment terms.
- Change only the affected visit, then inspect future visits and customer messages.
- Identify any unsupported behavior before migrating a real schedule.
Decision check. The team can explain the change, which visits remain and whether a charge is affected.
SCENARIO 04
A job is marked complete but a concern remains
A fictional customer reports an unfinished area after the job status changes.
- Find the agreed package and relevant appointment conversation.
- Use the current provider/platform support route and written terms.
- Keep the concern and response attached to the right booking without claiming an automatic quality guarantee.
Decision check. The review separates job status, payment release, support handling and the eventual service outcome.
Count the full operating cost, then make a decision.
Separate one-time setup from monthly costs, volume-based charges and staff work. SBA business-planning guidance uses one-time and monthly expense categories. Our application here is an original software-review worksheet, not an SBA standard or an industry cost survey.
Fictional arithmetic: $60 per month for software plus $15 per month for messaging equals $900 over twelve months. Add a fictional $120 setup cost and the first-year subtotal is $1,020. These invented amounts teach the calculation; they are not a quote, a market average or a Detailr savings claim.
Record any payment processing, accounting, telephone, insurance, labor or other tools you still require. In-app messaging can consolidate appointment conversations, but does not establish that every business can cancel every outside service. Customer retention and marketplace discovery are opportunities to evaluate, not guaranteed advertising savings.
Sources: U.S. Small Business Administration — Plan your business: calculate your startup costs
Use the same questions when you evaluate Detailr.
Detailr’s model has no Detailr software subscription for detailers and no Detailr commission on their service earnings. A customer transaction fee supports the platform. Review the current checkout and written terms for the actual payer, amount and payment arrangements.
Packages, add-ons with added time, employee scheduling, recurring bookings, subscriptions and in-app messaging address specific handoffs in this guide. Confirm the behavior and limits of the current app for your proposed use. Completion-dependent payment release is distinct from the service outcome and bank arrival time.
Keep a decision someone else can follow.
Record the intended use, tested version, accepted evidence, essential gaps, responsible role and next review date. Choose proceed, narrow the use, retest or stop. An essential unresolved requirement stays unresolved even when other features are convenient.
If you later publish pilot findings, record the sample, dates, conditions, missing observations and the exact outcome measured. This resource contains no verified improvement percentages, independent vendor scores or measured savings.