← Work Pine Brook Digital.
EarthCam.net · B2B catalog concept

EarthCam products & solutions, redesigned

An interactive concept rebuild of the live earthcam.net catalog page: a guided solution finder, a spec-first grid with live filtering, and a compare-and-quote flow that turns browsing into qualified quote requests. Then the part portfolios usually skip: a funnel dashboard wired to this very prototype, a scoped A/B test, and a 90-day plan that treats the redesign as a program to run, not a picture to admire.

Clickable prototype 3-tap solution finder Live filtering Compare & quote Live funnel metrics A/B test plan 90-day roadmap
01

Solution finder

The live catalog asks buyers to scroll thirty products and self-diagnose. Three taps here get them from project to hardware, with a reason attached.

🔒 www.earthcam.net/solution-finder
EarthCamPRODUCTS & SOLUTIONS
Solution Finder Quote 0
Step 1 of 3

Our picks for your project

Every answer is a project fact the buyer already knows. Nobody has to learn a thirty-product line to start shopping it.
1
Buyers self-segment in their own language. Project type, power on site, and what matters most. Not category names they'd have to decode first.
2
Auto-advance keeps it under fifteen seconds. Tap an answer and the next question is already there. Progress is visible the whole way.
3
Recommendations land with a reason attached. The why-line under each pick is what a sales engineer would say on a call, generated from the buyer's own answers.
02

Products at a glance

One scannable grid instead of a thirty-screen scroll. Filters and spec tags do the comparing before a single click.

🔒 www.earthcam.net/products-solutions
EarthCamPRODUCTS & SOLUTIONS
All Products Quote 0
No cameras match that.
The count, the chips, and the grid all update live. Try searching "solar" or filtering to Security & AI.
1
Spec chips carry the differentiators. Resolution, power source, and connectivity sit on the card, so comparison starts on the grid instead of ten tabs deep.
2
Filters mirror how buyers actually think. What the camera does, plus one amber toggle for the question every remote site asks first: can it run off-grid?
3
Interest is captured the moment it happens. Add to quote lives on every card and every finder pick, and the running count follows the buyer through all three screens.
03

Compare & quote

EarthCam sells by quote, so the quote is the cart. Shortlist cameras anywhere on the page, compare them side by side, send one form.

🔒 www.earthcam.net/quote
EarthCamPRODUCTS & SOLUTIONS
Request a Quote Quote 0
Your shortlist
Nothing here yet. Add cameras from the solution finder or the catalog above, and they'll show up ready to compare.

Request a quote

One form, answered by a solutions expert. No pricing games, no seven separate contact links.

Add your name so we know who to call back.
Enter a valid email for the written quote.
Add at least one camera to send your request.
✓

Request received

Within 1 business day: a solutions expert calls with pricing for your shortlist. With the quote: connectivity and power recommendations for your ZIP. No obligation: the shortlist stays saved to this request.
The request arrives with cameras, project type, and a timeline attached. That's a qualified lead, not a form fill.
1
One quote request instead of seven scattered links. The current page repeats "Get a quote" per category with nothing attached. Here the products, ZIP, and timeline ride along.
2
The compare table answers the last pre-sales question. Imaging, streaming, power, and connectivity side by side, so "which one do I actually need" gets settled before the call.
3
The concept respects the quote-based model. Nothing here invents pricing. It just makes the path to a rep shorter and better qualified.
Screens 04 to 06 · The operator's layer

The redesign is a hypothesis. Here is how I would measure it, test it, and run it.

04

The funnel, instrumented

This dashboard is not a mockup. It is wired to the prototype above and it is tracking your session right now. Instrumentation comes first, because you cannot optimize a funnel you cannot see.

🔒 store-ops.earthcam.net/funnel
EarthCamSTORE OPS
Conversion Funnel LIVE
Your session, right now
Use screens 01 to 03 above, then watch the stages clear down here.
Catalog sessionpage_view
Finder startedfinder_start
Finder completedfinder_complete
Camera shortlistedadd_to_quote
Quote requestedquote_request
1 of 5 stages cleared this session
What I would manage the store by
Quote request rate
3.2% → 5.0%
per 100 catalog sessions, modeled baseline to 90-day target
Time to first shortlist
4:10 → 0:45
landing to first add, the finder's whole job
Compare engagement
18% → 30%
sessions reaching side-by-side specs
Modeled figures for the concept. Day one of the job is replacing them with real baselines.
The GA4 spec behind it
EventFires whenThe question it answers
page_viewcatalog page loadshow much demand reaches the store
finder_startfirst finder answer is tappeddoes guided selling get discovered
finder_completerecommendations renderdoes the flow hold for all 3 taps
add_to_quoteany shortlist adddo recommendations turn into intent
quote_requestthe quote form submitsthe number the business actually feels
Every stage on this screen fires a real GA4 event on this page. Drop the same spec into the production store and it becomes the source of truth for screens 05 and 06.
1
The dashboard reads the prototype, live. A stage that will not clear is a finding: the same friction would surface in production data, just slower and more expensively.
2
One primary KPI, everything else diagnostic. Qualified quote requests per 100 catalog sessions is the goal. Finder completion and time to shortlist explain movement, they do not replace it.
3
Attribution rides the same rails. Capture UTM parameters at page_view, attach them to the shortlist at quote_request, and first-touch versus last-touch reporting comes from one clean pipeline.
05

