Cybersecurity marketplace with search-first discovery
Conceptual marketplace for physical appliances, virtual appliances, and service add-ons in a single catalog. The portfolio centerpiece is a new search and discovery model: faceted refinement, trust signals, comparison workflows, and an explicit instrumentation layer (Mixpanel + Pendo) designed to validate whether buyers reach confident shortlists.
Physical appliances, virtual appliances, and service add-ons in one taxonomy
Search-first
Faceted discovery, query refinement, and comparison built into the core flow
Mixpanel
Behavioral funnels, cohort segments, and drop-off diagnosis across discovery
Pendo
In-product guidance for first-time buyers navigating complex catalog structure
Who it was for
IT admins, security architects, and procurement buyers evaluating cyber infrastructure across hardware, virtualized deployments, and managed service bundles.
IT administrators replacing or scaling on-prem security appliances
Security architects comparing virtual appliance options across cloud and hybrid environments
Procurement and vendor management bundling appliances with support, monitoring, and compliance add-ons
The marketplace had to serve buyers with different evaluation mental models in the same catalog: hardware throughput specs, virtual deployment constraints, and recurring service entitlements.
Why discovery was the bottleneck
Cyber buyers don’t fail because options are scarce. They fail because the catalog is dense, vendor claims overlap, and add-on compatibility is opaque until late in the evaluation cycle.
Physical and virtual appliances listed as if they were interchangeable products
Service add-ons buried on detail pages instead of surfaced during search
Filters that reflect vendor taxonomy, not buyer intent (throughput, deployment model, compliance)
Comparison views that omit the dimensions buyers actually decide on
No signal for which results are certified, compatible, or commonly bundled together
The product thesis: make search the primary navigation model, not category browsing with filters bolted on afterward.
Before vs after search experience
Legacy catalog pattern
Browse categories → Open product page → Read specs → Check add-ons manually → Start over if wrong fit
Category-first navigation with shallow filters
Appliance types mixed without deployment context
Add-ons discovered only after deep page visits
Comparison requires opening multiple tabs
No instrumentation on where buyers stall
Search-first marketplace
Query or intent chip → Refine with facets → Compare shortlist → Surface compatible add-ons → Save evaluation set
Intent-aware search with progressive refinement
Deployment model as a first-class facet
Trust signals inline on results (certified, bundled, compatible)
Side-by-side comparison on buyer decision dimensions
Mixpanel funnels + Pendo guidance mapped to each stage
Search UX principles
The discovery model drew on established search UX patterns (progressive disclosure, scannable results, forgiving entry points) and translated them into a cyber marketplace context where buyers arrive with partial intent and need help narrowing without losing context.
1. Forgiving entry
Accept broad queries (“next-gen firewall branch office”) and map to intent chips before forcing facet selection. Zero-results states suggest alternate facets instead of dead ends.
2. Facets reflect buyer decisions
Deployment model, throughput tier, compliance certifications, and support tier, not vendor-internal product families. Facet counts update live so buyers see the effect of each refinement.
3. Trust signals on results
Certified compatible, commonly bundled, and deployment-validated badges inline on result cards so buyers don’t have to open every detail page to assess fit.
4. Comparison on decision dimensions
Compare up to four items on the attributes buyers actually weigh: deployment model, throughput, licensing model, add-on compatibility, and support SLA, not marketing feature lists.
5. Add-ons in the discovery path
Service add-ons surface during search and comparison, not only on product detail pages. Bundle configuration is a step in evaluation, not a post-purchase surprise.
6. Shortlist as the success state
Saving a shortlist is the primary conversion milestone in discovery, not page views. The UX optimizes for confident evaluation sets, not catalog browsing time.
Catalog taxonomy
Physical
On-prem appliances: NGFW, secure web gateway, IDS/IPS hardware. Facets: throughput (Gbps), form factor, port count, HA support, rack units.
Virtual
Virtual appliances: deployable on VMware, Hyper-V, cloud marketplace images. Facets: hypervisor compatibility, vCPU/RAM requirements, license model (perpetual vs subscription).
Cross-cutting metadata: certification badges (FedRAMP, Common Criteria), vendor-verified compatibility, bundle frequency signals, deployment validation status.
Compare dims
Comparison attributes: deployment model, throughput/licensing, compliance coverage, add-on compatibility matrix, support SLA, total cost framing.
Two buyer scenarios
Scenario A (IT admin, physical appliance): Query: “branch office firewall 2Gbps HA.” Refines with deployment=on-prem, throughput=2 to 5 Gbps, HA=required. Compares three NGFW appliances on throughput, port density, and support tier. Saves shortlist and views compatible monitoring add-ons before requesting a quote.
Scenario B (Security architect, virtual + services): Starts from intent chip “Virtual appliance · hybrid cloud.” Filters by hypervisor (VMware), license model (subscription), and compliance (SOC 2). Compares two virtual appliances, then configures a bundle with threat intel feed and 24/7 managed monitoring. Shortlist includes appliance + service bundle as a single evaluation unit.
Search UX
HTML-native reconstructions of the core discovery surfaces. Annotated to show where facets, trust signals, and comparison dimensions appear in the flow.
Add-ons surface during evaluation, not after purchase commitment
Key design decisions
Search over browse
Category browsing remains available but secondary. Primary navigation assumes buyers arrive with partial intent and need refinement, not a taxonomy tour.
Deployment model as primary facet
Physical vs virtual is the highest-friction confusion point in cyber catalogs. Making it the first facet prevents mismatched results early.
Shortlist, not cart
Enterprise cyber evaluation is a research phase, not impulse purchase. The success metric is a saved evaluation set, not checkout conversion.
Instrumentation from day one
Every discovery stage has mapped Mixpanel events and Pendo guidance triggers. The UX was designed to be measurable before it was designed to be pretty.
Rejected
Vendor-brand-first navigation; buyers don’t search by OEM, they search by capability and deployment context.
Rejected
Infinite scroll results; comparison and shortlist require stable positions. Paginated results with persistent compare tray.
Rejected
Add-ons as post-detail upsell only; bundle discovery must happen during evaluation, not after commitment.
Stack
Mixpanel for behavioral funnels and cohort analysis; Pendo for in-product guidance and feature adoption
Status
Conceptual design with instrumentation model defined for validation and iteration
Measurement model
The discovery UX was laid out with an explicit instrumentation model. Mixpanel handles what buyers do; Pendo handles whether they understand how to do it. This split mirrors how I structured analytics at BVXpress: behavioral telemetry for diagnosis, in-product guidance for activation.
Search→Refine→Compare→Shortlist→Evaluate add-ons
Mixpanel: behavioral layer
Event tracking, funnels, cohort segments, and drop-off diagnosis across the discovery flow.
Does in-product education improve activation of search, compare, and bundle behaviors?
Pendo nudge placement map: Walkthrough on first catalog visit → facet tooltip on first filter interaction → compare tray tooltip when 2+ items selected → bundle builder prompt when shortlist item has compatible add-ons → checklist completion tracked as adoption milestone in Mixpanel.
PM takeaways
Search is a product surface, not a utility widget bolted onto a catalog
Design facets for buyer decisions, not vendor taxonomies
Instrument discovery before polishing visuals; you need to know where buyers stall
Split behavioral measurement (Mixpanel) from in-product education (Pendo)
Shortlist is the discovery conversion event in enterprise evaluation workflows