Voqo.AI - Onboarding & Conversion
Led onboarding redesign and conversion-focused product flows for a pre-seed voice AI startup, balancing speed, clarity, and system consistency.
ROLE SNAPSHOT
Product Design — onboarding & product flows
UX Strategy — early segmentation & conversion
Frontend Support — rapid iteration with engineers
Client
Voqo.AI
Timeline
3 months
Focus Areas
Onboarding · Early Segmentation · Conversion
CONTEXT
VOQO.ai is a pre-seed voice AI startup helping property managers and real estate professionals manage missed and after-hours calls through automated voice agents. In early-stage SaaS, onboarding and messaging clarity are critical—if users don’t understand value quickly, they drop off.
PROBLEM
New users weren’t sure what to do first or why it mattered
Onboarding needed personalisation without slowing activation
Homepage and product flows needed clearer conversion direction
APPROACH
Benchmarked onboarding patterns from best-in-class tools such as Notion, Miro, and Webflow
Mapped user journey from landing → activation to locate friction points
Used lean validation (internal feedback, demos with quick prototype)
Iterated quickly with engineering constraints in mind
KEY DESIGN DECISIONS
How design decisions balanced clarity, speed, and conversion in an early-stage product.
#Decision Theme 1 — Reducing early cognitive load
Onboarding was structured as a progressive flow to avoid overwhelming users early. I captured only essential information upfront, then deferred complexity until users had momentum.
Evidence: progressive onboarding steps designed to build confidence and reduce early drop-off.
#Decision Theme 2 — Early user segmentation & personalisation
I introduced lightweight segmentation early (e.g., who VOQO is being used for) to capture intent without adding friction. This decision enabled downstream messaging and flows to adapt to different contexts.
Evidence: intent captured early so later experiences can adapt without slowing activation.
#Decision Theme 3 — Designing for speed in real workflows
VOQO’s users operate in time-sensitive environments, so flows needed to support quick action and low effort. I prioritised fast interactions over perfect completeness, and shipped updates quickly when friction was clear.
Evidence: streamlined post-call actions and multilingual support designed for real operational speed.
#Decision Theme 4 — Consistency through systems
As the sole designer within the company at the time, I established reusable components and patterns to keep the product consistent as it evolved. This reduced design debt and accelerated future iteration.
Evidence: reusable patterns applied across onboarding and product flows for consistency and speed.
OUTCOME
Clearer onboarding narrative aligned to user intent
Reduced early friction through progressive steps
Reduced design-to-dev turnaround from days->hours for small flow changes during active development
Established reusable components and patterns used across onboarding, homepage, and post-call flows, enabling faster future experiments
REFLECTION
This project strengthened my ability to design under ambiguity - balancing user empathy with startup speed. I learned to communicate decisions through prototypes, prioritise what matters most for activation, and build systems that scale beyond individual screens.
Check out some of my recent projects.
Voqo.AI - Onboarding & Conversion
Led onboarding redesign and conversion-focused product flows for a pre-seed voice AI startup, balancing speed, clarity, and system consistency.
ROLE SNAPSHOT
Product Design — onboarding & product flows
UX Strategy — early segmentation & conversion
Frontend Support — rapid iteration with engineers
Client
Voqo.AI
Timeline
3 months
Focus Areas
Onboarding · Early Segmentation · Conversion
CONTEXT
VOQO.ai is a pre-seed voice AI startup helping property managers and real estate professionals manage missed and after-hours calls through automated voice agents. In early-stage SaaS, onboarding and messaging clarity are critical—if users don’t understand value quickly, they drop off.
PROBLEM
New users weren’t sure what to do first or why it mattered
Onboarding needed personalisation without slowing activation
Homepage and product flows needed clearer conversion direction
APPROACH
Benchmarked onboarding patterns from best-in-class tools such as Notion, Miro, and Webflow
Mapped user journey from landing → activation to locate friction points
Used lean validation (internal feedback, demos with quick prototype)
Iterated quickly with engineering constraints in mind
KEY DESIGN DECISIONS
How design decisions balanced clarity, speed, and conversion in an early-stage product.
#Decision Theme 1 — Reducing early cognitive load
Onboarding was structured as a progressive flow to avoid overwhelming users early. I captured only essential information upfront, then deferred complexity until users had momentum.
Evidence: progressive onboarding steps designed to build confidence and reduce early drop-off.
#Decision Theme 2 — Early user segmentation & personalisation
I introduced lightweight segmentation early (e.g., who VOQO is being used for) to capture intent without adding friction. This decision enabled downstream messaging and flows to adapt to different contexts.
Evidence: intent captured early so later experiences can adapt without slowing activation.
#Decision Theme 3 — Designing for speed in real workflows
VOQO’s users operate in time-sensitive environments, so flows needed to support quick action and low effort. I prioritised fast interactions over perfect completeness, and shipped updates quickly when friction was clear.
Evidence: streamlined post-call actions and multilingual support designed for real operational speed.
#Decision Theme 4 — Consistency through systems
As the sole designer within the company at the time, I established reusable components and patterns to keep the product consistent as it evolved. This reduced design debt and accelerated future iteration.
Evidence: reusable patterns applied across onboarding and product flows for consistency and speed.
OUTCOME
Clearer onboarding narrative aligned to user intent
Reduced early friction through progressive steps
Reduced design-to-dev turnaround from days->hours for small flow changes during active development
Established reusable components and patterns used across onboarding, homepage, and post-call flows, enabling faster future experiments
REFLECTION
This project strengthened my ability to design under ambiguity - balancing user empathy with startup speed. I learned to communicate decisions through prototypes, prioritise what matters most for activation, and build systems that scale beyond individual screens.
Check out some of my recent projects.
Voqo.AI - Onboarding & Conversion
Led onboarding redesign and conversion-focused product flows for a pre-seed voice AI startup, balancing speed, clarity, and system consistency.
ROLE SNAPSHOT
Product Design — onboarding & product flows
UX Strategy — early segmentation & conversion
Frontend Support — rapid iteration with engineers
Client
Voqo.AI
Timeline
3 months
Focus Areas
Onboarding · Early Segmentation · Conversion
CONTEXT
VOQO.ai is a pre-seed voice AI startup helping property managers and real estate professionals manage missed and after-hours calls through automated voice agents. In early-stage SaaS, onboarding and messaging clarity are critical—if users don’t understand value quickly, they drop off.
PROBLEM
New users weren’t sure what to do first or why it mattered
Onboarding needed personalisation without slowing activation
Homepage and product flows needed clearer conversion direction
APPROACH
Benchmarked onboarding patterns from best-in-class tools such as Notion, Miro, and Webflow
Mapped user journey from landing → activation to locate friction points
Used lean validation (internal feedback, demos with quick prototype)
Iterated quickly with engineering constraints in mind
KEY DESIGN DECISIONS
How design decisions balanced clarity, speed, and conversion in an early-stage product.
#Decision Theme 1 — Reducing early cognitive load
Onboarding was structured as a progressive flow to avoid overwhelming users early. I captured only essential information upfront, then deferred complexity until users had momentum.
Evidence: progressive onboarding steps designed to build confidence and reduce early drop-off.
#Decision Theme 2 — Early user segmentation & personalisation
I introduced lightweight segmentation early (e.g., who VOQO is being used for) to capture intent without adding friction. This decision enabled downstream messaging and flows to adapt to different contexts.
Evidence: intent captured early so later experiences can adapt without slowing activation.
#Decision Theme 3 — Designing for speed in real workflows
VOQO’s users operate in time-sensitive environments, so flows needed to support quick action and low effort. I prioritised fast interactions over perfect completeness, and shipped updates quickly when friction was clear.
Evidence: streamlined post-call actions and multilingual support designed for real operational speed.
#Decision Theme 4 — Consistency through systems
As the sole designer within the company at the time, I established reusable components and patterns to keep the product consistent as it evolved. This reduced design debt and accelerated future iteration.
Evidence: reusable patterns applied across onboarding and product flows for consistency and speed.
OUTCOME
Clearer onboarding narrative aligned to user intent
Reduced early friction through progressive steps
Reduced design-to-dev turnaround from days->hours for small flow changes during active development
Established reusable components and patterns used across onboarding, homepage, and post-call flows, enabling faster future experiments
REFLECTION
This project strengthened my ability to design under ambiguity - balancing user empathy with startup speed. I learned to communicate decisions through prototypes, prioritise what matters most for activation, and build systems that scale beyond individual screens.