Service 02
Product Design built for conversion, not for the portfolio
A beautiful interface that doesn't convert is a cost, not an asset. We design screens from an explicit decision: what this flow needs the user to be able to do, and what stands in the way. Wireframe before visuals, system before screens, evidence before opinion.
- Duration
- 4 to 12 weeks, depending on product scope
- Format
- Remote, with incremental deliveries and biweekly reviews
- For
- Teams building or rebuilding
- Reply
- Within 2 business days
When it makes sense
Do you recognize any of these signs?
If two or more show up in your context, this service is probably the right starting point.
- Every new screen looks like it belongs to a different product
- The design system exists in Figma, but nobody uses it
- Dev and design clash at handoff every sprint
- Onboarding loses users and nobody knows at which step
- Every visual change reopens the same debate about taste
How it works
The Product Design steps
The process is the same in every project. What changes is the domain, never the decision criteria.
- Step 01
Architecture
We define the information structure and the critical flows before any pixel. This is where most usability problems are either solved or created.
- Step 02
Wireframe
Low fidelity first, on purpose. Without color or style, the conversation stays on hierarchy and flow, which is what really decides conversion.
- Step 03
System
Documented tokens, components and states. The system comes before the final screens so that consistency is a result of structure, not of discipline.
- Step 04
Handoff
Specs that answer questions before the developer has to ask: error, empty, loading and focus states, plus responsive behavior.
Deliverables
What you get
Scope closed and documented before kickoff. No surprise deliverables and no creative black box.
- Low and high fidelity wireframes with the rationale behind each decision
- Interactive prototypes ready for user testing
- Scalable design system with tokens, components and states
- Handoff documentation the development team can actually follow
- Accessibility specs for each component, to the WCAG 2.1 AA standard
Who it is for
Teams about to build or rebuild a product who need design that supports scale, not just the next release.
Questions
Frequently asked questions about Product Design
What people usually ask before closing the scope.
Do you deliver the design system or just the screens?
The design system is a standard deliverable, not an add-on. Delivering screens without a system guarantees that consistency is lost by the third sprint after we leave. The system is what makes the work outlast the project.
Do you work with the client's in-house development team?
Yes, and it's the preferred scenario. Handoff is documented so the in-house team can maintain and evolve the product without depending on us. Client autonomy is a quality criterion for the delivery.
Is accessibility in scope or an extra cost?
It's in scope. Contrast, visible focus, keyboard navigation, semantic hierarchy and labels are specified for each component. Treating accessibility as a later phase costs more and delivers worse results.
Next step
Your product is losing users somewhere. The question is where.
Describe the context and we get back to you within 2 business days with an initial read of the problem. If Heuristik is not the right fit for your case, we tell you on the first call.