Resources · Internal working document

Website revision: what changed, and why.

This prototype is a proposed rebuild of bluefletch.com, built against a benchmark of the best B2B software sites of 2025 and 2026. This page documents the research, the recommendations, and the reasoning, and lays out next steps if we move forward.

⚠ Internal review page. Remove before any public launch. Pricing shown on this prototype is not published pricing.
Step 1 · The benchmark

We analyzed the top 40 sites in enterprise SaaS.

Three research passes, cross-referencing 2025-2026 design roundups, CRO teardowns (including a 50-site scoring study), public traffic data, and first-hand review of every major site in our own category.

SiteWhy it made the benchmark
Group A · Modern design benchmarks (15)
LinearDark-mode masterclass; most consistent design execution in the industry
StripeSet the template: interactive demos, gold-standard docs and pricing
VercelBlueprint-grid aesthetic; developer speed-to-answer
NotionWarm counter-programming; product-as-hero
RampThe bento-grid system everyone copies; subtle motion
MercuryEditorial-grade fintech UI
AttioAI-native reference; live product query in the hero
FramerMotion as brand positioning
WebflowThe site is a demo of the product
PostHogLive embedded dashboard; explicit positioning
CursorLive product demo in the hero
ResendTransparent pricing, zero demo-gating
FigmaLive multiplayer functionality on the page
IntercomOpens with the live product instead of a form
LoomDemo-first hero architecture
Group B · Enterprise conversion leaders (13)
HubSpotPersona self-selection nav; best-studied B2B funnel
AtlassianHero demonstrates capability without copy
SalesforceEnterprise trust architecture at scale
SnowflakeThe Enterprise-Ready trust-page standard
DatadogMakes complex multi-product pricing legible
TwilioUsage-pricing pioneer; code on the homepage
SlackTop score (91/100) in the 50-site CRO analysis
GongRole and industry routing without nav crowding
VantaConcrete metrics as trust signals
CalendlyThe reference pricing-comparison page
RetoolRestraint as a design choice for technical buyers
SegmentColor-coded persona navigation
Checkout.comWebflow's 2025 Website Experience of the Year
Group C · Our category: mobility / UEM / frontline (12)
MosyleBest in category: transparent per-device pricing, audience routing
WorkJamBest problem-to-solution copy in frontline software
YOOBICSharpest pain-first headline reviewed
IvantiBest social-proof layering; customer-zero narrative
AxonifyBest stat-driven opening hook
JamfAI-era positioning; community as differentiator
EsperClosest analog to our dedicated-device story
SOTIThe incumbent look; instructive anti-patterns
AddigyDirect vs-Jamf comparison, rare in the category
NinjaOneClearest funnel in the adjacent set
Iru (was Kandji)Live rebrand case study, Oct 2025
HexnodeModern design; cautionary tale on message dilution
Step 2 · The shortlist

Five core principles of sites that aligned well with BlueFletch.

Brett reviewed all 40 and shortlisted 17: Notion, Ramp, Cursor, Intercom, HubSpot, Atlassian, Snowflake, Slack, Vanta, Calendly, Mosyle, WorkJam, YOOBIC, Esper, Addigy, NinjaOne, and Iru. The pattern across every pick:

1. Light, clean, calm

Light theme for a 40+ enterprise IT audience. "Clean" appeared in 8 of the 17 review notes. Slack named as the aspiration for focus.

2. Product first

The best sites show the product working in the hero: Ramp, Cursor, Intercom, Vanta. Nobody makes you scroll to find out what the product looks like.

3. Restrained motion

Sites were rejected from the shortlist specifically for over-animation (Mercury, Datadog, Jamf). Motion budget goes to product footage, not decoration.

4. Nothing hidden

Full navigation always visible. Products and Solutions split. Pricing at top level. No condensed menus, no buried capabilities.

5. Demo always one click away

A persistent, single high-emphasis demo button, and short forms. The category anti-pattern is SOTI's 10-field demo form.

