Where the sharpest work starts. We look at your market, your users and what is
already live, then turn that into a scope with a shape: what comes first, what can wait, and the number we are
trying to move.
Most briefs describe a solution. We look for the problem.
A redesign, a new feature, an app: most briefs arrive describing a solution. Discovery finds
the problem underneath it. Interviews, a teardown of what already exists, and the analytics you have but
haven’t read, all hunting for one thing: the question worth answering.
On AusFreight that question changed the whole site. Most freight marketing is written for
procurement: tonnage, lanes, transit times, rates. The real reader was shipping a household for the first
time. Nobody is anxious about a pallet. Everybody is anxious about their own belongings.
Five ways we do discovery, on their own or as the opening stages of a full project. Each
one ends in something written down.
Stakeholder Interviews
Founders, sales, support, and the people who actually use the product. We ask what has to be true in a
year and where those groups disagree, because that gap is usually the real brief.
You get
One shared picture of who this is for, and why
Market & Competitor Research
A teardown of the products your buyers compare you with: what they promise, how they onboard, where they
leave room. So the design argues for a position instead of copying the category.
You get
A map of where you can be different on purpose
UX Audits
A walkthrough of what is already live: where people drop, what is costing you conversions and what to fix
first. It starts with the free recorded 20-minute audit and goes deeper when the question is bigger.
You get
A prioritised fix list, with the evidence
Requirements & Scoping
Scope, timeline and price, agreed before a single hour is billed, alongside the list of what we are
deliberately not developing. If something later falls outside it, we say so and re-quote.
You get
A fixed scope, a date, and an explicit not-doing list
Analytics Review
The analytics you have but haven’t read. We find the number the project is supposed to move, check
that it can be measured, and point the tracking at it before design starts.
Interviews, a teardown of what already exists, and the analytics you have but haven’t read. We
look at your market, your users and what is already live. We are hunting for one thing: the question
worth answering.
Most briefs arrive describing a solution. This stage finds the problem underneath it.
A written problem statement, and the evidence behind it. Then, from Define: a fixed scope, a date, a
price, and an explicit list of what we are deliberately not developing.
They are written documents, so they are yours to keep and to act on, with us or without us.
Usually less of it, rarely none. Being wrong on a prototype costs a week. Being wrong after
development costs a quarter. Discovery is the cheapest place of all to be wrong, because nothing has
been designed yet.
When the brief really is right, this stage confirms it quickly and turns it into a scope with a date
and a price.
The audit is a recorded 20-minute walkthrough of what is costing you conversions, what to fix first,
and what it would take. No deck, no obligation.
Discovery goes further: interviews, competitor research, your analytics, and a scope you can start
developing from.
Design: research, then structure, then interface. The prototype goes in
front of people who are not us before development starts.
One team carries it the whole way, so nothing learned in discovery gets lost in a handoff.
“Working with Dcycle was a game-changer for us. Their expertise in design and development
helped us elevate our platform with a seamless, user-friendly experience.”
Divyesh PatelCMO, Gumlet
“Dcycle transformed our vision into a sleek, intuitive platform. Their attention to detail
and technical expertise exceeded our expectations.”
A recorded 20-minute walkthrough of what’s costing you conversions, what to fix first,
and what it would take. No deck, no obligation. You keep the audit either way.