We designinterfaces thatflow.
Product studio from Poland. We run two of our own products every day — Cumuj and Naczarter. We built this site ourselves too.
01Manifesto
We don't make apps on commission. We make products, and every interface is the proof.
We work with founders who are already selling something — and know why.
Naczarter
Yacht charter on Masurian Lakes · since 2001
The most modern yacht-charter platform on the Great Masurian Lakes. Sailboats, motorboats, houseboats and licence-free boats from many operators. Online booking, free cancellation up to 30 days before the cruise. 25 years of business, a second digital life — the interface rebuilt from scratch, with a client base kept across a quarter-century.
Cumuj
Marina berth reservation · real-time
A map of yacht marinas on the Great Masurian Lakes with live berth availability. Reserve a numbered berth or metres of quay with online payment, check in with a QR code — no queue. Three roles — sailor, dock master, port manager — in one system: on the water in your pocket, in the office on screen.
02How we work
Three phases.
Zero deck.
We don't have a six-step process from a blog. Three phases, each with artifacts you can see and verify.
Discovery
3 daysBefore we open the first file, we understand the business.
Three days with the client team. User interviews, competitor analysis, a map of product decisions. No fancy documents. Just notes that anyone can still read a week later.
- User interviews
- Business needs
- Competitor analysis
Design
4–6 wks.Design that works, not design that poses.
A visual system from scratch: typography, colour in OKLCH, motion as part of the language. Mock-up and a working version grow in parallel — whatever won't build in the browser won't go into the spec.
- Visual system
- Interactive prototype
- Motion spec
Ship
6–10 wks.A working version in week one.
Every change gets its own preview link right away. Features rolled out gradually, monitoring from day one. Launch isn't a moment — it's the permanent mode.
- Preview links
- Staged rollouts
- Performance > 90
03Scope
We take. We pass.
Short filter. No negotiation.
- 01Digital products from zero.
- 02Rebuilds of old systems that still make money.
- 03Design and code in one pair of hands.
- —Branding on its own.
- —Analysis without shipping.
- —Projects without ambition.
We pass means — we recommend someone who does it better than us.
04Most often
Five questions,
they ask.
How much does a project with Ideopay cost?
We don't have a "from–to" price list. We price by scope, not hours. Full builds start in the range of tens of thousands of zloty net — the exact number lands after the first call, within 48 hours of a brief.
How long does a project take?
Three phases: discovery (3 days), design (4–6 weeks), ship (6–10 weeks). Together 10–17 weeks for a product built from zero. Rebuilds tend to be shorter. Every phase has artifacts you can see and verify before the next step.
Who owns the design and the code?
You do. Full IP handover. The repo sits on your GitHub from the first commit, the designs in your Figma workspace. We don't lock you into our tools.
Do you bill by the hour or by the project?
By project. Hourly billing forces counting time instead of counting value. We agree on scope and price up front. If something new shows up along the way, we split it off as a separate stage — no quiet invoice inflation.
What if we already have a designer or a developer?
Great. We join the team, we don't replace it. Most often: we design the system and the key flows, your developer ships the rest. We work in your git flow, your Figma, your standups — without taking over the whole structure.
05Contact
Tell uswhat you're building.
We take projects where the client's team knows their product better than we do — that's when craft has something to stand on. Write a few sentences about what you're working on. We reply within 48 hours.