Mahlis product roadmap
This roadmap combines planned work with current progress. Dates guide scheduling; completed evidence determines whether a product advances.
Current stage
Mahlis is preparing its public platform, product definitions, prototype plans, staffing model and pre-seed materials.
Completed
- Built the first Mahlis web application
- Established controlled Markdown publishing
- Added public articles, RSS, sitemap and machine-readable discovery files
- Built authentication, server-side sessions, CSRF protection and login rate limiting
- Established database migrations, backup foundations and release verification
- Defined the initial Vitalis OS and Atari Eyes boundaries
- Began the Vitalis Drug Planner definition from a lived medication-planning problem
In progress
- Public website and language revision
- Vitalis OS architecture definition
- Drug Planner calculation and information-boundary design
- Atari Eyes intended-use and prototype definition
- Pre-seed materials and investor presentation
- Staffing scopes, expected results and worker-health principles
- Privacy-conscious analytics and contact management
Product sequence
Phase 1 — Public and operational foundation
Purpose: Make the company, products, evidence and boundaries understandable.
Deliverables: Public website, product pages, roadmap, articles, protected administration, contact workflow, release process and deployment documentation.
Exit gate: Security, privacy, accessibility, backup, test and production checks pass.
Phase 2 — Product definition
Vitalis OS: Intended use, users, workflows, non-goals, architecture decisions and hazard log.
Drug Planner: Source-information model, transparent calculations, correction history, privacy boundary and simulated test cases.
Atari Eyes: Intended use, sensing boundary, feedback vocabulary, device-state signals and controlled-test plan.
Exit gate: Each product has a reviewed scope and a measurable prototype plan.
Phase 3 — First prototypes
Vitalis Kernel prototype: Identity, permissions, audit, encrypted local storage, offline search, signed packages, backup and recovery.
Drug Planner prototype: Plan entry, date and quantity calculations, daily view, correction history, export and restoration using simulated information.
Atari Eyes prototype: A small controlled sensing device that distinguishes left/right, near/far, normal operation and device fault.
Exit gate: Automated tests, documented failures, recovery demonstrations and safety-boundary review pass.
Phase 4 — Simulation and usability
Representative users test defined workflows in controlled settings. No prototype advances merely because it runs on the developer's machine.
Exit gate: Usability findings, accessibility results, unresolved hazards and corrective actions are documented and independently reviewed.
Phase 5 — Controlled pilots
Each pilot remains narrow: one product, one defined workflow, named operational owners, explicit stopping rules and no unsupported clinical claims.
Exit gate: The pilot produces reliable evidence of usefulness, safety, failure handling and support needs.
Initial staffing plan
Mahlis will begin remote-first with a small team and one clear chain of responsibility.
| Role | Initial responsibility | Expected result |
|---|---|---|
| Founder and System Architect | Product scope, architecture, operations and final decisions | Coherent product direction and accountable releases |
| Software Engineer | Application, database, testing and deployment | Secure, maintainable working software |
| Product and UX Designer | Accessible workflows, prototypes and usability | Interfaces people can understand and test |
| Healthcare Research and Safety Lead | Intended use, evidence, hazards and clinical boundaries | Responsible product claims and reviewed safety records |
| Operations and Compliance Coordinator | Documentation, controls, suppliers and release evidence | Traceable operations and audit-ready records |
| Partnerships and Customer Development Lead | Research relationships, pilot preparation and market learning | Qualified conversations and realistic pilot opportunities |
Specialist legal, accounting, cybersecurity and regulatory work may begin through defined contracts instead of premature full-time hiring.
Worker-health principles
Mahlis intends to design work around sustainable output rather than constant availability.
- Fair, liveable compensation
- Clear job scope and expected results
- Remote-first work where the role permits
- Protected rest and leave
- Realistic workload and release dates
- Accessible tools and communication
- Minimal unnecessary meetings
- No hidden expectation of unpaid availability
- Health support considered part of operating capacity
Pre-seed planning baseline
The current planning target is CAD $500,000 through a post-money SAFE with a CAD $5,000,000 valuation cap and a target dilution of approximately 10%, subject to legal review and final investor terms.
The raise is intended to fund people, prototype development, security, compliance preparation, infrastructure, research and operating runway. It is not a claim that financing has been secured.
How progress will be reported
Public updates will show completed work, current work, evidence, blockers and next milestones. More detailed financial, hiring and supporting records will remain in the protected administrative or investor area.
The roadmap will change when evidence changes the plan. Earlier versions remain preserved through version control.