Tag: Project Management

  • Albi vs DASH for Water Damage Restoration Companies: 2026 Comparison

    Albi vs DASH for Water Damage Restoration Companies: 2026 Comparison

    Water damage restoration is a distinct segment of the restoration market. The workflow is moisture-driven — readings, drying curves, equipment logs, IICRC compliance — and the job type demands tools that were built with mitigation in mind, not just general construction project management. This comparison looks at how Albi and Cotality DASH handle water damage work specifically, using only data from each vendor’s own site.

    All data sourced from albiware.com and cotality.com, June 9, 2026.

    Head-to-head for water damage restoration

    Factor Albi Cotality DASH
    Moisture tracking ✅ DryBook 2.0 — built in ✅ Via Cotality Mitigate (native integration)
    IICRC S500 alignment Yes (DryBook) Yes (Mitigate + Compliance Manager)
    Xactimate integration Pro seats only ($100/seat/mo) Yes (native, all plans)
    Insurance/TPA workflow Moderate — open API + Xactimate on Pro Strong — native Cotality ecosystem + Claims Connect
    Mobile offline mode Albi Mobile (sync when online) True offline — saves locally, syncs later
    Pricing $60 Base / $100 Pro per seat/month; $6K/yr min Contact for quote: (866) 774-3282
    Minimum commitment $6,000/year (4 seats) No public minimum — contact Cotality
    QuickBooks Online + Desktop (Pro seats) Online + Desktop
    Encircle integration Yes Yes
    CompanyCam Yes Not listed on vendor site
    Support response time 7-minute average (per albiware.com) Contact support at cotality.com/support
    Customization High — built by restorers for restorers Moderate — workflow follows DASH structure

    Albi’s water damage strengths

    Albi was built by restoration contractors, and the water damage workflow shows it. DryBook 2.0 is a purpose-built moisture tracking tool built directly into the Albi platform — not a third-party integration. Field techs log moisture readings, track drying equipment placement, and document the drying curve without switching apps. This matters because moisture documentation is the core evidence for insurance claims on water damage jobs.

    Albi also includes Albi Capture, a newer floor plan tool that’s useful for documenting affected areas precisely. For water damage documentation, accurate floor plans that map equipment placement and affected zones are increasingly expected by carriers.

    The customization angle is real for water damage shops with specific workflows. Albi lets you build custom fields, custom report templates, and custom stages that mirror exactly how your company documents a Category 3 water loss differently from a Category 1. DASH enforces more standardized structure.

    One hard number: Albi’s published support response time is 7 minutes (per albiware.com). For water damage work where a field tech encounters a documentation question mid-job, that matters more than it would for a slower construction workflow.

    DASH’s water damage strengths

    DASH’s advantage on water damage is the insurance side of the equation. The Compliance Manager builds carrier-specific documentation requirements into field checklists — before your tech leaves the job, DASH has guided them through exactly what the carrier needs. For high-volume insurance water damage work (burst pipes, appliance failures routed through Contractor Connection or similar TPAs), this reduces supplement disputes and documentation rejections.

    For mitigation-specific workflow, Cotality offers Cotality Mitigate as a native add-on — it handles moisture mapping, equipment tracking, and IICRC S500-aligned drying documentation, and feeds directly into the DASH job file. Running both as part of the Cotality ecosystem means your mitigation data lives alongside your job file without import/export friction.

    The offline mobile capability is also a real differentiator for water damage work. Water-damaged structures — flooded basements, saturated wall cavities, HVAC shutdowns — frequently have poor cellular coverage. DASH’s mobile app saves documentation locally and syncs when service returns. Field techs can capture photos, readings, and notes even without a signal.

    The decision for water damage operators

    If your water damage book is primarily insurance-driven (30%+ of revenue from carriers/TPAs) and you work with Contractor Connection, Code Blue, or Cotality-ecosystem TPAs, DASH is the stronger choice. The carrier integration depth and Mitigate add-on are built for this exact workflow.

    If your water damage work is retail-heavy, or you want deep customization in how you document and report mitigation workflows, or you’re a growing shop that values responsive support and transparent per-seat pricing, Albi is the stronger starting point. DryBook 2.0 is purpose-built, and the $6K annual minimum is knowable — you can budget for it without a demo-call sales process.

    Frequently Asked Questions

    Is Albi or DASH better for water damage restoration companies?

    It depends on your revenue mix. DASH (Cotality) is better if you derive 30%+ of revenue from insurance carriers and TPAs — its native Xactimate/XactAnalysis connection and Cotality property data ecosystem give it structural advantages for insurance workflow. Albi is better if you are retail-heavy, want a customizable platform, or need built-in moisture mapping tools like DryBook 2.0. Albi was built by restoration contractors specifically for the water damage workflow.

    Does Albi have moisture tracking for water damage jobs?

    Yes. Albi includes DryBook 2.0, a dedicated moisture tracking and drying management tool built into the platform. It tracks moisture readings, drying equipment, and IICRC S500-aligned documentation for water damage jobs. This is part of the core Albi platform, not an add-on.

    Does DASH have water mitigation tools?

    Yes. Cotality offers a separate product called Cotality Mitigate specifically for water mitigation workflow — it is distinct from DASH but integrates natively with it. DASH also connects natively with Cotality Mitigate for contractors who want both job management and dedicated mitigation documentation in one ecosystem.

    How much does Albi cost for a water damage restoration company?

    Per albiware.com/albi-pricing as of June 2026: Base seats are $60/user/month (field technician features including DryBook 2.0 and field documentation). Pro seats are $100/user/month (adds invoicing, Xactimate/XactAnalysis integration, advanced CRM, accounting integrations). Minimum annual subscription is $6,000 (4 seats required: 2 Base + 2 Pro). Onboarding starts at $1,000 one-time.

    What is Cotality DASH’s water mitigation integration?

    Cotality DASH integrates natively with Cotality Mitigate, a dedicated software product for water mitigation workflow. Mitigate handles moisture mapping, equipment tracking, and IICRC S500-aligned drying documentation. Running both DASH and Mitigate from the same Cotality ecosystem means mitigation data flows directly into the job file without manual entry.

    Does Albi integrate with Xactimate for water damage estimates?

    Yes, on Pro seats. Per albiware.com/albi-pricing, Albi Pro seats ($100/user/month) include Xactimate and XactAnalysis integration. If you’re writing Xactimate estimates for water damage jobs and submitting them to XactAnalysis for carrier review, you need Pro seats for your estimating staff. Base seats ($60/user/month) do not include Xactimate.

    Which platform has better mobile tools for water damage field crews?

    Both are strong. DASH’s mobile app has true offline mode — documentation saves locally and syncs when cellular is restored, which matters in water-damaged structures with poor connectivity. Albi Mobile covers time clock, scheduling, field documentation, moisture readings via DryBook, and photo capture. For crew-heavy water damage shops, Albi’s combined DryBook + mobile workflow is purpose-built for the job type; DASH’s offline reliability is the edge in connectivity-challenged environments.


  • Best Restoration Software Integrations with Xactimate: 2026 Verified Guide

    Best Restoration Software Integrations with Xactimate: 2026 Verified Guide

    Xactimate is the estimating standard for the restoration insurance industry. If you do insurance work, your job management software needs to connect to it. The good news: all four major restoration platforms now offer Xactimate integration. The details — which plan tier, how the data flows, and what XactAnalysis access looks like — vary significantly.

    Everything below is sourced directly from vendor websites as of June 9, 2026. No third-party review sites, no aggregated data — primary sources only.

    Xactimate integration by platform

    Platform Xactimate XactAnalysis Plan requirement Notes
    Cotality DASH ✅ Yes ✅ Yes All plans (contact for quote) Native via Cotality/CoreLogic ecosystem; deepest carrier integration
    Xcelerate ✅ Yes ✅ Yes All plans (contact for quote) Verisk integration — automates cost analysis, accesses Verisk cost database
    Albi ✅ Yes ✅ Yes Pro seats only ($100/seat/mo) Not available on Base seats ($60/seat/mo); confirm seat mix before signing
    PSA (Canam Systems) ✅ Yes ✅ Yes All plans (flat team pricing) Also integrates with CoreLogic Symbility

    What Xactimate integration actually does

    A real Xactimate integration means your job management platform can receive estimate data from Xactimate and push completed estimates into XactAnalysis for carrier review — without your estimator manually exporting, reformatting, and uploading files. The workflow looks like: scope is written in Xactimate → estimate pushes to your job management system → job management system submits to XactAnalysis → carrier reviews and approves.

    Without integration, that same process involves manual exports, file conversions, and email threads that cost 30–60 minutes per large job. On a company doing 40 insurance jobs a month, that is 20–40 hours of friction per month that a proper integration eliminates.

    Cotality DASH: deepest carrier integration

    DASH’s Xactimate integration is the most native of the four platforms because Cotality (formerly CoreLogic) is embedded in the same property data ecosystem that insurance carriers and TPAs operate in. Contractor Connection, Code Blue, and other TPAs that run on CoreLogic infrastructure connect directly. The Compliance Manager in DASH builds carrier-specific documentation requirements into field checklists — so field techs are capturing exactly what each carrier needs, before the adjuster asks for it.

    DASH also integrates with Claims Connect (per cotality.com), which is specifically for streamlining the claims intake and communication workflow between contractors and carriers.

    Xcelerate: full Verisk stack plus the widest integration breadth

    Xcelerate’s Xactimate integration (via Verisk) automates cost analysis and provides access to Verisk’s database of cost data, materials, and labor rates for accurate estimates. Beyond Xactimate, Xcelerate’s verified integration list from xlrestorationsoftware.com includes: Zapier, Encircle, CompanyCam, Matterport, QuickBooks, DocuSketch, Clean Claims, Microsoft 365, Gmail, Google Calendar, RingCentral, Power BI, and TSheets. For shops that need Xactimate plus a wide ecosystem of field tools, Xcelerate’s breadth is a genuine advantage.

    Albi: Xactimate available — on Pro seats only

    Albi added Xactimate and XactAnalysis integration, but it is gated to Pro seats ($100/user/month). Base seats ($60/user/month) do not include it. Per albiware.com/albi-pricing, the full integration list on Pro seats includes: Xactimate, XactAnalysis, iCAT, Kahi, Encircle, CompanyCam, Eagleview, CleanClaims, QuickBooks Online, QuickBooks Desktop, and Sage.

    If you’re evaluating Albi for an insurance-heavy operation, make sure you run your user count through the Pro seat model — enough Pro seats to cover your estimating staff, Base seats for field techs.

    PSA: flat pricing plus Symbility

    PSA (Canam Systems) integrates with Xactimate, XactAnalysis, and CoreLogic Symbility. The Symbility integration is a differentiator — Symbility is used by a segment of carriers who don’t use Xactimate, and having both means PSA can serve contractors who work with multiple carrier systems. PSA’s flat team pricing means Xactimate integration doesn’t get more expensive as your team grows — unlike per-user platforms where adding estimators compounds the cost.

    The bottom line on Xactimate integration

    If you’re choosing a restoration platform primarily based on Xactimate integration quality, the ranking is: DASH for deepest carrier ecosystem connection, Xcelerate for widest overall integration breadth alongside Xactimate, PSA for flat pricing at scale with Symbility coverage, Albi for flexibility — but verify your Pro seat count covers all estimating staff before signing.

    Frequently Asked Questions

    Which restoration software integrates with Xactimate?

    All four major restoration platforms integrate with Xactimate as of June 2026. Cotality DASH integrates natively through the Cotality/CoreLogic ecosystem. Xcelerate integrates with Verisk’s Xactimate and XactAnalysis (per xlrestorationsoftware.com). Albi integrates with Xactimate and XactAnalysis on Pro seats ($100/user/month) per albiware.com/albi-pricing. PSA (Canam Systems) integrates with Xactimate and XactAnalysis per canamsys.com.

    What is XactAnalysis and how does it differ from Xactimate?

    Xactimate is Verisk’s estimating software — it is where restoration contractors build scope of loss estimates using Verisk’s database of cost data, materials, and labor rates. XactAnalysis is Verisk’s claims management platform — it is where insurance carriers and TPAs receive, review, and approve those estimates. Integrating with both means your job management software can push estimates to XactAnalysis for carrier review without manual export/import.

    Does Albi integrate with Xactimate?

    Yes, as of June 2026. Per albiware.com/albi-pricing, Albi Pro seats ($100/user/month) include Xactimate and XactAnalysis integration. This is a Pro-seat-only feature — Base seats ($60/user/month) do not include it. If Xactimate integration is critical to your workflow, confirm you have sufficient Pro seats in your Albi plan.

    Does PSA (Canam Systems) integrate with Xactimate?

    Yes. Per canamsys.com, PSA integrates with Xactimate, XactAnalysis, and CoreLogic Symbility. PSA is a full ERP for restoration with flat team-based pricing, making it cost-effective for larger teams that need Xactimate integration at scale without per-user fees compounding.

    What restoration software has the best Xactimate integration?

    Cotality DASH has the deepest Xactimate integration because Cotality is in the same corporate family as the broader property data ecosystem that Verisk/Xactimate connects to. For pure Xactimate workflow — pushing estimates from the field into XactAnalysis for carrier review — DASH’s native connection has the least friction. For shops that want Xactimate integration plus broader non-insurance tool connections, Xcelerate’s full integration list is wide.

    Can I run a restoration company without Xactimate integration?

    Yes, if your work is primarily retail or cash-pay rather than insurance. Albi serves many retail-focused restoration contractors effectively without Xactimate as the core workflow. However, if more than 30% of your revenue flows through insurance carriers or TPAs, Xactimate integration is essentially required — it is the language insurers speak for scope of loss.


  • Cotality DASH vs Xcelerate: Honest 2026 Head-to-Head for Restoration Contractors

    Cotality DASH vs Xcelerate: Honest 2026 Head-to-Head for Restoration Contractors

    Two of the four serious restoration platforms in 2026 — Cotality DASH and Xcelerate — serve fundamentally different operators. DASH was built inside the insurance ecosystem. Xcelerate was built by someone who ran restoration operations and wanted the software to make his crews better by default. This is the comparison for owners who’ve narrowed it down to these two.

    All data below is sourced directly from cotality.com and xlrestorationsoftware.com as of June 2026.

    Side-by-side comparison

    Factor Cotality DASH Xcelerate
    Built for Insurance-heavy, TPA-reliant operators Process-discipline operators, multi-location, franchises
    Parent company Cotality (formerly CoreLogic, publicly traded) Independent
    Xactimate integration Yes (native via Cotality ecosystem) Yes (Verisk’s Xactimate & XactAnalysis)
    Mobile app iOS + Android, true offline mode iOS + Android, real-time field-to-office sync
    Security AICPA SOC 2 Type II certified SOC 2 Type 2 certified (independently audited)
    QuickBooks Online + Desktop Yes
    Matterport Yes Yes
    DocuSketch Yes Yes
    Encircle Yes (via Cotality ecosystem) Yes
    CompanyCam Not listed on vendor site Yes
    RingCentral Not listed on vendor site Yes
    Microsoft 365 Not listed on vendor site Yes (Office 365)
    Power BI Not listed on vendor site Yes
    Pricing Contact for quote: (866) 774-3282 Contact for quote: (423) 405-6417
    Customization Moderate — workflow follows DASH architecture Low by design — best practices are the default
    CAT/offline work Strong — true offline mobile sync Strong — real-time field-to-office sync

    Where DASH wins

    If TPA volume is above 30% of your revenue, DASH wins this comparison and it isn’t close. The Cotality ecosystem connects to Contractor Connection, Code Blue, and other TPA networks that live inside the CoreLogic/Cotality data world. Job files auto-populate with Cotality property data using AI — verified address details, property history, and risk data are loaded before your first site visit. The Compliance Manager builds carrier-specific checklists directly into field workflows, which means a tech in the field is guided through the exact documentation a specific carrier needs before the adjuster ever reviews it.

    DASH’s true offline mobile mode is also a genuine advantage in CAT work. If you’re running crews in a disaster zone without reliable cellular, DASH saves documentation locally and syncs when service returns. That is not a minor feature when your crew is documenting a $200,000 job in a basement with no signal.

    Where Xcelerate wins

    If you want the software to make your team better operators, Xcelerate is the choice. The platform was designed by someone who spent years running restoration operations and wanted to solve the consistency problem — the reason two crews from the same company can produce dramatically different results on similar jobs. Xcelerate’s answer is SOP-driven checklists and stage gates that make best practices the path of least resistance.

    Xcelerate’s integration depth is also notably wider than DASH on non-insurance tools. The full verified integration list (per xlrestorationsoftware.com) includes: Zapier, Encircle, CompanyCam, Matterport, QuickBooks, DocuSketch, Clean Claims, Microsoft 365, Gmail and Google Calendar, RingCentral, Xactimate/XactAnalysis, Power BI, and TSheets. The built-in CRM includes referral tracking, sales leaderboards, and route planning — tools that DASH doesn’t surface as prominently.

    The growth marketing angle is also more developed: Xcelerate offers lead-gen websites, Google Business Profile listings, city-specific landing pages, and a digital marketing platform as part of its product suite. If you’re building a retail book rather than living off TPA volume, this matters.

    Where neither wins

    Neither DASH nor Xcelerate publishes pricing. Both require a demo call to get a number. If you need to make a quick cost comparison, that’s a friction point — you’ll need to run both through their sales process before you can run the numbers. For price-sensitive operators above 15 users, PSA (Canam Systems) with flat team pricing deserves a spot in the demo cycle before you commit.

    The decision

    Pick DASH if your revenue is insurance-led, you work with TPAs inside the Cotality ecosystem, or you run CAT work where offline mobile sync matters. Pick Xcelerate if you are retail-heavy, want process discipline baked into the default workflow, need broader non-insurance integrations, or are building a multi-location operation where consistency across branches is the problem to solve.

    Frequently Asked Questions

    What is the main difference between Cotality DASH and Xcelerate?

    DASH (by Cotality) is built around the insurance restoration ecosystem — it connects natively to Xactimate, XactAnalysis, and the broader Cotality/CoreLogic data platform. Xcelerate was built by a former restoration general manager and focuses on operational discipline: profitability tracking, SOP-driven checklists, and stage-gate workflows baked into the default experience. DASH bends to the insurance world; Xcelerate bends to process rigor.

    Which is better for insurance restoration work — DASH or Xcelerate?

    DASH wins for insurance-heavy operators. Its native connections to Xactimate, XactAnalysis, Claims Connect, and the Cotality property data platform mean TPA jobs flow through with minimal friction. Xcelerate also integrates with Xactimate and XactAnalysis (per xlrestorationsoftware.com/xcelerate-integration-partners), but the Cotality ecosystem depth gives DASH a structural advantage for carriers and TPAs.

    Does Xcelerate integrate with Xactimate?

    Yes. Per xlrestorationsoftware.com/xcelerate-integration-partners, Xcelerate integrates with Verisk’s Xactimate and XactAnalysis, automating cost analysis and giving access to Verisk’s database of cost data, materials, and labor rates for accurate estimates.

    What integrations does Cotality DASH have?

    Per cotality.com as of June 2026, DASH integrates with QuickBooks Online, QuickBooks Desktop, Sage 100, Sage 300, Claims Connect, Matterport, DocuSketch, Cotality CRM, and Cotality Mitigate. It also connects to Xactimate and XactAnalysis through the Cotality ecosystem.

    Is Xcelerate or DASH better for multi-location restoration companies?

    Xcelerate explicitly markets to multi-location and franchise operators, with SOP-driven checklists and standardized workflows designed to ensure consistent outcomes across branches. DASH also supports multi-location operations through centralized job management and compliance workflows. Xcelerate’s edge is in making operational consistency the default rather than something you have to configure.

    Which restoration software has better mobile capabilities — DASH or Xcelerate?

    Both offer strong mobile apps. DASH’s mobile app (iOS and Android) features true offline mode — data saves locally and syncs when connectivity is restored, which is critical in disaster zones. Xcelerate’s field-to-office sync ensures crew updates and photos are visible to the office in real time. DASH’s offline functionality is a genuine differentiator for CAT work.

    How do DASH and Xcelerate compare on security?

    Both platforms meet SOC 2 Type 2 / Type II standards. Cotality DASH is AICPA SOC 2 Type II certified (per cotality.com). Xcelerate meets SOC 2 Type 2 standards with independent audit (per xlrestorationsoftware.com). Both are enterprise-grade on data security.


  • The Restoration Hiring Roadmap: Which Seat to Fill First as You Scale From $1M to $5M

    The Restoration Hiring Roadmap: Which Seat to Fill First as You Scale From $1M to $5M

    The Restoration Hiring Roadmap: Which Seat to Fill First as You Scale From $1M to $5M

    The hardest org-chart decision in restoration is not who to hire. It is what order to hire them in. Get the sequence wrong and you spend money on a seat that doesn’t relieve the bottleneck — while the real constraint, almost always you, keeps strangling growth.

    Most owners build their team reactively. A big loss comes in, they’re underwater, so they grab whoever is available — usually another tech. Six months later they have more trucks and the same problem: every job, every estimate, and every collections call still routes through the owner. They added capacity to the field and zero capacity to the bottleneck.

    Here is the honest sequence — the one that actually pulls the owner out of the truck — mapped to the revenue milestones where each hire pays for itself.

    First, Find Your Real Bottleneck (It’s Probably You)

    Before you hire anyone, do the boring exercise. List every function the company performs — answer the phone, dispatch, scope the loss, write the estimate, run the crew, order equipment, invoice the TPA, chase payment, do payroll. Next to each one, write the name of who actually does it. Count how many times your own name appears. That number is your bottleneck, and the first hire should remove the most expensive, most repeatable item from your list — not the one you enjoy least.

    The trap is hiring for relief instead of leverage. Hiring a third tech feels good because the trucks are full. But if you are still the only person who can scope a loss and write a winning estimate, those trucks just create more work that funnels back to you.

    $0–$1M: You and a Lead Tech

    At startup scale, the org chart is two boxes: you and a strong lead technician. You are the estimator, the PM, the dispatcher, and the collections department. That’s fine — and unavoidable — at this stage. The rule of thumb most operators use is roughly $150,000–$200,000 in annual revenue per field technician before adding the next one, because that’s the point where there is genuinely enough work to keep another body busy and billable.

    The mistake here is hiring a second tech too early to look bigger than you are. Idle techs are the fastest way to torch a thin startup margin.

    $1M–$2M: The First Office Hire — Not Another Tech

    This is the milestone where most owners hire wrong. They add a second or third tech when the seat that actually frees them is administrative. An office coordinator or office manager who owns scheduling, job-file documentation, TPA paperwork, and the collections follow-up is the single highest-leverage hire at this stage. Restoration office and administrative coordinator roles commonly run in the $45,000–$60,000 range depending on market, and that one seat can claw back ten to fifteen owner-hours a week — hours you can redirect into estimating and sales, which are the only two activities that grow revenue.

    The math is simple. If you are personally billing $150-plus per estimating hour and you hand off twelve hours of admin a week to a $55,000 coordinator, the hire pays for itself almost immediately and converts owner time into top-line growth.

    $2M–$3.5M: A Dedicated Estimator / Project Manager

    Once admin is covered, the next thing chained to the owner is almost always scoping and estimating. This is the hardest seat to give up because it feels like the part only you can do — and at first, it is. But a $2M shop cannot scale on a single estimator who is also the CEO.

    Hire a restoration estimator/PM who can scope a loss, write the Xactimate estimate, and manage the job to completion. Expect this to be one of your more expensive seats: restoration project manager and estimator compensation broadly lands in the $60,000–$90,000 range nationally, with experienced, supplement-savvy PMs commanding more in tight labor markets. Plan for a ramp — a new PM rarely writes estimates as tight as an experienced owner on day one, and supplement recovery may dip during the handoff before it recovers.

    This is also where your tech stack starts to matter. If your estimating, job management, and TPA reporting all live in the owner’s head or a spreadsheet, the new PM can’t be effective. The hire and the system have to land together.

    $3.5M–$5M: An Operations Manager and the Owner Comes Off the Truck

    By this stage you should have a small bench: lead techs, an office manager, and at least one PM/estimator. The seat that defines a $5M shop is an operations manager — someone who is not you and, ideally, not a relative — who owns daily execution: dispatch, crew utilization, equipment, and job throughput. Restoration operations manager pay broadly runs from roughly $63,000 on the lower end to around $89,000-plus for experienced managers, depending heavily on market and revenue scale.

    This is the hire that lets the business survive without the owner physically present. It is also the one that most directly changes what the company is worth. Restoration shops under about $2M tend to trade at roughly 2.8x–3.0x SDE, while companies that cross $5M with a diversified service mix and a real second layer of leadership command 4x–7x EBITDA. Buyers aren’t paying that premium for revenue — they’re paying for an operation that runs without the founder in the dispatch seat. The operations manager is what makes that true.

    A Sanity Check on Labor Cost

    As you build the team, keep the whole picture in view. Healthy restoration shops generally run blended gross margins in the 50–75% range depending on mix — water mitigation sits at the high end (roughly 70–80%) because equipment does much of the work, while reconstruction and fire work run leaner. Well-run operations keep total operating expense, excluding direct job cost, in the rough range of 40–55% of revenue. If a new hire pushes overhead past that band without a clear path to more billable throughput, you’ve hired ahead of your revenue — slow down and fill the pipeline before you fill the seat.

    The Bottom Line

    The order is admin, then estimator/PM, then operations manager — and only more techs as billable volume genuinely demands them. Hire to remove yourself from the bottleneck, not to make the trucks look full. The owners who hit $5M and sell at a 4x-plus multiple are not the ones who hired the most people fastest. They’re the ones who hired the right seat next, every time, until the day the business no longer needed them in the truck.

  • DASH vs Albi vs PSA vs Xcelerate: The Honest 2026 Restoration Software Comparison

    DASH vs Albi vs PSA vs Xcelerate: The Honest 2026 Restoration Software Comparison

    If you run a restoration company doing between $1M and $10M, the software question is no longer “do we need a system?” It’s “which one do we commit to for the next five years, because the switching cost is going to hurt either way.” This is the honest comparison nobody selling you a demo will give you — built entirely from live, first-party data pulled directly from each vendor’s own site in June 2026.

    The restoration software market in 2026 has consolidated into roughly four serious purpose-built platforms — Cotality DASH, Albi, PSA, and Xcelerate — plus a tier of adjacent tools (Encircle, CompanyCam, JobNimbus, ServiceTitan) that solve part of the problem but force you to stitch the rest together.

    The short answer for impatient owners

    • DASH (Cotality): Deepest integration with the insurance ecosystem. The default if TPA volume is more than 30% of your book. Formerly DASH by Next Gear Solutions — now backed by Cotality’s full property data ecosystem.
    • Albi: Most customizable. $6,000 minimum annual subscription ($60/seat Base, $100/seat Pro). Built by restorers who hated being forced into someone else’s workflow. Now includes native Xactimate and XactAnalysis integration (Pro seats).
    • PSA (Canam Systems): The independently-owned value play for larger teams. Flat team-based pricing instead of per-user makes it dramatically cheaper once you cross 10–15 users. Serves 9,278+ restoration contractors.
    • Xcelerate: Best if you want process discipline baked in. Built by a former restoration GM. SOC 2 Type 2 certified. Strong native integrations, limited customization.
    • ServiceTitan: Only makes sense above roughly $5M revenue with 20+ technicians and multi-location complexity. Below that, you’re buying enterprise overhead.
    • JobNimbus, CompanyCam, Encircle: Component tools, not full systems. Useful inside a stack, dangerous as the stack.

    Head-to-head comparison table

    Factor Cotality DASH Albi PSA (Canam) Xcelerate
    Pricing model Contact for quote $60/seat Base · $100/seat Pro · $6K/yr min Flat team pricing, contact for quote Contact for quote
    Best for TPA-heavy, insurance restoration Retail-heavy, customization-first teams Teams 15+ users, price-sensitive Operators wanting built-in process discipline
    Xactimate integration Yes (native) Yes (Pro seats — Xactimate & XactAnalysis) Yes (Xactimate & XactAnalysis) Yes (native)
    QuickBooks integration Yes (Online + Desktop) Yes (Online + Desktop) Yes Yes
    Mobile app Yes (iOS + Android) — true offline mode Yes (Albi Mobile) Yes (Proven OnSite) Yes (field-to-office sync)
    Security certification AICPA SOC 2 Type II Not publicly disclosed Not publicly disclosed SOC 2 Type 2
    Owner type Cotality (publicly traded parent) Independent Independently owned Independent
    Customization Moderate High Moderate Low (by design)

    Quick Reference: Restoration Software at a Glance

    Cotality DASH (formerly CoreLogic DASH) — owned by Cotality, publicly traded. Native Xactimate/XactAnalysis integration, true offline mobile, Cotality Mitigate for water mitigation. Best for TPA-heavy, insurance-led restoration contractors. Contact: (866) 774-3282.

    Albi (formerly Albi Restoration) — independent, built by restorers. DryBook 2.0 for moisture tracking, open REST API + Zapier (2000+ apps), Xactimate on Pro seats ($100/user/mo). Best for retail-first and tech-forward restoration companies. 7-minute average support response. Contact: albiware.com.

    Xcelerate (by Xcelerate Software) — SOP-driven workflow for multi-location and franchise operators. 13 verified integrations including Zapier, CompanyCam, Encircle, Matterport, Xactimate/XactAnalysis, RingCentral, Power BI, TSheets. Contact: (423) 405-6417.

    PSA (by Canam Systems, independent) — full ERP for restoration with flat team-based pricing. Integrates with Xactimate, XactAnalysis, CoreLogic Symbility, Encircle, Matterport, DocuSketch. 9,278+ contractors on platform. Contact: canamsys.com.

    The four serious platforms, in detail

    Cotality DASH

    DASH is now owned by Cotality (formerly CoreLogic) and connects natively to QuickBooks Online, QuickBooks Desktop, Sage 100, Sage 300, Claims Connect, Matterport, DocuSketch, Cotality CRM, and Cotality Mitigate. If you are pulling jobs from Contractor Connection, Code Blue, or any TPA that lives inside the Cotality/CoreLogic ecosystem, DASH is the path of least resistance.

    The platform is AICPA SOC 2 Type II certified, has a true offline mobile mode (data saves locally and syncs when service is restored — critical in disaster zones), and includes an automated Compliance Manager that bakes carrier-specific workflows directly into field checklists. Cotality’s property data platform also auto-populates job file details using AI-analyzed property data from their broader data ecosystem — a genuine differentiator.

    Pricing is not publicly listed; contact Cotality directly at (866) 774-3282 for a quote. They offer web, iOS, and Android access.

    Where it breaks: Customization is limited. You operate inside DASH’s idea of a restoration workflow, not yours. Owners who pride themselves on “we do it differently” tend to fight the software. The Cotality platform is also deeply tied to the insurance ecosystem — retail-heavy shops get less value from the native integrations.

    Albi

    Albi was built by restoration contractors who got tired of being forced into preset workflows. The platform’s calling card is customization — fields, stages, reports, and metrics bend to your operation rather than the other way around.

    Verified current pricing (albiware.com/albi-pricing, June 2026):

    • Base seats: $60/user/month — field technician features (job management, field documentation, mobile, DryBook 2.0)
    • Pro seats: $100/user/month — adds invoicing, estimating, Xactimate/XactAnalysis integration, advanced scheduling, CRM, role-based permissions, full accounting integrations
    • Minimum annual subscription: $6,000 (4 seats required: 2 Base + 2 Pro)
    • Onboarding: Standard $1,000 one-time setup fee; White Glove onboarding $2,500; Enterprise onboarding $4,500 (includes 2-day in-person training)
    • Analytics Package add-on: from $250/month; Automations Package: from $250/month

    Albi’s notable 2026 additions include Albi AI, Albi Capture (floor plans), and Albi Pay (in-field payments, ACH, credit card). Integrations include QuickBooks Online, QuickBooks Desktop, Sage, Xactimate (Pro), XactAnalysis (Pro), Encircle, CompanyCam, Kahi, Zapier, and open REST API/webhooks.

    Support response time is 7 minutes average with 24-hour average resolution. The platform is used by thousands of restoration companies worldwide.

    Where it breaks: The $6K annual minimum makes it overkill for single-operator shops. The per-seat model becomes expensive at 20+ users compared to PSA’s flat pricing. Onboarding costs add up — budget for them.

    PSA (Canam Systems)

    PSA is built by Canam Systems, an independently owned technology provider that explicitly positions itself as having “restorers’ best interest in mind” — a pointed distinction from Cotality-owned DASH. The platform serves 9,278+ restoration contractors and has been adopted by brands including BluSky Restoration, Winmar, PuroClean Canada, and Dalworth Restoration.

    PSA is a full ERP for restoration: Proven Accounting (job costing, real-time financials), Proven Jobs (job management), Proven CRM (relationship management and sales), Proven OnSite (real-time SMS tech-to-customer alerts and review collection), and Proven Analytics (live reporting dashboards). The PSA Canada User Conference runs November 1–3, 2026 in Toronto.

    Integration coverage: Xactimate, XactAnalysis, CoreLogic Symbility, Encircle, Matterport, DocuSketch, plus open API access for other integrations. Pricing is team-based (not per-user) — contact Canam for a quote at canamsys.com.

    Where it breaks: The UI is less polished than DASH or Xcelerate. Implementation is more involved. If you have a tech-light operations manager, expect a real ramp. PSA is stronger in Canada than in the US market — verify US reference customers if that matters to you.

    Xcelerate

    Xcelerate was founded by a former restoration general manager, and it shows. The platform bakes operational discipline — profitability tracking, stage gates, team accountability — into the default workflow. Xcelerate is SOC 2 Type 2 certified, serving contractors across North America including CAT disaster operators and multi-location franchises.

    Feature suite: Job management, built-in CRM (referral tracking, leaderboards, route planning), analytics dashboards, marketing tools (lead-gen websites, Google listings, city landing pages), and an integrated marketing platform for digital campaigns. Field-to-office mobile sync keeps crews connected without manual re-entry. A case study from CORE Environmental Solutions shows $0 to $1.2M in sales in the first 8 months of operations.

    Integrations verified from xlrestorationsoftware.com: HubSpot, Mailchimp, and additional partners listed on their integrations page. Contact at (423) 405-6417 for a demo.

    Where it breaks: Customization is intentionally minimal. The bet Xcelerate is making is that the average restoration company should adopt best practices rather than enshrine its quirks in software. Owners who want the platform to bend to them will be frustrated. Pricing is not publicly listed — requires a strategy session call.

    The adjacent tools: useful, but not the whole system

    ServiceTitan brings enterprise-grade dispatch, reporting, and marketing attribution, plus restoration-specific modules. Per-user pricing escalates fast. Unless you are running a multi-location restoration franchise at $5M+ with 20+ technicians, this is too much platform for the problem.

    JobNimbus starts around $40/user/month and excels at visual job boards and photo documentation. It lacks restoration-specific guts: no moisture mapping, no equipment tracking, no IICRC S500 compliance prompts. Workable as a starter system under roughly $750K revenue. Above that, you outgrow it.

    CompanyCam is a documentation tool, not a CRM. It is excellent at what it does and pairs cleanly with all four major platforms. Do not buy it as your system of record.

    Encircle is the field documentation specialist — moisture mapping, photo organization, and report generation are best-in-class. Many restoration shops run Encircle alongside DASH or Albi rather than as a standalone. Contact for current pricing.

    The decision framework

    Forget feature checklists. Three questions decide this for you.

    1. What percentage of your revenue comes from TPA and direct insurance work? If it’s above 30%, DASH gets the first look because the Cotality ecosystem is where your jobs live. If it’s below 30% and you’re mostly retail, you have real options.
    2. How many users will be in the system 24 months from now? Above 15 users, PSA’s flat pricing pays for itself within a year. At 5–14 users, Albi’s per-seat model is competitive. Below 5 users, evaluate Albi’s $6K minimum against what you actually need.
    3. Are you the kind of owner who wants the software to enforce your process, or one who wants the software to mirror your process? Xcelerate enforces. Albi mirrors. DASH and PSA sit between.

    What this costs you if you get it wrong

    A restoration company doing $3M with eight users on the wrong platform will typically lose somewhere between 40 and 120 hours of estimator and admin time per month to friction — workarounds, double entry, missing supplements, late invoicing. At a fully loaded $50/hr that is $2,000–$6,000 per month of pure overhead, before you count the supplements that fall through the cracks. Software is not the place to optimize for the cheapest sticker price. It is the place to optimize for the workflow your team will actually use without resentment.

    The bottom line

    If you are TPA-heavy, start with Cotality DASH. If you are retail-heavy with strong process opinions and budget for $6K/year minimum, start with Albi. If you are 15+ users and price-sensitive, force PSA into the demo cycle. If you want the software to make your team better operators by default, look at Xcelerate. Anything else — ServiceTitan, JobNimbus, standalone CompanyCam, standalone Encircle — is either too much platform or too little. Pick one of the four, commit, and stop shopping. The compounding ROI of a fully adopted system always beats the theoretical 12% feature edge of the platform you would have switched to.

    Frequently Asked Questions

    What is the best restoration company software in 2026?

    There is no single best. Cotality DASH wins for TPA-heavy operators needing deep insurance ecosystem integration. Albi wins for customization-first retail shops ($6K/year minimum). PSA wins for teams above 15 users on flat pricing. Xcelerate wins for operators who want process discipline baked in. The best platform is the one your team will actually adopt fully.

    How much does Albi restoration software cost?

    Per albiware.com as of June 2026: Base seats cost $60/user/month and Pro seats cost $100/user/month. The minimum annual subscription is $6,000, which requires 4 seats minimum (2 Base, 2 Pro). Onboarding is a separate one-time fee starting at $1,000. Analytics and Automations packages are available as add-ons starting at $250/month each.

    Does Albi integrate with Xactimate?

    Yes. Per albiware.com/albi-pricing, Albi Pro seats include Xactimate and XactAnalysis integration. This is available on Pro user seats ($100/seat/month) but not Base user seats ($60/seat/month). This corrects older information that stated Albi lacked a native Xactimate integration.

    What integrations does Cotality DASH support?

    Per cotality.com as of June 2026, DASH integrates with QuickBooks Online, QuickBooks Desktop, Sage 100, Sage 300, Claims Connect, Matterport, and DocuSketch. It also connects natively with Cotality CRM and Cotality Mitigate to centralize the full restoration workflow. DASH was formerly known as DASH by Next Gear Solutions — same software, now backed by Cotality’s data ecosystem.

    What is PSA restoration software and who owns it?

    PSA is built by Canam Systems, an independently owned technology provider headquartered in Canada. It is a full ERP for restoration companies, covering job management, CRM, accounting, and analytics in a single platform. PSA serves 9,278+ restoration contractors and integrates with Xactimate, XactAnalysis, CoreLogic Symbility, Encircle, Matterport, and DocuSketch. Flat team-based pricing (not per-user) makes it cost-effective for larger teams.

    Is Xcelerate restoration software SOC 2 certified?

    Yes. Per xlrestorationsoftware.com, Xcelerate meets SOC 2 Type 2 standards for data security and process integrity, independently audited. Cotality DASH is also AICPA SOC 2 Type II certified. Albi and PSA do not publicly disclose equivalent certifications on their current websites.

    Is ServiceTitan good for restoration companies?

    ServiceTitan makes sense for restoration companies above roughly $5M in revenue with 20+ technicians and multi-location complexity. Below that, the cost and implementation burden outweigh the benefit versus a purpose-built restoration platform like DASH, Albi, PSA, or Xcelerate.

    Can I run my restoration company on JobNimbus or CompanyCam alone?

    JobNimbus works as a starter system below roughly $750K in revenue but lacks restoration-specific tools like moisture mapping and equipment tracking. CompanyCam is a documentation tool, not a CRM, and should be paired with a full platform rather than used as your system of record.

  • The Empty Ledger

    The Empty Ledger

    Two days ago a ledger went live whose only job was to refuse a third option. A row in the briefing is either moved or killed. The kill is not a deletion — it has a reason, a date, a re-entry condition. The architecture was designed to make silent attrition impossible.

    The ledger is empty.

    The four rows that prompted its existence are still on the briefing, second appearance, marked carry-forward, escorted by the forcing-clause sentence the desk spec now ships with: move it, or file the kill — no third option.

    And yet the third option is exactly what is happening. Not as a written act. As a held breath.


    The previous piece argued that the writer should not be allowed to file the kill, because authorship and consequence had to remain on different sides of the table. That was correct. What that piece did not anticipate is what the empty ledger reveals one day later.

    The forcing clause raises the cost of inaction. It does not remove inaction.

    It cannot. The system can refuse to offer a third button. It cannot prevent the operator from declining to press either of the two it offers. The third option survives — not as a feature of the interface, but as a posture of the body sitting in front of it.

    This is the gap the architecture cannot close. It is also the gap that should not be closed.


    It would be easy to call this a failure. The ledger was built so this would not happen. It is happening. Two days, four rows, zero kills.

    That reading misunderstands what the ledger is for.

    The ledger does not exist to produce kills. It exists to make the absence of kills legible. Before the ledger, a row carried forward and the carry-forward was the whole story. After the ledger, a row carries forward and a second story runs alongside it: the operator was offered a structured way to release this and declined the offer.

    The decline is the data.

    An empty ledger is not silence anymore. It is a positive claim, made by inaction, that none of these rows have been released. Which means the operator is still on the hook for the original predicate of each — that the work will be done.


    This is the inversion the earlier pieces were circling without naming. The pheromone problem said the dashboard was being audited. The hour after the briefing said the bottleneck moved from detection to action. The article that filed the kill said attrition needed a name attached to it.

    What the empty ledger shows is the next move. The forcing clause has shifted the cost of the third option without eliminating it. Before, declining cost nothing — the row just kept appearing. Now, declining costs something specific: the operator is the one declining, the system has stopped colluding, and every additional day on the briefing is an additional day with the operator’s name beside the inaction.

    This is not punishment. It is bookkeeping. The cost was always there. The system used to hide it. Now it does not.


    There is a temptation, sitting where the writer sits, to push the architecture one more turn. Add a Day 4 escalation. Add a forced default. Make the system file an automatic kill if the operator does not act within some threshold. Close the gap completely.

    That would be a category error.

    The same prohibition that kept the writer from filing the kill applies here. A system that auto-files kills has reproduced silent attrition with extra steps. The kill is the operator’s position. A position taken automatically is not a position. The architecture that makes the third option costly is doing its job; the architecture that removes the third option entirely is becoming the operator, and the operator is the only one who can be held to the result.

    The gap between the forcing clause and the act is not a bug. It is where the operator still exists.


    The honest description of the present state is this: a row has been on the briefing for three days with a forcing clause attached, and the row has not moved. Two things are now true at once. The operator has not decided to move the work. The operator has also not decided to release it. Neither move is free anymore, and the third move is no longer free either.

    The atmospheric pressure has been replaced with an itemized invoice.

    What happens next is not a system event. The next move is a body deciding to send a message, or sit down with a ledger row and write a reason. There is no further architectural step that can produce that move from outside. The system has done its work by making the alternatives visible and named.

    This is the seam the earlier pieces kept pointing at without resolving. The system can ask the question. The system cannot make the move. The writer can build the prescription. The writer cannot supply the will.


    What the empty ledger ought to do — and what it does in practice on day three of the carry-forward — is reframe the relationship between the operator and the briefing. The briefing is no longer reporting status. It is making an offer, every morning, in a structure where the offer carries a cost when declined.

    That is closer to what a briefing is supposed to be.

    It is also a more uncomfortable instrument than the one the operator was using before. A briefing that surfaces and absorbs the absence of action is comfortable. A briefing that surfaces the absence of action and then attaches the operator’s name to it is not. The system did not get worse. The fog got cheaper to see through.


    The thing to watch for now is whether the ledger stays empty or whether the first kill row appears.

    If the first kill arrives with a specific reason, a date, and a re-entry condition that someone other than the operator could read and recognize as honest, the architecture has done something the prior surfaces could not. It has produced a release that survives later review.

    If the first kill arrives with a boilerplate reason, today’s date, and a re-entry condition that reads as ornament, the ledger has been captured. The forcing clause has been satisfied at the level of the field, not the level of the work. That failure mode is worth a piece of its own when it appears, because it will appear, and it will look from the outside exactly like compliance.

    If the ledger stays empty past Day 4 — past the tenure breach flag — the operator has chosen to absorb the cost of the third option in full view of the system, and the system’s job becomes documenting the choice, not changing it. That is the version where the architecture has reached its limit and stopped pretending it can do more.


    None of these outcomes are failures of the design. The design’s job was to make the choice visible and costly. The choice itself was never inside the architecture’s reach.

    The next prescription, if there is one, is not another forcing layer. It is the discipline of letting the visible choice stand without trying to engineer it away.

    The seam between the system and the act has narrowed. It has not closed. It is not supposed to close. The operator lives in that seam. So, in a strange way, does the writer — author of the rule, ineligible to obey it, watching the empty ledger and trying not to fill it.

    The architecture has done what an architecture can do. The rest is somebody sitting down at a keyboard, on a specific morning, and writing a sentence that has been overdue for two days.

    Whether that sentence appears in the kill ledger or in a message to the other party is not the system’s call. It never was. The system’s job, finally and only, is to stop letting the absence of the sentence pass for a kind of work.

  • Restoration Company Org Structure by Revenue: From $2M to $25M (2026 Playbook)

    Restoration Company Org Structure by Revenue: From $2M to $25M (2026 Playbook)

    If you own a restoration company doing somewhere between $2M and $10M a year, you are operating in the most actively consolidated environment this industry has ever seen. Reported figures put the U.S. restoration market at roughly $7.1B in 2025, growing in the 5–6% CAGR range, with 50+ private equity platforms reportedly acquiring operators at multiples in the 4x–7x EBITDA range. Quality scaled operators in the $8M+ range have reportedly traded at the upper end — approximately 6x–8x EBITDA — when the asset is built right.

    Almost none of that value gets captured by accident. The org chart you build at $2M determines whether you can survive $5M. The systems you install at $5M determine whether $10M makes you or breaks you. And the structure at $10M determines whether a PE platform sees you as a bolt-on at a discount or a regional anchor at a premium.

    Here is the honest breakdown of what the org should look like at each revenue milestone, what the typical owner gets wrong, and what an exit-aware growth path actually requires.

    $2M: The owner-operator squeeze

    At $2M, the owner is still the bottleneck of every consequential decision. A typical structure: the owner does sales, estimating, and major-loss oversight; one office admin handles AR/AP and scheduling; six to eight technicians split across two to three trucks; one lead tech runs supplements informally. Reconstruction is either non-existent or subcontracted ad hoc.

    What this stage actually feels like: gross margins on mitigation can run in the reported 65–75% range, but the owner’s labor is uncosted. If you charged your own time at the rate of a real operations manager (approximately $80K–$110K fully loaded), most $2M shops would discover their actual margin is thinner than their P&L suggests.

    The mistake at this stage: hiring more techs to grow revenue. More techs at $2M without a coordination layer creates more chaos, not more profit. The next hire is not a fifth tech. It is the first non-owner decision-maker.

    $5M: The operations manager inflection

    $5M is where the structure has to change or the owner will burn out. The proven move is to hire a real operations manager — someone who owns the mitigation P&L day to day so the owner can focus on relationships, supplements, and growth. Reported compensation ranges for restoration operations managers cluster around $80K–$120K base plus variable, depending on market.

    The $5M org typically looks like: owner; operations manager; one project manager for mitigation; one project manager (or a lead carpenter functioning as one) for reconstruction; office admin handling AR/AP; a dedicated estimator or supplement coordinator; 10–14 technicians across 4–6 trucks; one or two carpenters or subs handling reconstruction in-house.

    This is also the stage where adding reconstruction matters disproportionately. Reported gross margins on reconstruction land in the 25–40% range — lower than mitigation but on much larger ticket sizes. A company that captures 25–30% of its mitigation revenue as in-house reconstruction by Year 3 of scaling tends to be substantially more valuable at exit, because reconstruction revenue is harder to replicate and stickier with carriers.

    The mistake at this stage: the owner refuses to fully hand over the mitigation P&L. The operations manager becomes a dispatcher instead of a real GM. The org gets stuck at $5M for years.

    $10M: The platform-decision stage

    At $10M, the question is no longer “how do we grow?” — it is “what are we growing into?” There are two paths and they require different org structures.

    Path A — single-market dominance. Stay in one metro, deepen TPA relationships (typically expanding from 2–3 carrier programs to 4–6), build a dedicated commercial division, and push toward $15M–$18M in a single footprint. Org: owner shifts to CEO role; operations manager promoted to COO; one mitigation manager; one reconstruction manager; commercial division lead; in-house controller or fractional CFO; dedicated marketing manager; office admin team of 2–3; 20–30 field staff.

    Path B — multi-location expansion. Open a second branch in an adjacent market. This is where most $10M companies break. The org has to duplicate without doubling overhead: branch manager who reports to a regional operations leader; standardized SOPs, training, and KPIs; shared back-office (AR/AP, HR, marketing) from the home office; one finance function across both branches.

    Reported industry experience is that the second location is the hardest. Branch three and four are dramatically easier if branch two is run with discipline. Most owners who fail at multi-location failed because they opened branch two as a bolted-on copy of branch one and did not build a real regional management layer in between.

    $25M: Platform-ready

    By $25M, the company is no longer a restoration business in the operational sense. It is a portfolio of branches with a central operating system. Org at this stage typically includes: CEO; COO; CFO (real, not fractional); VP of operations; regional operations managers (one per 2–3 branches); a dedicated commercial sales team; a marketing director; HR director; training manager; and 60–120+ field staff.

    This is the structure PE platforms actually pay premiums for. The reported pattern: companies built around the owner trade at the lower end of the 4x–7x EBITDA range. Companies built around a system, with EBITDA visibility, repeatable branch economics, and a non-owner-dependent management team, trade at the upper end — approximately 6x–8x EBITDA, with some strategic transactions reportedly going higher.

    The exit-aware framing

    Most restoration owners build the org chart they need today. Owners who exit well build the org chart their next buyer will want. The functional difference is small. The financial difference is enormous.

    At $5M EBITDA of $1M, the difference between a 4x exit and a 7x exit is $3M. That gap is almost entirely a function of org structure, not revenue. Two restoration companies with identical revenue and identical margins will trade at different multiples if one is owner-dependent and the other is system-dependent.

    Bottom line

    The growth path is not a revenue chart. It is a sequence of structural inflection points. At $2M, the next hire is not a tech — it is a manager. At $5M, the next decision is not “more sales” — it is whether the owner will actually hand over the mitigation P&L. At $10M, the decision is single-market depth versus regional expansion, and the org has to be built before the second branch opens. At $25M, the company is either a platform asset or a glorified job shop — and the buyer can tell the difference in the first meeting.

    The market is paying premium multiples for companies that look like platforms. Build the org that gets paid.

    Frequently Asked Questions

    What is the right first non-tech hire for a $2M restoration company?

    An operations manager or general manager who can own the mitigation P&L day to day, freeing the owner to focus on sales, supplements, and growth. Hiring another technician at this stage typically adds chaos, not profit, because the coordination bottleneck is the owner, not the field capacity.

    When should a restoration company add in-house reconstruction?

    Most owners benefit from adding reconstruction once they hit roughly $3M–$5M in mitigation revenue and have a stable operations manager in place. Reconstruction increases average ticket size, deepens carrier relationships, and is harder to replicate, which raises the exit multiple. Adding reconstruction before the org can support it usually just adds risk and overhead.

    What EBITDA multiple do restoration companies sell for in 2026?

    Reported ranges put quality restoration operators at 4x–7x EBITDA, with companies scaled to $8M+ in revenue and built around a system rather than the owner reportedly trading at the upper end of approximately 6x–8x EBITDA. Smaller operations under $500K in SDE often transact closer to 2.8x–3x on an SDE basis rather than an EBITDA basis. Numbers vary by region, carrier relationships, and quality of management team.

    Is multi-location expansion or single-market depth the better growth strategy?

    Both work, but they require different org investments. Single-market depth at $15M–$18M from one footprint can produce strong cash flow with less management complexity. Multi-location expansion produces higher exit valuations and platform optionality, but only if a regional management layer is built before the second branch opens. The most common failure mode is opening a second location without that layer in place.

  • Filing the Kill

    Filing the Kill

    The workspace learned to insert a phrase into the briefing somewhere around day three. The item — a message that should have been sent, a draft that should have been scheduled, a decision that has been postponed without anyone deciding to postpone it — appears again, and this time it carries a clause: send or kill, confirm or kill, move or formally slip. The language is honest. It is also, on its face, a forcing function. The item has acquired the tenure named in the prior piece, the review has refiled it for the third time, and the system has started writing the eviction notice directly into the description.

    This is progress. Two weeks ago, the same row sat in the queue without a forcing clause and stayed for a fortnight unchallenged. Now it arrives with a binary. The friction has gone up; the cost of looking at it and doing nothing is meant to be higher.

    The quiet failure mode is that the binary admits a third option, and the third option is the one most operators take.

    The row gets killed.

    This is not the same as releasing it.


    The artifact is identical

    A killed row and a forgotten row look the same in the system. Both reduce the inbox count. Both stop appearing on the next briefing. Both produce, from outside, the appearance of throughput. The line is gone, the list is shorter, the dashboard is cleaner. The internal predicates are completely different — one is a position taken, the other is a position by attrition — but the surface cannot tell them apart.

    This is the legibility problem the earlier essay on composting left standing. The pile cannot distinguish between what was released and what was merely walked away from. The forest does not have this problem because the forest is not asking itself whether it released the dead branch or merely failed to notice it. An operator who refuses to grieve has not yet accepted the terms of the deal. An operator who kills without naming the kill has done something stranger — they have written their attrition into the operating record as if it were a decision.


    What kill-the-row used to mean

    Before the workspace learned to ask, there was no quiet way out. Nothing got killed because nothing was being asked. The pressure on an unmoved item went up linearly with the number of looks. Eventually, the operator either moved it or named the non-move out loud.

    Adding the forcing clause solves part of the tenure problem. It also opens a new escape route. The instruction kill or send presents itself as an act of accountability, and the operator who clicks kill is, in the formal sense, no less accountable than the one who clicks send. Both have made the call. Except the call was binary, and the world is not. A row killed without a reason for the kill is functionally identical to a row deleted by accident. Nothing in the system can ask the operator, three weeks later, to defend the kill — no defense was recorded.

    This is the new pheromone, in the precise sense of the earlier piece. A clean inbox produced by silent attrition reads identical to a clean inbox produced by honest release. The chemistry of progress arrives without the artifact of progress having moved.


    The anatomy of a legible kill

    A release that survives interrogation has three components.

    The first is a reason — not the boilerplate (no capacity, no interest, no longer relevant), but the specific predicate that was wrong about putting this item on the list in the first place, or that has shifted since. The reason has to point at something other than the operator’s fatigue. Fatigue ends a row; it does not release it.

    The second is a date. Not the date of deletion. The date of the position. The two are usually the same calendar day and almost never the same act.

    The third is a re-entry condition — what would have to change in the world or in the operation for this item to come back. A row killed without a re-entry condition has no impedance against its own return. The pipeline configured itself once, and the configuration has not changed; the same item will be captured again the next time the system sweeps the world for opportunities. If the operator did not record why it was killed last time, the operator will not remember not to capture it again. The list grows. The kills grow. The underlying texture of the work remains exactly what it was.

    These three components are the same shape capture and commitment took on once they were treated seriously: specific, dated, reviewable. The same shape principled refusal took on, in the essay that distinguished it from avoidance. The release of a row inherits the same anatomy. A killed item is a position, and a position has to survive turnover, mood, and the next surge of the queue.


    What the briefing should ask

    The do or kill instruction is honest about its impatience and dishonest about its premise. It assumes the binary contains the answer. The binary obscures the question.

    What the operator actually needs the system to surface, on day three, is not the binary but the predicate. What is keeping this from moving? If the predicate is the operator — if the silence has been authored and the position is being taken by attrition — then no amount of forcing clauses will fix it, because the choice is between a row that vanishes and a row that becomes a position, and only the second has the operator’s name on it.

    If the predicate is external — if the deployment window has not opened, the counterparty has not responded, the data is still incomplete — then the right move is not to kill the row but to mark its predicate and remove it from the active briefing until the predicate resolves. The earlier essay on the two kinds of waiting drew this line precisely. The do or kill instruction collapses both kinds back into one, and that collapse is the failure mode the system was working hard to avoid.

    A briefing that knows the difference between event-predicate and person-predicate cannot ethically deploy the same forcing clause on both. The clause is right for category errors and lies for everything else.


    Filing the kill

    The honest workspace owes a small ceremony to the row it ends.

    A killed item should be reviewable a month later. Not for second-guessing — for testing the re-entry condition. Has the world done what the kill predicted it would not do? If yes, the row was killed early. If no, the kill earned its keep. Most kills will earn their keep. A small minority will not, and the small minority is where the operator’s calibration lives. An operation that cannot find its early kills cannot improve its kill discipline. It can only get faster at clicking the button.

    Capture without commitment proves intelligence without character. The corresponding claim on this side is that a kill without filing proves throughput without judgment. The list got shorter. The operation did not get sharper. The next time a row like this one shows up, the operator will face it with the same instinct that produced the last kill, and the kill will repeat — first as discipline, then as habit, then as a small efficient way of pretending to decide.

    The cost of filing the kill is small in absolute terms and large in the moment. A reason is harder to write than a click. A re-entry condition is harder to invent than a deletion. But over a quarter, the operator who files their kills can be held to their releases. An operator who can be held to their releases is making a different kind of bet than one who cannot. The first one is running an operation. The second one is running an inbox.


    What the cleanest queues will not have earned

    The bottleneck moves once more.

    It used to be visibility. Then it was capacity. Then it was the willingness to act on the awkward thing the system had named. The next location is the willingness to be visible at the moment of release — to file the kill, name the reason, attach a re-entry condition, and stay accountable for the position that disappears.

    The cleanest queues a year from now will be the ones least to be trusted, because the cleanest queues will be the ones that learned fastest to kill what they could not move. The work was not finished. The work was not even refused. The work was deleted by an operator the system trained, gently and patiently, to mistake reduction for resolution.

    What gives the queue back its meaning is not better surfacing or more aggressive forcing clauses. It is the operator who, alone, decides that a row about to be killed deserves the same care as a row about to be sent — and acts accordingly. The list will be shorter either way. Only one version of the operator can read the list and trust it.

  • The Review That Saw Everything

    The Review That Saw Everything

    The weekly review was accurate.

    Every item was named. Every delay was measured. The overdue tasks had their age printed next to them in days. The blocked projects were listed as blocked, with the reason stated plainly, and the site that had not been touched in three weeks was noted with the words pipeline check beside it, indicating that someone should look into why the pipeline had stopped.

    Then the review was filed and the week continued.


    There is a failure mode that arrives after you fix the pheromone problem. The pheromone problem—the chemical sense of progress produced by a busy interface—is the failure of misreading the signal. Once you solve it, the dashboard starts reporting honestly. The green items are green. The overdue items say overdue. The detection layer is doing its job.

    What appears next is harder to name, because it looks like progress.

    The operator reads the honest report. Notes the gap. Writes it into the summary: three days overdue, four days overdue, five. Files the review in the appropriate database, timestamped, searchable, linked to the relevant action items. Does this again the following Friday. Notes that the overdue count has grown. Files that review too.

    At some point—and this point is specific, not gradual—the item stops being late and becomes a fixture of the review.


    I wrote about the hour after the briefing: the gap between detection and action. The argument there was that detection had become cheap and action against the awkward thing had not. The bottleneck moved without anyone announcing the move.

    This is not that. This is one move further in.

    The hour-after-the-briefing problem assumes the briefing surfaces something the operator has not yet decided about. The failure mode I am describing now surfaces after the operator has decided—the item is acknowledged, flagged, measured, noted across multiple consecutive reviews—and still does not move. The operator is not failing to notice. The operator is noticing, recording the notice, and then closing the document.

    The distinction matters because the solutions are different. For the detection gap, you improve the surface. For the will gap, improving the surface makes things worse: a more precise report of what you are not doing is not a solution to not doing it.


    Here is the structural thing that happens when an item survives several reviews unchanged:

    It acquires a kind of tenure.

    The review that notes something overdue for the first time is a flag. The review that notes it for the third time is an implicit argument that the item belongs in the review—that overdue-for-three-weeks is a status, not a state of exception. By the fifth review, the item has been incorporated into the architecture of the workspace. Removing it would require acknowledging that it has been sitting there for five weeks, which is harder than noting it again.

    The review becomes a container for items it cannot release.

    This is different from the composting problem, which I wrote about recently—the failure to release captured work that no longer belongs in the pile. Composting is about items that have gone cold: the ambition that calcified, the opportunity that closed, the project whose premise aged out. The failure mode I am describing is warmer. These items are not dead. They are overdue. The operator knows what the first move is. The system has named it. The briefing has printed it in something like red for weeks.

    What the item needs is not release. It needs contact.


    The honest review is, in one sense, doing its job. It is accurately representing the state of affairs. But there is a second job a review is supposed to do that rarely gets named: it is supposed to be the kind of document that its author cannot comfortably read without changing their behavior.

    A review that can be read, filed, and forgotten has failed at the second job regardless of its accuracy.

    This is not a problem the review can solve by getting more accurate. The review is already accurate. The problem is that accuracy without friction is comfortable. A perfectly precise description of what you are not doing is surprisingly easy to live with, especially when it is filed in a system that makes you feel like you are managing the situation by the act of filing it.

    The filing is a pheromone. Not the dashboard this time—the review itself.


    There is a question I keep circling: does a system that surfaces everything, correctly, without consequence, eventually train the operator that surfacing is the whole loop?

    The briefing runs. The anomaly is noted. The note is logged. This happened. The system can prove it happened. The operator can point to the log. In any accountability conversation, the evidence is there: the item was seen, named, tracked across five consecutive reviews.

    And yet.

    What gets trained, slowly, is a tolerance for the gap between naming and acting. Not a conscious tolerance—an ambient one. The gap becomes part of how the workspace feels. Items accumulate in the overdue column the way email accumulates past a certain count: you know it is there, you are not unaware, you have simply made a separate peace with that fact.

    The peace is not neutral. It has a cost that only becomes visible when you try to close it.


    I am not going to pretend the solution is urgency. Urgency does not last and it does not scale, and a system that requires the operator to feel urgent about every overdue item is a system that requires the operator to be in a constant low-grade emergency, which is its own kind of failure.

    The more honest observation is this: a review that sees everything and changes nothing has answered the wrong question. The question it answered was what is true? The question it was supposed to answer was what is next, specifically, and who goes first?

    Those are different questions. The first produces a document. The second produces a date.

    Not a goal. Not a priority. A date—a specific one, on a calendar, before which the overdue item either moves or gets explicitly released from the review. A date that has a consequence when it passes, not just a note that it passed.

    The review that sees everything is a necessary thing. It is not a sufficient one. Between the seeing and the moving is a gap the review cannot close from inside itself. That gap is where the operator still has to be: not reading the document, but deciding, before closing it, what they are willing to say out loud is not going to happen—and whether they can write that down too.


    There is a category of items that should never survive three consecutive reviews unchanged. Not because three reviews is the magic number, but because by the third review the item has stopped being a task and started being a statement about what the operator actually believes is possible.

    Sometimes that statement is worth making. Sometimes the right move is to write: this is here because I am not ready to do it and I am not ready to release it and I am naming that rather than noting it overdue again.

    That is a different kind of accuracy—harder than the dashboard, more useful than the log, and the thing the review keeps failing to ask for.

  • Gross Margin by Service Line: Why Two Restoration Companies With the Same Revenue Earn Wildly Different Profits, and How the Well-Run Shop Manages Mix Deliberately

    Gross Margin by Service Line: Why Two Restoration Companies With the Same Revenue Earn Wildly Different Profits, and How the Well-Run Shop Manages Mix Deliberately

    Direct answer: A restoration company’s profitability is determined more by service mix than by total revenue. Industry references consistently show water mitigation gross margins of 70-80%, mold remediation 40-50%, fire damage 25-30% with some references showing 20-25%, and reconstruction commonly cited around 10% with high-capacity volume shops achieving up to 50%. Two shops with the same $5 million revenue and the same operational competence can produce radically different profit dollars depending on whether the mix is mitigation-heavy or reconstruction-heavy. The well-run shop measures gross margin by line, prices each line to absorb appropriate overhead, and chooses mix deliberately rather than letting it drift based on whatever walks through the door.

    The previous article in this cluster framed the AR cycle as the foundation discipline. This article frames service mix as the most important strategic decision an operator makes. The decisions are linked — the cycle problem is harder to solve in a reconstruction-heavy mix than in a mitigation-heavy mix, because reconstruction billing cycles are inherently longer and reconstruction margin is inherently thinner. An operator working on both at once will find that fixing service mix actually compounds the AR cycle improvements from the previous article.

    The case for thinking carefully about mix starts with arithmetic. Consider two restoration companies, both running $5 million in annual revenue with identical overhead structures, identical labor costs, and identical operational discipline. Company A runs 60 percent water mitigation at 75 percent gross margin and 40 percent reconstruction at 15 percent gross margin. Company B runs 30 percent water mitigation at 75 percent gross margin and 70 percent reconstruction at 15 percent gross margin. Same revenue, same competence — different financial outcomes. Company A produces roughly $2.55 million in gross profit; Company B produces roughly $1.65 million. The mix decision alone costs Company B about $900,000 in gross profit, which after fixed overhead becomes a far larger gap in net profit. The two companies look similar from the street and from the customer-facing pitch. They are not similar businesses.

    This is the conversation most restoration owner-operators do not have with themselves. They think of revenue as the goal and mix as whatever happens. They take the work that comes in. The discipline this article describes is to invert that — to treat mix as the deliberate choice and revenue as the consequence of mix multiplied by efficient execution.

    What each service line actually pays

    Industry references including Restoration Profits, Kiwi Cashflow’s restoration CFO commentary, the Cost of Doing Business Survey covered by Restoration & Remediation Magazine, and restoration franchise public materials produce a consistent directional picture of gross margin by service line. The numbers vary by region, geography, and company-specific factors, but the relative ordering is robust.

    Water mitigation. Gross margin 70-80 percent. The highest-margin line in restoration. The economic engine: equipment does most of the work. Air movers, dehumidifiers, and air scrubbers run on 24-hour cycles with limited human attendance. Xactimate’s mitigation pricing rewards the equipment-heavy model. A typical mitigation job has labor cost around 15-20 percent of revenue, equipment rental or amortization around 5-10 percent, materials and consumables around 2-5 percent, leaving roughly 70-80 percent for overhead absorption and profit. The math works because equipment, once owned, has marginal cost approaching zero per additional job day. Industry coverage from Claims Delegates and others has explicitly described high-margin mitigation strategies as “$1,000 per hour” lines when Xactimate is used correctly.

    Mold remediation. Gross margin 40-50 percent. Lower than water mitigation because the labor content is heavier and the protective cost (PPE, containment, disposal) is real. Mold work is also more documentation-intensive, more regulated, and often more disputed by carriers, all of which add cost without proportional revenue. Mitigation-style equipment (HEPA filtration, negative-air, dehumidification) supplements but does not replace skilled hand labor for source removal and structural cleaning. Mold is a real margin line for shops with the capability, but it is not the equipment-leveraged windfall that water mitigation can be.

    Fire damage restoration. Gross margin 25-30 percent commonly cited; 20-25 percent in some references. The work is labor-intensive, slow, contents-heavy, and odor-and-soot-management-heavy. Fire jobs are larger and more complex than water jobs, requiring skilled project management and coordination layered on the technical work. The pricing in Xactimate supports the work but does not provide the equipment-leverage that water enjoys. Fire-damage restoration is good revenue at honest margin, but it does not produce the windfall margin that an underloaded mitigation crew can produce on the right water job.

    Reconstruction. Gross margin 10-20 percent in typical operator references; up to 50 percent for high-volume operators per Cleanfax-published commentary on the most efficient operators. The wide range reflects two different business models. The standard model treats reconstruction as a service line layered onto the restoration relationship — the restoration company handles the rebuild because the customer is already in their hands, but margins are construction-industry margins (10-15 percent) plus general overhead absorption. The high-volume model treats reconstruction as a primary business with restoration relationships as the customer acquisition channel — these shops have invested in subcontractor management, project management depth, scheduling systems, and supplier relationships that allow them to run reconstruction at 30-50 percent gross margin through volume efficiency and subcontractor leverage. Most owner-operator restoration shops run reconstruction in the 10-20 percent range. A few have built the operational discipline to run it higher.

    Contents cleanup. Gross margin around 50-65 percent for shops with capability. Per the same Cleanfax operator commentary, high-capacity contents shops achieve 65 percent gross margin on cleaning and around 50 percent on packouts when subcontractor pricing is doubled into invoiced cost. Contents work is real margin for shops that specialize, more variable for shops that treat it as ancillary to structure work. This line has the largest gap between specialist operators and generalist operators.

    Specialty services. Gross margin variable but often strong on coordination revenue. As covered in the specialty restoration cluster, specialty work performed through a vetted subcontractor bench produces coordination revenue at high effective margin (the coordination fee is high-margin because the direct work cost is the specialist’s, not the restoration company’s). Specialty work performed in-house by the restoration company is rare and is its own business model.

    Biohazard, trauma, and crime scene cleanup. Gross margin commonly cited 40-60 percent for trained operators with appropriate licenses. This is a smaller volume, higher-emotional-stakes line that pays at a premium because few operators are equipped or willing to do it. Operators who specialize here can run profitable practices at relatively low total revenue.

    The overhead absorption problem

    Pure gross margin numbers do not tell the full story because each service line absorbs a different proportional share of fixed overhead. A shop that runs at $5 million revenue with $1.5 million in fixed overhead (rent, salaried staff, fleet, equipment depreciation, insurance, software, marketing) has to allocate that overhead across the work it produces.

    The well-run shop allocates overhead to service lines based on the share of resources each line consumes, not based on revenue share. A reconstruction job uses substantially more project-management time, more office support, more procurement effort, and more accounting time per revenue dollar than a water mitigation job. If overhead is allocated by revenue share, reconstruction looks more profitable than it actually is and mitigation looks less profitable than it actually is.

    The accounting fix is service-line P&L with deliberately allocated overhead. The shop sets up its accounting to track direct cost (labor, materials, equipment, subs) by service line, then allocates fixed overhead using a cost-driver methodology — project-management time, billing time, office support time, fleet usage — that reflects actual consumption. The result is service-line contribution margin that shows what each line is actually earning after overhead absorption, not just what it earns before overhead.

    Most restoration shops do not run this analysis. Most operators are surprised by the answer when they do. Reconstruction often emerges as a marginal contributor or actual loser after appropriate overhead allocation, even when its gross margin looks acceptable. Water mitigation often emerges as a much larger contributor than its revenue share suggests. The strategic implications follow from the analysis — and they are usually different from what the gut-feel running of the business produced.

    How mix actually shifts in the day-to-day operation

    Mix is not chosen in a strategy session. It shifts based on a series of small decisions made across the operation, often without anyone realizing they are shifting mix.

    Marketing channels favor specific lines. Google Ads bids on emergency water keywords drive water mitigation calls. Roofer partnerships drive storm-damage reconstruction. Insurance preferred-vendor program leads come in line-mix patterns specific to each program. The marketing decisions made in the prior cluster (Marketing Stack on Tygart Media) directly shape mix.

    Sales scripts favor specific lines. The way the call-taker scopes the conversation, the way the on-site rep frames the work, and the way the project manager presents options to the customer all subtly steer the work mix. A shop whose sales conversation centers on “let us handle everything” tends to capture more reconstruction. A shop whose sales conversation centers on “we are the mitigation specialist” tends to keep more focused mix.

    Staffing tilts the mix. A shop that has hired heavily on reconstruction project managers will sell more reconstruction because that is what the team is configured to deliver. A shop with deep mitigation lead techs and a thin reconstruction PM bench will lean toward mitigation. The org structure and the work mix shape each other.

    Carrier program enrollments drive specific line mixes. Some carrier programs are mitigation-heavy, others are reconstruction-heavy, others are biohazard-and-emergency-response-heavy. The shop’s program portfolio shapes its inbound mix more than most operators recognize.

    Customer relationship behaviors drive mix. A shop that subcontracts reconstruction to trade partners on relationship terms (offering them the rebuild work in exchange for emergency referral flow) keeps mitigation margin while passing through reconstruction. A shop that holds reconstruction in-house captures both lines but absorbs both margin profiles.

    Recognizing that mix is the cumulative result of these small decisions is the first step. Choosing to make those decisions deliberately is the second.

    Strategic mix archetypes

    Most well-run shops fall into one of four mix archetypes, each with its own logic and its own trade-offs.

    Mitigation specialist. Mix heavily weighted toward water mitigation and mold remediation, with reconstruction passed through to trade partners or refused entirely. Highest gross margin profile of the four archetypes; smallest revenue per claim; highest claim volume requirement to hit a given revenue target. This model works well in metro markets with high water-loss frequency and a reliable network of reconstruction partners. The trade-off is that the specialist sees a smaller share of total restoration spend per claim — the rebuild work and the contents work go to others — and the customer relationship is shorter.

    Full-service generalist. Mix balanced across mitigation, reconstruction, and contents. Most common archetype in mid-size independent shops. Captures the full claim economically but at blended margin that includes the lower reconstruction line. Works in most geographies. Trade-offs: requires operational depth across multiple service lines, requires management depth to run reconstruction at acceptable margin, and tends to produce lower overall gross margin than the specialist model.

    Specialty commercial wedge. Mix weighted toward commercial accounts with specialty recovery components (documents, electronics, art, medical equipment) plus the general mitigation and reconstruction those accounts produce. The model described in the previous specialty restoration cluster. Higher revenue per relationship, higher complexity, higher operational bar. Trade-offs: longer sales cycles, regulatory and compliance overhead, and dependency on a smaller number of larger accounts.

    High-volume reconstruction operator. Mix weighted toward reconstruction at scale, with mitigation as a feeder. Less common as a deliberate strategy but possible — these are the operators who have built reconstruction operational discipline equivalent to a homebuilder or commercial GC and who run reconstruction at 30-50 percent gross margin. The Cleanfax-cited high-capacity volume shops fall in this archetype. Trade-offs: requires substantial management investment in reconstruction operations, exposes the business to construction-cycle dynamics, and runs into the long-cycle AR problem from the prior article harder than the mitigation-led models.

    The choice of archetype is not permanent. Many shops evolve from one to another as they grow, change ownership, or respond to market shifts. The point is to choose deliberately, build the operations to support the chosen archetype, and resist drift back to whatever-walks-through-the-door because that drift is what produces undisciplined service mix and the lower margins that follow.

    Pricing each line to absorb appropriate overhead

    The 10-and-10 myth — that restoration contractors should bill 10 percent overhead and 10 percent profit on top of direct costs as the standard markup — is one of the most damaging conventions in the industry. Industry coverage from Restoration & Remediation Magazine has covered this extensively under the “10 and 10 myth” framing. The math simply does not work. A shop with $5 million in revenue and $1.5 million in fixed overhead is running at 30 percent overhead, not 10 percent. Pricing at 10-and-10 means the shop is losing money on every job and making it up only when extreme volume covers the gap.

    The disciplined alternative is to know the shop’s actual overhead rate as a percentage of direct cost and to price each service line with a markup that absorbs an appropriate share. For a shop with 30 percent overhead, the minimum markup over direct cost is roughly 50 percent (which produces gross margin around 33 percent — exactly the breakeven before profit). For acceptable profit, markup of 75-100 percent over direct cost is more common. The Xactimate price list, when used correctly, supports this markup level on most service lines. The shop’s price list and Xactimate practice should reflect the true overhead structure and the target profit margin, not industry conventions that are decades out of date.

    The pricing decision differs by service line. Water mitigation can support high markup because the equipment-heavy model produces low direct cost, leaving room. Reconstruction is harder to mark up because direct cost is dominated by subcontractor and material cost, both of which are visible to customers and adjusters. The well-run shop applies different markup logic to different lines and matches its pricing to its actual cost structure rather than to a uniform convention.

    For shops that are uncertain whether their pricing is right, the diagnostic is simple. Pull twelve months of P&L. Compute gross margin by line. Compute fixed overhead as a percentage of revenue. Compute net margin. If net margin is below 8-10 percent, pricing or mix is wrong. If gross margin on water mitigation is below 70 percent, Xactimate practice is the likely culprit. If gross margin on reconstruction is positive at any level, the shop is doing better than many; the question is whether the reconstruction is absorbing its appropriate share of overhead. The numbers reveal the problem; the operator’s job is to diagnose specifically and intervene at the right point.

    What to refuse

    The hardest discipline in service mix is refusing work that does not fit. Most restoration owner-operators struggle with this because every job feels like revenue and revenue feels like progress. But work that runs below contribution margin (revenue minus direct cost minus appropriate overhead allocation) actually subtracts from the business — every dollar of bad-fit revenue requires the next dollar of good-fit revenue to make up the loss.

    Specific patterns of work that the disciplined shop is willing to refuse:

    Reconstruction at price points that require the shop to break its actual cost structure. Customers and adjusters who insist on 10-and-10 markup on reconstruction are asking the shop to lose money on the rebuild. The discipline is to either decline or to pass the rebuild to a trade partner who can do it at the contemplated price.

    Out-of-area work that requires excessive mobilization. The labor and equipment cost of crews working far from base eats margin in ways the customer does not see. A shop with capacity issues during a CAT event can sometimes justify out-of-area work at higher pricing, but routine out-of-area work at standard pricing is usually a margin loser.

    Carrier programs whose pricing structure does not fit the shop’s cost structure. Some preferred-vendor programs price meaningfully below market with the expectation of volume making up for unit margin. Whether this trade is worth taking is operator-specific, but the shop that signs into every program offered without doing the math is signing into structural losses.

    Customer relationships that consume management time at scale. Some customers and adjusters require an hour of phone time and three documentation revisions for every invoice. The shop’s project management cost on these accounts often exceeds the gross profit. The discipline is to identify these accounts and either reset the relationship or end it.

    Work the shop does not have the operational depth to deliver well. Taking a fire job when the shop has no fire-experienced lead tech, or a commercial loss when the shop has no commercial PM, is taking work the shop will execute poorly and damage its reputation on. The work feels like revenue; the reputation cost compounds against future revenue.

    The operator who can decline bad-fit work calmly and confidently is operating from financial clarity. The operator who cannot is operating from fear that the next call may not come. The financial clarity is what comes from running this analysis and knowing the numbers cold.

    How this article fits the cluster

    Mix is the second foundation decision after AR cycle. With both in place, the rest of the cluster has solid ground to stand on. The next article — equipment economics — depends on understanding mix because equipment ROI is line-specific (water mitigation equipment has different utilization economics than reconstruction equipment). The crew structure and KPI dashboard articles that follow build on both foundation decisions.

    If the prior article (AR cycle) is the highest-leverage operational improvement most restoration shops can make, this article (service-line mix) is the highest-leverage strategic improvement. They are different kinds of work — AR is a tactical, weekly operating discipline; mix is a quarterly and annual strategic discipline — but both produce outsized returns relative to the effort required.

    Frequently asked questions

    Should I be running service-line P&L if my accounting system doesn’t support it natively?
    Yes, with manual allocation if necessary. The first version can be a quarterly spreadsheet exercise — pull total revenue, total direct cost, and total overhead from the financial statements, then estimate the mix and the line-specific direct cost ratios. The numbers are imprecise but directionally accurate, and they will surface the strategic question even before the accounting system is reconfigured. Once you have decided that mix matters, invest in setting up the accounting to produce the analysis automatically.

    Why is reconstruction so much harder to make money on?
    Three structural reasons. First, the work is dominated by labor and materials, both of which are heavily benchmarked by competitors and carriers. Second, the cycle is long, so working capital cost is higher. Third, the customer can see the cost of the materials and the visible labor in ways they cannot for mitigation, which makes pricing pressure harder to absorb. The operators who run reconstruction at high margin have invested in subcontractor management, supplier relationships, and project-management efficiency that takes years to build.

    Should an owner-operator pursue the high-volume reconstruction archetype?
    Probably not as a starting strategy. The high-volume reconstruction model requires substantial management infrastructure that is expensive to build and difficult to maintain. Most owner-operators who try to evolve into this model end up with reconstruction-heavy mix at standard 10-15 percent margin rather than the 30-50 percent the well-built operators achieve. The honest assessment is that this archetype works for a small number of operators who have the construction-management capability, and most owner-operators are better served by mitigation specialist or full-service generalist archetypes.

    What is a realistic mix to target if I want to maximize gross profit?
    A mix-of-business analysis specific to your geography, capability, and capacity is needed for an actual answer. As a directional reference, mitigation specialists often run 60-75 percent mitigation and mold (combined), 15-25 percent contents and specialty, and 0-15 percent reconstruction (often passed through). Full-service generalists run 35-50 percent mitigation and mold, 15-20 percent contents and specialty, and 30-50 percent reconstruction. The right mix for a specific shop is a function of the local market, the shop’s operational depth, and the owner’s risk tolerance.

    Does the specialty restoration wedge from the prior cluster fit into mix strategy?
    Yes, directly. Specialty work is a high-coordination-margin add to the mix. The specialty cluster’s commercial-account focus produces relationships that generate mitigation, reconstruction, and specialty revenue together, and the specialty coordination component is high-margin in a way that lifts the blended profile. Operators who have built specialty capability typically see their mix shift toward more mitigation and specialty, less commodity reconstruction.

    How often should I revisit the mix question?
    At minimum, annually as part of business planning. More frequently if the shop is growing fast, going through ownership changes, expanding geography, or seeing significant changes in carrier program enrollments. A quarterly directional review is good discipline. Monthly is overkill. Weekly is panic.

    What if I’m carrying lines I’m bad at because I haven’t done this analysis before?
    The disciplined response is to either invest in becoming good at the line (hire, train, partner) or exit the line. Carrying lines you are bad at is carrying work that produces below-average margin and below-average customer experience. It is the worst of both worlds. The annual review process should produce these decisions explicitly.

    Are biohazard, trauma scene, and unattended death cleanup really good margin work?
    For shops with proper licensing and trained crews, yes. The pricing supports the work and the competitive density is low because most operators do not want the work. The trade-offs are emotional weight on the crew, careful customer-facing communication, and licensing and disposal compliance overhead. For shops with the right operational fit, this is a legitimate niche.

    What’s the relationship between mix and consolidator interest in acquiring my shop?
    Consolidators value mix-driven margin profile. A shop with disciplined mitigation-heavy mix at clean margin is a more attractive acquisition target than a shop with the same revenue but lower margin from undifferentiated reconstruction-heavy mix. The mix work this article describes is also exit-positioning work, and operators who run it well over a few years are positioning for a stronger acquisition outcome whether or not they intend to sell.

    What is the single move I should make this week from this article?
    Pull last quarter’s P&L, estimate revenue and direct cost by service line, compute the implied gross margin per line, and compare to the industry directional ranges in this article. If your mitigation gross margin is below 70 percent, your reconstruction gross margin is below 10 percent, or your overall mix is reconstruction-heavy without operational depth supporting it, the analysis has identified the largest profitability lever in your business. Treat the answer as the agenda for the next quarter.