Hey IH π
I'm Ramin β a second-year CS student based in Istanbul, Turkey.
I just launched Convertly: a service that builds full landing pages
(copy + design) for indie SaaS founders and small B2B teams.
The insight that started it: most SaaS landing pages explain the
product to the founder, not the buyer. The founder knows every
feature. The buyer just wants to know if it solves their problem.
Those are completely different pages.
So I built a service that fixes that β ICP research, conversion
copy, and design β delivered in 5β7 days, starting at $497.
I use AI heavily to deliver fast, which means I can undercut
agencies on price while keeping quality high.
Currently looking for my first clients and building in public.
A few things I'd love feedback on:
β Does the positioning make sense to you as a founder?
β Is $497 too high, too low, or right for this audience?
β What would make you trust a one-person service over an agency?
Live page: getconvertly.netlify.app
Happy to give anyone here a free landing page audit in return
for honest feedback β just drop your URL below.
β Ramin
The "founder knows every feature, buyer wants to know if it solves their problem" framing is the heart of it. Most landing pages I see read as a feature catalog, not a problem mirror.
One worth thinking through: how do you handle revision cycles at $497? Landing pages tend to spawn 2 to 4 rounds of "what if we tried X" once the founder sees the first draft. Fixed price plus tight delivery can pull you into uncompensated iteration unless you scope rounds upfront. Curious how you have structured that.
Really good question β and honestly one I've been
thinking through carefully.
The way I've structured it: Starter gets 1 round,
Growth gets 3 rounds. Each round is scoped as
"a list of changes" not "unlimited back and forth."
So the client sends consolidated feedback once,
I implement, that's one round used.
I also set the expectation upfront in the brief
confirmation β revisions are for refinements, not
direction changes. If the brief changes significantly
mid-project that's a new scope conversation.
At $497 I'm not pretending this is bulletproof β
it's a learning process and I'll tighten the scope
language as I see where friction actually happens.
Appreciate the flag though β "what if we tried X"
creep is exactly what kills fixed-price services.