Find where people get stuck, and fix it before it is built
We watch real people use your product, redesign the steps where they stall, and test the new version as a clickable prototype - so engineering builds a flow that has already been tried.
Where it goes wrong
Most products lose people at one step, not everywhere. We find that step first, because fixing it is worth more than polishing the other ten.
Pricing page
Trying to: pick a plan
Three plans and a Start free button.Sign up
Trying to: make an account
Email and password.Business details
Trying to: get to the app
A form for GST number, PAN and address - before the app has been seen.Most people who leave, leave hereFirst invoice
Trying to: send one invoice
The moment the product proves it is worth it.Invite a teammate
Trying to: share the work
An email field and a role.
What the analytics say
People leave at business details. That is where, and it is where most redesigns stop looking.
What watching five of them shows
They do not have the GST number to hand, and nothing on the screen says they can come back to it. That is why - and the fix follows from it.
A demo flow - the same sign-up as the review above.
What we deliver is one file you keep
From the first interview to the handoff, everything lives in one design file, organised the way your team will use it - not a folder of exported screenshots.
Research notes
Interviews, a review of the current product and what the analytics show - the evidence every later decision points back to.
Flows
Every path through the product, mapped from what people actually do, including the error and empty states.
Wireframes
Each screen in grey boxes first, so the structure is agreed before anyone argues about colour.
UI screens
The finished screens your team builds against, for every size and state the flows call for.
Design system
Tokens and components with rules for using them, so the next feature looks like this one.
Prototype
A clickable version of the key flows - the one we put in front of users before any code.
Dev handoff
Specs, spacing, states and exported assets, walked through with your engineers.
How we test before it is built
A round takes a clickable prototype and a handful of real people. It is cheap enough to run again after every change that matters.
1.Five people who match your users
Recruited from your customers or the people you sell to - not colleagues, who already know where everything is.
2.One task each
A real goal such as “send your first invoice”, given on the prototype with no hint of where to tap.
3.We watch rather than ask
Where they hesitate, what they say out loud, where they tap first and whether they finish.
4.We change it and test again
What more than one person tripped on is fixed in the prototype, and the next round runs on the new version.
A system, so the fifth feature matches the first
Type, colour and spacing are set once as tokens, and every component is built only from them - so your developers stop reinventing buttons.
A small sample, in the demo app’s tokens.
Questions we get asked
Something else? Email hello@gigax.net.
We already have a product. Do you redesign all of it?
Not by default. We start where people get stuck - one flow, like the sign-up above - fix it, test it, and move on to the next one.
Who takes part in the tests?
Five people who match your users, recruited from your customers or the people you sell to. Each gets one task on the prototype.
Is anything built before it is tested?
No. Changes are tested as a clickable prototype first, so engineering starts on a flow that has already been tried.
What do we get at the end?
One design file you keep: research notes, flows, wireframes, UI screens, the design system, the prototype and the dev handoff.
Can our own engineers build from it?
Yes. The handoff page carries the specs, states and assets, and we walk your engineers through it.
How is it priced?
Tell us the product and the flow that worries you, and we come back with scope, a timeline and a price - not a discovery call first.
Know where people drop off in your product?
Send us the flow that worries you - we come back with where we think people get stuck and how we would test the fix.