Deal Radar
Construction jobs leave a trail before they show up in the market. Deal Radar finds them and tells a contractor when to move.
Visit dealradar.dev → Data products company
We turn unusable data into products.
We monitor government and private-sector sources the moment they change, connect what we collect into data that exists nowhere else, and build the products that put it to work.
Live feedIllustrative
New permitCommercial tenant improvement, 12,400 sq ftLicense issuedMechanical contractor, new registrationPlan checkMultifamily, 36 unitsEntity resolved6 records linked to one companyFiling changeRegistered agent updatedGrading permitRetail pad, new constructionInspection passedFraming, commercial shellSource repairedExport format change detected and handledNew permitCommercial tenant improvement, 12,400 sq ftLicense issuedMechanical contractor, new registrationPlan checkMultifamily, 36 unitsEntity resolved6 records linked to one companyFiling changeRegistered agent updatedGrading permitRetail pad, new constructionInspection passedFraming, commercial shellSource repairedExport format change detected and handled
Infrastructure
Data that does not exist anywhere else until we build it.
Our datasets are assembled by acquisition systems we built, running on infrastructure we own, watching sources we choose.
Self healing
A renamed column, a moved form, an export that quietly changes shape. The engine detects the break, adapts and keeps running.
How it works →Real-time monitoring
Government agencies and private-sector sources are watched continuously. Changes are seen as they happen, not in next quarter's dataset.
Our standards →Products
Deal Radar
In build
DeliveryFeedback
SentientData Engine
Acquire
Monitor
Resolve
Repair
SignalsChanges
Sources
Government
Private sector
Proprietary acquisition
Collection systems are built in house and run on hardware we own. The methods stay internal, which is why this page describes what they do and not how.
About the company →Data that compounds
Every change is kept, and our products generate data of their own. You cannot buy last year's changes today if nobody was watching.
See the products → The problem
"One company. Six spellings. No shared identifier. That is what raw data looks like before the engine touches it."
Illustrative exampleIncoming recordsResolving
- MERIDIAN MECH & HTG INCLicense board
- Meridian Mechanical and Heating, Inc.Secretary of State
- MERIDIAN MECH HTGCity permit
- meridian mechanical incBusiness license
- MERIDIAN MECH & HEATING INC.County record
- Meridian Mech. & HtgInspection log
One entity
Meridian Mechanical & Heating, Inc.
- Records
- 0 linked from separate systems
- Status
- Active
- Latest
- New permit activity, filed today
Illustrative example. Not a real company.
Point it at a market. It runs itself.
HoursFrom a source changing to our products knowing about it
ZeroPeople needed to keep a feed alive
OneEngine behind every product we build
New signalToday
Commercial permit filed
Tenant improvement, 12,400 sq ft
Owner resolvedEarly stageUpdateYesterday
Plan check submitted
Multifamily, 36 units
Contractor linkedUpdate2 days ago
Grading permit issued
Retail pad, new construction
Illustrative. Not live data.
How we operate
You cannot buy history after the fact. So we never stop recording it.
Every product starts from everything the engine already knows. Four rules keep it that way.
Show the source
Every value we publish can be traced back to where it came from.
Narrow on purpose
A product does one job for one kind of customer, well enough to become part of their week.
Solve it once
When two records are the same company, that answer is kept. Nobody untangles the same mess twice.
Plan for change
Sources change without notice. We design for that on day one, not month three.
Products Live In build Partnerships
What the engine is powering today
Next product
More products are in development on the same engine. We name them when they ship.
Stay in touch →Work with us
You hold data we should know about, or you see a way to build something together.
Start a conversation →Frequently asked questions
Where does your data come from?
From government agencies and private-sector sources, collected by acquisition systems we build and run on our own infrastructure. The collection, and the history it builds up over time, are ours.
How current is it?
Sources are checked on a loop measured in hours. A record reaches our products as soon as practical after the agency publishes it.
What happens when a source changes its format?
The engine is built to notice when a source changes shape, adapt to it and keep running. Changes like that are the most common reason data feeds fail quietly, so we treat them as routine rather than exceptional.
How do you decide what to build next?
We look for industries where the records already exist, the people who need them cannot practically use them, and a focused product can prove itself quickly. We announce products when they launch.
I think something about my business is wrong. What do I do?
Email [email protected] with what you are seeing and where. We will check it against the original record and follow up.