A multi-tenant SEO monitoring SaaS with the commercial machinery attached
- Role
- Product definition, UX, data architecture and build
- Years
- 2026
- Status
- Deployed MVP in user testing
- Stack
- Next.js, Postgres, DataForSEO, Stripe, OAuth
Ranking data is cheap to display and expensive to collect, which is what makes SEO monitoring a genuine product problem rather than a dashboard exercise. RankPass combines scheduled collection, ranking analytics, Google data pipelines, subscriptions, cost controls, customer dashboards and an operator console in one connected system.
The problem
Monitoring rankings at any scale means paying per query to an external data provider on a schedule, for many keywords, across many customers.
That turns an apparently simple product into a cost-control problem: without frequency awareness and usage limits, the margin disappears quietly and only shows up on the invoice.
The insight
The interesting engineering is not the chart. It is the scheduling, the tenancy and the spend controls that make the chart affordable to produce.
Building the operator console alongside the customer product meant the commercial model was visible during development rather than discovered afterwards.
What I built
- Frequency-aware scheduled workflows collect ranking data on a per-plan cadence with explicit paid-API cost controls.
- External integrations, OAuth foundations, signed payment webhooks and lifecycle email are wired into a multi-tenant data model with isolation between customers.
- Customer dashboards cover keyword management, rankings history and multi-domain management.
- An operator console exposes plans, usage costs, subscriptions and system health on the same data.
Key decisions
Cost per tenant treated as a product constraint
Collection frequency is bound to plan level, so the unit economics are enforced by the system rather than by hoping customers behave.
Operator console built in parallel
Running a SaaS needs a view of plans, spend and health. Building it alongside the customer product kept the commercial model honest.
Forked deliberately from an existing foundation
RankPass was forked from REEI OS. Reusing the tenancy, monitoring and analytics groundwork was a deliberate choice, not a coincidence of two similar products.
Gallery
Customer dashboard
Proves: Productised reporting experience
Status and evidence
- Deployed and in user testing.
- Product definition, UX, data architecture, the SaaS commercial model and deployment design were my own work.
What this does not claim
- RankPass has no language-model or AI functionality. It is automation, analytics, API integration and product engineering, and calling it AI would be inaccurate.
- No users, revenue, ranking accuracy or customer outcomes are claimed.
- It is an MVP in testing rather than a commercially finished product, and not every advertised plan feature is fully enforced yet.