Aero StudioServices
Four things we do properly, rather than twelve we do adequately.
Product interface design
The core of what we do. Screens, flows, empty states, error states, and the unglamorous parts nobody demos — bulk actions, permissions, the settings page that quietly determines whether the product feels trustworthy.
We work directly alongside your engineers rather than throwing files over a wall. In practice that means we are in your issue tracker, we review the implementation, and we fix the spacing ourselves if that is faster than describing it.
Design systems
Component libraries that engineers actually adopt, which is a different problem from component libraries that look complete in a design file. We start from what you are already shipping, consolidate the accidental variations, and document the rules that matter.
The deliverable is a working library in your framework, a token set, and written guidance on when to reach for each component — including when not to. Where it makes sense we also set up the review process that stops the system fragmenting again six months later.
Brand identity
Wordmarks, colour, typography and the systems around them. We come at identity from a digital-first angle: if a colour palette fails contrast requirements or a typeface has no usable variable version, we would rather find out during design than during implementation.
Every identity project ships with a stylesheet and a set of web-ready assets alongside the usual print guidelines.
Audits and second opinions
A fixed two-week review of an existing product, with a written report and a working session with your team. Useful when you suspect something is wrong but the internal debate has stalled, or when you are about to commit budget to a rebuild and want an outside read first.
This is the lowest-commitment way to work with us, and it is often how longer engagements start.
How engagements are structured
| Phase | Duration | Output |
|---|---|---|
| Discovery | 1–3 weeks | Written findings, problem framing, scope proposal |
| Direction | 2–4 weeks | Two or three explored directions, one recommended |
| Production | 4–16 weeks | Final design, specifications, implementation support |
| Handover | 1–2 weeks | Documentation, asset library, team walkthrough |
Each phase is quoted and agreed separately. You can stop after any of them, and occasionally clients do — a discovery phase that concludes the rebuild is unnecessary has still paid for itself.
What we need from you
- One person empowered to make decisions, available for a weekly review.
- Access to whoever actually uses the product, at least for a few conversations.
- Honesty about constraints early. The ones you are embarrassed about are usually the important ones.