LIVE
TRAVEL · CONCIERGE
MoonFlight
Premium airport concierge for Vietnam. E-Visa, Meet & Greet, VIP Lounge.
● SERVICE · BRAND & PRODUCT DESIGN
We designed eight products we run daily.
We know what earns trust.
MoonFlight, MoonBeauty, MoonLinks — different markets, different users, the same discipline behind every screen. We design products we then have to live with in production. That changes what we prioritize.
8Products designed & operated
8Design systems in production
4Market verticals
2022Est. Prague
● CHAPTER 01 / IS THIS YOU?
Three teams that need design done right.
LAUNCHING
Founders building their first product
The idea is strong. The engineering plan is clear. But the product needs to look and feel like something a user can trust. First impressions aren't second chances — and early design mistakes compound as the product grows.
SCALING
Products that have outgrown their original identity
Version one worked. Now you have five developers adding screens without a shared system. Inconsistency is creeping in. Users notice before you do. You need a design system that grows with the product, not against it.
NO DESIGN TEAM
Engineering-led companies that need design capability
Your engineers build well. Design gets delegated to whoever has time. The result is a product that works but doesn't convert, retain, or communicate trust. We become your design team until you're ready to hire one.
If the design is holding the product back — let's fix it.
Book 30 minutes● CHAPTER 02 / WHAT YOU GET
Design that works
before it looks good.
Brand identity system
Logo, color system, typography, voice, and usage guidelines. A brand that communicates before the user reads a word.
Information architecture
Before any pixels: structure. Navigation, hierarchy, content prioritization — mapped to how users actually think.
User research & testing
We talk to users before we design for them. Assumptions tested early are cheap. Assumptions tested after launch are expensive.
UI design system
Components, tokens, patterns, dark/light modes. Built to scale with your engineering team, not fight it.
Mobile-first design
Designed for the smallest screen first, then expanded. Because most of your users are on a phone.
Interactive prototypes
Click-through prototypes before development starts. Test the flow before paying to build it.
Developer handoff
Specs, assets, annotations, and component documentation. Developers build from clarity, not from interpretation.
Conversion & retention focus
Design decisions connected to business metrics. We ask what the screen needs to do, then design it to do that.
● OUR TEAM
One engagement.
Eight disciplines.
You don't coordinate a roster of freelancers. You get one cross-functional team with a single delivery manager answering to you. Engineering, design, QA, marketing, and executive oversight — fully handled.
CTO
Technical Director
Architecture decisions, code quality, technical strategy. The engineering starts and stops here.
PDM
Delivery Manager
Your single point of contact. Scope, timeline, and budget — owned by one person.
DEV ×2
Senior Developers
Two senior engineers on every build. No juniors carrying the core product.
UX/UI
Product Designer
Design grounded in user research. Prototyped, tested, then built — not decorated after.
QA
QA Engineer
Testing before your users ever see it. Bugs caught in staging, not in production.
MKT
Marketing Specialist
Go-to-market strategy and analytics built alongside the product, not bolted on after launch.
CEO
Account Director
Executive oversight on every engagement. When escalation is needed, it reaches a decision-maker within hours.
● ON-SITE VISITS
We come to you — if that helps.
When it makes sense, we visit your location before writing a single line of code. We sit with your team, watch how the business actually runs, and talk to the people who live in the problem every day. It's not a sales call. It's a listening exercise. The domain understanding you get from two days on-site takes months to build over video calls — and it shows in the product.
● CHAPTER 03 / RECEIPTS
Products we designed and operate daily.
Design tested in production, by real users, in real markets. We maintain these — so every design decision has consequences.
LIVE
SAAS · BEAUTY CRM
MoonBeauty
CRM for beauty salons. Appointments, staff, finances, AI features.
● CHAPTER 04 / HOW WE DESIGN
Four phases. Research before pixels, always.
01
DISCOVER
1–2 weeks
WE DOAudit existing work, talk to users, understand business goals, review competitors. Design without context is decoration.
YOU GETResearch summary, competitive audit, design direction brief.
02
STRATEGY
1 week
WE DOBrand positioning, visual direction, design principles. The decisions that constrain everything that follows.
YOU GETVisual direction deck, brand principles, approved direction to move forward.
03
SYSTEM
3–6 weeks
WE DOBuild the design system: components, tokens, patterns, and the full UI. Prototyped and tested before handoff.
YOU GETComplete design system, interactive prototype, tested flows.
04
HANDOFF
1–2 weeks
WE DOSpecs, assets, usage guidelines, developer documentation. Everything your team needs to build from the design without interpretation.
YOU GETFigma files, exported assets, component specs, handoff documentation.
● CHAPTER 05 / HOW WE SCOPE
Design scope is defined by what the product needs — not by hours.
A brand identity for a new product is different from a design system rebuild for an existing one. We scope after we understand what you actually need.
01
Discovery audit
Fixed-price engagement to assess existing design, user research gaps, and what the product needs to communicate. A clear brief before any design work starts.
02
Scoped design sprint
Brand identity, design system, or full product design — agreed scope, agreed deliverables, agreed price. No open-ended retainers.
03
Ongoing design partner
After the system is in place, many clients keep us on for iteration, new feature design, and design QA during development.
● CHAPTER 06 / WHAT YOU MIGHT BE THINKING
The honest answers.
Engineering skill and design skill overlap — but they optimize for different things. Engineers build what works. Designers build what communicates. The gap shows up in conversion rates, user retention, and support ticket volume. We're not saying engineers can't design. We're saying a product that needs to earn trust from a stranger in 3 seconds needs both.
Yes. We extend what works and fix what doesn't. The discovery audit identifies which elements are assets worth keeping and which are liabilities worth replacing. We don't rebuild for the sake of it.
By establishing design principles before we touch pixels. When a decision is made against a principle, it's no longer subjective — it's wrong or right. We define principles in the strategy phase and use them to evaluate every design decision that follows. Feedback cycles get faster because there's a framework for resolving disagreements.
Our product designer leads, with the CTO co-owning decisions that have technical implications. We don't design in isolation from engineering. Handoff frictions are caught before they're designed, not after they're built.
We present two to three distinct directions after the strategy phase, before any system is built. You choose one. If none land, we go back to research before proceeding. The strategy phase exists specifically to prevent late-stage directional disagreements.
● CHAPTER 07 / FAQ
Practical questions.
Yes. All deliverables are in Figma with full component libraries, auto-layout, and developer-ready specs.
Yes. Full ownership transferred on final payment. Your Figma org, your files.
Every engagement: CTO, Delivery Manager, two senior developers (for prototyping), product designer, QA engineer, marketing specialist, and account director. Design-led projects have the designer as the primary voice — with the CTO co-owning technical decisions.
Yes. Most of our products are designed and built by the same team. Design to development handoff inside the same engagement eliminates the usual translation loss.
Yes. Prototype testing before development starts, and usability testing after launch if the engagement continues. We arrange user sessions and run the analysis.
Yes, mutually. Send yours or use ours.
Tell us about your product.
Eight products designed, shipped, and operated. If you need design that holds up in production — not just in a presentation — we know how to build it.
REPLY IN 4 BUSINESS HOURS · NO SALES PIPELINE · MAYBE WE SAY NO