IYABOKO Sentinel SaaS Roadmap
A phased roadmap for turning IYABOKO Sentinel Continuity OS from a WordPress product family into a serious online readiness software platform with saved reports, member resources, client dashboards, admin workflows, enterprise pilots, API foundations, and future sensor pathways.
Build seriously, but in phases. Validate demand first, protect ownership, and avoid overbuilding before customers prove the strongest use cases.
Do not build everything at once.
Sentinel should grow from a validated WordPress product into a SaaS-style platform through clear, affordable, and testable phases.
Build Sentinel as a real product in five controlled phases.
This is the structure to discuss with WordPress developers, partners, and early enterprise prospects.
Product family, calculator, pricing, consultation and support.
Complete the visible product system: Sentinel OS, 20 Laws Calculator, Dashboard direction, Resource Library, Client Portal, Pricing, Consultation, Support, Launch Status, and SaaS Roadmap.
Member-only resources, templates, worksheets and education packs.
Build a protected resource library for Silver members and active clients, including readiness templates, sector playbooks, consultation worksheets, and education resources.
Login-based score history and saved Sentinel reports.
Allow users to save calculator results, view report history, track evidence gaps, and access recommended resources inside the Client Portal and Dashboard.
Organisation dashboards, risk registers and scoped pilot management.
Support enterprise customers with multiple projects, risk register, evidence matrix, project status, manual invoice tracking, board-style summaries, and pilot roadmap.
API foundations, team accounts, automation and future sensor pathways.
After market validation, expand into API access, team accounts, advanced reporting, integrations, exportable PDFs, AI report support, and future hardware/sensor roadmap.
Core architecture blocks to discuss with WordPress developers.
Sentinel can begin inside WordPress, but the architecture should be prepared for ownership, security, data portability, and future SaaS expansion.
Report Database
Custom post type or custom database table for saved calculator submissions, readiness reports, user IDs, scores, and report status.
Member Roles
Clear roles for public visitors, Silver members, consultation clients, admins, and enterprise users.
Client Dashboard
Score summary, report history, evidence gaps, resources, consultation status, and next action.
Admin Workflow
Review intake, manage reports, client status, payment/invoice notes, enterprise scope, and resource access.
Resource Library
Public, member-only, client-only, paid, and enterprise resource categories.
Payment Pathway
Stripe/PayPal for small purchases, membership for Silver access, and manual invoice for enterprise work.
API Foundations
Future API endpoints for calculator, reports, dashboards, enterprise integrations, and external systems.
Security & Privacy
Backups, least-privilege access, spam protection, secure forms, payment safety, data export, and privacy compliance.
Questions to ask before paying for major development.
Use these questions in your Brisbane WordPress meeting to keep the conversation focused on product architecture, not only page design.
Product architecture questions
- Can users save 20 Laws Calculator results after login?
- Should reports be stored as custom post types or custom database tables?
- Can the dashboard show score history, evidence gaps, and recommended resources?
- Can the Client Portal show different views for public, Silver, client, and enterprise users?
- Can the resource library support public, member-only, paid, and enterprise resources?
- Can the plugin be extended safely without breaking future updates?
Business protection questions
- Will IYABOKO fully own the custom plugin code?
- Will IYABOKO own all report templates, customer records, and resource files?
- Can the data be exported if we move hosting or platforms later?
- How will backups, security, and privacy be handled?
- What can be done in Phase 1 without overbuilding?
- What should wait until customer demand is proven?
Features to build only after demand is proven.
These are powerful, but they should not be rushed before Sentinel has early users, paid clients, and clear demand.
AI Report Assistant
AI-supported report drafting, evidence summaries, readiness interpretation, and consultation preparation with clear human-review boundaries.
Enterprise Team Accounts
Organisation accounts, multiple users, project groups, role permissions, report sharing, and team-level dashboards.
PDF Report Export
Professional PDF exports for readiness snapshots, board-style summaries, evidence matrices, and pilot proposals.
API Access
Future endpoints for calculator scoring, report retrieval, resource recommendations, and enterprise integration.
Sensor / Hardware Pathway
Future integration with environmental, energy, vibration, air, water, or other sensor streams after validation and demand.
Multi-Sector Dashboards
Separate dashboards for Space OS, Energy OS, Environment OS, Health & Biotech OS, Quantum Net OS, and Cyber Continuity.
Sentinel architecture roadmap shortcode.
If the Sentinel plugin shortcode is active, it can display the internal architecture roadmap below. If it does not render, keep this page as the public SaaS roadmap.
Sentinel Architecture Roadmap
This area is reserved for the Sentinel architecture roadmap shortcode.
IYABOKO Sentinel SaaS Roadmap
Roadmap items are architecture-ready placeholders only. They do not represent active hardware control, public API access, automated AI advice, mobile app deployment, enterprise team permissions, payment automation, certification, or regulated approval.
API foundations
Planning only
AI report template
Template only
Payment automation
Manual CTA
Enterprise teams
Roadmap only
Sensor / hardware
Roadmap only
SaaS backend
Future phase
SaaS roadmap does not mean certified or regulated use.
IYABOKO Sentinel SaaS Roadmap describes future software architecture, client access, saved reports, resource workflows, dashboard planning, enterprise pilots, API foundations, and sensor/hardware direction.
It does not create engineering certification, medical advice, cybersecurity certification, legal advice, financial advice, regulatory approval, operational approval, hardware approval, emergency warning authority, clinical diagnosis, mining safety certification, aerospace certification, or guaranteed project acceptance.
Build Sentinel seriously — but build it in phases.
Start with public product credibility, then add resource library, saved reports, client dashboard, enterprise workflow, and finally SaaS/API/sensor expansion after customer demand is proven.