Untitled app

draft

untitled-app·web :4802 · api :4803·updated Jul 24

complete

Export bundle Resume in wizard

draft

building

testable

ready

Spec bundle · living

01readyEdit in wizard

Vision & positioning

The problem, who it is for, and what winning looks like.

The problem: Field service technicians finish a repair, then spend 15-20 minutes back at the truck typing up what they did — retyping part numbers, hunting for the right job code, and re-explaining work the customer already signed off on. Half the time they defer it to end of day, so notes are vague, warranty claims get rejected, and billing lags a week behind the work.
Target users: Field service technicians who complete 4-8 jobs a dayService dispatchers who reconcile job status and reassign workBilling and warranty coordinators who turn completed jobs into invoices and claims
Success criteria: A technician can close out a completed job — notes, parts used, labor time, customer signature — in under 90 seconds on a phone90% of jobs are closed out before the technician leaves the site (measured by GPS + timestamp)Warranty claim rejection rate due to incomplete documentation drops below 5%Median time from job completion to invoice generation falls under 24 hoursDispatchers see accurate live job status with under 60 seconds of lag
What it must feel like: Fast, forgiving, and trustworthy — like a tool built by someone who has stood in the rain with greasy gloves. It never punishes a mistake, never makes you start over, and always shows you're one tap from done.

Positioning narrative

Why this, why now

Field service software today was designed for the back office and bolted onto mobile as an afterthought. Technicians are the ones entering the data, but the forms are built for accountants. The result: documentation that happens hours late, in a parking lot, from memory.

What it replaces

This replaces the end-of-day paperwork ritual and the clipboard-plus-photos-plus-texts workflow techs improvise to get by. It collapses closeout into the moment the work is finished, while the details are fresh and the customer is still standing there.

What winning looks like

Winning is invisible: the technician never thinks about 'doing paperwork' again. Jobs close themselves as work happens, billing runs the same day, and warranty claims sail through on the first submission.

Vision & positioning

The problem, who it is for, and what winning looks like.

The problem

Field service technicians finish a repair, then spend 15-20 minutes back at the truck typing up what they did — retyping part numbers, hunting for the right job code, and re-explaining work the customer already signed off on. Half the time they defer it to end of day, so notes are vague, warranty claims get rejected, and billing lags a week behind the work.

Target users

Field service technicians who complete 4-8 jobs a dayService dispatchers who reconcile job status and reassign workBilling and warranty coordinators who turn completed jobs into invoices and claims

Success criteria

A technician can close out a completed job — notes, parts used, labor time, customer signature — in under 90 seconds on a phone90% of jobs are closed out before the technician leaves the site (measured by GPS + timestamp)Warranty claim rejection rate due to incomplete documentation drops below 5%Median time from job completion to invoice generation falls under 24 hoursDispatchers see accurate live job status with under 60 seconds of lag

What it must feel like

Fast, forgiving, and trustworthy — like a tool built by someone who has stood in the rain with greasy gloves. It never punishes a mistake, never makes you start over, and always shows you're one tap from done.

Positioning narrative