01Services
Four services, with the deliverables written down
No packages, no tiers, no vague statements of work. Each service below lists exactly what you receive, how long it takes and what it starts at.
01Service
Design audits
A clear-eyed read of the interface you already have.
We go through your product screen by screen and tell you exactly where it leaks: the inconsistencies, the accessibility failures, the flows that make people hesitate. You get findings ranked by severity and effort, not a list of opinions.
Best for
Teams who suspect the interface is holding them back but cannot yet name where.
- Typical duration
- 2 to 3 weeks
- Investment
- From $9,000
What you receive
- Screen-by-screen annotated review of every core flow
- Heuristic findings scored by severity and fix effort
- WCAG 2.2 AA accessibility findings with the specific failure noted
- Component inconsistency inventory across the product
- Prioritised fix list split into quick wins and structural work
- Recorded walkthrough of the findings, yours to keep
- A 90-day remediation roadmap your team can run without us
How the time is spent
Week 1
Access and inventory
We get into the product, map the flows that matter, and capture the current state of every screen in scope.
Week 2
Review and scoring
Heuristic pass, accessibility pass, consistency pass. Every finding gets a severity, an effort estimate and a screenshot.
Week 3
Roadmap and handover
We sequence the fixes into a roadmap, walk your team through it live, and leave you the annotated file.
02Service
UI/UX design
End-to-end interface design, from first flow to final state.
The core of what we do. We take a product area, or a whole product, and design the interface properly: the flows, the screens, the empty states, the errors, the loading, the breakpoints. Everything an engineer needs to build it without guessing.
Best for
Teams building something new, or rebuilding a product area that has outgrown its original design.
- Typical duration
- 6 to 12 weeks
- Investment
- From $28,000
What you receive
- User flows and task maps for every journey in scope
- Wireframes for structure, agreed before any visual work starts
- High-fidelity screens at mobile, tablet and desktop widths
- Every state drawn: empty, loading, partial, error, success, permission-denied
- Interaction and motion notes written next to the screens they belong to
- Redlines, spacing specs and component annotations for engineering
- Two rounds of build review once your team starts implementing
How the time is spent
Weeks 1 to 2
Discovery and flows
We learn the product, the constraints and the users. We agree what success looks like and draw the flows.
Weeks 3 to 6
Interface design
Wireframes to high fidelity. Weekly reviews, working in the open, no month-long silences before a big reveal.
Weeks 7 to 9
States and responsive
Every edge case, every breakpoint, every error. This is the part most projects skip and later regret.
Weeks 10 to 12
Handover and build support
Specs, annotations and a live walkthrough with the engineers, then review passes as the build lands.
03Service
Design systems
One set of components your designers and engineers both trust.
We build the tokens, the components and the documentation, then we make sure the system is actually adopted. A library nobody uses is an expensive Figma file, so adoption is part of the engagement, not an afterthought.
Best for
Teams running two or more products, or one product where every squad has quietly built its own button.
- Typical duration
- 8 to 16 weeks
- Investment
- From $45,000
What you receive
- Token architecture in JSON, with platform outputs for web, iOS and Android
- Figma library with variants and props named to match the code
- Component specifications covering states, sizes, slots and content rules
- Accessibility spec per component: roles, labels, focus order, keyboard behaviour
- Written usage documentation with do and do-not examples
- Contribution guide and a review process for proposing new components
- Two adoption workshops and a migration plan for the products already live
How the time is spent
Weeks 1 to 3
Audit and inventory
We count what exists. Every button, every shade of grey, every one-off input. The count is usually the moment the room agrees.
Weeks 4 to 8
Tokens and foundations
Colour, type, space, radius, elevation, motion. Named for intent, not appearance, so a rebrand does not become a rewrite.
Weeks 9 to 13
Component build
Components designed and specified in priority order, shipped in batches so engineering can build alongside us.
Weeks 14 to 16
Docs, adoption, handover
Documentation, workshops, contribution process, and a migration plan with owners and dates attached.
04Service
Prototyping
Something clickable in front of real people, fast.
When an argument cannot be settled in a meeting, we build the thing and watch people use it. Figma when clicking is enough, coded in the browser when the interaction depends on real data or real speed.
Best for
Teams stuck between two directions, or about to commit engineering months to an unvalidated idea.
- Typical duration
- 2 to 5 weeks
- Investment
- From $12,000
What you receive
- An interactive prototype covering the flows in question, not a slide deck
- A written test script with the tasks and the questions behind them
- Five to eight moderated sessions with participants matching your users
- Session recordings plus a short highlight reel of the moments that matter
- Findings memo separating what we observed from what we recommend
- Revised screens applying the changes the sessions argued for
How the time is spent
Week 1
Scope and script
We agree the question the prototype has to answer and write the tasks that will answer it.
Weeks 2 to 3
Build the prototype
Fidelity set by the question. Enough realism to get honest reactions, no more than that.
Week 4
Test sessions
Moderated sessions, your team watching live. Patterns are usually obvious by the fourth participant.
Week 5
Findings and revisions
We write up what happened, recommend the changes, and redraw the screens that need it.
05Working together
The parts people ask about before signing
Four answers we give on almost every first call, written down so you do not have to ask for them.
How we price
Fixed scope, fixed fee, agreed before we start. If the scope genuinely changes we tell you what it costs before we do the work, never after.
Who you work with
The designers who pitched the work do the work. No account layer, no handover to a junior team after the kickoff call.
How we work with your engineers
They join reviews from week one. Design that has not been pressure-tested against the build is a wish, not a spec.
What happens after
Every engagement ends with a handover session and a written summary. Retained support by the day is available if you want us close by.
05Start a project
Not sure which of these you need?
Most people are not, and that is fine. Describe the problem in a couple of sentences and we will tell you which service fits, or tell you that none of them do.
- Prefer email
- studio@baseline.design
- Current availability
- Taking on two engagements for the coming quarter.
- Typical reply time
- Two working days, from a partner rather than a form.
