1. The default mistake
Most trade contractors who buy a permit-intelligence feed go through the same arc: they're excited the first Monday when the Excel lands, they look at maybe 20 rows, they call 2-3, the CRM never gets updated, and by Wednesday the spreadsheet is buried in their inbox. Six weeks in, the subscription gets cancelled because "it didn't work."
The feed is fine. The workflow was missing.
This guide walks the 5-step CRM workflow that turns weekly permit Excel into booked jobs, and the disciplines that make it stick.
2. Step 1 — Import discipline
Every Monday, every permit row gets a CRM record. Not "the interesting ones." All of them in your service area.
Why: a permit you skip in May because it didn't look interesting becomes interesting in August when their MEP rough-in window opens. If you didn't log it, you'll forget. The cost of one extra CRM record is zero. The cost of missing a $50K job because you never logged the permit is $50K.
Practical setup:
- One CRM record per permit, named by address + permit number
- Standard fields: address, project value, applicant, contractor, work class, permit date, expected MEP date, next-call date
- Tag every record with "Permit feed" so you can filter / report later
3. Step 2 — Phase-based scheduling
The "when to call" column is the highest-value field in the feed. Use it to set next-call dates in your CRM, not to call right now.
For each row, calendar:
- The primary calling window for your trade (based on the row's "when to call" value)
- A secondary follow-up 4 weeks after the primary, in case the project slipped
- A tertiary end-of-project check for service / maintenance cross-sell
Now your CRM tells you what to do each morning instead of you sorting through old emails.
4. Step 3 — First-contact discipline
When the next-call date fires, the call has to be personalized to the specific permit. The exact opening that converts:
"Hi [Name], I'm [You] from [Company]. I saw you pulled permit [BP-number] for [address] for a [project type]. I'm [your trade], we serve [their area]. I noticed your frame inspection is probably scheduled for [week X] — I wanted to reach out before you finalize the mechanical scope. Do you have a couple minutes?"
Why this works:
- You reference the specific permit — proves you're not cold-calling random numbers
- You name the right phase — proves you understand their schedule
- You offer to add value before they've committed — gives them a reason to talk
- You ask for a short window — easier to say yes
5. Step 4 — Disposition discipline
Every call gets a CRM disposition. Standard set:
| Disposition | Next action |
|---|---|
| Connected · interested | Calendar quote walk-through within 1 week |
| Connected · not interested | Mark closed-lost, log reason |
| Connected · already-have-vendor | Calendar a follow-up at end-of-project for service |
| Voicemail · 1st | Calendar retry 3 days out |
| Voicemail · 2nd | Send email, mark dormant for 90 days |
| No answer | Calendar retry next business day |
| Wrong number | Re-research, update CRM |
The disposition is what turns a one-time spreadsheet read into a pipeline. Without dispositions, you can't measure conversion, you can't compare reps, you can't see what's slipping.
6. Step 5 — Weekly review
Every Friday, 30 minutes:
- How many calls did we make from this week's permit feed?
- How many connected?
- How many converted to quote requests?
- What's the per-call cost? (subscription cost ÷ calls made)
- What's the per-quote cost? (subscription cost ÷ quotes generated)
After 6 weeks of data, you'll know exactly what your trade × city × feed conversion looks like. That's the number that justifies (or kills) the subscription.
7. Tooling that works (and what doesn't)
You don't need an expensive CRM. What matters is import speed, calendar discipline, and disposition tracking.
| Tool | Works? | Why |
|---|---|---|
| Pipedrive ($14/user/mo) | Yes | Cheap, fast import, calendar baked in |
| HubSpot Free | Yes | Free tier covers up to 1,000 records |
| Zoho One ($45/user/mo) | Yes | If you need wider toolkit |
| Salesforce | No | Overkill, slow, expensive for a trade contractor |
| Excel only | No | No reliable date triggers, no disposition discipline |
| Spreadsheet + Google Calendar | Maybe | Works for 1-person ops, breaks at 2+ reps |
8. Common pitfalls
- Importing manually each week. Use the CRM's CSV import feature; map columns once, re-import every Monday.
- Forgetting to dedupe. If a permit shows up two weeks in a row (some feeds re-emit), match on permit number not name.
- Calling everyone immediately. Spreads your effort across rows that aren't ready. Trust the phase logic.
- Not assigning ownership. If 2+ people share a feed, every row needs an owner.
- Treating closed-lost as final. A "no" today is "yes" in 18 months when their next project starts.
9. The honest math
A working contractor running this workflow on the Shovel Radar Calgary vertical bundle ($349/mo) gets ~50 trade-routed rows per week, ~200/month. At 5% connection-to-quote and 25% quote close rate, that's:
200 rows × 5% × 25% = 2.5 closes/month
At a $10K average deal: $25K/month gross. At 25% margin: $6,250/month profit. Subscription cost: $349. Net: ~$5,900/month or 17× ROI.
The workflow is what converts the math from theoretical to actual.
10. Further reading
- When to Call: Construction Phases
- CASL Compliance Guide — for your outreach process
- All trades — pick your trade for phase-specific timing
Use the playbook
Shovel Radar gives you the trade-routed permit feed this guide describes.
Weekly Excel. 382 Canadian cities. Same playbook, scaled.
Get a 5-row sample · no credit card