The catalog
Five workflows, written as the problem and the senior person it eats.
These are the first five, chosen because they repeat across industries far more than the industries repeat. The catalog is open: every build adds to it, and your assessment decides which one comes first.
01 / Workflow
Estimate and quote
The senior person it eats
The estimator, the owner, the lead PM
A drawing, a render, a photo, a site walk, or an RFQ email has to become a priced list of materials and labor, using what things really cost this business, fast enough to win. It lives in one senior person's head and a spreadsheet. Two quotes for similar work drift, and the fastest quote usually wins.
Still spreadsheets, phones, and memory
Anything quoted from renders, photos, site visits, or RFQ emails: fabrication, signage, millwork, stone, events, catering, restoration, commercial remodel.
What we build
Any input in, a structured component list out, your people confirm the parts and dimensions, rules classify materials and methods with a model on the remainder, a deterministic take-off with waste factors, a price from your own cost memory with a reason on every line, labor and margin, the review gate, a frozen estimate, a purchase list by vendor. Every correction logged. The cost memory gets smarter with every invoice.
What you can buy, and where it stops
Plan-set takeoff tools read construction drawings. CAD quoting tools read part files. Field-service platforms quote from a price book. None reads a marketing render, a site photo, or an RFQ email for assembled or fabricated work, and none carries your own cost history with a reason on each number. If you quote from plan sets or CAD, the incumbents are good and we read their output rather than replace them.
02 / Workflow
Schedule and track
The senior person it eats
The production manager, the ops lead, the dispatcher
Who does what when, across departments or crews, held against the plan every day. The quote already knows the planned hours by department. Nothing turns that into a daily plan and a variance, so the day runs on a whiteboard and a walk around the floor.
Still spreadsheets, phones, and memory
Planned versus actual by department per day for multi-day custom jobs: fabrication, scenic, remodel, landscape installation, events.
What we build
Work orders with departmental or crew lanes, planned hours from the estimate, a daily planned-versus-actual per lane, a wall tablet or phone check-in, task lists from the line items that your people edit, routing rules on the same engine that prices the job, and a nightly digest.
What you can buy, and where it stops
Dispatch for route-based trades is solved. Shop and project management tools track order status or cards on a board. None derives a daily plan from the estimate that priced the job, and buying one means a second system of record and two quotes to reconcile.
03 / Workflow
Capture into the record
The senior person it eats
Everyone who says "I'll remember"
Commitments made on the phone, in a meeting, or on site never reach the job. Photos live on phones. Documents live in email. A missed dimension becomes a change order; a forgotten promise becomes a lost client.
Still spreadsheets, phones, and memory
Turning any channel into commitments, tasks, and notes on the right job.
What we build
We wire in the phone system and the meeting notetaker you already have. The model extracts commitments, quantities, dates, decisions, and open questions and files them on the job with a link to the transcript, behind a review step. Photos land in job folders from a phone upload page and get tagged. A spoken consent disclosure is the default.
What you can buy, and where it stops
Transcription, notetakers, and photo apps are cheap and good, and we buy them. All of them produce a transcript and a generic summary. None attaches the commitment to the right job in your own system, because none has your job record.
04 / Workflow
Produce documents
The senior person it eats
The person who assembles them by hand
The polished quote, proposal, purchase order, SOW, invoice, or report is assembled by hand into a template, re-keying numbers that already exist somewhere else. Then the numbers disagree.
Still spreadsheets, phones, and memory
POs, SOWs, reports, and proposals in your own templates, without re-keying.
What we build
Your own template, filled from the job record: figures traced to their source, renders and photos swapped in, a PDF out, every document frozen and versioned with the estimate it came from. You keep your template and your Drive.
What you can buy, and where it stops
Proposal and e-sign tools are a second place to type the numbers. The gap is the same as everywhere: the numbers live in the system of record, and the document should be a projection of it.
05 / Workflow
Follow up and sell
The senior person it eats
The owner, who is also the salesperson
Follow-ups are manual, generic, and lost in a flood of AI-written outreach. Repeat and referral work is the cheapest lead source most businesses have, and it runs from memory.
Still spreadsheets, phones, and memory
Trigger-based follow-up from job events; portfolio and case studies from completed work.
What we build
Triggers from your job data (a quote silent for five days, a client's annual event 120 days out, a job closed with photos approved) draft a specific touch with the right asset attached. You approve every send. Tracking stays in the CRM you already have. Completed jobs become portfolio pages and content briefs.
What you can buy, and where it stops
Your CRM is the right system of record for contacts and we wire it in. Volume email tools are the wrong purchase, and the reply rates say so. Reputation and marketing platforms are good at what they do, and none of them knows what you shipped last week.
Next in the catalog
Intake and lead handling
It sits in front of estimating: an inbound call, form, or email becomes a qualified request with the inputs the estimator needs (site, scope, photos, deadline, budget signal), or a polite decline. For trades it is the biggest leak. AI receptionists stop at the transcript.
How a workflow enters the catalog
A paying client's Blueprint ranks it high enough to build, and it passes one test: the input is unstructured, and the tools you can buy for it want structured input. The build leaves a module behind, so the second client gets a module rather than a project. A finance close, a reorder decision on noisy supplier signals, a research desk: same test.
Start here
What eats your senior people's time every week?
Thirty minutes, free, not a pitch. Bring the workflow that costs you the most and we will put a rough number on it before the call ends.