Our Team
InternetProviders.ai is run by its two co-founders. We keep the team page honest: there is no large editorial staff behind the site — every rating rubric, guide, and data pipeline is owned by one of the two people below.
George Olfson
Editor-in-Chief & Co-Founder
George leads editorial strategy and content. With a background in technology journalism and consumer advocacy, he writes and oversees the blog posts, guides, provider comparisons, and educational resources on the site.
Full profile →Pablo Mendoza
Lead Analyst & Co-Founder
Pablo builds and maintains the platform, coverage data systems, and analytical tools. He designed the pipeline that turns FCC Broadband Data Collection records into the address-level availability results on the site.
Full profile →Who Is Responsible for What
Editorial content
George OlfsonBlog posts, guides, provider comparisons, and educational resources. George reviews provider ratings and comparison analyses before publication.
Data systems & location pages
Pablo MendozaThe data pipeline that processes FCC Broadband Data Collection records, plus city, state, and ZIP code availability pages built from that data.
Provider ratings
BothRatings follow our published weighted criteria. See our review methodology for how scores are produced.
Corrections
BothReader-reported errors are investigated by whichever founder owns the affected content area. Significant fixes are documented in our public corrections log.
How Our Content Is Produced
Two kinds of pages live on this site, and we think readers deserve to know the difference:
- Editorial pages — guides, comparisons, and reviews written and edited by the team, following our editorial policy.
- Data-driven location pages — city, state, and ZIP code pages generated from FCC Broadband Data Collection records and provider plan data using templates the team designs and maintains. Software (including AI tooling) helps us produce these at scale; the underlying availability data comes from FCC filings, not from the AI.
Contact
Questions or feedback for the team? Use our contact page or see how to report an error.