Strategy Pivot — Application-Centric Website Model (2026-02-18)

Overview

During the ^[1], Mark and Melissa aligned on a fundamental reframe of the ^[2] website strategy. The current site is too product-centric — organized around machine models — and will be restructured around applications: the real-world contexts in which customers deploy the equipment.

The core insight: customers don't buy a juicing machine, they buy fresh juice at a grocery store, or a hotel breakfast bar experience. The website should meet them there.

The Decision

From: Product-centric navigation (Product A, Product B, Product C)
To: Application-centric navigation (4–5 pages organized by use case)

Mark's framing from the call:

"When you buy a lawnmower, you're buying short grass. People don't buy products. We're too focused on machines."

Each application page will:
- Feature the use case prominently (imagery of happy customers, the machine in context)
- Explain the benefits specific to that deployment scenario
- Surface the relevant product(s) for that application
- Drive toward a primary CTA: Get a Quote or Get a Proposal

Proposed Application Pages

Discussed examples (final list to be confirmed with Miriam):

Application	Notes
Fresh Juice at Retail	Grocery store produce department
Juice Bar	Standalone retail juice bar context
Hotel Breakfast Bar	Different machine profile than restaurant
Restaurant / Food Service	Large-volume food service application
(TBD 4th–5th application)	To be defined with client

Product pages remain — they are the destination, not the entry point. Application pages link into product pages, preserving SEO integrity without duplicating product content across segments.

Rationale

Citrus America's current site leads with machine specs and model names, which don't map to how buyers think about their problem
Miriam's team is increasingly in decision-making and sales mode; the site needs to support that motion
Application pages allow targeted ad groups and SEO content to align with buyer intent rather than product taxonomy
Avoids the SEO dilution risk of duplicating product pages per segment (e.g., two separate FAS/ABS pages for grocery vs. food service)

HubSpot SQL Criteria — Loosen for Lead Flow

The current Sales Qualified Lead (SQL) definition in HubSpot requires a full BANT+ profile that is nearly impossible to satisfy in practice. The Marketing Qualified Lead criteria are fine; the SQL threshold is the problem.

Action: Melissa to propose loosening SQL criteria to Miriam on the 2026-02-19 call. Revised framing: "Could this person use the product, and are they interested?"

ROI Calculator

Mark proposed adding an ROI calculator to the site. Melissa agreed it would be a strong conversion tool for this audience. To be discussed with Miriam on the 2026-02-19 call.

Blog Strategy

Ben produced a keyword positioning and topic strategy document derived from Mark's original skyscraper research. Includes competitor comparison content (e.g., Citricasa vs. ZoomX). To be reviewed on the 2026-02-19 call.

Next Steps

[ ] Melissa — Lead the 2026-02-19 Citrus America call (10 AM); present application-centric website pivot, loosened SQL proposal, and ROI calculator concept
[ ] Melissa — Walk through Ben's blog strategy doc with Miriam's team
[ ] Mark — Join 2026-02-19 Citrus call as strategic backup (pending PaperTube scheduling conflict resolution)
[ ] Mark — Coordinate with Carly to reschedule PaperTube call away from 10 AM on 2026-02-19
[ ] Team — Finalize list of 4–5 application pages with Miriam before website work begins
[ ] Team — Fix 32 inactive trade show geofencing campaigns still running in Google Ads (flagged by ^[3])

^[4]
^[5]
^[6]