SaaSInspector.
Built because comparing software meant fifteen browser tabs.
A directory of SaaS tools, arranged around comparison rather than ranking. Put any set of them side by side and the differences are on one screen, in the same rows, in the same order.
- Role
- Sole engineer
- Live site
- saasinspector.com ↗
- Built for
- Comparison side by side
- Status
- In production
saasinspector.com · homeFig. 01
I like this stuff. Trying new software for the business is something I do constantly, and AI has turned that from an occasional afternoon into a weekly one. Half of what I read about never gets used, but knowing what is out there is the part of the job that pays for itself.
Directories are not scarce. What is scarce is comparison that answers the question you actually have. If you want to know how two tools differ on one specific thing, the pricing tiers, the integrations, the export limits, the language support, you end up with a dozen tabs open, reading two marketing pages written to avoid exactly that comparison, and guessing.
SaaSInspector is built the other way round. The comparison is the product and the reviews sit underneath it, so the answer arrives as a difference you can see rather than as two pages you have to hold in your head at once.
Side by side, not a leaderboard.
A single ranked list is the least useful thing a directory can hand you, because the right tool depends entirely on what you are doing with it. Tools are scored against criteria written for their own category rather than against one global number, so a video tool is judged on the things a video tool has to get right.
Collect any set of tools and they line up column by column, the same fields in the same order, including the ones where the answer is that the vendor does not say. Around it sits the ordinary work of a site people use: instant search across the whole catalogue, saved favourites, category pages that stand on their own, and a news section for the launches worth knowing about.
Try the comparison ↗Most of the reading happens on a phone.
The catalogue, the categories and the news follow the viewport, and the theme follows the system. Comparison is the one screen that genuinely wants width, so it takes up to five tools at a time rather than pretending an unlimited table will ever fit on a handset.
saasinspector.com on a phoneFig. 02
Front end
Next.js 15 · App Router
React 19 · TypeScript 5.7
Tailwind CSS 4
Data
Supabase · Postgres
Client-side search index
Structured tool schema
Delivery
Vercel
Server components
Light and dark themes
Structure
Criteria per category
Comparison sets
Category and news pages
Also built: a Chrome extension, and an internal admin nobody but me sees.