Software design studio — Kathmandu
Software that
carries weight.
We design and build web and mobile products for small teams, and stay with them long after launch.
Start a projectProduct design
Interfaces that stay clear as the product grows — research, flows, and screens.
Web apps
Fast, maintainable products. From the first version to the one that scales.
Mobile apps
Native-feel iOS and Android apps, built by people who use them daily.
We're small on purpose. You talk to the people writing the code — no account managers, no handoffs. We plan in weeks, ship in increments, and sweat the parts most studios skip: the loading state, the empty state, the edge case nobody filed a ticket for.
-
Survey
A week of questions. What the product has to do, who it's for, what's already been tried, and where the real constraints sit. You get a written scope and a fixed estimate — not a proposal deck.
-
Route
Flows and screens for the paths that matter, in enough fidelity to argue with. We settle the hard interaction questions here, while they're still cheap to change.
-
Build
Weekly increments on a real URL or a real device build. You see the product every week, in the state it's actually in, and you can steer.
-
Carry
Launch isn't the finish line. We stay on for the bug reports, the store rejections, the dependency bumps, and the second version — the part most studios hand off.
yakcraft works out of Kathmandu, across European mornings and American evenings. Small teams, long engagements, and a strong preference for products we'd use ourselves.
- Based in
- Kathmandu, Nepal
- Time zone
- NPT · GMT+5:45
- Platforms
- Web, iOS, Android
- Engagements
- From four weeks
How small is small?
Small enough that the person answering your email is the person writing your code. If a project needs more hands than we have, we'll say so rather than staff up around you.
Do you work with existing codebases?
Often. Taking over something half-built is its own skill, and it's one we like. We'll spend the first week reading before we propose changing anything.
What does it cost?
We quote a fixed price per phase after the survey week, so you're never approving an open-ended hourly bill. If the scope changes, we re-quote before doing the work, not after.
Who owns the code?
You do — repository, designs, infrastructure, all of it, from the first commit. Nothing sits on a yakcraft account that you can't take with you.
What if we just need a second opinion?
That's a fine reason to write. A short technical review or a design critique is a real engagement, and sometimes it's the only one you need.
Tell us what you're building.
Send a short note about the project and where it's stuck. We'll tell you honestly whether we're the right studio for it.
hello@yakcraft.com