A product landing page with pricing, sign-up and funnel analytics.
A visitor to a SaaS landing page decides in ten seconds whether they get what it is and who it is for. Then they go to pricing — 57 % look at prices before the description. The site has to explain the product in one sentence and one screenshot, show plans without “contact us” and lead to sign-up without losing the event on the way.
reply within an hour · 10:00–20:00 UTC+3
- Timeline
- 10–21 days
- Price
- from ₽80,000 ≈ $890
- Key module
- Pricing and sign-up
- Integrations
- Stripe / YooKassa · Supabase · event analytics
01 — The difference
A typical site vs mine
Typical site
- Hero: “A next-generation platform for growing your business”
- Pricing: “Write to us and we’ll pick a plan”
- Sign-up leads to the app on another domain, events get lost
- Features: 12 icons with captions
Mine
- Hero: what the product does, for whom, a screenshot of the interface, a “Try it” button
- Three plans with prices, a yearly toggle, the middle one highlighted, enterprise separately
- Sign-up on the same domain, one signup event end to end: site → app → payment
- 3–4 scenarios “problem → how the product solves it → result”, with real screens
Hero: “A next-generation platform for growing your business”
How I do itHero: what the product does, for whom, a screenshot of the interface, a “Try it” button
Pricing: “Write to us and we’ll pick a plan”
How I do itThree plans with prices, a yearly toggle, the middle one highlighted, enterprise separately
Sign-up leads to the app on another domain, events get lost
How I do itSign-up on the same domain, one signup event end to end: site → app → payment
Features: 12 icons with captions
How I do it3–4 scenarios “problem → how the product solves it → result”, with real screens
02 — What’s inside
Modules
- 01
Hero with the product
one sentence, one screen, a free-trial button
- Next.js
- 02
Pricing
plans, yearly discount, seat calculator, billing FAQ
- Stripe Checkout / YooKassa
- 03
Sign-up and sign-in
email and OAuth, confirmation, redirect to the app
- Supabase Auth
- 04
Funnel analytics
view → pricing → signup → payment events in one place
- Metrica / PostHog
- 05
Use-case and comparison pages
“for whom”, “vs competitor”, indexed
- SEO pages
- 06
Changelog and docs
updates and documentation in markdown, no CMS
- MDX
03 — Offer
2 slots until January 31 · −15 %
I don’t have a published case in this niche yet.
I build two projects for SaaS and IT products at a 15 % discount — in exchange for the right to publish a case study with real sign-up numbers two months after launch. Timeline, scope and warranty are the same as for any project.
Set out as a separate clause in the contract
Related experience → Life OS: product → pricing → sign-up on your own domainTake a slot04 — What I take into account
57 % go to pricing before the product description
Pricing is not “a page in the footer” but the second most important screen.
Three plans with the middle one highlighted
the setup research agrees on; enterprise is not in the grid but a line under it
A free trial without a card brings more sign-ups, with a card a higher conversion to paid
The choice depends on the price point; we decide it in the brief.
If the site and the app are on different domains, the funnel breaks at sign-up
I make one event go through both.
05 — Timeline and price
10–21
days from brief to launch
from ₽80,000
price
What’s included
- structure
- hero
- pricing
- sign-up
- analytics events
- SEO basics
- deployment
- EN version on request
06 — Questions
Common questions
4 questions · 1 minute
Do we need the landing page in two languages?
If you sell abroad, yes: EN is built in the same project, URL /en/, hreflang. If your market is Russian-speaking, one language is enough; the second can be added later.
We haven’t settled on pricing yet
I build a page with three plans and a toggle; prices and limits live in one file you edit yourself. Imprecise pricing beats “contact us”.
Can we use Stripe from Russia?
Not directly. For rouble payments, YooKassa; for international ones, Paddle or Lemon Squeezy as merchant of record. I connect what fits your jurisdiction.
Should the site be separate from the app or inside it?
Separate: the site is static and fast, the app lives its own life. Shared domain, different subdomains or paths — we decide in the brief.
07 — Method
How I study a niche
grind — niche
$ research
> 10 competitor sites: what works for them and what doesn’t.
$ interview
> 30 minutes with you: how clients choose and why they leave.
$ map
> The client’s path from search to request. One action per screen.
$ build
> Modules for the niche, not a template.
Four steps before the mockup. Without them any niche is a template.