Restoration Management Software
Building a Business Case for Restoration Software Your Partners Will Approve
In brief
Partners rarely say no to software because of the software. They say no because the case is vague. Here is how to measure the problem, count the real costs, answer each partner's worry and ask for a decision they can review later.
Start with the problem, not the product
Most software proposals die in the first five minutes because they open with features. One partner hears "new system" and thinks about the last tool the company paid for and quit using. Another hears "subscription" and starts doing math in their head. Nobody is listening to the part about better photo documentation.
A business case that gets approved starts somewhere else: with a problem every partner already recognizes. Maybe jobs sit completed for a week before anyone builds the invoice. Maybe the office manager spends Monday mornings calling crew leads to find out where equipment is. Maybe the last carrier file came back with questions because the moisture readings for day three were on a technician's phone and never made it into the job file.
Pick the two or three problems that cost the most and that the partners have complained about out loud. Write each one as a single sentence in plain language. "We do not know a job's actual labor hours until the pay period closes" is a problem statement. "We need better visibility" is not.
Measure the current state for two weeks
Opinions about how bad a process is will not move a skeptical partner. Counts will. Before you write anything persuasive, spend two normal weeks measuring how the work actually flows today. Keep it simple enough that the people doing the work will cooperate.
| What to count | How to count it | Who tracks it |
|---|---|---|
| Hours spent re-entering job info into a second or third system | Tally marks on a sheet by the office computer | Office and admin staff |
| Calls or texts to find a job's status, crew or equipment | Quick log on a shared notepad or phone note | Office manager, PMs |
| Days from job completion to invoice sent | Pull dates from the last 20 closed jobs | Bookkeeper |
| Jobs closed with missing photos, readings or signed paperwork | Check the last 20 job files against your own checklist | PM or owner |
| Callbacks or customer complaints about not hearing from anyone | Count from voicemail, email and the CRM or spreadsheet | Whoever answers the phone |
| Time crew leads spend on paperwork after hours | Ask each lead to note it daily | Crew leads |
Two weeks will not be perfect. That is fine. Note anything unusual about the period, such as a storm surge or a key person on vacation, so nobody can wave the numbers away later.
Translate hours into cost without inflating anything
Partners think in money, but you do not need to guess at dollar savings to make the case. Convert what you measured into hours, then let each partner apply the company's own loaded hourly rate for the roles involved. Loaded means wages plus the taxes, benefits and overhead that come with each hour.
Keep the arithmetic visible:
- Total the hours per week spent on each problem you measured.
- Multiply by the loaded hourly rate for the role doing that work.
- Multiply by the number of working weeks in a year.
- Keep cash-flow items separate. Days from completion to invoice are not an expense, but they are money the company is waiting on. Show them as days, and let the partners decide what that delay is worth.
Do not add speculative items like "we will win more jobs." They may be true, but they invite argument. A case built only on things you counted is much harder to dismiss.
A hypothetical walk-through: three partners, three agendas
Picture a mitigation and reconstruction company with three owners. One runs field operations, one handles sales and carrier relationships, and one manages the money. They have five crews and two office staff, and they run jobs on a mix of spreadsheets, a shared drive full of photos, group texts and their accounting software.
The operations manager measured for two weeks and found:
- Office staff spent roughly six hours a week combined re-typing job information from intake notes into the spreadsheet and then into accounting.
- PMs and the office manager made about 40 calls and texts a week just to learn job status or which crew had which dehumidifiers.
- Of the last 20 closed jobs, seven were missing at least one item the company's own checklist calls for, usually a signed work authorization or a final set of photos.
- The average gap between job completion and invoice was nine days.
She presented it this way. To the field partner: "Crew leads are spending evenings sending photos and notes that still end up in the wrong folder." To the sales partner: "Seven of our last 20 files would have trouble answering a basic adjuster question without a phone call." To the finance partner: "We wait nine days on average to bill finished work, and the office is spending about six hours a week typing the same things twice. Multiply that by our office loaded rate and by 50 weeks."
She did not mention a single feature until the second page. By then each partner had already agreed the problem was real.
Count the real costs, including the ones nobody likes to mention
A business case that hides costs gets approved once and resented forever. Lay out everything the change will take, especially time.
- Subscription cost. Get a written quote for your user count and the roles you need: office staff, field technicians, subcontractors and possibly client access.
- Setup time. Someone has to configure job types, checklists, user roles and templates. Estimate the hours honestly and name who will do it.
- Data migration. Decide what moves over. Open jobs and active customers usually do; old closed jobs often can stay archived where they are.
- Training. Count hours for office staff and for each crew. Field training is better done in short sessions than one long meeting.
- Parallel running. For a few weeks you may run old and new processes side by side. That is real extra work. Plan for it rather than pretending it will not happen.
- Productivity dip. The first month on any new system is slower. Say so in the proposal. Partners trust a case that admits this.
- Integration work. If accounting is connected, someone needs to map customers, items and classes so records line up.
Answer each partner's real worry
Partners approve things when their personal concern is addressed. Those concerns are usually predictable.
| Partner focus | Typical worry | What answers it |
|---|---|---|
| Field operations | "Crews will hate it and stop using it." | A mobile app demo with an actual crew lead, a short list of what techs must do each visit, and a pilot crew |
| Sales and carrier relationships | "Will this change how we look to adjusters and TPAs?" | Show how documentation gets more complete and consistent, not how it gets "better looking" |
| Finance | "What does it really cost and how do we get out?" | Full cost list, contract terms, data export options, and a review date |
| Owner or general manager | "Will this become another abandoned tool?" | A named internal owner, success measures, and a scheduled 90-day review |
Talk to each partner privately before the meeting. Ask, "What would make you vote no?" Then build the answer into the document. Walking into the meeting with no surprises is half the work.
Define success before you sign
The most persuasive line in a business case is the one that says how the partners will know if it failed. Write three to five success measures tied directly to the problems you counted. Use the same method of counting so the comparison is fair.
Examples:
- Days from job completion to invoice drops from nine to a number the finance partner sets.
- Status calls and texts per week drop noticeably, counted the same way as the baseline.
- Closed jobs missing a required checklist item drop from seven of 20 to two or fewer.
- Office re-entry time falls by a target the office manager agrees is realistic.
- Every active crew lead is logging time and photos in the app by week six.
Put a review date on the calendar, usually around 90 days after launch. Agree in writing on what happens if the measures are not met: adjust the rollout, extend the pilot, or exit.
Reduce the risk so saying yes feels safe
Partners hesitate because a bad software decision is hard to undo. Make it easier to undo.
- Pilot first. Run one crew or one job type, such as water mitigation jobs only, for a few weeks before rolling out company-wide.
- Name an internal owner. One person is responsible for setup, training and the 90-day review. Not a committee.
- Check the exit. Ask how you get your job records, photos and customer list out if you leave. Write the answer in the proposal.
- Protect the busy season. Do not launch the week a storm system is forecast. Schedule rollout during your slowest stretch.
- Keep the old process documented. Until the review date, the team should know how to fall back if something breaks.
Put it on one page, with the detail behind it
Partners read the first page. Make it count.
- Problem: Two or three sentences built from your measured counts.
- Proposal: What you want to buy, for which roles, starting when.
- Cost: Subscription plus setup, training and parallel-running hours.
- Success measures: The three to five numbers and the review date.
- Risk controls: Pilot scope, internal owner, exit plan.
- Decision requested: Exactly what you want approved today.
Attach the tally sheets, the 20-job file review and the vendor quote as supporting pages. Anyone who wants to check your math can.
If you are evaluating RestoreUnited as one of the options, map your measured problems to specific tools rather than the whole feature list. For example, Job Management and Photos & Journals address scattered job files, Time Tracking addresses unknown labor hours, Custom Reporting gives you a way to pull the same success measures at the 90-day review, and QuickBooks Integration addresses double entry into accounting. Show the partners only the parts that solve the problems they already agreed exist.
What to do this week
- Write down the two or three problems the partners complain about most, each as one plain sentence.
- Set up simple tally sheets for the office and crew leads and start a two-week measurement period.
- Pull the last 20 closed jobs and check each one against your own documentation checklist.
- Talk privately with each partner and ask what would make them vote no.
- Request written quotes and contract terms, including how you would export your records.
- Draft success measures and pick a tentative review date about 90 days after a planned launch.
- Block a partner meeting for the week after measurement ends, and put the one-page summary on the agenda.
See it in RestoreUnited: Job Management
RestoreUnited product videoFrequently asked questions
How long should we measure before presenting a software business case?
Two normal weeks is usually enough to show the pattern, and four is better if one of those weeks was unusually slow or a storm week. The goal is a believable baseline, not a perfect one. Note anything unusual about the period so nobody can dismiss the numbers later.
What if one partner simply does not trust software?
Treat that as a risk to manage rather than an argument to win. Propose a limited pilot with a written exit plan and a review date, and ask that partner to define what would count as failure. People who set the test are far more likely to accept the result.
Should the business case include projected revenue growth?
Keep it out of the main case. Growth projections are easy to challenge and they pull attention away from the measurable problems you documented. If the partners approve on the basis of time recovered and fewer errors, any growth that follows is a bonus rather than a promise you have to defend.