How do you price projects?

Fixed scope against a signed brief, split into milestone payments. After discovery you get a number, not a range. If scope changes later, it is priced in writing before work starts — the change rate is agreed in the same document so nobody negotiates under deadline.

Who owns the code, accounts and store listings?

You do, from day one. Repositories, cloud projects and store accounts are created under your organisation; we collaborate inside them. That includes design files, documentation and any admin tooling we build for you.

Which mobile stack will my app use?

Our default is React Native or Flutter for product coverage at realistic budgets; native Kotlin when performance or deep OS integration justifies it. We maintain production apps in this family ourselves, so recommendations come with maintenance numbers, not vendor slides.

Practice 04

Design is documentation for behaviour.

We design like developers will read us closely — because they do. Every flow carries its empty, loading, error and offline states; every component maps to a token; every interaction has a written motion rule. Then we build it ourselves if you want.

Scope ui/ux & product design →2–6 weeks per product surface.

What’s in the box

01IA & user flows
02Wireframes → high fidelity
03Token-driven design system
04Interactive prototypes
05Motion & interaction specs
06Brand identity (logotype, palette, type)
07Design QA against the build

Deliverables at handover

Flow sets incl. failure states
Figma library mirroring implementation
Spec sheets for build
Design QA notes

Questions this practice gets

How do you price projects? Fixed scope against a signed brief, split into milestone payments. After discovery you get a number, not a range. If scope changes later, it is priced in writing before work starts — the change rate is agreed in the same document so nobody negotiates under deadline.: Fixed scope against a signed brief, split into milestone payments. After discovery you get a number, not a range. If scope changes later, it is priced in writing before work starts — the change rate is agreed in the same document so nobody negotiates under deadline.
Who owns the code, accounts and store listings? You do, from day one. Repositories, cloud projects and store accounts are created under your organisation; we collaborate inside them. That includes design files, documentation and any admin tooling we build for you.: You do, from day one. Repositories, cloud projects and store accounts are created under your organisation; we collaborate inside them. That includes design files, documentation and any admin tooling we build for you.
Which mobile stack will my app use? Our default is React Native or Flutter for product coverage at realistic budgets; native Kotlin when performance or deep OS integration justifies it. We maintain production apps in this family ourselves, so recommendations come with maintenance numbers, not vendor slides.: Our default is React Native or Flutter for product coverage at realistic budgets; native Kotlin when performance or deep OS integration justifies it. We maintain production apps in this family ourselves, so recommendations come with maintenance numbers, not vendor slides.

Begin the ascent

Let's build the ui/ux & product design the right way.

One paragraph is enough to start — we reply within a working day with questions, a direction, and whether we're the right studio for it.

Start a project →WhatsApp