Founders Weekend · Lovable
One page that takes money.
Lovable builds a web page from a written prompt. This weekend it does one job: turn the student's Session 3 template into one landing page with the offer as its headline and a button that takes money. It is deliberately not for apps, and the credits are deliberately tight.
Setup
Before the weekend · Ops
- Buy credits for every student, about $25 each, and confirm how students log in (school email or a Founders School account).
- Check the payment step in CofounderJr works for a test venture. Stripe links are built into CofounderJr, so nobody makes them by hand.
- Put the Lovable log-in steps in the family checklist so accounts exist before drop-off.
Before the weekend · every guide
- Do one practice build yourself: fill the Session 3 template in CofounderJr, paste the prompt into Lovable, publish, add the payment link CofounderJr gives you, and pay it on your phone.
- Know the five sections by heart: hero, how it works, who we are, delivery, pay.
- Read “Say no to” and “When it stalls” below. Redirect first; the technical lead handles repeat failures.
At drop-off
- Sign in to Lovable on the student's own laptop while the parent is still there.
- Leave it closed until Session 3 at 2:00.
The Session 3 flow
Fill the template
In CofounderJr, fill the five sections: hero with the offer sentence and price, how it works, who we are, delivery, pay.
Copy the prompt
The template turns the sections into one prompt. Copy it whole; do not rewrite it in Lovable.
Paste into Lovable and publish
Paste, let it build, and publish. Check the headline is the offer sentence, word for word.
Add the payment link
Copy the student's Stripe payment link from CofounderJr and ask Lovable to make the pay button open that link. Nothing else about payments.
Test on a second device
Open the published link on a phone, signed out, and get to the checkout. Working in the editor is not working.
Say no to
Lovable will offer these. Redirect the student to one page and one pay button rather than fixing it for them.
- Log-ins, accounts or a members area.
- A database, a dashboard or saving customer data.
- More pages, a blog, a shop with a cart.
- Subscriptions, or a payment system built into the page. One button to one one-time payment link is the whole of payments.
- Rebuilding from scratch to try a new look. Polish comes after somebody can pay.
When it stalls
The page does not match the template
Paste the whole prompt again into a fresh project rather than patching. Then change one thing at a time.
Lovable adds features nobody asked for
Ask it to remove them in one line: “Keep one page only: hero, how it works, who we are, delivery and a pay button.”
Credits are running low
Stop generating and edit the text directly where it can. The page only needs to be clear and payable; it does not need another version.
The pay button does nothing
Check the button opens the exact payment link, then test it on a phone. If the link itself fails, hand it to the technical lead with the student's name.
Stripe is not ready for this student
Publish with the price visible and a way to contact the student. Record the blocker for the technical lead. It must not stop the calls at 3:00.
The published page will not load for somebody else
Publish again and open the new link signed out. Send the student the link they should share, and check it on a second device before they use it.