# ULookSoGood / From idea to app
Case study0→1
From an idea to a clear product
We organised ULooksGood’s cycle tracking, personalised insights and wellness content into a clearer mobile experience.
Read the case studyThe work
The moments we design
What we put in writing before the design starts.
- The problem
- Who it’s for
- The value proposition
- Jobs to be done
- What’s in and what’s out
- Assumptions to test
- Risks and open questions
- Business goals
- Success measures
- Competitive position
- Key user journeys
- A brief the team can share
The problem
Sounds familiar?
If 2 or more of these ring true, define the product before designing it.
{{ countLabel }}
{{ ctaText }}Book a call
Selected work
Selected work
Client case studies
# Replicate Labs / AI sales coach
Case studyProduct and website
A novel idea, made specific
We redesigned Replicate Labs’ product and website around clearer conversations with its AI sales coach, Keenan.
Read the case studyProof
“Sevgi transformed U Look So Good from an idea into a product that genuinely connects with women.”
- Upwork Job Success
- 100%
- Regular clients
- 10+
- Recognized by
- Dribbble Select
Ways to start
2 ways to start
Define a new product, or a major feature.
-
# New product
Define your product
A shared brief before design and development start.
- Problem and audience
- Value proposition
- In and out of scope
- Product brief
-
# Major feature
Define your feature
Clarify the problem and boundaries of a big new feature.
- Problem and users
- Goals and success
- In and out of scope
- Feature brief
01What do we get at the end?
A short product brief: the problem, who it’s for, the value, what’s in and out, and the assumptions to test.
02How long does a project take?
It depends on the scope. Once we’ve seen the full picture, we’ll share a rough timeline.
03Do we need research first?
Not always. We start with what you know and recommend research only where the risk is high.
04Can this lead into an MVP?
Yes. Many MVPs start with product definition, then move into flows, validation and UI.
05Who should be involved?
The people who make product decisions. We keep the group small and the sessions focused.