- Checkout Continuity78
- Pdp Confidence72
- Mobile Usability60
- Product Discovery80
- Cart Motivation70
- Trust Signals75
- Recovery Paths82
Executive Growth Diagnosis
Lead Value Opportunity Model
Live calculator — adjust inputs and pick a scenario to explore live.
This is not actual revenue loss. This is a scenario model based on observed friction and mock assumptions. Adjust the inputs and pick a scenario to explore live.
Inputs
Scenarios
Opportunity = baseline lead value x a recovery rate derived from lead-form abandonment, scaled by scenario (Conservative 0.25x, Moderate 0.75x, Aggressive 1.5x) and capped at 35% of baseline.
Funnel Journey Map
Severity at each stage from Homepage to Payment.
What's Working
Elements already at or above category baseline. Keep these intact.
Strong, recognisable social proof
The homepage and activity pages carry an extensive wall of well-known client logos (Disney, Apple and many more), which is powerful credibility for a B2B buyer choosing a team-building vendor.
Multiple low-friction contact options
Beyond the form, the Contact Us page offers a phone number and a 'schedule a call' option with a dedicated event coordinator, meeting buyers who prefer to talk.
Clear activity range
Activities and games are well organised (virtual escape room, trivia, scavenger hunt, in-person and hybrid), making it easy to understand the offering.
Helpful 404 recovery
Not-found pages include a search box and recent posts rather than a dead end, giving lost visitors a way back into the site.
Benefit-led messaging
Copy consistently ties activities to outcomes leaders care about (morale, retention, engagement), which is the right frame for the decision-maker.
Critical Conversion Leaks
P1 issues — fix-immediately status.
At a 390px viewport the floating chat panel expands by default and sits on top of page content. On the Contact Us page it overlaps the inquiry form including the Submit button; on the homepage and Activities page it covers the client-logo social proof; on service pages it overlaps the lower content.
Why it matters: The chat panel obscures the single most important action, submitting the inquiry that becomes a lead, and the proof that builds confidence to do so. Anything covering the primary CTA on mobile directly suppresses lead submissions.
Behaviour risk: Mobile visitors mis-tap the chat instead of Submit, lose confidence when the form or logos are partly hidden, and leave without enquiring.
Collapse the chat launcher to a small bubble by default rather than an expanded panel, and use page-targeting so it never overlays the Contact Us form or primary CTAs on mobile. Offset it above the sticky area and consider hiding it entirely on the form page.
Expected KPI movement: Mobile lead-form completion rate up meaningfully from removing CTA obstruction. Requires GA4 lead-event validation.
Implementation notes: Most chat tools (the one in use included) expose default state, position, and per-page display rules. Set collapsed-by-default and exclude the Contact Us path.
Once form_start and generate_lead events exist, compare mobile form-start to submit rate for a 30-day window before and after the chat reposition.
If: If the chat widget no longer overlaps the form and CTAs on mobile, more visitors will complete the inquiry instead of mis-tapping or abandoning.
Primary KPI: Mobile lead-form completion rate
Secondary KPIs:
- Chat-launcher taps near the Submit button
- Mobile Contact Us bounce rate
- generate_lead events on mobile
form_start generate_leadIssue Dashboard
Top 8 issues by priority. Click any card to expand. Filter by severity below.
At a 390px viewport the floating chat panel expands by default and sits on top of page content. On the Contact Us page it overlaps the inquiry form including the Submit button; on the homepage and Activities page it covers the client-logo social proof; on service pages it overlaps the lower content.
Why it matters: The chat panel obscures the single most important action, submitting the inquiry that becomes a lead, and the proof that builds confidence to do so. Anything covering the primary CTA on mobile directly suppresses lead submissions.
Behaviour risk: Mobile visitors mis-tap the chat instead of Submit, lose confidence when the form or logos are partly hidden, and leave without enquiring.
Collapse the chat launcher to a small bubble by default rather than an expanded panel, and use page-targeting so it never overlays the Contact Us form or primary CTAs on mobile. Offset it above the sticky area and consider hiding it entirely on the form page.
Expected KPI movement: Mobile lead-form completion rate up meaningfully from removing CTA obstruction. Requires GA4 lead-event validation.
Implementation notes: Most chat tools (the one in use included) expose default state, position, and per-page display rules. Set collapsed-by-default and exclude the Contact Us path.
Once form_start and generate_lead events exist, compare mobile form-start to submit rate for a 30-day window before and after the chat reposition.
If: If the chat widget no longer overlaps the form and CTAs on mobile, more visitors will complete the inquiry instead of mis-tapping or abandoning.
Primary KPI: Mobile lead-form completion rate
Secondary KPIs:
- Chat-launcher taps near the Submit button
- Mobile Contact Us bounce rate
- generate_lead events on mobile
form_start generate_leadOn the Virtual Escape Room service page at 390px the hero area below the title renders as a large empty block, suggesting a hero image or video that is not loading or is not configured for mobile. The Book Now and FAQs links are present above it.
Why it matters: The hero is the first impression that justifies the activity. A blank hero on mobile, where most traffic lands, wastes the most valuable screen space and weakens the case to enquire.
Behaviour risk: Visitors perceive the page as broken or unfinished and lose confidence before reaching the Book Now path.
Audit the service-page hero on mobile; ensure the hero media has a mobile source and a fallback image, and lazy-load it without leaving a blank reserved space. Re-test across the main service pages.
Expected KPI movement: Service-page engagement and Book Now click-through up on mobile. Requires validation.
Implementation notes: Check the theme/page-builder hero block for a missing mobile asset or a broken background-video reference; provide a static poster image fallback.
Compare mobile service-page scroll depth and Book Now / form-start rate before and after the hero fix.
If: If service-page heroes render correctly on mobile, more visitors will engage and proceed to Book Now or the inquiry form.
Primary KPI: Mobile service-page to form-start rate
Secondary KPIs:
- Mobile scroll depth
- Book Now click-through
- Service-page exit rate
page_view form_startThe Contact Us form requests name, email, phone, activity of interest, estimated group size, preferred dates and times, budget, how-did-you-hear, and a question box, with several fields marked required (name, email, activity, group size, preferred dates).
Why it matters: Every extra required field lowers completion. For a first-touch inquiry the business mainly needs enough to start a conversation; details like exact dates and budget can be gathered by the coordinator on the follow-up call.
Behaviour risk: Buyers who are early in research abandon a form that feels like a full booking brief, especially on mobile.
Reduce required fields to name, email, and activity (or group size). Make phone, budget, dates, and how-did-you-hear optional. Consider a two-step form: contact details first, then optional event details.
Expected KPI movement: Lead-form completion rate up from fewer required fields. Requires GA4 validation.
Implementation notes: Most form builders allow toggling required and reordering fields, and support multi-step forms. Keep the optional fields visible but not blocking.
Track form_start to generate_lead rate before and after reducing required fields; monitor lead quality on the sales side.
If: If the inquiry form requires fewer fields, more visitors will complete it without reducing usable lead quality.
Primary KPI: Lead-form completion rate
Secondary KPIs:
- Field-level drop-off
- Leads per session
- Sales-qualified rate of submitted leads
form_start generate_leadThe Contact Us page leads with a phone number and copy but shows no client logos, testimonials, ratings, or reassurance (response time, no-obligation) next to the form itself. The strong logo wall lives on the homepage and activity pages, not where the visitor commits.
Why it matters: Proof works hardest at the point of action. Re-stating credibility beside the form reduces hesitation exactly when the visitor decides whether to hand over their details.
Behaviour risk: Visitors who arrive directly at the form, or scroll past the logos, submit at a lower rate without a confidence cue at the decision point.
Add a compact trust strip beside or above the form: a few recognisable client logos, a one-line testimonial, a star rating if available, and a reassurance line ('We reply within one business day, no obligation').
Expected KPI movement: Lead-form completion rate up modestly from proof at the point of action. Requires validation.
Implementation notes: Reuse existing logo and testimonial assets; place a small responsive trust block adjacent to the form column.
A/B test the form page with and without the trust strip; compare form-start to submit rate.
If: If trust signals appear beside the inquiry form, more visitors will complete it.
Primary KPI: Lead-form completion rate
Secondary KPIs:
- Form-start to submit rate
- Time on Contact Us page
- Scroll depth on the form page
form_start generate_leadAbove the fold the homepage states a general promise ('Effortless and Unforgettable Team Building Games and Activities') and a single Get More Info button, but no specific differentiator, quantified outcome, format/price cue, or rating. The proof (logos, outcomes) appears only after scrolling.
Why it matters: B2B buyers comparing vendors decide quickly whether a site is credible and relevant. A specific value line and a proof cue above the fold improve the rate at which visitors continue into activities or the form.
Behaviour risk: First-time visitors do not see why BreakoutIQ over a competitor and bounce before scrolling to the proof.
Add a concise value line (what makes BreakoutIQ different, e.g. fully-hosted, facilitator-led, X teams served) and a proof cue (a rating, a headline client, or a quantified outcome) into the hero, and keep one clear primary CTA.
Expected KPI movement: Homepage-to-activities and homepage-to-form rates up for new visitors. Requires validation.
Implementation notes: Edit the hero block; keep copy tight for mobile. Avoid adding a second competing CTA.
Compare new-user homepage engagement and click-through to activities/Contact Us before and after the hero change.
If: If the homepage hero states a specific value proposition and a proof cue, more first-time visitors will continue toward an inquiry.
Primary KPI: Homepage-to-inquiry-path click-through (new users)
Secondary KPIs:
- Homepage bounce rate
- Scroll depth
- Get More Info click rate
page_view form_startGA4 records sessions for breakoutiq.com but no lead key-events (generate_lead, form_submit) are configured, so form starts, completions, and abandonment are not measured. This is documented as a known gap in the client config.
Why it matters: Without lead events, none of the recommendations here can be validated with real numbers, paid spend cannot be optimised to cost-per-lead, and the revenue calculator must use estimates.
Behaviour risk: The business optimises on traffic, not leads, and cannot see which pages or campaigns actually generate inquiries.
Configure GA4 events: form_start on first field focus, generate_lead on successful submit (with a thank-you page or event), and phone_click. Mark generate_lead as a key event and import to Google Ads if running paid.
Expected KPI movement: Enables measurement and optimisation; indirect conversion lift via better decisions.
Implementation notes: Use GTM or the form builder's GA4 integration. A dedicated thank-you URL makes generate_lead trivial to track.
Confirm events fire in GA4 DebugView, then build a Contact funnel exploration (form_start to generate_lead).
If: If lead events are configured, the team can measure and improve the inquiry funnel and validate every other fix.
Primary KPI: Availability of generate_lead data
Secondary KPIs:
- Form-start to lead rate
- Cost per lead (if paid)
- Leads by landing page
form_start generate_lead phone_clickCredibility is carried by a large wall of client logos, but there are few named testimonials with a person and role, and no quantified outcomes (satisfaction score, repeat-booking rate, number of events run).
Why it matters: Logos prove who bought; outcomes and named quotes prove it worked. Adding outcome proof strengthens the case for a higher-consideration B2B purchase.
Behaviour risk: Buyers discount a logo wall as table-stakes and want evidence of results before enquiring.
Add two or three named testimonials (person, role, company) and a couple of quantified outcomes near the logos and on service pages.
Expected KPI movement: Modest lift in inquiry rate from stronger proof. Requires validation.
Implementation notes: Collect two or three short quotes with permission; add a small outcomes strip. Keep claims honest and specific.
Monitor inquiry rate after adding outcome proof; optionally A/B test the testimonial block.
If: If named testimonials and quantified outcomes accompany the logos, more buyers will trust the offering and enquire.
Primary KPI: Inquiry rate
Secondary KPIs:
- Time on page
- Scroll depth to proof
- Service-page to form rate
page_view form_startThe Contact Us page offers the form, a phone number, and a schedule-a-call link, while the chat widget runs simultaneously. Several parallel paths compete without one obviously primary action.
Why it matters: Choice is good, but on mobile a clear primary path (the form) with secondary options reduces decision friction and keeps most leads in a trackable channel.
Behaviour risk: Some visitors hesitate among options or default to chat, which may be unstaffed, instead of leaving contactable details.
Make the form the visual primary action; present phone and schedule-a-call as clearly secondary. Ensure chat has staffed hours or an after-hours capture-details fallback.
Expected KPI movement: More inquiries captured in trackable channels. Requires validation.
Implementation notes: Visual hierarchy change plus a chat after-hours fallback message that points to the form.
Track channel mix of inquiries (form vs phone vs chat) once events are configured.
If: If the form is clearly the primary contact path, more visitors will submit trackable inquiries.
Primary KPI: Form share of total inquiries
Secondary KPIs:
- generate_lead events
- Phone-click events
- Chat-initiated conversations
form_start generate_lead phone_clickCompetitor Inspiration
Patterns from named competitors — inspiration, not direct copying.
The category leader leads with a specific, benefit-led promise and surfaces quantified proof (number of teams served, ratings) high on the page rather than a logo wall alone.
Pair the BreakoutIQ logo wall with a specific value line and quantified outcomes above the fold.
Confetti keeps the path to enquiry short and surfaces pricing and format cues early, reducing the unknowns a buyer carries into the form.
Show format and price cues earlier and shorten the inquiry form to the essentials.
Outback repeats testimonials, ratings, and reassurance next to its request-a-quote form, not only on the homepage.
Add a compact trust strip beside the Contact Us form so proof is present where the decision is made.
Prioritised Roadmap
Severity-coded items grouped by horizon.
This Week
2 items- I-001 Chat widget overlaps the lead-form Submit button and CTAs on mobile
- I-008 No GA4 lead events configured, so conversions are unmeasured
This Month
4 items- I-002 Service-page hero renders empty on mobile
- I-003 Inquiry form is long, with many required fields
- I-004 No trust signals beside the inquiry form
- I-005 Homepage hero lacks a specific value proposition and outcome proof above the fold
This Quarter
2 items- I-006 Social proof is logos-only, without quantified outcomes or named testimonials
- I-007 Competing contact paths without a clear primary action
Measurement Plan
KPI × GA4 events × segments needed to validate each fix.
| Issue | KPI affected | GA4 events | Segment | Funnel report | Validation |
|---|---|---|---|---|---|
| I-001 | Mobile lead-form completion rate | form_start generate_lead |
device=mobile | Contact funnel: form_start to generate_lead | 30-day pre/post chat reposition |
| I-002 | Mobile service-page to form-start rate | page_view form_start |
device=mobile, service-page entrances | Service-page engagement | 30-day pre/post hero fix |
| I-003 | Lead-form completion rate | form_start generate_lead |
all sessions reaching Contact Us | Form field drop-off | 30-day pre/post field reduction |
| I-004 | Form-start to submit rate | form_start generate_lead |
Contact Us page sessions | Contact funnel | A/B test trust strip vs control |
| I-005 | Homepage-to-inquiry-path click-through | page_view form_start |
new users landing on homepage | Landing-page engagement | 30-day pre/post hero change |
| I-008 | Availability of lead conversion data | form_start generate_lead phone_click |
all sessions | Contact funnel exploration (new) | Confirm events in DebugView, then baseline 30 days |
Experiment Backlog
One hypothesis per P1 and P2 issue.
If: If the chat widget no longer overlaps the form and CTAs on mobile, more visitors will complete the inquiry instead of mis-tapping or abandoning.
Primary KPI: Mobile lead-form completion rate
Secondary KPIs: Chat-launcher taps near the Submit button, Mobile Contact Us bounce rate, generate_lead events on mobile
If: If service-page heroes render correctly on mobile, more visitors will engage and proceed to Book Now or the inquiry form.
Primary KPI: Mobile service-page to form-start rate
Secondary KPIs: Mobile scroll depth, Book Now click-through, Service-page exit rate
If: If the inquiry form requires fewer fields, more visitors will complete it without reducing usable lead quality.
Primary KPI: Lead-form completion rate
Secondary KPIs: Field-level drop-off, Leads per session, Sales-qualified rate of submitted leads
If: If trust signals appear beside the inquiry form, more visitors will complete it.
Primary KPI: Lead-form completion rate
Secondary KPIs: Form-start to submit rate, Time on Contact Us page, Scroll depth on the form page
If: If the homepage hero states a specific value proposition and a proof cue, more first-time visitors will continue toward an inquiry.
Primary KPI: Homepage-to-inquiry-path click-through (new users)
Secondary KPIs: Homepage bounce rate, Scroll depth, Get More Info click rate
If: If lead events are configured, the team can measure and improve the inquiry funnel and validate every other fix.
Primary KPI: Availability of generate_lead data
Secondary KPIs: Form-start to lead rate, Cost per lead (if paid), Leads by landing page