The category gap

Almost nobody in our category does pricing transparency (except Mosyle), head-to-head comparisons (except Addigy), or real product footage. All three are open ground.

Step 3 · The recommendations

Thirty changes, ranked. This prototype implements most of them.

The full list lives in the internal research docs; the headlines, all visible on this prototype:

Navigation & structure

Full menu exposed, Addigy-style three-column products menu (Core products / Key features / Add-ons), Solutions by industry, Pricing with per-product pages, Admins menu with portal and docs, site search.

Product-first homepage

Real badge-tap footage in the hero, one message per screen, two CTAs, static customer logo row, the "shift clock" problem narrative, six-feature grid matching the menu, quantified outcomes.

Conversion path

Demo form cut to two required fields with a 24-hour free lab-demo promise. Transparent per-device pricing with volume tiers on one page per product. A working savings calculator.

Trust architecture

Snowflake-style security section, Trust Center page, quantified outcome claims tied to deployment case studies, compliance-forward Government page (CMMC, PIV/CAC).

Real product everywhere

Feature pages open with actual product UI (launcher home, Device Finder map, badge prompt). Solutions pages open with real usage footage cut from existing BlueFletch video assets.

AI-search ready

Static server-rendered HTML (AI crawlers do not execute JavaScript), answer-first copy structure, and a documented GEO playbook: schema, robots.txt AI policy, G2/Capterra investment.

Why this works for our buyer

Built for our Admin ICP Persona, not for a designer.

Simplicity is the strategy

Our buyer is a 40+ IT leader or infrastructure engineer evaluating tools between interruptions. Every page opens with a plain answer, every menu shows everything, and nothing moves unless it is the product itself. The site respects their time, which is the trust signal that matters most to this audience.

See the product in seconds

Real badge-tap footage plays in the hero before a visitor scrolls. Feature pages open with actual product screens. Solutions pages open with real usage video. A skeptical engineer can verify the product exists and works without booking anything, which is exactly what makes them willing to book.

Add-ons in the light

Agentic Login, Chat, Phone, Identity, Virtual Device Locker, Playbook, and Remote Control each get a named menu slot and a real page. Hidden capabilities do not get bought, and half our differentiation lives in the add-on list. The menu now sells the whole catalog, not just the launcher.

Next steps

If we move forward.

Suggested sequence, roughly in order:

1. Marketing and Sales team review

Full content pass by marketing and sales: messaging, claims, customer references. The site needs to be an extension of how our sales team and partners present the product to customers, with the same story, the same product names, and the same demo motion. Every metric and named customer needs sign-off; the placeholder quote and case-study stubs need approved replacements.

2. Pricing decision

The transparency debate has to resolve before launch. This prototype shows real list rates behind an "illustrative" banner; ship it, soften it to "starting at," or pull it, but decide deliberately.

3. Video and imagery refresh

Current footage is repurposed from existing assets. Commission a proper shoot: badge tap on current hardware, per-product screen captures at high resolution, industry b-roll for each solutions page, and a real-world hero montage.

4. Staging migration test

Rebuild the templates on a separate WordPress staging site (or evaluate a static/headless build, which would also lock in the AI-crawler advantage). Verify all content renders server-side with JavaScript disabled.

5. Full QA matrix

Browser matrix (Chrome, Safari, Edge, Firefox), real mobile devices, accessibility pass (keyboard, contrast, screen reader), performance targets (90+ Lighthouse), and forms wired to HubSpot with tracking verified.

6. Search & measurement

Implement the GEO playbook: Organization schema, robots.txt AI-crawler policy, llms.txt, G2/Capterra profile investment. Start monthly AI-answer prompt testing now for a pre-launch baseline, and validate priorities against HubSpot lead-flow data.

Research artifacts behind this page: 40-site benchmark, shortlist review with taste profile, top-30 recommendations, GEO/AI-search playbook, and brand-voice review, all in the internal project docs.