- SerkoBusiness Travel
- Corporate travel booking hasn't fundamentally changed in decades - until now. We started to rethink how business travel happens, from shifting from dozens of tabs to personalized, dynamic AI-powered booking.
- What we did
- Smart Curation. Smart recommendations to eliminate comparison fatigue.
- Proactive Intelligence. A conversational layer that feels like working with a thoughtful assistant.
- Consistent Patterns. Learn the system once, apply it across your entire booking experience.
Design your first version right.
We design new B2B SaaS and AI products, from the first flow to every screen of version one, with a coded prototype to test before you build. An MVP takes 6 to 8 weeks.
When it’s time. The idea is clear,
but there’s nothing to click yet.
A round that just closedYou raised, and now investors expect a product, not another deck.
A waitlist that’s waitingPeople signed up, and the first version has to win them over.
Engineers ready to buildYour team can ship, but nobody has designed what they should ship.
A pitch that needs a demoInvestors and pilot customers want something they can click.
A product that lives in docsThe idea is in specs and Loom calls, not in screens anyone can test.
An AI feature to shapeThe model works, but the experience around it doesn’t exist yet.
What you get. A first version you can test,
and files your team can build from.
A product mapEvery user, job and flow mapped, so version one has a clear scope.
Your core flowsThe flows that make the product, designed and reviewed every week.
Every screen of v1Each screen and state of the first version, ready for your team.
A design systemTokens and components your developers build every screen from.
A coded prototypeA live prototype investors and your first users can click through.
Help with the buildReviews of each screen as it’s built, and front-end help when needed.
Inside a project. Real products we’ve designed,
part by part.
How it runs. A focused MVP,
in six weeks.
A 25-minute call about your idea, then a written scope with a fixed price.
- You decide
- What version one has to do.
- We need from you
- Your idea, your users and any specs.
- You get
- A written scope and a fixed price.
Every user, job and flow mapped, then cut down to what version one needs.
- You decide
- What’s in version one, and what waits.
- We need from you
- An hour with whoever knows the users.
- You get
- A map of the product and its flows.
The flows that make the product, designed and reviewed every week.
- You decide
- What stays, what changes, what goes.
- We need from you
- Feedback on each round, every week.
- You get
- The core flows, closer each week.
Tokens and components taken from the flows, so every new screen matches.
- You decide
- What goes into the first version.
- We need from you
- Your brand, if there is one yet.
- You get
- Tokens and components to build from.
A live prototype of the core flows, tested with real users before the build.
- You decide
- Who tries the prototype first.
- We need from you
- Five people from your waitlist.
- You get
- A prototype you can share and test.
Every screen and state of version one, from empty states to settings.
- You decide
- The last details before the build.
- We need from you
- Quick answers on the edge cases.
- You get
- Every screen of v1, specced in Figma.
Files cleaned up and specced, then a review of each screen as it’s built.
- You decide
- When the build starts.
- We need from you
- An intro to the engineers building it.
- You get
- Figma files and specs. Everything is yours.
- Intro call and scopeBefore
A 25-minute call about your idea, then a written scope with a fixed price.
- Product mapWeek 1
Every user, job and flow mapped, then cut down to what version one needs.
- Core flowsWeeks 2–3
The flows that make the product, designed and reviewed every week.
- Design systemWeeks 2–5
Tokens and components taken from the flows, so every new screen matches.
- Coded prototypeWeeks 3–5
A live prototype of the core flows, tested with real users before the build.
- Every screenWeeks 4–6
Every screen and state of version one, from empty states to settings.
- Handoff and buildWeek 6
Files cleaned up and specced, then a review of each screen as it’s built.
A project, start to finish. How we shaped Serko’s
AI travel booking.
Products we’ve designed. From first versions
to products used every day.




What clients say. Design and product leads we’ve worked with,
in their own words.
“I’m kind of speechless. I love the interface. I love the design. I love how you’ve treated the branding. It’s perfect.”
Melissa Helyer-AkharaGlobal Head of Design, Serko
“It took me almost a decade to find a designer as talented as you to help drive the brand and product forward.”

Ryan ChartrandCEO, X-Team
“This is, without doubt, your biggest superpower. When it comes to visual design, you are the most skilled person at this company.”

Rachel SeoHead of Product, Hyperquery
Is it for you? It works best for new products
with a team ready to build.
It’s for you if
- You have a product idea and a team.
- You’re B2B SaaS or AI, pre-seed to Series A.
- You can decide things every week.
It’s not for you if
- Your product has users (see redesign).
- You only need a landing page.
- You want it built with no team of yours.
What it costs. A fixed price, agreed in writing
before any work starts.
MVP design
Starting from
$15,000
A fixed price for 6 to 8 weeks of work, set after the intro call from the scope.
- A product map
- Your core flows
- Every screen of v1
- A design system
- A coded prototype
- Help during the build
Questions. The ones founders ask before an MVP.
Email usHow long does it take to design an MVP?
Between 6 and 8 weeks for most B2B products: a product map in week 1, then the core flows, a design system, a coded prototype and every screen of version one. The scope says how long yours takes.
How much does MVP design cost?
From $15,000, as a fixed price we agree in writing after the intro call. If you want to try us first, the two-week pilot is $7,500.
What should be in an MVP?
Only what your first users need to get their job done. The product map in week 1 lists every flow, then we cut it down to version one with you, and the rest waits.
Can we test it before we build it?
Yes. The coded prototype goes in front of people from your waitlist before the build starts, and we change it based on what they do.
Do you build it too?
Your team builds it. We hand over Figma files and specs, review each screen as it’s built, and help with the front-end when it’s needed.
Who does the work?
Charles, a senior product designer with 10+ years of experience, does the work and reviews every change. No account managers, no hand-offs to juniors.
Who owns the work?
You do. The Figma files, prototypes and any code are yours, and stay yours if we stop working together.
Related services. What teams often pair with it.
Product redesignFrom $15,000, 4 to 12 weeks. Core flows that got hard to use, redesigned.
Live prototypesIn every project that needs one. Coded prototypes your users click before it’s built.
Website designFrom $15,000, 2 to 4 weeks. Designed and built in Astro, ready to rank.


