A serious system takes more than a polished screen.
This is the planning basis for building a Lekka-style operations platform from scratch: what has to be built, how long it takes, what to charge, and what it costs to operate.
Build one isolated deployment first. Productize the repetition second.
The current architecture is best suited to a single-tenant rollout: one customer, one Firebase project, one deployment, and a clear security boundary.
Once the product and support process work for the first 5–10 customers, automate provisioning and decide whether multi-tenancy is worth the additional security and operational complexity.
React + Vite
Modular SPA with partner branding
Firebase Auth
Sessions, claims, App Check
Cloud Firestore
Real-time records and transactions
The UI is not the security boundary. Firestore rules, custom claims, transaction preconditions, audit records, and immutable workflow states are.
6–9 months solo.
3–5 months with a small team.
Planning basis: approximately 1,400–2,200 engineering hours for the full operational scope.
Discovery & design
Workflow mapping, roles, data model, acceptance criteria, and rollout plan.
Application foundation
React/Vite surfaces, navigation, responsive system, Firebase Auth, sessions, and environments.
Core operations
People, finance, documents, timesheets, PTO, Work Calendar, planning, and approvals.
Control layer
Firestore rules, transactions, notifications, audit, backups, analytics, and security hardening.
Verification & launch
Unit and rules tests, data migration, UAT, training, deployment, and hypercare.
Price the business system,
not the number of screens.
These figures are for building an equivalent platform from scratch — bespoke engineering effort, quoted once. If you’d rather license the existing Lekka platform and brand it for your clients instead of building it, that’s a different, ongoing commercial model — see partner pricing.
Focused MVP
A smaller first release covering auth, people, finance basics, documents, and one approval workflow.
Full platform
The complete operations product: Work Calendar, tasks, planning, payroll, finance, inventory, audit, and launch support.
White-label enterprise build
A from-scratch build with partner branding, isolated deployment, data migration, integrations, and a support model — the DIY alternative to licensing Lekka as a partner.
Keep infrastructure transparent.
The client should usually own the cloud accounts and billing. You can charge a management margin for monitoring, releases, backups, and support instead of quietly absorbing usage risk.
Vercel Pro
Professional deployment, collaboration, custom domain, and included usage credit.
Firebase Blaze
Firestore, Storage, Functions, Hosting, and other Google Cloud usage beyond free quotas.
Domain & email
Domain renewal plus transactional email or business inboxes.
Messaging & integrations
SMS, WhatsApp, payment gateways, accounting tools, or client-specific connectors.
Operations
Monitoring, backup review, support tooling, and release operations at an early stage.
Early-stage monthly planning range
Budget approximately ₹5K–₹20K/month for a small deployment before significant traffic, messaging, storage, or integration usage. Review actual Firebase and hosting usage monthly.
Vendor prices change by region and usage. Verify current rates before signing a proposal: Firebase billing, Firestore pricing, and Vercel pricing.
Don’t sell it as a website.
Sell it as an operational system that replaces disconnected spreadsheets, approvals, finance tools, HR records, and work tracking. That is where the implementation value, support value, and recurring value come from.