User flows, component library, prototype, and a real engineering handoff — in four to twelve weeks.
What you get
-
User flows and decision points
The logic between every screen is documented. Future features become easier because the team can open the doc and answer “why this way?” without inventing reasons.
-
Component library (Figma + code)
We don't ship a Figma file alone — primary components are also implemented in code (React or Vue, project-dependent). The design-engineering gap shrinks.
-
High-fidelity prototype
Clickable, with realistic data. Usable for user testing. The prototype is built as a real handoff document, not a stakeholder pitch.
-
Handoff documentation for the engineering team
Sixty-plus pages of handoff: per-screen behaviour rules, edge cases, error states, accessibility requirements. Engineers should answer ninety percent of their questions inside that document.
How we approach it
1. Problem framing
Week one is conversations with real users — as many as possible. Existing flow timed and counted. This is the lowest-design and highest-impact stage.
2. Wireframes and flow
Weeks two and three are low-fidelity layout. Every screen starts as a black-and-white box. Decisions happen at flow and layout level, not visual level. The partner often gets nervous here (“it looks too plain”) — that's the right signal.
3. High fidelity and systemise
Weeks four to six add visual layer. Component library, design tokens, documentation — the system emerges, not a pile of separate screens.
4. Prototype and test
Weeks seven to ten: prototype and user testing. Real users push the prototype, we observe and adjust. Skipping this step ships bad design to engineering.
When not to hire us for this
- You only need a mock-up for an investor deck — we build prototypes, not slide art. Cheaper and faster work fits better.
- Engineering team hasn't been hired and won't be in the next six months — a system that sits on the shelf loses value fast.
- Product position isn't clear yet — that's a strategy job, not a design job. Position locks first.
Work from this service
-
Rebuilding a treasury dashboard in three weeks
A nine-person treasury desk was burning twenty-three minutes every morning on a Bootstrap admin panel. We rebuilt it in three weeks and cut margin-check time by 68%.
-
An internal contract-review tool for a thirty-lawyer firm
We automated the mechanical half of contract review with an AI assistant. Per-contract human time dropped from 90 minutes to 12, with false positives under 4%.
If the product is real but engineering handoff is the bottleneck, we can move that. Send a short brief.
salam@qaynaq.com