DEV Community: Animiso

I built a tool to stop clients from texting 'any update?' at 11 PM - Here's the tech stack and what I learned

Animiso — Tue, 10 Feb 2026 10:33:44 +0000

The Problem

As a freelance developer, I was spending 6+ hours/week answering "any update?" messages from clients.

Even though I'd just sent them an update yesterday.

The issue wasn't lack of communication. It was communication scattered across 5 platforms (email, Slack, WhatsApp, SMS, DMs).

Clients genuinely forgot what I told them because it was buried in threads.

The Solution

Built Animiso - a dead-simple client update feed.

How it works:

Freelancer posts updates (text + images)
Client gets one permanent link
Client checks progress anytime (no login required)
No more "any update?" texts

The Tech Stack

Frontend:

Vanilla HTML/CSS/JS (keeping it simple)
Bootstrap Icons + Lucide
No framework bloat

Backend:

Node.js + Express
PostgreSQL for data
JWT auth for freelancers
Cloudflare for CDN/caching

Why no React?
Speed. The client-facing pages load in <100ms because there's no JS framework overhead. Just fast, static HTML.

File uploads:

Cloudflare R2 (S3-compatible, cheaper)
Image optimization on upload
Max 5MB per image

Early Results (Week 3)

18 beta users testing
4.2 hours avg saved per user/week
89% would recommend
0 "any update?" texts reported since onboarding

What I Learned

1. Authentication should be frictionless

Freelancers use email magic links (no password)
Clients don't need accounts at all
Lower friction = higher adoption

2. Mobile-first is critical

70% of client views are on mobile
Had to optimize for small screens first

3. Real-time isn't necessary

Thought about WebSockets for live updates
Realized clients check once a day max
Saved weeks of dev time by skipping it

4. Speed > Features

Clients don't care about fancy UI
They care about seeing updates fast
Sub-100ms load time matters more than animations

What's Next

Opening 25 beta spots next week for freelancers who want to test it: animiso.fun

Questions for the community:

What would you add to this stack?
Any security considerations I'm missing?
How would you handle file versioning?

Building in public. Code is closed source for now but happy to discuss architecture.

Cheers,
Levi

animiso.fun

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

Animiso — Wed, 21 Jan 2026 20:45:25 +0000

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.

Create project → get link
Post updates (screenshot + note, 30 sec)
Share with client (no login for them)
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:

Try it: animiso.fun
Use it for one real project
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

What else would you test?
Where are obvious conversion leaks?
For devs who freelance:
Would you actually use this? Why/why not?
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 👇

I'm 17 and built my first SaaS. Here's the tech stack and what I'd do differently.

Animiso — Tue, 20 Jan 2026 13:21:15 +0000

The "I wish I knew this before I started" thread

3 months ago I started building Animiso - a tool to help freelancers stop the "any update?" text chaos.

Today (Day 3 of launch): 0 users, $0 revenue, infinite lessons learned.

Here's what I built, how I built it, and what I'd change.

The Problem

As a freelance, clients would ask "any update?" via:

Text at 9 PM
Email at 6 AM
Slack during lunch
Calls that should've been a screenshot

I'd spend 2+ hours/week just on status updates.

The Solution

Animiso: A shareable project timeline.

Freelancer creates project → gets unique link
Posts updates (screenshot + note) in 30 seconds
Shares link with client (no login for them)
Client checks whenever they want

Simple. Boring. Solves a real problem.

What Took the Longest

Not the code. The uncertainty.

"Is this even useful?"
"Will people pay for this?"
"Am I wasting my time?"

I spent more time doubting than coding.

What I Learned

1. Ship before you're ready

I wanted to add:

Email notifications
File uploads
Comments
Custom branding

But I shipped without them.

Good decision. I can add features when users ask for them.

2. Building ≠ Success

I thought: "Build it and they will come."

Reality: Building is 10%. Distribution is 90%.

I have a working product and 0 users.

The hard part isn't done. It's just starting.

3. Talk to users BEFORE building

I built what I thought freelancers needed.

Should have:

Asked 50 freelancers first
Validated the problem
Pre-sold it

Live and learn.

Current Status

Users: 0
Revenue: $0
Runway: Infinite (I'm 17, live with parents, no costs)
Plan: Send 100 DMs/day until I get 10 users

What I'd Do Differently

Validate first
Talk to 50 potential users before writing code
Build an audience first
Post daily for 3 months WHILE building
Start with a waiting list
Collect emails before launch
Make a demo video
Show don't tell
Be more aggressive
10 DMs/day is nothing. Should be 100/day.

Want to Try It?

animiso.fun

Code LAUNCH50 = $1.50/month forever

I'm desperate for feedback from real developers who freelance.

Tell me what sucks. I'll fix it.

Questions for Devs Who've Launched

How did you get your first 10 users?
How long until you hit $100 MRR?
What marketing channel worked best?
What would you tell your past self?

Drop your answers below. I'm reading everything.

Also: If you're a dev who's thought about building a SaaS but hasn't started - do it. You'll learn more in 3 months than 3 years of tutorials.

(Even if you end up with 0 users like me 😅)

I built a client update tool for freelancers (and launched today)

Animiso — Sun, 18 Jan 2026 13:36:32 +0000

The Problem

Every freelancer gets "any update?" messages that kill productivity.

What I Built

Animiso - share one link with clients, post updates, they see timeline.

No login needed on client side.

Tech Stack

Cloudflare Workers
D1 Database
Vanilla JS
Lemon Squeezy

Try It

https://animiso.fun

Free for 1 project, $3/mo unlimited.

Feedback?

What features would make you actually pay for this?

Be honest! 🙏