Product design
in two weeks
Anyone can make software now. Few make it feel considered. That's the part we do.
Amondo, Assets, Boekhouding, DealDash, Homr, Jugyah, Plans, pod.network, Polymail, remark, Sandstorm, Shaders, Solflare, Turtles
Pricing
- Sprint
-
Two weeks, one fixed price, agreed up front.
We take your onboarding, a core flow, or a feature nobody has figured out yet, and hand it back designed and built as a working front-end you can put in front of users. Your engineers wire up the backend. If the work turns out bigger than planned, we cut scope, not the budget.
- You get
- Production-ready front-end code in your stack, in one repo with everything we built. You also get the Paper designs behind it, notes for your engineers, and a shared Slack channel for ongoing communication.
- Who
-
We're a small team on purpose, with decades of experience shipping products for startups. One senior designer leads your sprint and stays your direct point of contact, with the whole team behind every decision.
Book a call
Need more than two weeks?
Some teams keep going after the sprint. We become your design team and pick up right where we left off, whenever there's more to build.
Ask about partnershipsWe onboarded our first surveyor center yesterday. It was awesome, and they loved it. We feel even more confident than before about the design direction we’ve chosen together.
Frequently asked questions
What fits in two weeks?
The part of your product that matters most right now. Most sprints are one of these:
An onboarding overhaul. The first minutes of your product, redesigned and built.
One feature, start to finish. From a rough idea, or a rough vibe-coded version, to something you can ship.
A product audit, with fixes. Where the product gets in the way, and the most important fix already built.
Do we get code?
Yes. Every sprint ends with production-grade front-end code in a repo you own. Your engineers wire up the backend and ship it. Plans had our work in front of users within days.
We build in React and Next.js by default, or whatever you run, matched to your components and design tokens. You get a clean repo instead of a pull request, so nothing touches your codebase until your team says so.
We already built it with AI. Can you work with that?
That's our favourite starting point. A rough version tells us what you want faster than any brief.
What if we don't like where it's going?
You'll know early. We check in on day 3 and day 7, and you're on Slack with the designer the whole time. Nothing waits for a big reveal on day 10.