All projects
B2B SAAS / ONBOARDING AND ACTIVATION · 2026
Turn2C
From prospect to partner through mutual qualification.
I redesigned B2B partner onboarding around three goals: reduce registration time, maintain high conversion where the journey needs to flow, and control drop-offs at strategic qualification stages. New partner registration went from up to 45 days to a maximum of 2 days. Progression through intermediate stages ranged from 93.4% to 97.8%, with each rate based on the preceding stage.
SHORTER REGISTRATION TIME
45 → 2
days
From up to 45 days to a maximum of 2 days
New partner registration
HIGH CONVERSION
93.4–97.8
%
Progression through fluid intermediate stages
Hotjar · Jul–Sep 2026 · base: previous stage
CONTROLLED DROP-OFF
Qualification
At strategic stages of the journey
Fluid intermediate steps; qualification at decision points
IN 30 SECONDS / WHAT CHANGED


FIG. 00 / The account already exists; the demo is available before full approval.
< 01 > PROBLEM AND CONTEXT
Before asking for commitment, we needed to show value.
The sequence demanded effort and trust before making the platform’s value clear.
PREVIOUS JOURNEY / CONTEXT
70
%
Did not complete document submission
Leads who started pre-registration · historical context
Registration front-loaded company details, contacts, address, digital presence and documents. Individuals also entered a journey intended for businesses; the mismatch surfaced late.
The order of eligibility, effort and value made every field more costly.
Original interface / Turn2C

1
2
3
1
Too much effort before value was clear
2
Documents required at first contact
3
Business eligibility was not clearly stated
FIG. 01 / Previous experience in a partner operation. The screen shows effort concentrated at the start.
Who goes through this journey
Owners, salespeople and operations staff at businesses interested in selling Brazilian consórcio products, a group-based purchasing model. They arrive mainly through acquisition campaigns, usually on mobile, with limited attention and documents not always at hand.
GOAL
Understand the platform’s value, assess its fit for the business and access simulation and sales tools.
CONDITION
The person starting registration may not be the company’s legal representative.
SCOPE
This journey is for partner businesses; consumer registration follows a different path.
< 02 > WHAT CHANGED OUR DIRECTION
The diagnosis changed the order of the journey.
I combined behavioral signals, team knowledge and business rules to identify the conflicts shaping the journey.
The shift that guided the product
BEFORE
Registration and documents before value. Late qualification and little clarity about what came next.
NEW DIRECTION
Eligibility first. A demo before full commitment. Documents in context and visible status through activation.
“The user moves forward with uncertainty, and the human team becomes the glue holding the process together.”
Author’s synthesis · discovery diagnosis recorded on Jan 30, 2026.
Research approach and limitations
The research connected registration behaviour with the needs of the teams supporting the operation.
APPROACH
Multi-method discovery: behaviour, experience and business rules.
METHODS
Internal interviews, Hotjar, journey analysis and benchmarking.
SYNTHESIS
Marketing, Sales, Legal and Support: four perspectives on the same journey.
TYPE
Qualitative + behavioural
SOURCE
Internal teams + Hotjar
SCOPE
Diagnosis dated Jan 30, 2026
Diagnosis of the journey before the redesign. Usage signals were cross-referenced with team accounts; this evidence explains design decisions rather than measuring the new experience’s results.
FROM EVIDENCE TO DECISION
Around 94% of registrations captured in Hotjar took place on mobile. Requesting documents and explaining ownership roles at the start demanded effort before the value proposition was clear. In interviews, Support reported uncertainty about pending requirements and access; Sales, repeated lead qualification work; Marketing, a mismatch between acquisition promises and the next steps.
Legal provided the counterpoint: documents and checks protected the operation and could not simply disappear. The direction was to organise the journey around intent, status and potential: qualify early, demonstrate value before full commitment, and make documents, pending requirements and next steps explicit. Smooth progression, with clear qualification criteria.
< 03 > ARCHITECTURE AND DECISIONS
A clearer journey that still handles complexity.
Eight internal states support two qualification gates. For the partner, the journey appears as four clear milestones.
WHAT THE PARTNER SEES
01
Pre-registration
Account + demo unlocked.
02
Company
Details and documents in context.
03
Review
Timelines and pending items visible.
04
Signature
Formalization and activation.
WHAT THE PRODUCT COORDINATES
01
Pre-registration
Gate 1 · business eligibility (CNPJ)
02
Screening
Company and profile qualification
03
Account creation
Explore before committing
04
Demo
Gate 2 · product fit through the demo
05
Company registration
Business details
06
Review
Internal review
07
Awaiting signature
Digital contract
08
Completed
Active partner
FIVE DECISIONS / FROM DIAGNOSIS TO INTERFACE
DECISION 01 / 05
Confirm the business before asking for commitment.
EVIDENCE / CONTEXT
Individuals were entering a journey designed for businesses. Sales identified the mismatch late, creating requalification and extra effort on both sides.
DECISION
Use the CNPJ business ID as the only initial field at Gate 1, before screening. This keeps entry short and makes the intended audience clear.
TRADE-OFF
Typing, lookup or comprehension errors can block eligible businesses before they see value.
I connected Sales criteria to the entry flow and defined the eligibility gate and the instrumentation needed to investigate it.
Screening dimensions and logic
SCREENING / MATURITY, FIT AND POTENTIAL

