Build apps · Your App Cloud
Publish a landing page for one campaign
Give a launch, a season or a single offer one page with one button and a closing date. Keep every sign-up in a list behind your sign-in, and write what the page says once it closes.
Built around a purpose
One offer, one button, one closing date.
For anyone with one offer and a deadline, such as a farm opening its spring box list or a founder collecting early-access requests. A page meant to stay up for years fits the one-page website guide below, and an event with sessions and check-in fits the event management guide.
For illustration: a small vegetable farm in Sonoma County, California, is taking sign-ups for a spring box delivered on Thursdays from mid-April. It has room for 60 households in six ZIP codes around Santa Rosa and Petaluma, with a half share at $28 a week and a full share at $45. You have a paragraph describing a typical box and eight photos from last season. The link will go in three places: the farm newsletter, a sign at the Saturday market and a social media post.
One page with one button: a headline naming the box and the delivery area, three answers about contents, deliveries and payment, and a short form. Behind your sign-in sits the list of every household with its share size, ZIP code and channel, and the closed message waits for the day places run out.
Storing sign-ups, closing at 60 households, a list you sign in to read and confirmation email make this an app with data, and your own domain needs Pro. If the farm already takes sign-ups through a form elsewhere, a page that describes the box and links to that form is a one-page site. Build and preview it on any plan. Putting it live needs Go or Pro. See pricing
Choose the one thing a visitor should do
Write the action as a verb and an object: join the spring box list. Anything that doesn't help someone decide to do that comes off the page. Links to the farm's online shop and its blog would each offer a second action, so they move to the footer or go.
Put the audience and the offer in the headline
A visitor should know from the first line whether the page is for them. "Spring vegetable boxes, delivered Thursdays in Santa Rosa and Petaluma" names the offer and the area together. Three short answers follow: what a box holds, when deliveries run and when you ask for payment.
Ask for no more than the next step needs
The farm needs a name, an email address, a ZIP code to check the delivery area and a half or full share. A phone number and allergy notes can wait until a place is confirmed. To see which channel brought each sign-up, add one optional question listing the three.
Write the message that follows the button
Draft the confirmation before you build: what was received and what happens by when, such as places confirmed by March 20, payment details to follow. Give a ZIP code outside the area its own reply explaining why. The app can also send that wording as an email, which you test before the first real sign-up.
Settle what the page says once places run out
Describe in Studio when the form gives way to a closed message: after March 15 or once 60 households sign up, whichever comes first. That message says when the summer list opens. Publish on your Exepad address, or your own domain with Pro, and share that one address in all three places.
Scope the first version
What a first version includes.
Headline and a single button
The offer and the delivery area in one line, with the day sign-ups close printed beside the button. The button can repeat at the foot of the page, but no second action appears anywhere.
Three short answers
What a box holds in a typical April week, the Thursday delivery window and the ZIP codes covered, and when payment is requested. A sentence or two each.
Proof you can stand behind
Your own photos from last season and one sample week's contents. Leave out quotes you can't attribute and counts you haven't checked, such as "hundreds of happy families".
A short form
Name, email, ZIP code and share size, plus the optional channel question. Required fields are marked, and each error message says what to change.
Three written states
The confirmation after a sign-up, the reply for a ZIP code outside the area, and the closed message with the date the next list opens.
The sign-up list
One record per household with the time it arrived, share size, ZIP code and channel, kept behind your sign-in. Sorted by arrival, it shows who gets the 60 places.
Test it in the preview
Before you share it.
- On your phone, sign up as a stranger would. The button should be reachable without zooming, and the confirmation should give the date you will be in touch.
- Count what a visitor can click. Beyond the sign-up button and the footer, each link is a second action to remove or move down.
- Send the form with a ZIP code outside the area, an email address with no @ and no share size. Each attempt should get a message saying what to change. Then check that the list holds only the sign-ups you meant to keep.
- Change the closing date to yesterday and reload the preview: the closed message should replace the form. Restore it, lower the limit to two households and sign up three times; the third attempt should meet the closed message too. Then reset the limit and delete the test entries.
- Sign out, then paste the list's address into the browser. A sign-in screen should appear, not your neighbors' names and ZIP codes.
- If the app emails confirmations, sign up with two of your own addresses at different providers. Each message should name the share size and the March 20 date; look in the spam folder too.
Together in your app cloud
The pieces behind the possibility.
Choose the models and services that support the experience you want to create.
File storage
A home for your documents and media
Database
Keep data and context for apps and agents
Email
Keep conversations moving
Authentication
Give the right people access
Shape the details
Make it work for your world.
- Put the weekly price and the payment date on the page even though the form takes no money. Everyone who signs up has then seen both before you confirm a place.
- Promise only a reply date you can keep. If the confirmation says places are confirmed by March 20, block time on the 19th to go through the list.
- A sign-up list holds names, email addresses and where people live. Decide who besides you signs in to read it, and how long you keep it after the season settles.
A little more context
Good questions.
How is a landing page different from a one-page website?
Both fit on one page. A landing page serves one campaign, asks for one action and ends, then says so. A one-page website stays up and answers standing questions about a club, a service or a person. A campaign that never closes has become a one-page site, which the guide below covers.
What should the page do after the campaign?
Leave it published with the closed message, so an old post or a printed sign still leads somewhere. Give the date the next list opens. You can export your app's data if the list needs to go elsewhere, and remove details you no longer need once every place is settled.
Can sign-ups feed a lead tracker?
Each sign-up is already a record, so add what a tracker needs: a status such as new, confirmed or waitlisted, a next step and a due date. For a sales campaign with stages and follow-ups, the lead tracking guide below goes further.
How do people pay for their box?
The way you take payment today, with a link to it in the confirmation. With only 60 places, take the sign-up first and ask for payment once a place is confirmed, so nobody who missed out needs a refund.
Explore Pricing for plans, included capabilities, and usage details.
Start from what you have
Bring the file you already use.
Keep exploring.
Your ideas, up and running
Your next idea has a home.
Build an app. Run an agent. Make it yours.
Start building