BRAND, PRODUCT & CODE.
One team takes it from naming to production. Nothing gets handed down the chain, because the chain ends with us.
One full-cycle team: brand, product and the automation that keeps it running. Same repo, same accountability through release.
See the work →11
4
24h
Healthcare app for patients and providers
React Native app: provider search, pharmacy map, patient ID, visit history.
Open case →
Services
Experience
| Domain | Role | Stack | Period |
|---|---|---|---|
| iGaming platform | Engineering lead | TypeScript, Node.js | 2025 → |
| Telegram Mini Apps (games) | End-to-end | TypeScript, Node.js | 2024–2025 |
| Web application | Fullstack | Next.js, Node/Bun, PostgreSQL, MongoDB | 2021 → |
| Mobile apps | React Native | Expo, iOS + Android | 2021–2024 |
| CMS product | Fullstack | Payload CMS, Next.js, PostgreSQL | 2026 → |
| Open edX | Micro-frontend customization | React | 2022 |
Why we're back
From 2018 to 2021 we built brands. Then we spent five years inside products: leading the engineering team of an iGaming platform, building an LMS for an education provider, a healthcare app, games, infrastructure for AI agents.
That taught us something branding alone never does: a system developers can't ship isn't a system — it's a PDF. Now we do both halves ourselves, one team, brand to code.
How we work
A brand book is worthless if it can't survive production.
We work across both halves without a seam: identity systems and brand books on one side; an iGaming platform's engineering team, an LMS, mobile apps and automation infrastructure on the other.
One team holds both — and owns the outcome through release, not through PDF.