u/pudkovah

I'm the CMO at Claspo. We recently migrated our marketing website to Framer. Sharing the actual costs, timeline, and a few unexpected limitations in case it helps someone considering the same move.

Sharing the real numbers and experience in case it helps someone who is considering the same move.

Cost
Full migration: $1,300 one-time
Framer: $130/month plan
Team seats: 2 × $50/month
Timeline: The migration took around 2 months.

It could have been closer to 1 month, but we decided to redesign several page types at the same time - use cases, templates, and blog pages. That caused content rework. Vacations slowed things down a bit too.

Main limitations we faced

1. Overlay content like dropdown menus is not crawlable by default in Framer.
2. We could not set custom lazy loading for blog images by default.

That was basically it. No major blockers.

The biggest win is speed.

Before Framer, a typical website request could take 2–5 weeks from idea to release. Now it usually takes 1–2 hours.

The marketing and design team can work directly on the website. We skipped the long planning cycle. If someone on the team needs a change, they can usually make it themselves.

Framer also has an API, which opens a lot of automation opportunities. For example, our team can now use agents to help with things like:

• finding internal linking opportunities
• updating repeated wording across pages
• adding alt text to images
• identifying pages that may need to be deindexed
• converting images to WebP

We have not used Framer’s built-in analytics and A/B testing properly yet, but that is one of the next things we want to try.

Overall, the biggest impact was operational. Framer made the website much easier to run as a marketing asset, not as a development project.

I keep seeing ecommerce teams judge popups by one number:

“How many emails did it collect?”

That’s useful, but also incomplete.

A popup can lift signup rate and still create a worse list: discount hunters, fake leads, one-time buyers, people who unsubscribe before the welcome flow does anything useful.

From benchmark data I’ve worked with, basic signup forms often sit around the 3–5% range.

Gamified forms can go much higher.

But I don’t think the real question is:

“Did the popup get more emails?”

I think it’s:

“Did the popup create better buyers?”

For ecommerce, I’d rather look at:

• signup conversion rate
• first purchase rate from popup leads
• revenue per subscriber
• AOV after offer claim
• unsubscribe rate
• margin impact
• repeat purchase rate

This is where gamification gets interesting.

A spin-to-win or gift-box flow is not just “more fun than a form.” It changes the interaction.

Instead of:

“Give us your email for 10% off”

it becomes:

“Play, reveal a reward, then decide if it’s worth claiming.”

That can increase engagement, but it can also attract people who just want the reward.

So the win is not automatically “more emails.”

The win is more revenue from the right visitors, without training everyone to wait for a discount.

Curious how others measure this.

Do you still judge popups mainly by opt-in CR, or do you track downstream revenue from those subscribers?

Disclosure: I work on Claspo, so I obviously think about onsite conversion a lot. Not trying to pitch a tool here — more interested in how teams measure this properly.

There’s a real growth trade-off here. On one side, typo checks, email validation, and double opt-in can improve list quality and downstream deliverability. On the other side, every extra step adds friction at the moment when you’re trying to maximize conversion.

In practice, this is a problem we see a lot at Claspo because users actively ask for these safeguards in popups. The demand is real. But I still think there’s a difference between **hygiene** and shifting the cost of deliverability onto the popup signup flow itself.

My take: the form should protect against obvious bad data, but the ESP and the deliverability stack should carry more of the responsibility for inbox placement. Otherwise, merchants end up paying a conversion penalty for an infrastructure problem.

Curious where others draw the line: what belongs in contact capture, and what should be solved downstream?