Design
Approval screens, the assistant's voice, and dashboards, tested with the people who will use them.
Quoted after a call
- Time
- On its own, or alongside a build
- Terms
- Quoted after a call, priced before work starts.
- Nothing expands without your agreement
What you get.
- 01
UI/UX for AI tools, including review and approval screens
- 02
Assistant design: how it talks, and when it hands off to a person
- 03
Dashboards and reports your team can read in seconds
- 04
Prototypes tested with real users before anything is built
A approval screen: an approval screen with one decision and numbered notes on why it is built that way.
How it runs.
- 01
Meet the people
Who uses it, what they need to trust it, and where they decide.
First - 02
Prototype
Clickable screens and the assistant's voice, built around real tasks.
Then - 03
Test
With the people who will use it, before anything is built.
Then - 04
Hand off
Designs and components ready for the build.
Last
Is it a fit?
Choose it when
- Your team will approve agent work every day and the screen has to take seconds.
- You are shipping an assistant and need its voice and hand-off rules decided first.
- Your team reads a dashboard every week and it has to make sense in seconds.
Skip it when
- The workflow has no screen and a person approves from their inbox: go to the Build Sprint.
- You need positioning, messaging, or an identity: that is the Brand service.
- You have no plan to build the screens: start with the Assessment to find the workflow first.
Not included
- The build itself. Designs hand off to a Build Sprint or to your own team.
- Identity, messaging, or positioning. That is the Brand service.
- Marketing campaign copy.
What this looks like for you.
Financial services
An advisor's approval screen for client emails, readable on a phone, with the evidence one tap away.
Private equity
An operating partner's review screen for the weekly portfolio pack: what changed, and one action to approve.
Digital assets
A controller's match screen: the bridge from activity to bank amount, with the safe action first.
Before you book a call.
01What is handed off?
Clickable screens, the assistant's voice and hand-off rules, and the dashboard layouts, in files your team or ours can build from.
02Does it work without a build?
Yes. Hand the designs to your own team, or keep them for a later Sprint.
03Who tests it?
The people who will use it, before anything is built. We watch them run real tasks on the prototype and fix what slows them down.
04Why is it quoted?
Because the scope ranges from one approval screen to an assistant and a set of dashboards. We price it before work starts.
05What makes an approval screen good?
One decision per screen, the evidence one tap away, and the safe action as the primary button. A person can approve, edit, or skip in seconds.
06Can the assistant talk in our voice?
Yes. We write the voice from how your team already speaks to clients. Anything about a client's money, a dispute, or a complaint hands off to a person.
Make it something people trust.
UI/UX and product design, tested with the people who will use it.
- Quoted after a call
- Priced before work starts
- On its own, or alongside a build
Ground track · wherever our clients operate