SaaS landing pages without engineers
Your marketing site lives outside the app repo, so a new headline or a feature page ships this afternoon instead of waiting on a sprint.
Every page change is a ticket
A new headline takes a PR, a review and a deploy. A/B testing needs an enterprise contract or engineering time nobody has, so you do not test.
Test pricing and demo CTAs on one URL
Split tests run server-side on one URL, with sales, revenue and EPC per variant and a significance check on conversion rate against a minimum sample size.
A CRM you define yourself
Demo requests, trials and closed deals, in the entities and stages your process uses. A round-robin node splits follow-up across the team.
MRR and churn next to the pages
Dashboards from 80+ card types: cohort retention, funnel flow, MRR and churn, next to the pages that acquired them.
What SaaS teams build here
Marketing autonomy, without losing engineering rigour.
Feature launch pages
Describe the page and the AI writes it. Live the same day.
Pages as files
Cursor or VS Code, git-versioned, with PR reviews if you want them.
The marketing site
Homepage, features, pricing, blog and changelog, off the app repo.
Webinar registration
The registration page and the follow-up sequence.
Marketing ships, engineering reviews
The app repo stays untouched.
Describe the page
The AI builder writes the structure. Marketing edits the copy.
Test it on one URL
Variants run server-side until the statistics call a winner.
Keep it in git
Engineers pull the pages as files with the ef CLI when they want review.
SaaS landing page builder FAQ
Does the marketing site have to live in our app repo?
No. The marketing site runs on ElasticFunnels and the app stays in your repo, so marketing ships pages without touching your codebase.
Can engineers still work in code?
Yes. Pages are files you edit in Cursor or VS Code, keep in git and review in pull requests if you want to. The CLI and the API cover the rest.
How are A/B tests decided?
Server-side, on the same URL. Each test shows sales, revenue and EPC per variant, and checks significance on conversion rate with a p-value and confidence interval. You mark the winner yourself, or turn on auto-winner, which waits until every variant reaches its minimum sample size.
Do server-side tests hurt SEO or ads?
No. Variants are served under the same URL, so there is no redirect and no second URL for an ad platform or a search engine to pick up.
Where do demo requests go?
Into a CRM you define yourself, with the entities and stages your process uses. A round-robin node splits follow-up across the team, and Slack gets a message on the ones that matter.