Proposify Onboarding Redesign #

Key Result: Before the redesign, only ~14% of Proposify trial users completed the onboarding steps - the baseline that prompted rebuilding onboarding around Time to First Behavior (company-reported). BS-0078

Background #

Proposify sells proposal software to sales teams, and like most SaaS companies it discovered its activation problem in the onboarding funnel: only about 14% of trial users were completing the onboarding steps (company-reported). BS-0078 The original flow followed the conventional pattern - welcome the user, then walk them through setup decisions like choosing templates and configuring settings before they ever produce anything.

The redesign started from a behavioral diagnosis rather than a UI one. The behavior that defines an activated Proposify user is not “choose a template” or “complete setup.” It is “send a proposal” - the first performance of the product’s core job, and the moment a trial user experiences actual value. Everything the old flow put in front of that moment was a pre-value choice: a decision demanded of a user who had not yet received any benefit that would justify the effort. Proposify rebuilt onboarding to minimize the distance to that first behavior.

What actually drove the redesign’s logic #

The organizing metric is TTFB, Time to First Behavior, and the measurement framing is what makes this case precise. TTFB puts a clock on the interval between signup and the first performance of the target behavior, over a defined denominator (new trial users) and window (the first 14-30 days). The redesign’s thesis: every pre-value choice lengthens that interval and bleeds users, so the flow should be engineered to shorten it.

The mechanism has two working parts:

• Remove pre-value choices. Templates and settings decisions increase decision friction and abandonment when they arrive before value. The redesign deferred them, guiding users directly toward creating and sending a first proposal.
• Make the first behavior feel achievable. Proposal creation had to work without prior training or heavy configuration, with in-context help carrying the user to the “aha” moment instead of front-loaded setup.

Proposify’s own funnel data supplied the reason to care about the first send. In the company’s analysis of 1.28 million proposals, proposals sent through the platform close at 36% against a ~20% industry average, 43% of won proposals close within 24 hours of being opened, and e-signature-enabled proposals close at three times the rate of those without (company-reported). The same friction-removal logic that drives the onboarding redesign shows up at the prospect’s decision point: an e-signature collapses “print, sign, scan” into one click. And users who send a first proposal convert to paid at higher rates (company-reported correlation) - which is why the redesign aims the entire flow at that single behavior.

The company reports the redesign reduced time from signup to first proposal and raised the share of trials sending one, though exact post-redesign values are not disclosed.

Behavior Fit Assessment #

These ratings are analyst examples of a Behavior Fit Assessment inferred from the company’s account, not direct measurements. For the target behavior, send a first proposal, Identity Fit is high: sending proposals is precisely the work a Proposify trial user signed up to do, so no identity change is being requested. Capability Fit is medium: proposal creation is achievable but only if the product carries the user through it without prior training or heavy configuration. Context Fit is medium: the trial context contains the behavior’s natural trigger (a live deal needing a proposal), but the original onboarding buried it under pre-value template and settings decisions, the friction the redesign existed to remove. The fit profile explains the strategy: with identity already aligned, the leverage was entirely in capability support and context clearing.

Results #

• Pre-redesign baseline: only ~14% of trial users completed onboarding steps (company-reported). BS-0078

• Proposals sent via Proposify close at 36% versus a ~20% industry average (analysis of 1.28M proposals, company-reported).
• 43% of won proposals close within 24 hours of being opened by the prospect (analysis of 1.28M proposals, company-reported).
• E-signature-enabled proposals close at 3x the rate of those without, consistent with friction removal at the prospect’s decision point (company-reported).
• Post-redesign TTFB and the share of trials sending a first proposal are reported as improved, but exact values are not disclosed (company-reported); paid conversion correlates with sending a first proposal (company-reported correlation).

Limitations #

This is single-company, company-reported evidence: use it for the behavioral mechanism and the TTFB measurement frame, and treat the quantitative claims as company-reported unless independently verified. The activation-to-conversion relationship is a correlation confounded by cohort quality, marketing mix, and concurrent product changes - users with a live deal in hand are both more likely to send a proposal and more likely to convert regardless of onboarding design. Exact post-redesign TTFB and delta-behavior values were not disclosed, so the improvement’s magnitude cannot be assessed. The 36% close rate compares Proposify-sent proposals to an industry average across different tools, senders, and deal types, not a controlled comparison.

Lessons #

1. Define activation as a behavior, not a checklist. “Completed onboarding steps” measured compliance with the flow; “sent a first proposal” measures value realization. Once the metric changed, the redesign designed itself: everything between signup and the first behavior is a cost.
2. Defer every pre-value choice. Decisions demanded before a user has experienced benefit are paid in abandonment. Templates and settings can wait; the first performance of the core behavior cannot.
3. Put TTFB on a clock with a real denominator. “New trial users, first 14-30 days, time to first proposal sent” is falsifiable and comparable across cohorts. Vague activation talk is not. What gets a window and a denominator gets managed.

Sources #

• An in-depth case study of how we redesigned onboarding at Proposify (Racki, Medium)
• New user onboarding process (Proposify blog)
• The State of Proposals (Proposify, analysis of 1.28M proposals)
• Evidence Ledger: BS-0078