Enterprise & data licensing
License the deepest, freshest Arizona construction dataset.
Permits, the AZ ROC contractor roster, parcels and sales — fused into one graph, refreshed daily, and delivered in bulk to your warehouse. Power your sales org, your underwriting model, or your own product, with the right to build on it.
Latest permit in the feed: Jun 23, 2026 · 286 new in the last 7 days — this is a live, daily-moving dataset.
Self-serve is the product. Enterprise is the data.
The dashboard ($199/seat) and the API ($499/mo) are for using Plumb. The data license is for building on it — bulk, embeddable, and contracted.
| Self-serve API — $499/mo | Enterprise data license | |
|---|---|---|
| Access | Rate-limited REST (10K/day) | Bulk delivery + warehouse share + high-limit API |
| Scope | Query as you go | Full filtered dataset, nightly |
| Redistribution | Not permitted | Licensed — embed / resell |
| Delivery | JSON over HTTPS | CSV/Parquet to S3/GCS, or Snowflake/BigQuery share |
| SLA & support | Best-effort | Uptime + freshness SLA, dedicated contact |
| Security | API key | SSO, security review, DPA |
| Contract | Self-serve, monthly | Annual, signed MSA |
Just want to query it yourself? The self-serve API or a Pro plan may be all you need.
What’s in the feed
Five fused layers. License all of it, or just the tables and jurisdictions you need.
Permits
permit number, type, work class, description, valuation, square footage, lifecycle stage, lead score, applied/issued/finaled dates, full address, normalized APN, lat/long, jurisdiction, source lineage
Contractors (AZ ROC)
license number, business name, DBA, ROC classification + class detail, status, issue/expiration dates, qualifying party, disciplinary actions, unlicensed-violator flag, phone/website/rating where enriched
Property (Maricopa Assessor)
APN, owner of record, owner mailing address, property type, land use, year built, living area, total sqft, units, acres, assessed value, full-cash value, subdivision
Sales / transactions
APN, sale date, sale price — for the “sold but no permit yet” renovation signal
Derived intelligence
permit↔contractor linkage + match confidence, multi-permit project clusters, contractor relationship graph (who works with whom), inferred purchasing profiles, lead scores, daily demand signals
The fusion is the hard part — and the moat: every permit named to the licensed contractor who pulled it, vetted against the ROC roster, clustered into real projects. See how the data is built →
Licensing packages
Priced on breadth of use, not row count. Annual terms; prepay is discounted.
Data Feed — internal use
Nightly bulk delivery or a warehouse share, used inside your own organization — analytics, territory planning, demand forecasting, underwriting.
- ✓Full filtered dataset, refreshed nightly
- ✓Bulk file or Snowflake/BigQuery share
- ✓Uptime + freshness SLA, dedicated contact
- ✓No redistribution
Embed / Redistribution
Everything in the internal feed, plus the licensed right to incorporate the data into a product or service you offer to third parties.
- ✓Redistribution & embed rights (with attribution)
- ✓Higher / uncapped API limits
- ✓Joint go-to-market on request
- ✓Priority support + roadmap input
Full-market / custom
Multi-county as we expand, exclusive verticals, white-label, custom enrichment, or one-off historical extracts.
- ✓Exclusivity options
- ✓Custom fields / enrichment
- ✓White-label delivery
- ✓Annual or multi-year terms
Who licenses the data
Material distributors & manufacturers
The pain: Demand and territory planning across dozens of reps — you can’t seat everyone or pull leads by hand.
What you get: The full demand picture — who’s building, where, at what value, and which licensed contractor pulled it — piped into your CRM/BI for the whole sales org. Rank every GC by inferred material spend.
Surety, insurance & contractor-credit underwriting
The pain: Underwriting and monitoring contractors on thin, stale signals.
What you get: License status + the AZ ROC disciplinary / unlicensed overlay + permit volume, velocity and project mix as underwriting and portfolio-monitoring inputs. Daily updates flag a revocation or activity drop before you’re exposed.
Proptech / contech / SaaS platforms
The pain: A national product with thin or absent Arizona coverage — and building AZ ingestion yourself isn’t worth it.
What you get: License our AZ layer under the redistribution package and ship Arizona coverage overnight — permits, contractors, and the fused intelligence — without standing up pipelines.
Market research, PE & construction lenders
The pain: Market sizing, deal diligence and lending decisions on AZ construction with no ground truth.
What you get: Construction-market intelligence plus contractor diligence — is this GC real, licensed, clean and growing? — for investment, M&A and lending.
Delivery, your way
Nightly bulk file
CSV or Parquet pushed to your S3 / GCS bucket. The simplest option, and what most buyers start with.
Warehouse share
A live Snowflake, BigQuery, or Databricks Delta Share — no ETL on your side, always current.
High-limit / uncapped API
The same v1 REST API as self-serve, with raised or removed rate limits, for buyers who prefer to pull.
How onboarding works
- 1Scoping call
We confirm internal-use vs. redistribution (this sets the package), the jurisdictions, date range and fields you need, and your delivery preference.
- 2Sample & evaluate
We send a sample extract or sandbox access so your team can validate fit against your own systems before you commit.
- 3MSA + setup
Sign the agreement, configure delivery (bucket, warehouse share, or API keys), and complete any security review / DPA. One-time onboarding gets schema mapped.
- 4Nightly delivery
Fresh Arizona data lands every day, with an uptime + freshness SLA and a dedicated contact for changes and questions.
Typical time from first call to first delivery: 1–2 weeks.
Coverage & quality
| Phoenix · Mesa · Scottsdale · Tempe · Gilbert · Peoria | Daily |
| Maricopa County (unincorporated) | Weekly |
| AZ ROC contractor roster | Continuous overlay |
| Maricopa Assessor + property sales | Master refresh + daily joins |
| Chandler · Glendale · Surprise | On the roadmap (records requests filed) |
Coverage is Maricopa County (Phoenix metro) today; Pima and Pinal are on the roadmap. Source records are public; the value — and what you license — is our fusion, freshness, and the right to redistribute. Data is provided for your verification against the authoritative government source.
Common questions
How is this different from the $499 self-serve API?
The self-serve API ($499/mo) is rate-limited REST for querying as you go, and its terms prohibit redistribution. The data license adds bulk / warehouse delivery of the full filtered dataset, an uptime + freshness SLA, security review / DPA, and — on the redistribution package — the licensed right to embed or resell the data in your own product.
Can I resell or embed the data in my own product?
Yes, under the Embed / Redistribution package. Internal-use feeds may not be redistributed; the redistribution license grants the right to incorporate the data into a product or service you offer to third parties, with attribution and reasonable caps spelled out in the MSA.
What areas do you cover?
The Phoenix metro across Maricopa County — six city permit feeds plus unincorporated county, the statewide AZ ROC contractor roster, and Maricopa Assessor parcels and sales. Additional jurisdictions (Chandler, Glendale, Surprise) and counties are on the roadmap; ask about timing for your market.
How fresh is the data, and how is it delivered?
Permits refresh daily. We deliver as a nightly CSV/Parquet file to your cloud bucket, as a live Snowflake / BigQuery / Databricks share, or via a high-limit API — your choice.
How is it priced?
Internal-use feeds start at $2,000/mo ($24K/yr); redistribution licenses start at $5,000/mo ($60K/yr). Pricing scales with breadth of use (internal < embed < redistribute) and the size of the audience you serve, not raw row count. Annual prepay is discounted.
Do you handle security reviews, a DPA, and procurement?
Yes — SSO, security questionnaires, a data-processing agreement, and standard procurement / invoicing are all part of the Enterprise motion.
Tell us what you’re building.
A short scoping call tells us internal-use vs. redistribution, your jurisdictions and fields, and how you want it delivered. We’ll send a sample to evaluate.