“JobNimbus already reports on the pipeline.”
It does, thoroughly. It has no record of the canvasser, ad or storm list that produced the contact.
For JobNimbus
Export collected work from JobNimbus, upload the leads behind it, and rank channels on the stage that actually pays.
CloseRev reads a JobNimbus export of invoiced or collected work — the customer's phone or email, the amount and the date — and matches it against the canvassing, calls and ads that produced the lead. JobNimbus tracks a job from lead through sold to built, and the gap between those stages is where a contractor's real economics live. Revenue with no traceable lead is reported as Direct / Unknown.
Page updated September 25, 2026.
The gap
The pipeline says sold. The crew calendar says otherwise, and the bank says something else again.
What was sold, to whom, and for how much.
The click, the keyword, the call, and what each one cost.
The file
Three things carry the match: who, how much, and when. Anything else is optional and only changes how the report can be sliced.
On the contact record. Phone carries the match in this trade, canvassed leads included.
What was received. A signed contract is a stage and a percentage of them never get built.
When money arrived. The lead date belongs in the lead file; the gap can run to months on insurance work.
Retail or insurance, mapped as Product / service. The workflow stage is not read; append it to the campaign value if you want to see where jobs stop.
Step by step
Written for somebody with JobNimbus open in the next tab. Report names vary by edition, so each step says what to look for.
One row per payment with a customer contact detail, the amount and the date.
Keep them in the lead file, out of the sales file. They are a real cost — a measure-up, a contract, sometimes a deposit refunded — and they can cluster by source.
Map the job type as Product / service. Their values are set by different people on different timelines, and averaging them describes neither.
Canvasser codes, tracked numbers, search and social, storm lists and any marketplace you buy from.
The join runs on the phone and the email, normalized; the matched-records export carries the lead date beside each payment.
What comes back
Revenue by channel, the count of sales behind each figure, and an honest bucket for the ones nobody could trace. Sample figures, from the worked example on the Roofing Contractors page — not from a JobNimbus account.
| Channel | Share | Sales | Revenue |
|---|---|---|---|
| Google Ads | 19 | $342,000 | |
| Meta Ads | 9 | $153,000 | |
| Email marketing | 3 | $45,000 | |
| Direct / Unknown | 21 | $360,000 |
Unmatched sales stay in Direct / Unknown. They are never spread across the paid channels to make the total look better.
The argument
A job can be sold and then die: the adjuster reduces the scope, the homeowner changes their mind, the mortgage company sits on the check, the crew never gets scheduled.
Every one of those has already consumed a measure-up, a sales appointment and a contract, and none of them produced revenue.
Ranking channels on sold jobs therefore rewards whichever source produces the most contracts, not the most roofs, and the two lists are different.
Keeping every lead in the lead file, sold-and-never-built included, sets each source's leads beside its collected jobs, which is the number worth acting on.
It can be a process finding rather than a channel one: append the stage a job died at to the campaign value and the drill-down shows where each source's jobs stop.
On an insurance job the price is set by an adjuster, the timeline is set by a carrier, and the contractor's sales process is mostly about documentation.
On a retail job the price is the contractor's, the timeline is the homeowner's, and the sale is a sale.
Blending them produces an average value that describes neither and a conversion rate that moves with the weather rather than with the marketing.
Mapped as Product / service, a job type lets the report cut revenue by it, and the matched-records export pairs each payment with its source.
The sources feeding each may barely overlap, which would argue for two budgets rather than one.
Door-knocking can produce a large share of exterior work in storm markets, and the cost of it — wages, commission, vehicles — is entirely knowable.
Because it is a payroll line rather than an advertising invoice, it sits outside the marketing report and is never ranked against paid search.
Canvassing as a source in the lead file, with the canvasser code as the campaign, puts it into the same comparison on the same collected revenue, against what it genuinely cost.
The finding can be about which crews and neighborhoods produced collected work rather than signatures — with them in the campaign column — which changes next season's plan more than a channel ranking would.
A hail event fills the pipeline for two weeks. Those leads arrived because of the sky, and crediting them to whatever campaign happened to be running produces a conclusion that will not repeat.
Reading those weeks separately — through a job type or insurance flag mapped as Product / service, or by narrowing the report's date range — keeps the rest of the year honest.
The point is not to discard the revenue, which is real, but to stop it being used as evidence that something works.
A contractor who does this consistently ends up with a defensible picture of the baseline, which is the thing that decides whether to spend in a quiet season.
It also stops the reverse error, which is cutting a channel that looked poor during a month when every crew was busy with storm work and nobody answered the phone. That is a capacity problem wearing a marketing problem's clothes.
Fair questions
It does, thoroughly. It has no record of the canvasser, ad or storm list that produced the contact.
Sold is a stage, and a percentage of sold jobs never get built. The channels differ on that percentage.
Then map the job type, and the retail figures become readable for the first time.
No. It reads an exported file, so your boards, documents and photographs stay where they are.
Collected work with a customer contact detail, the amount and the date.
A share of them never get built, and that share differs by source. Ranking on contracts rewards whichever channel produces the most paperwork.
Yes, in the lead file. Each consumed a measure-up and a sales appointment, and they can cluster by source.
Yes, mapped as Product / service where the export carries a job type, and they should be — different price setters, different timelines.
Yes, as a source in the lead file with the canvasser code as the campaign, ranked on collected revenue to set against its payroll cost.
Through a job type or insurance flag mapped as Product / service, or a narrower date range, so weather is not mistaken for marketing.
A year; there is no window to set. Seasonality and insurance timelines both make anything shorter a comparison of conditions.
From the matched-records export, which carries the lead date; the report dates by payment. That grouping is what makes a seasonal budget decidable.
Anything with no traceable lead — untracked calls and referrals included.
A contact detail, an amount and a date, plus a job type if you include one. No property addresses required, no photographs, no claim documents. Encrypted in transit and at rest and deleted with the import.
Collected revenue per source with its leads beside it, insurance and retail apart where mapped, and everything unmatched kept visible.
By trade
What the report looks like once the export is in, written for each one.
Other systems
Running more than one system, or comparing? The method is the same and the columns are not.
JobNimbus and the other product names and logos on this page belong to their owners and are shown to identify the software a file comes from. CloseRev is not affiliated with or endorsed by them, and connects to none of them: it reads a file you export.
From the blog
Multi-crew home and field services businesses run on phone calls and job management software, not on web forms. Which means the standard marketing dashboard is measuring the smallest part of the business and missing where the money actually is.
Read the articleCall tracking answers one question well: which campaign produced the ring. It has no view of what happened after the call ended, which is where the money is decided. This is what the gap costs, and how to close it without replacing the call tracker you already have.
Read the articleThe export is the part of an attribution project that everyone treats as trivial and that determines whether the whole thing works. Here is the field list, the date-range trap, the deduplication rule, and the six columns to leave out on purpose.
Read the articleStart today
Nothing to install in JobNimbus, no API key, and no need to have been tracking anything until now. Last year works as well as this month.