A lead-gen page is one offer, one form, and somewhere for the answer to land
A lead generation landing page makes one offer and asks the visitor for a way to reach them. No navigation to wander into, no second product competing for attention, no link that leads anywhere except the form.
That form is the whole difference. If the action on your page is a booking, a purchase or a signup rather than a captured enquiry, you want the general landing page walkthrough instead.
Most advice stops at the layout. The part that decides whether the page earns you anything is quieter: where a submission goes after the visitor hits send. On Birta it goes to two places. It appears in your project's Leads tab right away, and it arrives by email about 15 minutes later, in one message to everyone with access to the project.
That is the whole delivery story. No Telegram, no Slack, no webhook, no field where you type a different address. Knowing it now saves you building the page and then hunting for an integrations screen that does not exist.
| What you have | Where to go |
|---|---|
| An offer you can sell today, and you want to reply to the people who ask | This guide. |
| Nothing to sell yet, just collecting emails to notify later | A waitlist page instead: one field, and a promise about the future rather than a reply. |
| More to say than one page holds, with sections that link to each other | Settle the shape first with the landing page or website questions. |
| The visitor should pay on the page | Not here. Birta sites don't take payment yet, so put a payment link on the page and take it elsewhere. |
What has to be on the page
Five things, each doing one job. Judgment rather than research, and the judgment behind most pages that work: say what you are offering, prove you can deliver it, and ask for the least you need to reply.
| Element | What it has to do | What to tell the agent |
|---|---|---|
| The headline | Answer "what am I getting" before the visitor scrolls | The offer in the visitor's words, not your product name |
| The offer | Say what happens next and what it costs, if anything | Two or three lines, concrete, no feature list |
| The form | Collect only what you need to reply | The exact fields, with types, and which ones are required |
| One piece of proof | Give a reason to believe you | A real testimonial, a named client, a number you can stand behind |
| One button | Leave one thing to do | The submit label as a promise: "Send my brief", not "Submit" |
The form is where most pages leak. Every extra field is another reason to close the tab, and you can ask the rest in the reply: name, email and one line about what they need is usually enough to start a conversation. A Birta form allows up to 20 fields, far more than a page like this should want. Leave off the phone number unless you intend to call.
Tell the agent what you want
Birta ships no form block and no template. You describe the page and the fields, and the agent writes the markup in your site's own design, along with the code that sends a submission. The "thanks, we'll be in touch" line is yours too.
Paste something like this and change the specifics:
Build a single-page lead generation landing page for <your offer>.
Above the fold: a headline answering what the visitor gets, two or three lines
on what happens after they enquire, and the form. Below it: one testimonial and
nothing else. No navigation.
Declare a Birta form with key "enquiry" and these fields:
- name, short text, required
- email, email, required
- brief, long text, required
- consent, consent, required
Write the form markup to match the page, handle the refusal codes, and show my
own wording on success. Don't publish yet, I want to read it first.If you want the mechanics underneath that, the contact form walkthrough covers what the agent is actually writing. If you have no site at all yet, start one step earlier with building a site without a builder and come back here for the form.
Publish it, then send yourself one lead
- Step 1PublishThe form only starts working on the live site.
- Step 2SubmitFill in the real form on the public URL, once.
- Step 3Find itOpen the Leads tab and check the fields arrived intact.
- Step 4WaitConfirm the email digest reaches your inbox.
Step 1: Publish the page
Ask the agent to publish. A form starts accepting submissions once the project has both a declared form and a published site, and the order does not matter: declare it first or publish first, either works.
Step 2: Send one real submission
Open the public URL in a private window and fill the form in as a visitor would. One submission, not five.
You have to do this on the published page. A version preview refuses every submission on purpose, because a lead belongs to the live site rather than a draft, so there is no way to rehearse this privately.
Step 3: Find it in the panel
Open the project's Leads tab. Your submission should be sitting there with every field exactly as you typed it, and the tab carries a badge counting the leads nobody has opened yet.
Check the fields, not just that something arrived. A required field the agent forgot to declare is the failure you want to catch before the page gets traffic.
Step 4: Wait for the email
The first lead in a project opens a 15-minute window. When it closes, one email goes out covering everything that landed inside it. The window is checked once a minute, so a digest closes on the first check after its time and arrives at about 15 minutes rather than exactly on the mark.
If it doesn't reach you, look in spam before assuming the form broke. The lead in the panel is the copy that matters, and the email is a convenience on top of it.
Where an inquiry actually goes
Every accepted submission is stored on the project and shown in the Leads tab straight away, with the form it came from, the time and each field the visitor filled in. On submit, no delay.
The email is the second half: one message per window, covering every lead that arrived while it was open, sent to the project's owner and every account the project is shared with, at the address each signed in with, in the language their account reads in. No toggle, no alternative recipient, no per-form routing, no unsubscribe. The way to stop the mail is to stop having access to the project.
That is the end of the list. No Telegram, no Slack, no webhook, no CRM, and no way to choose where a lead goes. A project that needs a submission to land somewhere else needs a layer this one does not have.
For the contract the agent codes against, including field types and refusal codes, the lead forms reference prints the running server's own limits.
The plan a working page runs on
A lead-gen page you send traffic to runs on the Free plan: the page, the form, the leads and your own domain. Team, at $12 a month, matters when colleagues work the page with you or the Birta mark has to go.
Submissions are never turned away. Every one arrives, is stored whole, and shows the visitor the same success message, whatever plan the project is on.
The domain is the other half of looking like a business rather than a test, and connecting one is its own short job.
What you can measure, and what you can't
A published project reports unique visitors per day, over the last 7 days, 30 days, or 3 months. That is the whole of it.
On a one-page site that is enough for a rough conversion rate, because visits to the site and visits to the page are the same thing. Divide the month's leads by the month's visitors and you have a number worth watching for direction. For the shape that number usually takes, 707 measured forms put visit to lead at 5.74%. Treat it loosely: a visitor is counted once a day and counted again tomorrow, so somebody who thinks about it over a week appears several times.
What you won't get is where they came from. No referrers, no campaign sources, no per-page breakdown, no A/B testing, no heatmaps, and no line connecting a particular visit to a particular lead. If you need to know which ad produced the enquiry, put that in the form and ask.
Build the page and take the leads
Describe it in Birta's chat and its agent builds and publishes it. Or connect the agent you already use.