Sign in

The SEOFUXX roadmap

From a working foundation through a controlled beta to a stable product. Our priorities are reliability, measurable value, and honest feedback.

View the next milestone Share beta feedback

Proposal based on the project status as of August 27, 2026 · The order and scope may change in response to beta findings.

From the foundation to a robust product

Each section ends with a verifiable gate. The next phase becomes the focus only after that gate has been met.

1 Achieved

Foundation · current status

Technical foundation in place

The core components for a robust beta are in place. The focus is now shifting from adding features to stability, guidance, and measurable user feedback.

  • On-page analysis, Page Audit, crawler, sitemap, SERP data, and keyword data
  • Customer dashboard with metrics and historical score trends
  • Accounts, plans, invoices, personal API keys, and MCP access
  • Security foundation with centralized secrets management, 2FA, and passkeys
  • Automated unit, integration, API, and browser tests
  • AI visibility foundations: data model, measurement definition, provider layer, and prompt management
2 Up next

Milestone 1 · Beta readiness

Prepare the closed beta

The next meaningful milestone is not a broader feature set, but a reliably testable core product for a limited group of real users.

  • Define the key user journeys: register, create a project, start an analysis, understand the result, and identify the next action
  • Harden error handling, queues, timeouts, and retry logic for analyses and crawlers
  • Establish monitoring, structured logs, backups, recovery, and a documented rollback process
  • Review permissions, rate limits, uploads, dependencies, and privacy flows in a targeted manner
  • Complete onboarding, in-app help, and the existing bug and UX feedback channel for testers
  • Freeze the beta scope and clearly mark unfinished or unreliable features as experimental
Decision point: Exit: All core journeys run reproducibly, there are no known critical errors, monitoring and rollback are ready, and beta feedback can be prioritized consistently.
3 Planned

Milestone 2 · Closed beta

Validate with real projects

A small, supported group of testers evaluates value, clarity, and reliability under real-world conditions. New features are added only when they solve an observed problem.

  • Invite 20 to 30 suitable testers in stages and support them actively
  • Measure activation, successful analyses, error rate, processing time, and repeat usage
  • Validate result quality and recommendations professionally using real websites
  • Review feedback weekly: critical, blocking, frequent, valuable, and later
  • Systematically improve mobile usability, accessibility, and clear error messages
  • Derive documentation and support processes from the most common questions
Decision point: Exit: At least four stable weeks of testing, at least 95% successful core analyses, no unresolved critical bugs, and clearly demonstrated recurring value for the target group.
4 After that

Milestone 3 · Public beta

Open scalable access

After product validation, the beta opens to a wider audience. Self-service, cost control, and operational processes must now work without direct guidance.

  • Fully test self-service onboarding, plan limits, billing, and cancellation paths
  • Publish status communications, support targets, and transparent release notes
  • Run performance and load tests for analysis, crawlers, external providers, and background jobs
  • Complete API and MCP documentation and version public interfaces
  • Gradually release AI visibility measurement runs, provider execution, and robust comparison reports
  • Repeat privacy, security, and operational reviews before opening access
Decision point: Exit: Onboarding and payment work without assistance, operations withstand the defined load, and support and incident communication have proven effective in everyday use.
5 Target state

Milestone 4 · Version 1.0

Release a stable core product

Version 1.0 represents a reliable core product with clear pricing, not the end of development.

  • Document the committed feature set and supported integrations
  • Define service targets for availability, job runtimes, backups, and support
  • Complete an independent security review and full recovery test
  • Safeguard migrations, data export, account deletion, and billing for regular operations
  • Establish product metrics and a fixed release cadence for continued development
Decision point: Exit: The core scope is stable, secure, documented, economically viable to operate, and can be supported sustainably for paying customers.

Topics beyond the stable core

These topics are valuable, but will only be scheduled once beta data confirms their benefit.

Expand AI visibility

More providers, recurring measurements, competitor comparisons, source analysis, and actionable, transparent recommendations.

Reports & collaboration

Exports, shareable reports, comments, roles, and recurring client reports for teams and agencies.

Expand integrations

Search Console, notifications, webhooks, and additional interfaces, prioritized according to actual beta demand.

The beta is built with users

Found a bug, an unclear flow, or a missing core feature? Your feedback influences what we prioritize next.

Send beta feedback Contact us

Was this content helpful?

·