DEV Community

Animiso
Animiso

Posted on

I A/B tested my SaaS landing page copy. Here's the conversion data (Day 4)

#buildinpublic #saas #marketing #startup

The Problem: 847 visitors, 0 signups

Day 4 of launching Animiso (my first SaaS).

I had traffic. But 0% conversion.

Something was broken. So I rewrote everything using conversion psychology.

Here's the framework + data.

The Before/After

Version 1 (Days 1-3)

Hero:
"Keep clients updated without the email chaos"

Stats:

  • Visitors: 847
  • Avg time: 34 seconds
  • Bounce: 87%
  • Signups: 0

Conversion rate: 0%

Version 2 (Day 4)

Hero:
"Stop the 'any update?' texts. Share one link. Done."

Stats (first 400 visitors):

  • Avg time: 1:47 (3x improvement)
  • Bounce: 64%
  • Signups: Testing now

Target: 3% conversion

The Conversion Framework I Used

Based on studying 50+ high-converting SaaS pages (Stripe, Linear, Vercel, etc).

1. Pain-First Headline

❌ Don't: Explain what you do
✅ Do: State the problem you solve

Bad: "Client communication platform"
Good: "Stop wasting 5 hours/week on status emails"

2. Quantified Value Prop

❌ Don't: "Save time"
✅ Do: "Get back 5 hours every week"

Specific > vague. Always.

3. Visual Proof Above Fold

Added screenshot showing:

  • Before: Messy email thread
  • After: Clean timeline

Show, don't just tell.

4. Remove Friction from CTA

❌ "Start Your First Project" (what am I starting?)
✅ "Try Free - No Credit Card" (zero commitment)

5. Social Proof (Even Small Numbers)

"Join 12 freelancers who tried Animiso this week"

Small number > no number.

Creates perception: "Other people are trying this."

6. Strategic Urgency

"7/50 early adopter spots claimed"
"Price increases to $5/month after first 50"

Scarcity works. But must be real.

7. Risk Reversal

"Free forever plan"
"No credit card required"
"Cancel anytime, keep your data"

Remove every objection.

What Animiso Actually Does

(For context)

Problem:
Freelance devs/designers waste hours on client updates.

"Any update?" texts.
20-min emails for 2-min changes.
30-min calls to share one screenshot.

Solution:
Shareable project timeline.

  1. Create project → get link
  2. Post updates (screenshot + note, 30 sec)
  3. Share with client (no login for them)
  4. They check whenever

Live: animiso.fun

The Copy Changes (Specific Examples)

Hero Section

Before:
"Keep clients updated without the email chaos"

After:
"Stop the 'any update?' texts.
Stop the 30-minute calls for 30-second changes.
Share one link. Post updates in 30 seconds. Done."

Why: Specific pain → specific solution → specific outcome.

Value Proposition

Before:
"Share one link. Post updates. Keep clients happy."

After:
"Freelancers waste 5+ hours every week on client status updates.
Animiso gives you 5 hours back."

Why: Quantified problem → quantified solution.

CTA Button

Before:
"Start Your First Project"

After:
"Try Free - No Credit Card"

Why: Removed ambiguity + friction.

Social Proof

Before:
"No credit card required • Free forever plan"

After:
"Join 12 freelancers who saved 892 hours this week"

Why: Real usage > features.

The A/B Tests I'm Running

Test 1: Headline

A: "Stop the 'any update?' texts"
B: "Get back 5 hours every week"

Hypothesis: Outcome (5 hours) > pain relief (stop texts)

Test 2: CTA Copy

A: "Try Free - No Credit Card"
B: "Start Saving Time Today"

Hypothesis: Benefit (save time) > feature (free)

Test 3: Pricing Display

A: $3/month with strikethrough, $1.50 shown
B: $1.50/month "locked in forever"

Hypothesis: Anchoring works better than scarcity

Early Results (Will Update)

Hour 1: 47 visitors, 2 signups (4.2% conversion)
Hour 2: 93 visitors, 3 signups (3.2% conversion)
Hour 3: 156 visitors, 4 signups (2.5% conversion)

Trending toward 3% conversion.

10x better than 0%. But still optimizing.

The Offer (DEV Community Only)

First 10 devs who freelance:

Code LAUNCH50 = $1.50/month forever

Just:

  1. Try it: animiso.fun
  2. Use it for one real project
  3. Tell me what sucks

Expires in 48 hours.

What I'm Learning

Lesson 1:
Your landing page is a sales conversation, not a product spec.

Lesson 2:
Conversions come from clarity + removing friction.

Lesson 3:
Test everything. Assumptions are expensive.

Lesson 4:
Small wins compound. 0% → 3% feels huge at day 4.

Questions for Dev Community

  1. What else would you test?
    Where are obvious conversion leaks?

  2. For devs who freelance:
    Would you actually use this? Why/why not?

  3. Landing page critiques:
    What's stopping you from signing up?

I'll update this article tomorrow with final conversion data from the new page.

If it doesn't hit 3%, I'll rewrite again.

Feedback welcome in the comments 👇

Top comments (0)