Captured locally on August 17, 2026

nimo onboarding before and after

Every stage below has a numbered before and after screenshot: landing page, signup, magic-link message, website setup, alert connection, audit start, and paywall. This pass removes the homepage calculator inputs, replaces them with one focused ecommerce impact animation, simplifies paywall cards around nimo as the agent, and moves detailed features into a table below pricing.

Journey: homepage to paywall Before: origin/main baseline After: current PR branch Auth/API: disposable local mocks
Landing Reduced the impact section to one bottleneck and three business outcomes.
Signup Restored the simpler, familiar sign-in framing.
Onboarding Removed sidebar, outer wrappers, duplicate copy, and unnecessary choices.
Paywall Simplified plan cards around nimo, audits, connectors, and a detail table.

Read This As The Funnel

The goal is a calmer path with one focus point per screen. The user lands on the homepage, starts with a URL, signs up, connects alerts if they want, runs the first check, then sees pricing. The latest pass keeps the educational lift on the landing page and keeps the account/payment steps familiar.

Step 1: Landing Page

Before, the landing page either explained the free check abstractly or made the next section too input-heavy. After, the next section shows one page slowdown, then connects it to conversion, ROAS, and monthly upside in a single visual surface.

Before
After
Homepage before revision
The earlier version had weaker value framing and extra hero elements.
Homepage after revision
The hero is cleaner, and the next section has one headline, one bottleneck, and three outcomes.
Step 2: Signup

The previous revision tried to make signup feel like saving the audit, but the feedback was clear: familiar signup language is better here. The after state restores the simple old framing.

Before
After
Signup before revision
Simple "Sign in to nimo" framing.
Signup after revision
Restored simple signup copy: people already understand this step.
Step 3: Signup Message

The extra continuation sentence did not add enough value. The after state keeps the message short: check your email, link sent, expiry note, and a way to use a different method.

Before
After
Magic link message before revision
The original waiting state was simple and direct.
Magic link message after revision
The after state stays simple instead of over-explaining the next step.
Step 4: Website Setup

Before, the screen showed the app sidebar, an outer panel, duplicate educational copy, three fields, and an add button. After, there is one centered task with a white setup surface, stronger subtitle, no repetitive orange eyebrow, and progressive website inputs.

Before
After
Website setup before revision
Too many simultaneous elements for a first setup step.
Website setup after revision
White setup surface, stronger subtitle, entered site, and one next field.
Step 5: Alerts

Before, tool connection and alert routing appeared together inside nested frames. After, the choice is just Telegram or Slack, with skip and continue directly underneath.

Before
After
Alert setup before revision
The alert routing section competes with the provider choice.
Alert setup after revision
The screen is now focused on where the user talks.
Step 6: Audit Start

Before, the last step emphasized scheduling and repeated that the site was ready. After, the repetitive audit label is gone and the screen centers the first check plus the Run audit action.

Before
After
Audit step before revision
Scheduling is the dominant concept before the first payoff.
Audit step after revision
"Start the first check" avoids repeating audit language above the button.
Step 7: Paywall

Before, the plan cards listed too many granular features and AI quota details. After, the primary paywall focuses on nimo as the agent, audits, watched sites, Slack/Telegram, and a first fix; the full feature detail sits below the cards.

Before
After
Paywall before revision
The old card mixed plan value with too many feature details.
Paywall after revision
The revised card is shorter; detailed capabilities move into the table below.

Mobile Spot Checks

Homepage mobile before revision
Before: homepage mobile baseline.
Homepage mobile after revision
After: homepage mobile with the funnel bridge.
Website setup mobile after revision
After: setup fits without sidebar, secondary heading, or add button.
Paywall mobile after revision
After: paywall keeps the primary decision shorter on mobile.

Capture Limits