Open-Source Networking & Router Client — Use Cases

The client had built a strong open-source product and a loyal technical community, but had not yet formalized a marketing strategy oriented toward commercial growth. The engagement began with stakeholder interviews across co-founders, VP of Sales, and marketing team members — mapping the current state of programs, channels, content types, and CRM data against where the client needed to go as a business.

Key findings: marketing efforts had been predominantly focused on the "freemium" persona (open-source users) rather than the paying commercial segment; platforms were underutilized; data was fragmented; and there was no formal content strategy or publishing cadence. The assessment produced a clear picture of gaps and a ranked set of recommendations to guide the remainder of the engagement.

Three personas were defined: the actively paying customer between engineers, solutions architects, Dev/Ops engineers ages 25–45 who had moved past "why this product" and needed to justify the cost to their manager; the freemium user satisfied with the free version; and the commercial prospect not yet converted to the commercial offering using a substitute product, requiring a differentiation and switching-cost strategy.

For the primary paying segment, a full customer experience journey was mapped across nine stages — Awareness through Advocacy — including touchpoints, emotional state, drop-off risks, and recommended actions. The journey closely mapped the pre-sales, point-of-sale, and post-sales experience, and was used to anchor the content strategy and website UX recommendations that followed.

The client had a substantial material already in existence but it was primarily oriented toward the technical freemium users. The audit identified six high-priority content types missing or underrepresented for the commercial persona: a "Why Us" one-pager in infographic, customer stories and testimonials, a competitor analysis decision matrix, a product/offerings description, a subscription model comparison, and a "cost of waiting" sales asset.

The assessment linked each content type to specific funnel stages. The strategy also included recommendations around a marketing-to-sales handover — improving the quality and quantity of leads passed to the sales team through more intentional content CTA design. Specific performance benchmarks were recommended using AWS Cloud and IDS Blog CTAs like performance URLs, click rate, and key pages tied to key conversion goals.

The client had 3,376 total contacts in HubSpot but significant gaps in closed-loop reporting. SSL tracking was not in place, form submission data was inconsistent, and analytics weren't being stitched across platforms. Key data points surfaced during the audit included: 77% of all subscription signups choosing the free tier; 71% of all active subscription owners choosing free; three key traffic sources — all of which required data stitching since HubSpot alone wasn't capable of capturing this fully.

The audit also included a Google Analytics performance report for 90 sessions, 67,378 traffic, 4,056 new sessions — indicating strong but not market-traffic-as-significant drop-off in key conversion paths. Top-performing pages were identified: homepage, subscriptions, products, VMware solutions pages and enterprise download pages drove strongest engagement. Recommendations were made for additional data capture points, a formal reporting cadence, and customer-centered reporting.

The website analysis identified several structural issues limiting conversion: the above-the-fold features list was heavy and didn't feature the primary CTA; the navigation was oriented toward the open-source technical persona, not the commercial buyer; and multiple dropdown options were given equal or greater prominence than paid subscription — undermining the commercial goal.

A full navigation redesign was proposed, organizing the site across Subscriptions, Products & Services, Downloads, Resources, Community, About, and Contact — with nested dropdowns to separate the commercial and open-source audience. A staging server was proposed with an unblocked Manu-San approach, with specific decisions for the client to make: channel mix, "Why Us" specificity. The lead to conversion guide, organising the site's by-funnel-stage, launch-ready vs. post-launch functionality, platform gaps — so the session produced alignment, not just conversation.