Most AI products now have a moment where the software has done some work and a person has to sign it off: a reconciled ledger, a drafted contract, a flagged payment, a suggested plan. That screen decides whether people trust the product. When it's wrong, they either re-check everything by hand or approve without reading.
This is a fixed week to get one of those screens right, end to end.
One approval flow, five days, £5,000. Designed and built in your codebase, handed over as a pull request your engineers review. Written updates every day. No meetings needed.
Signs you need it
What you get
How the week runs
Before day 1. You send a short written intake: the flow, who uses it, three to five real examples, and access to the code and a staging environment.
Day 1. I map the flow and send a written plan by the end of the day: what changes, what stays, what fits in the week. You reply yes, or tell me what to change.
Days 2 and 3. Design, shared as working screens as they develop, with notes on each decision.
Day 4. Build, in your codebase.
Day 5. Polish, the pull request, the decision record and a written handover.
What it isn't
Not a redesign of your whole product, not a design system and not a strategy deck. One flow, designed and shipped. If you need more afterwards, it's quoted separately.
A worked example
In Kaido, the clinical workspace I design and build, a physio records 19 heel raises against a target of 25. The record updates straight away. The patient's status stays at Not yet, because readiness is the clinician's decision, not the number's. The software records and suggests; the person decides, and the screen shows which is which.
That separation is the core of every approval flow I design. The rest are in Keep the judgment, the twelve patterns I work from.
Who does the work
Dan Andrews. Ten years designing and building software across developer tools, financial data, clinical care and consumer apps. I was a Senior Product Designer at Spotify for three and a half years, before that a host of start-ups and scale-ups. I design and ship in code, so the week ends in your product, not in a file.
Questions
Do we need meetings?
No. Everything runs in writing: a short intake, a written plan on day one, daily written updates and a pull request at the end. If your team prefers a call at some point, that's fine too.
What do you need from us?
Access to the code (a branch or a fork is fine), a staging or demo environment, three to five real examples of the decision the flow supports, and one engineer who can review the pull request and answer questions in writing.
What if the flow is bigger than five days?
You'll know on day one. The written plan says what fits in the week and what doesn't. We either cut to fit, or I quote the rest separately before any extra work starts.
What stack do you work in?
I design and build in code, on the web and natively on iOS. I work in your front end and follow your conventions and components, so the result reads like your team wrote it.
What about our data?
I work under your NDA, with staging or anonymised data wherever possible. Nothing from your product appears on this site without your written permission.
How does payment work?
£5,000 for the week, fixed. Half to book the start date, half on handover.
How do we start?
Email hello@cybercyber.ai with the flow you mean and a line on who uses it. You'll get a written reply within a working day, with a yes or a no and the earliest start date.
Email hello@cybercyber.ai with the flow you mean and a line on who uses it. You'll get a written reply within a working day, with a yes or a no and the earliest start date.