BPAI

Two Page Verdicts for an AI education platform: what was costing it signups and sales, and how to fix it.

BPAI (Business Programme AI) is an education platform about AI at work and in business: video courses, tutorials, webinars, e-books and checklists with 12 months of access, under the patronage of MIT Sloan Management Review Polska.

  • 2

    Page Verdicts

    the waitlist page and the sales page

  • 3 days

    to deliver both

    PDFs with fixes and 2 Loom walkthroughs

  • 3

    fixes already live

    email first, phone step announced, BPAI explained on screen one

BPAI Early Birds 2027 waitlist page

Client

Business Programme AI

Industry

Online education

Market

Poland

Platform

Audit (Page Verdict)

Scope

Page Verdict x2 (waitlist page + sales page)

Timeline

3 days

Year

2026

In short

BPAI is a Polish education platform about AI in business. Its waitlist page for 2027 was losing signups: the email from the first step wasn't saved, and the page said what BPAI is only on the 4th screen. In 3 days we delivered two Page Verdicts with every fix and two Loom walkthroughs. The waitlist page now asks for the email first and explains BPAI on the first screen.

The problem

What was the problem?

BPAI runs a waitlist page for its 2027 edition and keeps the 2026 sales page as the base for the next one.

  • 24,496 people were on the 2026 list.

  • 10,000 seats are planned for 2027.

  • So every lost signup counts, and the fixes had to be ready to hand straight to BPAI's own developer.

The fix

Here’s what we’ve changed

We went through both pages and wrote down every fix, with screenshots and two Loom walkthroughs of the live pages. The biggest ones on the waitlist page:

1. Save the email after the first step

The email from the first step of the form wasn't saved anywhere, so everyone who left at the phone number step was lost. The fix: save it after the first step, with consent right under the first button.

2. Put the form first, not the video

The studio video was too long and sat above the form instead of next to it.

3. Promise only what the numbers allow

"Guaranteed seat" clashed with 10,000 seats for 24,496 people on the last list.

4. Say what BPAI is on the first screen

On a phone, the cookie banner covered almost half of the first screen with the form, and the page said what BPAI is only on the 4th screen on desktop and the 7th on a phone.

Results

And did it actually work?

Both Verdicts went out on November 2, as PDFs with fixes and two Loom walkthroughs. BPAI has its own developer, so the Verdicts were written to be handed straight to them.

Today the waitlist page asks for the email first, tells people the phone number comes in the next step, and says what BPAI is on the first screen.

Want the same for your page? Start with the Page Verdict.

Takeaways

What you can take from this project

  • Save the lead as early as possible. A form with several steps should keep the email from step one.

  • Say what you are on the first screen. People won't scroll to the 4th screen to find out.

  • Check the phone view with the cookie banner on. It can hide half of your first screen.

  • Keep promises in line with your numbers. "Guaranteed seat" breaks trust when seats are limited.

FAQ

Questions about this project

  • An audit of one page: what costs it signups or sales and how to fix it, as a PDF with screenshots and a Loom walkthrough of the live page.

  • Two Page Verdicts, one for the 2027 waitlist page and one for the 2026 sales page, with two Loom walkthroughs, delivered in 3 days.

  • Saving the email after the first step of the form. Before, everyone who left at the phone number step was lost.

  • Yes, on the waitlist page: it now asks for the email first, says the phone number comes in the next step and explains what BPAI is on the first screen.

Planning something similar?

Book a call and talk to me directly. I’ll tell you honestly if I can help.

Or email me here: