INSTIG8.

Kit 346 November 2026

Operations, tile and shower repair, a family-owned company of just under 200 people

The work order that waited two days

A starter kit for turning work order PDFs into jobs. Make it yours, then build it with your AI.

Lost: the job, about $1,100, and a duplicate record to clean up. An example: how it goes today

Sources
Research only
Run
Not yet
Built clean
Not yet
The capabilityTurning work order PDFs into jobs

Approval limits

What needs a yes, and what happens when it fails?

The kit says: Never: create a new client

Rules from builds that went wrong

  • Have a dispatcher read 5 ready records beside their PDFs every weekday, and count every field a person corrects.
  • Look up open jobs by the client's order number and the address before creating anything, and update the first record when an order is sent again.
  • Never create a new client on its own, and leave any field that is not on the page empty for a person.
  • Take every date from the page it is printed on, and hold the record for a person when there is none.
  • Hold for a dispatcher any order whose address matches an open job, even when the sender is different.
The kit's whole answer
It never
Create a new client; accept or turn down a job; message a client or a tenant; quote a price; merge or delete a record; fill a field that is not on the page.
Waits for a person
A dispatcher approves every held record, every new client and every new address; accepts each job in the client's system; books every technician; decides on any price above the client's limit; and each weekday reads 5 ready records beside their PDFs.
It tells you when
Alerts go to the dispatcher on shift, and to the operations lead for anything past its deadline. A PDF in the inbox with no record after 10 minutes; a held record unread after 2 office hours; any order within 4 hours of its deadline to accept with nobody on it; the same order number on two open jobs; the workflow not running; monthly runs past 2,000; and the wrong-but-green count: records marked ready that a person later corrected, such as a re-sent order filed as a new job or a date filled in that was not on the page.
When it breaks
What you see: a PDF with no record, the same order twice on the dispatch board, or held records piling up. Check first: the inbox connection still answers; the job system still accepts new records; a large client has not changed its PDF layout. Safe fix: turn off the workflow; the office types orders in by hand, as today.
Switching it off
Turning off one switch, the workflow, in the software that runs the steps. No PDFs are read, no records are created or updated, and no orders are raised near their deadline. Records already created stay as they are, and new orders wait in the inbox for the office to type in, as today. It takes under a minute. Try it once in week one.

0 of 8 answers made yours

Free for your email. Your changes go into the build prompt, and the next kit comes each weekday.

How it goes today

A family-owned tile and shower repair company of just under 200 people turned its pile of work order PDFs into job records in two minutes. Here is how an order goes missing while it waits, what went wrong for others who automated it, and a build that reads, checks and enters but accepts no job on its own.

On 1 October 2026 the chief technology officer of a family-owned tile and shower repair company, just under 200 people with about 180 technicians, told a trade publication: “The team were really struggling with work order processing, with PDF documents constantly coming in.” Their agent now “reads them, does the duplicate checking and creates the records”. Before it: “waiting one to two business days for us to get to it, then another 10–15 minutes to have it processed”. After: “it's done within two minutes, 24/7”.

Here is how it goes without it. At 4:40pm on a Monday a property manager emails a work order: a leaking shower in a rented unit, with 24 hours to accept. On Tuesday morning, having heard nothing, the manager sends it again with a new tenant phone number. The office is working the inbox oldest first.

On Wednesday at 10:30am a dispatcher types in Monday's PDF. At 11:00am a second dispatcher types in Tuesday's copy as a new job. By then the property manager has given the job to another contractor.

Nobody here is slow. Every order waits its turn in one inbox, and each takes 10 to 15 minutes to type in, so the oldest gets done first and the one with the shortest deadline gets no special place. Property managers' own rules give a contractor 24 hours or less before the job goes elsewhere. At about 750 orders a month, if 1 in 100 goes that way, about $8,300 a month of jobs go to someone else (an estimate, at a typical US regrout of $1,100).

The order, the times and the second copy are an example. The 750 orders a month, the 125 hours, the $1,100 job and the $8,300 are estimates the company's own counts replace.

Who it needs

Owns it: The dispatcher, with the operations lead. Nobody holds this? Konstellation starts with the expertise, not the build

Runs it day to day: The person who builds it and runs it. Nobody to run it? A part-time operator through INSTIG8

