Design that earns attention.
A senior-only studio building brands, products and apps for companies that plan to be here in ten years.
Trusted by teams at
Fintech, climate, healthcare, commerce and developer tools — since 2016.
01 / Point of view
Mostagenciessellyoualook.Wesellyouadecision—aboutwhoyouare,whoyouarefor,andwhathastobetrueforsomeonetochooseyou.Thenwebuildthethingthatprovesit.
A small senior team. Two projects at a time. No juniors learning on your budget.
02 / What we do
Eight disciplines, one team, no handoffs.
Strategy, design and engineering sit in the same room and ship in the same sprint. Take the whole thing or the piece you are missing.
We start with the uncomfortable questions. Who is this actually for, what do they believe now, and what has to change for them to choose you? Everything downstream is cheaper when this part is right.
Typical2–4 weeksPairs withDeliverables
- Stakeholder & customer research
- Competitive positioning map
- Messaging hierarchy
- Naming & narrative
- Measurement framework
Most engagements combine three or four of these. We will tell you which ones you actually need.
Full service breakdownFlagship capability/ Mobile
Mobile apps that feel native, not merely shipped.
Most studios hand you a website in a shell and call it an app. We build the real thing — one codebase, both stores, and the small frictionless details people never consciously notice but always feel.
- 01
One codebase, two stores
React Native and Expo, so iOS and Android ship from a single source of truth — not two teams quietly drifting apart.
- 02
Gestures that track the finger
Interaction runs on the native thread at sixty frames. No web view wearing an app costume.
- 03
Offline that works on a train
Local-first data, queued writes, and sync that reconciles itself the moment the signal comes back.
- 04
Through review, first time
EAS pipelines, staged rollouts and store metadata handled — no two-week scramble the week before launch.
Shipped apps
Apps out in the world, not in a deck.
Real screens from apps we have designed and built, live in the stores and in people's hands every day.
01 / 04EdTech · Kids
Deutsch mit Tim und Tina
A companion app for a German course for children. Point the camera at a page of the book and the app finds it, then opens its audio and vocabulary — alongside videos, playful mini-games and rewards that keep young learners coming back.
- Camera page scan
- Audio & video
- Vocabulary cards
- Mini-games
- Rewards
01Home 
02Page found 
03Book picker 
04Games 
05Memory
New capability/ TON
Web3 on TON, inside an app they already have.
TON is the chain Telegram built, and that changes the first ninety seconds of every product: no extension, no seed phrase, no browser tab. The Mini App opens in a chat with the wallet already beside it. We build everything after that — on a chain that settles asynchronously and punishes anyone who pretends it does not.
- 01
Opens where they already are
A Telegram Mini App and TON Connect, so the first run is two taps inside a chat. No extension, no seed phrase, no app store — the wallet is already sitting next to your product.
- 02
Contracts for an async chain
Tact and FunC, exercised in Blueprint's sandbox and then handed to an external auditor. TON has no atomic cross-contract call, so every flow is designed around messages that can arrive late or bounce back.
- 03
Fees nobody has to fund
W5 wallets and a relayer, so the app pays the network fee and your customer never buys Toncoin to get started. When they do pay, they can pay in your jetton instead.
- 04
Traced to settled, not to sent
One tap can spawn four messages across four contracts, and any of them can bounce. We follow the whole trace before the interface says it worked — the single thing that makes most TON products feel broken.
Nothing reaches mainnet without an external audit and a full run on testnet. That is a gate, not a phase we can compress when the launch date moves.
Education technology
Software for a room with thirty children in it.
Learning platforms, exams, mobile revision and smart board applications — designed in real classrooms and built to survive a school network. We made a page that shows it working.
- 01
Smart board apps
Pardus ETAP, Android and Windows, from one codebase.
- 02
Platforms & exams
Homework to report card, as one product.
- 03
Built with teachers
Prototyped on the real board, piloted with one class.
03 / How it goes
A process with no mystery in it.
You will always know what week we are in, what we are making, and what we need from you. Here is the whole thing.
01
Listen
Week 1–2
Five phases, sixteen weeks for a typical engagement. Longer builds repeat phases three and four in sprints.
- 01Week 1–2
Listen
We interview your team, your customers, and the people who said no. We read your support tickets. We come back with a point of view, not a questionnaire.
- 02Week 2–4
Frame
The strategy gets written down in language a new hire could understand. Scope is agreed, risks are named, and we all sign the same sentence about what success is.
- 03Week 4–12
Make
Design and engineering run together, not in sequence. You see working software in the browser every Friday, and you can change your mind while changing it is still cheap.
- 04Week 12–16
Ship
Performance budgets met, accessibility audited, documentation written. We hand over a codebase your team can own and a system they can extend.
- 05Ongoing
Sharpen
We watch what real people do with it, and we keep going. Small, measured improvements, shipped continuously.
Five phases, sixteen weeks for a typical engagement. Longer builds repeat phases three and four in sprints.
04 / In their words
“We interviewed nine studios. K10 was the only one that pushed back on the brief in the first meeting — and they were right to.”
Next step
Tell us what you are building.
One reply from a founder or director within a working day — not a form confirmation and a three-week silence.
Replies within one working day
Prefer to look around first? See how we work.