One test, scoped to ship

The finder is the concept's biggest bet, so it ships as an experiment, not a redesign. Flip the variant: the preview and the modeled readout follow.

🔒 store-ops.earthcam.net/experiments/exp-01
EarthCamSTORE OPS
Experiments 1 scoped · 3 queued
EXP-01Design review

Guided entry versus the category wall

Hypothesis: if the catalog leads with the 3-tap finder instead of a category grid, more buyers reach a recommendation, and qualified quote requests rise without hurting form completion.

Products & Solutions
Live
streamingTime-lapseSecurity
& AIMobile
Contact us for a quote
Finder starts
11%
modeled, control
Quote requests
3.2%
modeled, control
Sample
2,400
sessions per arm
Decision rule, set before launch: ship B if quote requests lift with 95% confidence and form completion holds. Detecting a lift off a 3.2% baseline needs about 2,400 sessions per arm at 80% power, roughly a 3-week run. Otherwise A stays and the learnings go back to design.
Next in the queue, ranked by ICE
TestPrimary metricICEScore
EXP-02 · Spec chips on product cardsshortlist adds44513
EXP-03 · One quote form versus per-category CTAsquote requests54312
EXP-04 · Solar toggle placementfilter engagement33511
The toggle swaps real markup, not screenshots. In production the same switch is a feature flag, and this readout is the live experiment dashboard.
1
One variable, one primary metric, one guardrail. EXP-01 moves the entry point and nothing else, so a win actually means something and a loss teaches something.
2
The math sets the runtime, not the meeting. Sample size and duration are fixed before launch, which is how a test survives an impatient Tuesday.
3
The queue keeps every team oriented. Impact, confidence, and effort scores mean Creative, Dev, and Sales always know what ships next and why it beat the alternative.
06

The first 90 days

Business target in, development cycles out. Three phases in two-week cycles, each with owners, ships, and exit criteria a stakeholder can verify.

🔒 store-ops.earthcam.net/roadmap
EarthCamSTORE OPS
Roadmap · Q1 2-week cycles
The targetGrow qualified quote requests 25% by day 90 without degrading lead quality.
DAYS 1 TO 30

Instrument & baseline

  • GA4 event spec from screen 04 goes live
  • Funnel dashboard shared with stakeholders
  • Speed audit with a budget: LCP under 2.5s, images to a CDN, lazy loading below the fold
  • Quote requests land in the CRM with the full shortlist payload
DevITSales
Exit: real baselines replace the modeled numbers, and the weekly funnel report sends itself.
DAYS 31 TO 60

Test & learn

  • Finder ships behind a feature flag
  • EXP-01 runs its full 3 weeks, EXP-02 staged behind it
  • Weekly readouts with Creative, Dev, and Sales
  • Losing ideas retired in writing, not in hallways
CreativeDevSales
Exit: EXP-01 called at 95% confidence, decision documented either way.
DAYS 61 TO 90

Scale & integrate

  • Winning variant rolls to 100% of traffic
  • Quote-to-order handoff wired into order management and the ERP
  • Billing gateway scoped for direct-purchase SKUs
  • Channel report comparing first-touch and last-touch attribution
DevITBizDev
Exit: target hit or a documented reason why, plus a ranked Q2 backlog.
One payload, four systems
Storefront eventsGA4 spec → CRMlead + shortlist → Order mgmt / ERPfulfillment → Billing gatewaydirect purchase
The quote request object is the seam. One JSON payload feeds analytics, sales, and fulfillment, so no system tells a different story about the same customer.
The format is disposable. The discipline is not: targets translated into cycles, dependencies named, and an exit door on every phase.
1
Roadmap ownership means exit criteria, not vibes. Every phase ends with something a stakeholder can verify without scheduling a meeting with me.
2
The team chips are the coordination plan. Creative, Dev, Sales, IT, and BizDev each appear exactly where their work sits on the critical path, which is what cross-functional actually means.
3
Integrations come after instrumentation on purpose. Wiring the ERP before the funnel is measured just automates guesswork at enterprise scale.