PermitGrab VS LayerStack Arm-based Cloud Server

PermitGrab's answer

Building permits are public record everywhere in the United States. Anyone can go and read them. In practice almost nobody does, because there is no such thing as 'the permit database' - there are hundreds of separate municipal and county systems, each on different software, each with a different schema, and most with no way to ask the only question a contractor actually cares about: what is new since yesterday?

So the information sits there, free and public, and the contractor who could use it finds out about the job weeks later, if at all.

PermitGrab exists to close that gap. The hard part was never getting a permit record. It was doing it every day, across hundreds of jurisdictions that change their endpoints without warning, and turning inconsistent municipal records into something a roofer can act on before breakfast.

PermitGrab's answer

PermitGrab combines three public records that are normally sold separately, or not sold at all: building permits, code-enforcement violations, and property-owner contacts. Most permit tools stop at the permit. Pairing a filing with the violation history on that property and the owner of record is what turns an address into a conversation.

The other difference is the delivery model. It is one ranked email each morning rather than a dashboard you have to remember to check, and it is a flat monthly rate rather than per-lead pricing. Leads are not resold, so you are not calling a homeowner who just heard from seven other contractors.

PermitGrab's answer

It depends what you are comparing against.

Against lead-generation marketplaces such as Thumbtack, HomeAdvisor or Angi: those sell you a shared lead that several contractors receive at once, priced per lead. PermitGrab is a flat monthly rate and the records are not resold, because they are public filings rather than a homeowner form submission. You are reaching out first instead of competing on response time.

Against construction data platforms such as BuildZoom, Shovels or ConstructConnect: those are generally built for enterprise research, analytics or commercial project intelligence, and are priced accordingly. PermitGrab is aimed at the individual contractor who wants to know what got filed in their city this morning, and it adds code violations and property-owner contacts alongside the permit rather than the permit alone.

Against checking the county portal yourself: the data is genuinely free and public. The work is that it is spread across hundreds of separate municipal systems with different formats, and none of them tell you what changed today.

PermitGrab's answer

Small and mid-sized contractors who sell into residential and light commercial work, and who do their own prospecting.

The clearest fits are roofing, HVAC, plumbing, electrical, general contracting, remodeling, restoration, solar, fencing, concrete and landscaping. A new-construction permit means every one of those trades has work coming. A re-roof permit means a solar installer has a fresh roof to quote.

It also works for building-material suppliers and manufacturer reps who want to know which builders are active in a territory, and for investors and agents who use code-enforcement records to find owners with a reason to sell.

It is a poor fit for anyone who needs national enterprise coverage with an SLA, or who wants commercial project intelligence at the pre-bid stage. That is a different product category.

PermitGrab's answer

• Python and Flask for the application and the collection daemons
• PostgreSQL for the permit, violation, contractor and property-owner records
• Render for hosting, split across a web service and a background worker
• Stripe for billing and Resend for the daily digest delivery

On the ingestion side the work is mostly adapters rather than a single framework. Municipal data arrives through ArcGIS FeatureServer and MapServer endpoints, Socrata, CKAN, Accela ACA portals, Tyler EnerGov self-service, OpenGov and a handful of one-off formats, so each source gets its own field mapping and freshness check.