About ONE ELEVEN
One team, brand to code — running continuously since 2018.
For a project in the $8,000–18,000 range, who you're hiring matters as much as what they'll deliver. Here's the actual history, not a mission statement.
A continuous practice, not a new studio
ONE ELEVEN started in 2018 under a different name, Juiced. The name changed in 2026 — the team, the client relationships and the body of work didn't. Ridex, Soloway and the other early identity work in the case studies were built under that name, by the same practice that operates as ONE ELEVEN today. That makes this a seventh year, not a first one.
From 2018 to 2021, that meant brand work — naming, identity, brand books, mostly for businesses entering a category their market hadn't seen yet: a scooter-sharing service in a city with no prior sharing economy, a coffee roaster moving from counter sales to subscriptions.
From 2021, the same practice spent five years mostly inside products rather than brands: leading the engineering team of an iGaming platform, building an LMS for an education provider, a healthcare app, games, and infrastructure for AI agents. That's the gap a lot of branding-only studios don't have — and it's the reason the brand work since has looked different.
What five years inside products changed
Branding on its own never teaches you this: a system a developer can't ship isn't a system, it's a PDF. Leading engineering on a live platform means watching a brand book actually get implemented — where the rules break, which ones nobody follows past the second sprint, what's missing that the guidelines never mention because whoever wrote them never had to build the button themselves.
Now both halves happen inside one practice. The list below is what that looks like in practice, not in theory.
We write the code ourselves
Not a slogan — Ridex and Secret Coffee are both cases where we did the brand and the product. That means our brand books don't contain rules that can't be built.
No handoff gap
The most expensive stage on most branding projects is handing a PDF to a developer who wasn't in the room when it was designed. Ours ends inside the same team.
Design tokens, not just a PDF
A developer gets variables that plug in with one line, not a document they retype colors out of by hand.
We stay after handover
A brand book isn't the end of the work, it's the start of using it. Questions show up in month three, and we're still around to answer them.
Experience, 2021–2026
| 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 |
Who this is a good fit for
Good fit
- You need brand and product as one deliverable, not two agencies you coordinate yourself
- Your current identity was made informally and doesn't hold up applied to a real interface
- You want one point of accountability instead of a chain of contractors pointing at each other
Not a good fit
- You need a logo in a week for $300 — that's a real job, just not ours; a freelancer will do it faster and cheaper
- The brand already exists and you like it — you just need a website. That's still worth talking to us about, but read this as a product engagement, not a rebrand
- Decisions go through an eight-person committee with no single sign-off — we work with one point of contact who can say yes
- The brief is “like our competitor, different color” — we'll say no to that; it isn't savings, it's deferred rework
Talk to us
See open pricing for all four packages or tell us what you're launching — we reply within 24h on working days.