Construction business development from permit data: a practical workflow
Short answer: Business development teams use permit data to identify new projects, qualify whether they match the firm, map owner and architect relationships, and start outreach before opportunities become crowded. The workflow: find recent filings, filter for fit, identify decision-maker signals, prioritize outreach, and track the pursuit.
- BD managers: build a weekly pipeline of projects worth pursuing.
- Preconstruction leaders: identify opportunities before estimating starts.
- Owner-operators: run a repeatable BD motion without a full BD team.
Why BD teams use permit data
Most contractors hear about projects through relationships, bid lists, brokers, architects, owners, or public bid platforms. Those channels are useful, but they often arrive late. Permit filings can show activity earlier: the owner has taken a step, the architect or applicant may be named, the scope is described, value may be declared, and the location is known.
The workflow
- Define what a good project looks like. Examples: commercial TI over $500k, multifamily renovations, facade and envelope work, mechanical upgrades, restaurant buildouts, soft-story retrofits, new build residential over $2M, or specific neighborhoods. If the fit criteria are vague, the feed becomes noise.
- Pull recent filings. Focus on the last 7 to 30 days. Prioritize filings that are recent, meaningful in value, clear in scope, in your service area, and tied to a real owner, applicant, or architect.
- Score for fit. Consider location, project type, scope, value, owner signal, architect signal, GC or buyer signal, permit stage, filing freshness, and relationship history. This keeps the team from chasing everything.
- Decide the outreach path. Owner named and no GC named: consider owner or architect outreach. GC named: for subs, consider GC outreach. Multiple related filings: check whether a larger project is forming.
- Write project-specific outreach. Reference the filing and ask a careful question.
- Track the pursuit. A filing should create a pursuit record: project, owner, architect, GC or buyer signal, outreach date, response, follow-up date, status, and reason won, lost, stale, or not a fit.
See today's top-graded filings before they issue
PermitPipeline scores new permit filings and emails contractors only the leads worth pursuing, matched to your trade and market.
Start 14-day free trial →A weekly BD rhythm
Monday: review new filings and pick the top 10. Tuesday: research owner, architect, and GC signals. Wednesday: send project-specific outreach. Thursday: follow up and update pursuit status. Friday: review what turned into conversations. That is how permit data becomes business development, not browsing.
- Find recent filings in your market.
- Score each for location, type, scope, value, and decision-maker signals.
- Decide the outreach path from who is named.
- Reach out with a project-specific reason.
- Track the pursuit before the filing goes stale.
How PermitPipeline fits
PermitPipeline ranks new filings so BD teams do not start from raw city portals. The Daily Project Brief surfaces projects by fit, timing, value, scope, and who is already involved, so a BD or precon person can answer one practical question each week: which projects are worth action now?
See what's getting filed in your city, every week
Permit Insights is our free weekly brief: what just got filed, where the work is, and what the data shows.
Want live projects in your market?
Tell us your city and trade. We'll send 3 current matches, no card needed.
Request 3 sample projects →