
Project Management
One hub per job ties estimates, proposals, work orders, schedule, invoices, and job costing together — with punch lists, change orders, photos, and stage-triggered automations.
14-day free trial — no credit card required
One job record
Estimate → proposal → work orders → schedule → invoices → costing
Stage-triggered
Automations create tasks and send notifications when stages change
Two portals
Clients and vendors see their own view — fewer status phone calls
See it in action
Stage and sub-stage at the top, the document chain and schedule in the middle, punch list and activity on the side — one screen answers 'where is this project?'
Hendricks — Kitchen Remodel
Production · Rough-inJob documents
Contract + COs
$51,890
Billed to date
$34,125
Job cost so far
$21,407
Punch list · 2 of 4 done
Activity
Automation created 3 tasks on stage change
Maria G. uploaded 12 photos → Rough-in album
Client signed Change Order #2
The whole job lifecycle
Every pain below comes from contractors running jobs across disconnected tools. Each maps to a specific Breche feature.
The pain
The estimate is in one app, the schedule in another, the invoice in a third — and none of them agree.
What Breche does
Every Breche project is a single hub. The estimate becomes the proposal, the approved proposal drives work orders and the schedule, invoices pull from the approved scope, and job costing reads actuals from all of it. One record, one chain of custody from first bid to final payment.
The pain
"Where is this job, really?" takes three phone calls to answer.
What Breche does
Pipeline stages — and sub-stages within them — show exactly where every project sits, from lead through production to closeout. View the pipeline as a kanban board or a list, drag projects between stages, and let stage changes trigger the next steps automatically.
The pain
Punch list items live on a legal pad in the truck.
What Breche does
Tasks and punch lists attach directly to the project. Assign items to a team member, check them off as the work completes, and walk the final punch list from a phone at the job site instead of transcribing a paper list back at the office.
The pain
Finding the signed contract — or the pre-demo photo — means digging through email.
What Breche does
Every project carries its own documents and photos, organized in folders and albums. Signed PDFs file themselves automatically, crews upload progress photos from the field, and the album is there when a dispute or warranty question surfaces a year later.
The pain
Change orders happen on a handshake and vanish from the numbers.
What Breche does
Change orders run through the same e-signature approval flow as the original estimate, then extend the contract value automatically. Job costing and invoicing both see the new number — no side spreadsheet reconciling what the job "really" sold for.
The pain
Repetitive admin work eats the hours the software was supposed to save.
What Breche does
The automations engine fires actions off stage changes: move a project to a stage and Breche can create tasks, send notifications, or advance the workflow for you. Meanwhile the activity history logs who did what and when, and client + vendor portals answer status questions before they become phone calls.
Features
Estimates flow into proposals, work orders, the schedule, and per-line invoices — each document links back to the one it came from.
Track every project through your stages, with sub-stages for finer-grained status. Kanban board and list views, drag-and-drop between stages.
Assignable tasks and job-site punch lists live on the project. Check items off from the field and see completion at a glance.
Same e-signature flow as the original estimate. Approved change orders extend the contract value, and costing + invoicing pick it up automatically.
Contracts, permits, signed PDFs, and vendor docs organized in per-project folders — with signed documents filed automatically.
Progress photos organized by album per project. Crews upload from the field; the office and the client portal see them organized, not as text attachments.
Stage-triggered actions: when a project hits a stage, Breche creates tasks, sends notifications, or advances the workflow — no manual follow-through.
Every meaningful change on the project is logged — who moved the stage, who sent the proposal, who edited the invoice — for a clean audit trail.
FAQ
Common questions about running jobs in Breche.