What we find
The CLI is loved and the dashboard is tolerated.
- Time to first successful call is measured in hours.
- Your errors say what failed and never what to do.
- The docs are the product, and they were written last.
- Everything needs a mouse, and your users resent it.
What you get
Measured on time to first success.
We time it first: signup to a working call, on a real machine, with somebody who has never used it. That number becomes the brief. Everything standing between them and success is justified or removed, and every error message gets a fix inside it.
- Time signup to first working call, then cut it down
- Build onboarding around a working example, not a tour
- Make every error name the fix, not just the failure
- Design keyboard-first navigation and a command palette
- Design the docs and the product as one thing
- Treat dark mode as a design rather than an inversion
How it runs
Time it, cut it, fix the errors, match the docs.
Time it
Signup to working call. Always longer than anyone thinks.
Cut the path
Every step justified or removed.
Fix the errors
Each one names the cause and the fix.
Match the docs
Product and documentation designed together.