FIG. 07 / Two paths, Specialist and Standard, organize questions about context and potential.
FAMILIARITY
Knowledge of consórcio products informs how much context is needed.
FIT
Business segment and its connection to consórcio sales.
CAPACITY
Monthly volume and the share of revenue from consórcio products.
Additional questions complete the commercial and operational profile. The aim is to tailor follow-up without relying on a single indicator or requiring full registration first.
DECISION 02 / 05
Let prospects try the product before full registration.
EVIDENCE / CONTEXT
Prospects had to complete most of the process before understanding the product.
DECISION
Create the account and unlock demo modules before full company registration and approval. Turn2C assesses the business; the prospect assesses product fit.
TRADE-OFF
Early access may create expectations of full activation or expose restricted features.
DECISION 03 / 05
Move complexity to the right moment.
EVIDENCE / CONTEXT
Documents and checks were necessary, but were concentrated before users could see value.
DECISION
Distribute data collection across the journey and use OCR and autofill to reduce manual typing.
TRADE-OFF
Incorrect extraction can create false confidence, discrepancies and rework.


1
2
1
OCR reduces manual typing
2
Validated data stays protected
FIG. 11 / Document uploaded, fields populated using OCR.
DECISION 04 / 05
Replace silent waiting with status and direction.
EVIDENCE / CONTEXT
Partners did not know where they stood, what was missing or what would happen after submission.
DECISION
Show four main milestones, status, timelines, pending items and the next action. The experience continues during review.
TRADE-OFF
Visual simplicity must remain consistent with internal states and the timelines communicated.
DECISION 05 / 05
Give every team the same operational view.
EVIDENCE / CONTEXT
Teams tracked different parts of the same lead, without clear continuity across source, status and history.
DECISION
Integrate the journey with the CRM and create a shared view of the eight registration states.
TRADE-OFF
Synchronization failures can produce conflicting versions of the partner’s status.
I mapped shared states, connected milestones to CRM operations and aligned responsibilities across Product, Engineering, Sales, Legal and Support.
Original interface / Turn2C

1
1
An 8-stage pipeline, with status and progress visible in real time
FIG. 14 / Sanitized pipeline: eight stages, source, status and history.
The same journey, from both sides
Sales, Legal and Support can follow the same state model as Product and Engineering.
< 04 > RESULTS AND INTERPRETATION
What changed, and what the journey began to reveal.
Results span three areas: new partner registration went from up to 45 days to a maximum of 2; progression reached 93.4%–97.8% in smooth intermediate steps; and controlled drop-off occurred at strategic qualification stages. The July–September Hotjar aggregate shows how progression is distributed across the journey.
HOTJAR / JUL–SEP 2026 / AGGREGATE SEQUENCE
How progression varies across the stages.
Entry
100%
Starting reference
Gate 1 · CNPJ and eligibility
46.1%
First progression after eligibility
Contact
93.4%
Base: previous eligibility step
Questions
97.8%
Base: previous contact step
Login
96.2%
Base: previous questions step
Gate 2 · Continuation after the demo
49.2%
Continuing registration after trying the tool
HOW TO READ THIS SAMPLE
Scale: 0–100%. Each rate uses the immediately preceding stage as its denominator. This is neither a cumulative funnel nor a monthly series. Stage volumes and a comparable baseline were not provided.
The next step is to understand the two qualification gates, rather than maximize raw completion.
Operational impact
Structured rules and automation reduced recurring manual Legal review in parts of qualification. Operational effort was not instrumented; the case does not quantify hours saved or attribute staffing changes to the redesign.
Methodological note · operational attribution
Before the redesign, part of qualification depended on manual Legal review. This statement describes less recurring review in part of the flow; it does not quantify hours saved or attribute staffing changes to the redesign.
Journey events and instrumentation
Six product events in Mixpanel began tracking progression from pre-registration to contract. Hotjar later added an aggregate sequence covering three months.
01
Pre-registration
pre_cadastro_iniciado
02
Screening
triagem_iniciada
03
Company
cadastro_empresa_iniciado
04
Submitted
cadastro_enviado_para_analise
05
Approved
cadastro_aprovado
06
Contract
contrato_assinado

FIG. 15 / Historical view of the six milestones instrumented in Mixpanel.
TYPE
Instrumentation delivered
SOURCE
Mixpanel
SCOPE
Active since June 18, 2026
This dashboard documents the instrumented events. The case’s results use the July–September Hotjar aggregate, with rates calculated against the previous step.
< 05 > DELIVERY AND LEADERSHIP
Sustaining direction during and after delivery.
My role was to preserve a coherent vision across discovery, architecture, detailed UI, Engineering, CRM, QA and launch.
Launch a significantly better journey without waiting for the whole organization to be ready for a new governance model.
What the next projects could build on
A formal cross-functional initiative, teams involved from start to finish, clear roles, a controlled launch and post-release measurement. The retrospective became an action plan and a model for future projects.
Delivery records and the 4Ls retrospective

FIG. 16 / Internal UX Wall record: a synthesis built across teams.

FIG. 17 / The 4Ls retrospective: liked, learned, lacked and longed for.
01
Diverge
Record perceptions without assigning blame.
02
Consolidate
Turn accounts into patterns.
03
Prioritize
Separate the immediate response from future cycles.
04
Assign ownership
Make explicit who decides, validates, executes and communicates.
< 06 > NEXT CYCLE
The next decisions start with three questions.
The next cycle focuses on eligibility, perceived value and technical friction while preserving meaningful business qualification.
ELIGIBILITY
Who stops because of a business rule, and who encounters avoidable friction?
DEMO VALUE
What does the partner understand, try and consider before continuing?
CONDITIONS OF USE
Which failures and technical contexts need intervention?
Proposed measures
- Time to activation
- Operational effort
- Rework
- SLA
- Conversion by channel
- Activation quality
- Business impact
Research, direction, solution, measurement and learning: continuity was design’s central responsibility.
Back to the start of the case







