Technical foundation
Monorepo, app shell, API structure, PostgreSQL/Prisma, auth, teams, Stripe billing, credit ledger, queues, Brevo and monitoring.
Interactive roadmap
The Citovera roadmap from foundation to market attack
This roadmap follows the architecture plan: first the technical foundation, then project data, content production, differentiation and finally AI visibility, agency workflows and API expansion.
Project and website data
Projects, domains, WordPress connections, GSC connections, crawl v1, URL inventory and technical SEO metrics.
Content production
Keyword import, briefing engine, AI gateway, editor, quality checks, versioning and WordPress draft publishing.
Differentiation
Internal link graph, content map, SERP analyzer, affiliate product blocks and content refresh agent.
Market attack
AI visibility, GEO workflows, agency operations, white-label reporting, ecommerce extensions and API access.
Sequence
What each phase has to prove before the next one starts.
The roadmap is sequenced to prevent building against ourselves. Data, billing, queues and measurement come before large-scale content automation.
Foundation first
Auth, teams, billing, credit ledger, queues, Brevo and monitoring are not back-office details. They decide whether the product can operate reliably.
Data before generation
Projects, domains, WordPress, GSC, crawl data and URL inventory create the context that makes content decisions useful.
Differentiation before scale
Internal links, content maps, SERP analysis, affiliate blocks and refresh workflows are the features that make Citovera more than another writer.
Market attack after proof
AI visibility, agency workflows, white-label, ecommerce and API expansion only make sense when the first workflow is already measurable.
Guardrails
What this roadmap deliberately prevents.
No blind bulk publishing.
No SEO page without useful product explanation.
Every major feature must connect to data, workflow, publishing and measurement.
Next step
The website has to model what the product will later automate.
FAQ
Roadmap questions
Why does Citovera start with infrastructure instead of AI features?
The architecture plan depends on teams, billing, credit ledgers, queues and monitoring. Without that foundation, expensive AI and crawl jobs cannot be controlled or priced safely.
When does the actual content workflow start?
The content workflow begins after project and website data are in place. That means WordPress, GSC, crawl data and URL inventory come before briefing, editor and publishing automation.
What makes Phase 4 important?
Phase 4 contains the differentiation: internal link graph, content map, SERP analyzer, affiliate product blocks and content refresh agent. This is what moves Citovera beyond a generic AI writer.
Does the roadmap include GEO and LLM visibility?
Yes. AI visibility and GEO workflows are part of Phase 5 after the core publishing and measurement workflow is stable enough to support market expansion.