Two Inputs Set The Branch
Free-text business description plus state are enough to decide whether the visitor gets a matrix, a curated package, a policy-specific route, or a compressed fast lane.
Competitive Research · Signup Branching Read
One signup shell. Five different MQL branches.
Simply Business is useful because it shows how one calm intake frame can branch into very different quote and MQL paths after only two early inputs: business description and state. Once classification firms up, the system swaps recommendation container, route family, question depth, and contact timing.
Artifact Pack
5
Branch patterns
4
Browser videos
9
Embedded screenshots
4
Route families
Key Finding
Simply Business does not treat every started quote as the same kind of lead. The MQL decision is which branch the visitor earns: matrix-first exploration, curated package, BOP underwriting, or a compressed quick_to_quote lane.
What The Signup Flow Is Really Doing
This is a branching MQL router disguised as one quote form. The shell stays stable while early classification decides what package logic, qualification depth, and contact posture the visitor gets.
All fake user data used
example.com emails only
Live run date: 2026-04-05
Selective Friction Protects Routing
The contractor ambiguity modal is not generic education. It is a containment device that keeps an expensive or noisy lead from entering the wrong branch.
Package Type Signals MQL Quality
Some visitors earn broad comparison before contact capture. Others get one recommended package, which is a stronger sign that Simply Business already trusts the classification enough to narrow the sale.
Route Family Is The Real Output
The route family changes with the trade. Generic underwriting, BOP underwriting, and quick_to_quote are the real downstream outputs of the signup branch decision.
Signup Branch Model
For our own MQL branching, the useful pattern is how Simply Business keeps one calm first screen and then decisively swaps package logic, route family, and qualification depth.
White-Collar Advisory Path
Broad recommendation matrix, then a short business-details step, then lead capture. This is the cleanest “earned contact capture” branch.
- Top choice is Professional Liability / E&O.
- Coverage cards explain rationale, what is covered, and limit teases.
- Contact collection comes after the user has already seen a tailored recommendation layer.
Platform-Aware Retail Path
Instead of a matrix, the user gets “Essential protection” and then Amazon-specific underwriting language immediately after they start.
- Seller requirement copy is explicit and operational.
- Experience and operating-location questions show up early.
- The package-first pattern reduces comparison burden.
Premises And Property Path
The system leans hard into property and premises risk, then routes into a BOP-specific questionnaire rather than a generic business path.
- Package copy centers slips, fire, equipment, inventory, and building limits.
- Route and title become policy-specific.
- Contact framing is more policyholder-oriented than generic lead capture.
Compressed Service-Business Path
Janitorial gets a tailored package, then a much slimmer qualification step than the branches above.
- Very short first screen after start quote.
- Plain Next CTA instead of Next step.
- Fewer visible questions and less cognitive load.
Ambiguity Resolution That Actually Branches
The modal does not just educate the user. Choosing Handyperson rewrites the classification and drops the user into a cheaper, lighter funnel.
- Handyperson essential protection replaces the contractor framing.
- Package is GL-led, not heavy construction-led.
- The route resolves into quick_to_quote, proving a real downstream fork.
Route Families
These route families are the clearest evidence that Simply Business is assigning different signup and MQL outcomes rather than sending every lead through one universal form.
| Route Family | Observed On | What It Means | Behavioral Signal |
|---|---|---|---|
| /q/coverage_selection/recommendationsMatrix screen | IT consulting | Coverage comparison comes before underwriting. | The system wants the user to inspect multiple relevant coverages first. |
| /q/coverage_selection/tailored_coverageCurated package | E-commerce, restaurants, janitorial, handyperson | A default package is presented with a secondary “pick and choose” path. | The system makes a recommendation before it starts asking operational questions. |
| /q/usa/usa/business/...Generic underwriting | E-commerce, IT consulting | Standard business details flow after recommendation. | Flexible enough for trade-specific questions without a policy-specific shell. |
| /q/business_owners_policy/usa/business/...BOP-specific underwriting | Restaurants | Policy container shifts to Business Owners Policy up front. | The risk shape is premises-heavy enough to justify a policy-specific route. |
| /q/usa/usa/quick_to_quote/...Fast-lane qualification | Janitorial, handyperson | Compressed questionnaire with fewer visible questions. | These trades are being funneled toward momentum and reduced friction. |
TOFU / MQL Configs
Recovered from the strongest live branches rather than invented from theory: these are the actual signup configurations Simply Business appears to switch between once the business is classified.
Matrix-First Exploration
Best fit for white-collar advisory intent. The visitor earns a comparison surface before contact capture, which makes the lead feel informed rather than prematurely gated.
Curated Package First
Used on e-commerce and several service trades. The system picks a default package first, then lets the buyer explore alternates second.
Policy-Specific Questionnaire
Restaurants get routed into a BOP-specific container rather than a generic business-details path, which signals Simply Business already knows the policy frame it wants.
Quick-To-Quote Fast Lane
Janitorial and handyperson routes compress the visible question stack and push for momentum. This is the clearest high-speed MQL branch in the set.
Ambiguity Correction Reroute
The contractor modal is a real branch switch. The user can be rerouted into a lighter handyperson funnel instead of being forced through the heavier contractor path.
Video Walkthroughs
Native browser recordings so you can evaluate where each branch narrows the visitor, when recommendation logic appears, and how late contact capture arrives.
IT Consulting
Shows the matrix-first branch: welcome → recommendations → short business-details underwriting.
E-commerce
Shows the curated Essential protection package and the Amazon-specific underwriting transition.
Restaurants
Shows the premises-heavy BOP package and the route shift into business-owner-policy underwriting.
Contractor → Handyperson Fork
Shows the ambiguity correction resolving into its own package and then a lighter quick_to_quote path.
Screen Evidence
A scrollable field guide to the strongest screenshots, with enough room to actually read the screens before jumping to interpretation.
Corrective Modal
The system interrupts the flow to teach the contractor vs handyperson boundary before proceeding.
E-commerce Package
Curated recommendation with a default package and a subordinate exploration path.
Amazon-Specific Questions
Clear platform requirement copy appears early and makes the underwriting feel purpose-built.
Restaurant Merchandising
Property and premises risk dominates the copy, which is very different from consultant language.
Service-Business Package
Janitorial gets a lighter package with tools coverage and a cleaner jump to a fast-lane quote path.
Quick-To-Quote Shell
The shell collapses into a much slimmer question stack with a plain Next button and fewer visible asks.
Taxonomy Depth
Food service is not treated as one bucket. The search results already reflect Simply Business’s internal ontology.
BOP-Specific Underwriting
The restaurant route becomes policy-specific, which reinforces the seriousness of the package framing.
Rerouted Handyperson Path
After correction, the user is not returned to contractor underwriting. They are sent into a lighter handyperson funnel.