On this page
Career background
I started my career as a front-end web developer, first at a small SaaS startup called AuctionWagon, then at The Active Network where I worked on consumer-facing digital products. From there I moved into the public records data industry, joining The Control Group to build the user interfaces for consumer record search products.
That first role was entirely hands-on: writing code, building search flows, and improving how records surfaced in a way that regular people could actually use. Over time I moved into managing a team of developers, then into product leadership as VP of Product, and eventually into my current role as Senior Vice President. That progression matters because I have direct experience at every layer of how these products are built, not just how they are presented from the outside.
I have spent more than 13 years working on the same category of product. The specific record types, the data sourcing challenges, the jurisdictional gaps, the ways consumers misread or misuse results. These are things I have dealt with in a professional context for over a decade, and that depth of experience is what this site is built on.
What this role actually covers
As SVP, my work spans the full product and marketing organization. Day to day that means setting the multi-year product strategy and translating it into a roadmap with measurable outcomes across acquisition, conversion, retention, and lifetime value. I lead teams across Product, UX, CRO, CRM and Email, and Front-End Engineering, and I work closely with Analytics and Finance to build the decision framework those teams operate inside.
A meaningful part of the role is maintaining experience quality standards across consumer-facing products. That includes overseeing how records are displayed, how search results are contextualized, and what signals users need to interpret what they are looking at. I interact with a legal team daily that monitors public records law across all 50 states and surfaces anything that might affect product behavior or consumer guidance. That is not background reading. It is a direct input into what I publish here and how I frame the limitations of any given record type or state system.
Why the industry background matters for this site
Most public records content is written by people who have searched these tools once or twice. I have spent 13+ years building the products, testing the competitors, and monitoring the legal landscape that governs all of it. That difference shows up in the specificity of what I write, particularly around jurisdiction gaps, record type limitations, and the cases where official government sources and commercial aggregators diverge.
How I test people-search products
I have done extensive hands-on testing of every major people-search product on the market. That includes Infotracer, PeopleLooker, BeenVerified, Spokeo, PeopleFinders, CheckPeople, BrightCheck, Whitepages, and numerous smaller services that have come and gone over the years, in addition to Instant Checkmate, TruthFinder, Intelius, and US Search.
My testing methodology is consistent. I always start by comparing individual feature sets and pricing relative to what the major platforms offer. Then I run a search on myself and document the results in detail: how many phone numbers are returned, what percentage are accurate, and the same for email addresses, date of birth, relatives, and address history. I then search immediate family members, my wife, my parents, my brother, and evaluate the same data points. From there I move to second-degree connections like in-laws. By the time I have looked up 15 or so people across different demographics and life stages, I have a reliable picture of how a product actually performs rather than how it is marketed.
That process has given me something that is hard to replicate from the outside: a calibrated sense of where different products genuinely differ, and where the marketing claims do not hold up in practice.
What testing has taught me
Marriage records are the hardest category to get right
In my testing, marriage records are consistently the weakest area across most people-search products. The majority either do not carry them at all or return results that are too thin to be useful. The services that do it well are Instant Checkmate, TruthFinder, and Intelius. Their coverage is stronger in part because they have a data relationship with Newspapers.com. That relationship is not a secret. If you pull a report on either platform, you will see Newspapers.com linked directly inside the report for marriage record data.
One thing I have noticed consistently is that the coverage quality is not uniform. Records for older individuals tend to be more complete and accurate. For younger people with more recent records, the data appears to come from scraped public sources, which means it is patchier. This is worth knowing before you interpret a result as definitive.
When a people-search aggregator and an official government source diverge
I have done detailed testing on the San Diego County website for marriage and divorce records. The official county portal genuinely had more detail in many cases, with more complete filings and clearer case information. But the only reason I was able to use that portal effectively is because I already knew from running a people-search first that the person I was researching had lived in San Diego County when they filed. Without that jurisdictional anchor, I would have had no idea which of California's 58 county court systems to search.
That experience is what the "people search first" approach on this site is built on. The aggregator may not have every detail, but it gives you the location and identity context you need to find the actual record in the right official system. The paid service and the government portal are not competing alternatives. They are sequential steps in the same research process.
What this means for how I write
I do not write about these products as a neutral outsider comparing feature lists. I write from a position of having run the searches, hit the walls, and figured out the workarounds. When I recommend starting with a people-search aggregator before going to a county courthouse portal, that recommendation comes from testing the alternative and seeing where it breaks down without that first step.
Editorial approach
The content on this site is written to be useful first. That means explaining the strengths and limits of different sources honestly, including the cases where a free government resource will serve someone better than a paid platform, and the cases where it will not. I do not treat affiliate relationships as a reason to overstate what a product can do.
| Principle | What it means in practice |
|---|---|
| Specificity over generality | State and county pages reflect actual jurisdictional structure. Real courts, real portals, real coverage gaps. Not generic descriptions that could apply anywhere. |
| Honest limitations | If a record type is frequently incomplete, that is stated. If an official portal requires knowing the county before you can search, that context is given. |
| Sequential guidance | Research is usually a process, not a single lookup. Content reflects that by explaining what step comes before and after the one being described. |
| Transparency | Affiliate relationships are disclosed clearly. Placement and ranking may reflect those relationships, as noted in the disclosure on every page. |
| FCRA compliance | All content is scoped to personal research use cases. The services discussed here are not consumer reporting agencies and cannot be used for employment, housing, or credit decisions. |
How this site stays current
Public records law changes at the state level more frequently than most people realize. New expungement statutes, updated public records access rules, court system consolidations, and portal migrations all affect whether the guidance on a given page is still accurate. I stay current on this through daily involvement with a legal team that monitors legislative and regulatory changes across all 50 states and flags anything relevant to how these products and portals operate.
Portal links are tested programmatically every six months to verify that county and state court links are still active and pointing to the right resources. When a portal changes structure or moves to a new system, which happens with some regularity as older state court systems migrate to platforms like Odyssey or eCourts, those pages are updated to reflect the current access path.
Content is also updated when product behavior changes in a way that affects the guidance. If a platform's marriage record coverage improves or a state's court portal adds free public access to a record type that previously required an in-person visit, that context gets reflected in the relevant pages.
Important FCRA note
The people-search services referenced on this site are not consumer reporting agencies as defined by the Fair Credit Reporting Act. The information they provide cannot be used to make decisions related to employment, tenant screening, insurance, credit, or any other purpose regulated by the FCRA.
PublicRecordsService.org is an informational site focused on personal research and public records education. Every page on the site includes a disclosure and FCRA notice that reflects this scope. If you have questions about whether a specific use is FCRA-regulated, consult a qualified attorney. That determination is outside the scope of what this site covers.