Understand
Three source documents reviewed; MVP scope, user journey and conflicts documented.
Project record
Where MeroDesk stands: the source brief, design decisions, what is delivered and what is still planned.
Design
Original mock-ups kept; user flow, design tokens and finished screens prepared.
Build
Responsive pages in plain HTML, CSS and JavaScript on a Supabase database and a Vercel API: accounts, server-side metering, usage export and a help guide.
Handoff
Screen exports, design tokens and an editable user-flow diagram ready to import into Figma.
14-week team plan
Bars come from the finalised Gantt spreadsheet. Status labels are the Week 8 snapshot from the review report (August 2026).
Delivered in this build
- Landing page, accounts with email and password
- Postgres database on Supabase with row-level security
- API on Vercel: desktops, sessions, profile, support
- Three-tier configuration and cost preview
- Start, connect and stop with server-side metering
- Session history, filters and CSV download
- Profile settings and help guide saved to the account
- Responsive layouts and editable design assets
Built, waiting to be switched on
- Desktops on Google Cloud VMs, started and stopped from the site
- The desktop streamed in the browser through Apache Guacamole
- Idle auto-stop, and a disk per desktop that keeps files
- Prepaid wallet with eSewa and Khalti top-ups
- AI help guide with the rule-based guide as fallback
Still planned
Applying the database migration and generated Google Cloud settings in Vercel, then adding merchant accounts for eSewa and Khalti and an AI service key. Until deployment, the preview does not start or imitate a desktop and nothing is charged.
Measuring start-up time and latency on Nepali home internet, then user testing. Team accounts and resource recommendations remain later scope in the source report.