A small team that stays with your project
People stay on the products they build — the same faces across Enzioo, Mobipath, and MetroDokan, and the same for client projects. This is the structure of who owns what.
Who's who
The people behind the products
Leadership
Founder & CEO
Name reserved
- Client direction
- Product strategy
- Company accountability
Reserved: write a short, specific bio — background, what this person owns across Enzioo, Mobipath, and MetroDokan, and how they work with clients.
Leadership
Head of Engineering
Name reserved
- Node.js
- System architecture
- Engineering standards
Reserved: write a short, specific bio — the architecture decisions this person owns and the platforms they're accountable for in production.
Leadership
Head of Product
Name reserved
- Product ownership
- Roadmaps
- User research
Reserved: write a short, specific bio — the product decisions this person makes across the companies' own operated products.
Engineering
Engineering Lead — Platforms
Name reserved
- Multi-tenant platforms
- Monitoring & evaluation
- Reporting
Reserved: write a short, specific bio focused on the platform systems (e.g., monitoring & evaluation software) this person leads.
Engineering
Engineering Lead — Mobile
Name reserved
- React Native
- Offline-first sync
- Android & iOS
Reserved: write a short, specific bio focused on the mobile products (e.g., school/institute management) this person owns.
Engineering
Engineering Lead — Commerce
Name reserved
- E-commerce
- Marketplaces
- WordPress
Reserved: write a short, specific bio focused on the commerce and marketplace platforms (e.g., MetroDokan) this person leads.
Design
Design & UX Lead
Name reserved
- Design systems
- Product UX
- Accessibility
Reserved: write a short, specific bio focused on the design systems and interfaces this person owns across the products.
Delivery
DevOps & QA Lead
Name reserved
- AWS
- CI/CD
- Automated testing
Reserved: write a short, specific bio focused on infrastructure and release reliability — the systems this person keeps boring on purpose.
How we work
Small teams, real accountability
We keep teams small on purpose. On a client project you know exactly who is doing the work — and they stay on it long enough to own the result, not just the ticket. That consistency is a deliverable, the same way it is across our own products.
Engineering Lead — Platforms
Multi-tenant platforms · Monitoring & evaluation
Engineering Lead — Mobile
React Native · Offline-first sync
Engineering Lead — Commerce
E-commerce · Marketplaces
Design & UX Lead
Design systems · Product UX
DevOps & QA Lead
AWS · CI/CD
Get in touch
Talk directly to the people building your project
No account-management layers and no small-print outsourcing. The fastest way to know if we're the right team is a conversation with the people who'd do the work.