Skip to content
iKOTB
iKOTB Roadmap

A step-by-step roadmap for building iKOTB correctly.

iKOTB is being developed in stages. The goal is not to build every feature at once. The correct path is to create a strong public website, then a private internal dashboard, then real property management workflows, then future SaaS and mobile expansion.

Development Phases

Build the foundation first, then expand.

Each phase should make the project more useful, more organized, and easier to scale.

Phase 1

Current

Public Website

Build the public iKOTB website, explain the brand, present the platform vision, and prepare the project for early credibility.

Homepage
About page
Platform page
Contact page
Privacy and Terms
Shared header and footer

Phase 2

Next

Internal Office Dashboard

Create the first private dashboard for internal property management work before opening the system to external users.

Dashboard layout
Authentication
Properties database
Owners database
Tenants database
Basic admin workflow

Phase 3

Planned

Property Management MVP

Build the first practical property management system for real daily operations, not only a display website.

Contracts
Payments
Maintenance requests
Documents
Reports
Tasks and reminders

Phase 4

Future

Owner and Tenant Portals

Prepare controlled access for owners and tenants after the internal office workflow is stable and tested.

Owner login
Tenant login
Property updates
Document access
Payment visibility
Request tracking

Phase 5

Future

SaaS Expansion

Expand iKOTB into a multi-office SaaS platform with proper roles, permissions, subscriptions, and audit records.

Multi-office accounts
User roles
Permissions
Subscription billing
Audit logs
Advanced reports

Phase 6

Later

Mobile App

Build a mobile app only after the web platform is stable, useful, tested, and ready for mobile workflows.

Owner mobile access
Tenant mobile access
Maintenance updates
Notifications
Document access
Mobile-first workflows

Build Principles

The roadmap protects the project from becoming too complicated too early.

The best strategy is to build useful parts in the correct order, test them with real workflows, then expand only when the foundation is stable.

Website before dashboard
Dashboard before SaaS
Database before automation
Internal testing before public users
Web platform before mobile app
Simple workflow before advanced features