What went wrong for others (5)
  • “with AI, it could do something 99 times, then one time it won't because it's interpreted it slightly differently.” The chief technology officer of the tile and shower repair company, October 2026. Read it
  • “The expensive failure isn't a bad extraction, it's a plausible duplicate or wrong-customer order silently becoming system-of-record data.” A reply to a field service owner who automated work order entry, August 2026. Read it
  • “If the AI is allowed to create customers freely, near-duplicates pile up” and “Empty is better than plausible.” A field service software maker, November 2026. Read it
  • “Early scheduling work produced incorrect days of the week” The tile and shower repair company, on its own first build, October 2026. Read it
  • “I got a work order yesterday fix x-issue at store. Then a little while later I was routed for the same exact thing but from a different buyer.” A field technician, June 2026. Read it
Sources (19)

Read 6 November 2026 unless a date is given.

  1. The interview: Mi3, "The Grout Guy's growth bet: Agents process work orders in two minutes, speed email triage", 1 October 2026; the company's chief technology officer, quoted above. The interview was given at the conference of the software maker whose products the company runs (Salesforce's Dreamforce, San Francisco), and the reporter attended as part of that maker's media tour; the numbers are the company's own claims
  2. The company's site: "180+ technicians nationally"; "Trusted by homeowners, strata managers & commercial clients nationwide"; "Our teams work Monday to Friday" (undated)
  3. The company's FAQ: a regrout takes 4 to 6 hours, mostly in one visit (undated)
  4. US Bureau of Labor Statistics, wages for May 2025: dispatchers, except police, fire and ambulance, median $24.20 an hour; general office clerks $21.64
  5. Angi, shower regrouting cost, updated 28 October 2026: average $1,500, most $600 to $2,500
  6. SmoothQuotes: typical paid $1,100, 53 reports over the last 24 months (page undated)
  7. Prefix Maintenance, vendor terms, last modified 24 July 2026: non-urgent orders accepted within 60 minutes; an order not accepted in time "shall be deemed declined"
  8. GC Realty & Development, 2026 vendor agreement: "High Priority: Scheduled and completed in <24 hours"
  9. Switchback Property Management, vendor FAQs (undated): "You must accept or decline the work order within 24 hours."
  10. Fieldproxy, "Can AI read a PDF work order and create the customer and job?", 3 November 2026: "Empty is better than plausible"; near-duplicate customers; send anything new or unclear to a person
  11. r/ClaudeAI, a field service owner who automated work order entry from PDFs, 17 August 2026, and a reply: "a plausible duplicate or wrong-customer order silently becoming system-of-record data"
  12. r/ITSupport (mirrored), automating a property maintenance company's work order emails and PDFs, 9 May 2026: "inconsistent email formats", "PDF extraction problems"
  13. r/FieldNationTechs, 24 June 2026: the same job routed twice "from a different buyer"
  14. Salesforce Agentforce pricing: $500 per 100,000 Flex Credits, 20 credits an action; $125 a user a month for the Field Service add-on
  15. Docparser pricing: Business $159 a month billed monthly, 1,000 documents
  16. Go Hire Virtual, trades virtual assistant, $12 an hour, updated October 2026
  17. Wishup, trade business virtual assistant, 22 June 2026: $1,999 a month full-time
  18. Building it, the workflow runner: Starter, 20 euros a month billed annually, 2,500 workflow executions a month (n8n pricing; the run count as read 5 November 2026)
  19. Building it, the model: $2 per million tokens in, $10 out for Claude Sonnet 5.5 (Claude API pricing, re-read 6 November 2026)

Estimates name their figures: about 750 work orders a month (sources 2, 3 and an assumed 1 in 5 jobs); about 125 hours and $3,000 a month (source 1's 10 minutes, source 4); $1,100 a job (sources 5, 6); about $8,300 a month of lost jobs (sources 7, 8, 9 and an assumed 1 in 100); about $4,100 a month kept (the same, half assumed kept); the $142,500 ceiling (the same at 1,900 orders, 1 in 20, $1,500); about 16 hours redrawn and $31,600 a year freed (assumed holds and checks; source 4); about $45 a month and 980 runs (sources 18, 19); about $225 a month inside the company's software (source 14 and an assumed 3 actions an order); the $81,000 a year a build quote is set against.

Next job: Taking every signed house contract to closing at a home-buying company of about 18 people: about 150 hours of a coordinator's month, and about $3,700 a month of holding cost on resales that slip or fall through. Ask for a kit