Paid lead spend
$4,000
$4,000
Same starting point.
Equal spend gives us a clean place to begin.
It does not tell us which source produced more useful work.
For home-service businesses
Progress stops somewhere.
You can be getting calls, booking jobs, and keeping the team busy while the business still feels stuck. Somewhere between getting found, getting booked, doing the work, and making the numbers work, progress is getting held up. We find where and work from there.
Illustration unavailable.
Recognize the situation
You don’t need the answer yet.
Start with what you can see.
Different situations can look similar from the outside. We start with what is actually happening before deciding why.
Evidence first. Interpretation second.
Operating snapshot
When something feels off
- Call volumeThis month+15.7% MoM486calls
- Last month
- 420
- This month
- 486
Calls are up.Completed revenue isn’t moving with them.
- RevenueThis month−7.3% MoM$196.8K
- Marketing
- Calls
- +15.7% MoM
- CRM
- Booked
- +15.6% MoM
- Accounting
- Revenue
- −7.3% MoM
$212.4K last month
Marketing, CRM, and accounting are telling different stories.
- Booked appointment outcomesThis month+15.6% MoM340booked70% of calls
- 170Estimate only50%
- 118Completed35%
- 52Pending / other15%
The schedule is full.The numbers still don’t look right.
- Estimate follow-up3 / 5 / 7-day standard170estimate-only outcomes
- 960 logged follow-ups56%
- 40Late / inconsistent24%
- 34On standard20%
Logged activity only. Unrecorded contact would change the count.
Calls and estimates are getting uneven follow-up.
When something needs to move
You’re adding capacity, a service line, or a new market.
You know what needs changing.You need help getting it done.
A closer look comes next
The same symptom can have different causes.
That’s why we establish what is happening before deciding what deserves attention.
Follow the lead
Same spend.
Different economics.
Two lead aggregators received the same $4,000 budget. One produced more qualified inquiries. The other produced more completed work. Follow the numbers before deciding which source deserves more attention.
See the full comparisonQualified inquiries
100
What this means
We divided the $4,000 paid-lead spend by the number of inquiries that met the qualification criteria.
$4,000 ÷ 100 qualified inquiries = $40 per qualified inquiry
$40 per qualified inquiry
50
What this means
We divided the $4,000 paid-lead spend by the number of inquiries that met the qualification criteria.
$4,000 ÷ 50 qualified inquiries = $80 per qualified inquiry
$80 per qualified inquiry
Aggregator A looks stronger here.
It produced twice as many qualified inquiries and cut the cost per qualified inquiry in half.
If the report stopped here, Aggregator A would look considerably more efficient.
Completed jobs
24
24% of qualified inquiries
28
56% of qualified inquiries
Keep following the lead.
Aggregator B produced half as many qualified inquiries, but more completed jobs.
The difference happened somewhere between the inquiry and completed work.
Lead spend per completed job
$166.67
What this means
We divided the $4,000 paid-lead spend by the number of jobs that were actually completed.
$4,000 ÷ 24 completed jobs = $166.67 per completed job
This includes lead spend only. It does not include labor, materials, or operating costs.
$142.86
What this means
We divided the $4,000 paid-lead spend by the number of jobs that were actually completed.
$4,000 ÷ 28 completed jobs = $142.86 per completed job
This includes lead spend only. It does not include labor, materials, or operating costs.
The cheaper inquiry became the more expensive completed job.
Aggregator A cost less at the inquiry stage.
Aggregator B cost less for each completed job.
Completed revenue per job
$500
$1,000
The jobs were different too.
Each completed job from Aggregator B produced twice the completed revenue on average.
That changes the value of the lead source again.
Completed revenue
$12,000
3.0× completed revenue / spend
$28,000
7.0× completed revenue / spend
Same spend. Very different result.
Aggregator A produced more qualified inquiries.
Aggregator B produced more completed jobs and more completed revenue.
Before changing the budget
What would change the decision?
Aggregator B looks stronger in this comparison. Before moving the budget, we would check what those jobs cost to deliver, whether the team could handle more, and whether the result is likely to repeat.
Choose a factor to see what we would check.
Gross margin
What remained after the direct costs of doing the work?
What we would check
Completed revenue against direct labor, materials, and other direct job costs, compared on the same basis for both aggregators.
Why it could change the decision
A revenue advantage may shrink when the work costs more to deliver.
Gross marginWhat remained after the direct costs of doing the work?
What we would check
Completed revenue against direct labor, materials, and other direct job costs, compared on the same basis for both aggregators.
Why it could change the decision
A revenue advantage may shrink when the work costs more to deliver.
Technician capacityCan the team take on more of this work?
What we would check
Available technician hours, the skills required by the incoming work, and the scheduling constraints already on the board.
Why it could change the decision
More demand only helps when the operation can absorb it without crowding out stronger work or creating service problems.
Service mixWhich types of jobs drove the result?
What we would check
The services completed, their ticket sizes, and whether a small number of unusually large jobs are carrying the comparison.
Why it could change the decision
Two channels can produce similar revenue through very different kinds of work, with different economics and capacity needs.
GeographyWhere was the work, and what did travel require?
What we would check
Job locations, drive time, routing friction, and whether the work falls inside the parts of the service area the team can serve efficiently.
Why it could change the decision
A job can look valuable in the revenue column while consuming much more field time than another job with the same ticket.
Lead exclusivityWas the inquiry shared with other providers?
What we would check
The provider agreement and source records for the lead, rather than assumptions about how the marketplace distributes inquiries.
Why it could change the decision
The same lead volume can behave very differently when multiple companies are competing for the same customer.
TimingHave both sets of leads had enough time to become completed work?
What we would check
Lead dates, booking dates, completion dates, and whether both groups are being measured across comparable observation windows.
Why it could change the decision
A younger group of leads can look weaker simply because some booked work has not been completed yet.
AttributionCan we trace the completed job back to the inquiry?
What we would check
The connection between the source, customer, booking, and completed job, including duplicate records and existing customers.
Why it could change the decision
A channel comparison is only as reliable as the link between the original inquiry and the work that ultimately closed.
RepeatabilityDoes the pattern hold beyond a few jobs?
What we would check
Additional periods, the number of completed jobs, unusually large outcomes, and operating conditions that changed during the comparison.
Why it could change the decision
A good result becomes more useful when the pattern survives another period instead of depending on a small number of outliers.
See it together
The first metric told one story.
The completed work told another.
| Measure | Aggregator A | Aggregator B |
|---|---|---|
| Paid lead spend | $4,000 | $4,000 |
| Qualified inquiries | 100 | 50 |
| Cost per qualified inquiry | $40 | $80 |
| Completed jobs | 24 | 28 |
| Inquiry → completed job | 24% | 56% |
| Lead spend per completed job | $166.67 | $142.86 |
| Completed revenue per job | $500 | $1,000 |
| Completed revenue | $12,000 | $28,000 |
| Completed revenue / spend | 3.0× | 7.0× |
More inquiries did not produce more valuable completed work.
Aggregator A generated twice as many qualified inquiries at half the cost per inquiry.
Aggregator B produced more completed jobs, a higher inquiry-to-completion rate, lower lead spend per completed job, and more completed revenue.
That changes the question. The next step is to understand why before moving the budget.
The number you optimize changes the decision.
Cost per inquiry answers one question.
Completed work, job value, margin, capacity, and repeatability answer others.
Plain Progress connects those parts before recommending where attention or budget should move.
Sometimes the question is what happened.
Sometimes you already know what needs changing.
How we work
Start where you actually are.
We can help you understand what’s happening or put an established decision into practice.
Start with Audit
Need to understand what’s happening?You need to understand what your business is doing.
We review the relevant information and your team’s context, explain what they support, and identify what deserves attention.
Start with Implement
Already know what needs changing?You already know what needs changing.
We build on what you’ve already established, agree on the work, and help put the change into practice.
See Services & PricingOr preview either route below.
Audit
Understand what deserves attention.
Implement
Make the agreed change.
Results
Review what happened.
Audit
Understand what deserves attention.
Begin with the question
What deserves attention?
Relevant information.
Your team’s context.
Further work is a separate decision.
Implement
Make the agreed change.
Begin with an established need
A change you’ve already defined.
Agreed work.
Clear responsibilities.
Results
Review what happened.
Outcome review
Compare what happened.
The goal. The starting point.
The outcome and its limits.
Further work is a separate decision.
Keep what works.
A useful answer shouldn't require you to replace the people and systems already serving your business. We agree on what needs attention and where our involvement makes sense.
Your business
Your team
- Your people
- Your tools
- Your processes
Scoped work
Scoped workRevise one service page.
- Scope defined
- Owner assigned
- Review date
Plain Progress provides scoped support.
Existing providers
- SEO agency
- Paid media partner
- Web developer
Scoped work
Align the handoff across providers.
- Scope defined
- Roles clear
- Review date
We can work alongside the providers already in place.
Working systems
- Call tracking
- CRM
- Scheduling
Scoped work
Tighten the handoff between systems.
- Scope defined
- Inputs mapped
- Review date
We can improve how the systems already in place work together.
A useful answer can stand on its own.
Use the findings with your team or an existing provider. A standalone diagnostic does not require a follow-on implementation project or retainer.
Good work stays in place.
Keep the people, providers, and systems that are serving the business. We define our role around the work that needs attention.
Agree on the work before it starts.
Any implementation has its own scope, responsibilities, and review point. A focused change can remain a focused change.
Your business stays in your hands.
You retain access to the accounts and information you own. Approval responsibilities are clear, and further work is a separate decision at the end of the agreed scope.
Know what deserves attention next.
Tell us what you're trying to understand or improve. We'll review the situation and see whether a diagnostic is a useful next step.