Loading uxbubble
Book a Call
Work

Appxiom · B2B SaaS · Website Redesign

A redesign that finished, then never shipped.

Appxiom is a bug and crash monitoring platform for mobile and web apps — competing directly with Sentry, Datadog, and New Relic on a specific angle: connecting bugs to business impact, not just technical severity. uxbubble redesigned the marketing website, building out feature pages, a competitive comparison page, and self-serve pricing that hadn't existed before. The work was completed; the client changed direction before launch, and it was never published.

Engagement
Website redesign
Duration
2–3 months
Scope
Full marketing website redesign — new information architecture including dedicated feature pages, a competitive comparison page, FAQ, and self-serve pricing tiers, replacing what had been a single landing page with a beta-signup form.
Year
2026
HERO — PRODUCT OVERVIEW
01SECTION

Appxiom is a bug and crash monitoring platform for mobile and web apps, built to do something the established players — Sentry, Datadog, New Relic — don't: connect every bug directly to its business cost in lost revenue, churn, and conversions. The old site didn't carry that positioning. It was a single landing page ending in a beta-style signup form — name, email, company size — not a product a serious engineering team could evaluate on its own.

There was no way to actually compare Appxiom against the tools it was competing with, no dedicated explanation of what Goal Friction Impact, Quality Score, or Version Analytics actually did, and no real pricing — just a form that asked you to wait for someone to get back to you. For a product entering a category with entrenched, well-known competitors, that's a credibility gap before a visitor even reaches the product itself.

uxbubble redesigned the full marketing site: dedicated feature pages, a head-to-head comparison page against Sentry with a real-world example scenario, an FAQ, and self-serve pricing across three tiers. Two to three months, client work, delivered in 2026.

02WHAT WE FOUND

No independent user research here — direction came from two places: the founder's own clear view of what Appxiom needed to become, and a direct competitive analysis of Sentry, the tool it's most often measured against.

No independent user research here — direction came from two places: the founder's own clear view of what Appxiom needed to become, and a direct competitive analysis of Sentry, the tool it's most often measured against.

01

The founder didn't want another generic SaaS site

One instruction shaped almost every decision that followed: avoid the look every other developer-tools startup defaults to. That ruled out the safe, interchangeable SaaS template — gradient hero, three-icon feature grid, logo wall — and pushed toward something that looked considered rather than assembled.

02

Sentry's own site revealed exactly what to argue against

Sentry's site is developer-first and technically dense — logs, stack traces, exceptions. It doesn't talk about business impact at all. That gap became the whole spine of the comparison page: not "we do what Sentry does, better," but "we answer the question Sentry's own site never asks — what did this bug actually cost you."

IMAGE
04WHAT IT LOOKED LIKE

SCREEN 01
SCREEN 02
SCREEN 03
05WHAT CHANGED

The redesign was completed in full — and never published. Appxiom changed direction before launch.

Every page shown here — the feature breakdowns, the comparison against Sentry, the pricing tiers — was finished, reviewed, and ready to ship. What happened next wasn't a design failure or a client rejection of the work; the company's priorities shifted, and the site never went live.

Worth stating plainly rather than glossing over: this case study doesn't end with a metric or a launch. It ends with real, completed work that a business decision outside the design process overtook. That happens in this industry more often than portfolios usually admit.

06WHAT’S NEXT

No updates since the redesign was completed. Appxiom's direction changed before launch, and there's nothing currently in motion — but the relationship with the team stayed intact, and contact hasn't dropped off. If their direction settles into something that needs a website again, that's a conversation that's still open, not one that ended.

Finished work. Open door.

Bring us the part nobody wants to touch.

If you're mid-build and something feels off, that's usually the right time to look, not the wrong one. Twenty minutes. No deck. No proposal to sit through.

Broken doesn't mean beaten.

Book 20 minutes