Orbit Analytics

A self-initiated concept examining the gap between how SaaS products are marketed and how they actually look after signup. Orbit Analytics is an invented company; nothing here is client work and no results are claimed.

Marketing sites illustrate the product; the product ships something else. Trials then begin with a small disappointment, and pricing pages built as comparison walls make buyers estimate their own bill and guess high.

Raise trial-to-paid conversion by making pricing legible and showing the real product rather than an illustrated version of it.

• Audited fifteen analytics pricing pages; most required arithmetic the buyer could get wrong.
• Reviewed trial drop-off patterns and found the empty dashboard as the common abandonment point.
• Interviewed the questions sales teams answer most: cost at scale, data limits, migration effort.

• Pricing modelled two ways — comparison table versus usage calculator — and tested for confidence, not preference.
• Onboarding sketched to reach a populated dashboard before any card details are requested.
• Documentation shell wireframed around search first, navigation second.

A single token set spanning marketing and application UI: identical type scale, spacing and states, so the two surfaces cannot drift apart.

Pricing modelled with a usage calculator instead of a comparison wall, and an onboarding path that reaches a populated dashboard before asking for card details.

• Usage-based pricing calculator
• Interactive product tour built from live components
• Shared component library across site and app
• Documentation search with keyboard shortcuts

• React
• TypeScript
• Tailwind CSS
• Design tokens

Comparison and integration pages targeting evaluation-stage searches, SoftwareApplication schema, canonical handling for paginated docs.

• Route-level code splitting so the marketing site never loads dashboard bundles.
• Documentation search index loaded on interaction rather than on page load.
• Component-rendered screenshots served as static assets at build time.

• The pricing calculator becomes a stepped mobile flow instead of a compressed table.
• Dashboard shell collapses to a prioritised single-column view with the primary metric first.
• Documentation navigation converts to a searchable sheet below the large breakpoint.

• Calculator inputs fully labelled, with results announced politely on change.
• Keyboard shortcuts documented, discoverable and disableable.
• Focus management verified across dialogs, sheets and the onboarding flow.

Fewer pricing questions in sales conversations and trials that begin with the buyer already knowing what they will pay.

Expected, not measured: this is a concept project with no client data behind it.