PRO · BUILD IT WITH THE COHORT

Stop renting software that almost fits.

Take one seat and bring one clear problem. You build the production software around it on Lovable with T24 in the room, connect the tools you already use and leave owning what shipped. AI is included only when it improves the result.

Reserve your seat
01 / 06 · WHAT WE SHIP

An internal app  portal, dashboard, or intake tool.

An automation that ends the manual process.

A customer-facing website or product experience.

02 / 06 · HOW A SEAT WORKS
01
RESERVE

Pick an open date and pay to hold your seat — minimum 8 to run, maximum 16, maximum 3 people per company.

02
DIAGNOSTIC

Before the day, we name the one process worth replacing and bound the scope around it.

03
BUILD & SHIP

You build it on Lovable with T24 beside you and it goes live — not a demo you still have to approve.

04
YOURS

You leave able to run and extend it. Lovable platform access for the day is on us.

Built on Lovable and connected to your stack—your database, email and existing tools. Every Pro seat ends with you able to run what shipped.

03 / 06 · VISIBILITY

When AI answers, be the source.

When what we build is public-facing, it's structured to be read, cited, and surfaced by AI engines — Perplexity, ChatGPT, Google AI Overviews. Semantic, answerable, verifiable. Visibility is architecture now.

04 / 06 · PRICING

One seat. One problem solved.

$790

CAD per seat. One problem built and shipped, no hourly billing.

8–16 SEATS

First come, first served — maximum 3 people per company. Lovable access included.

GUARANTEE

If your cohort doesn't run — under 8 seats — or your problem doesn't ship by the end of the day, full refund.

Reserve your seat
PRO · RESERVE YOUR SEAT

Pick your build day.

$790 CAD per seat. Choose an open cohort date below, pay to hold your seat, and you're confirmed — no application, no waiting on a reply.

Upcoming cohorts
05 / 06 · STRAIGHT ANSWERS

The four questions we always get.

“One day? Really?”

The scope is fixed before the day starts, and we build on Lovable rather than from scratch. That is the whole difference. The price is published because we are willing to be held to it.

“What if the scope changes?”

We rescope before the day, not during it. The seat covers one bounded problem — no creep, no hourly drift, no invoice you did not see coming.

“Is it actually ours?”

Yes. You own the build, it runs on your accounts, and your team is trained to extend it. Nothing is rented back to you.

“We want more than three of us there.”

Then Pro is the wrong offer. A Pro cohort is for one bounded problem per organization. When a department needs its full workflow backlog prioritized, measured and routed into clear decisions, start with an outcome-discovery conversation about Team.

06 / 06

Five things to remember.

01

Yours, not rented.

02

In production the same day.

03

Production standard, focused scope.

04

Public builds, built to be cited.

05

You run it after.

FAQ

What is the Pro cohort?

An open-enrollment build day. You take one seat, bring one problem, and build an app, portal, website, workflow or automation on Lovable with T24 in the room. It goes to production before you leave.

How much does a Pro seat cost?

$790 CAD per seat. Lovable platform access for the day is included. No hourly billing and no surprise invoice.

How many seats are there?

Minimum 8 seats for the day to run, maximum 16, and no more than 3 people from the same company. Seats are reserved first-come, first-served — pay to hold yours, then we help bound the problem before the day.

What if the cohort doesn't run, or nothing ships?

Full refund. If the cohort doesn't reach 8 seats, or your problem isn't shipped by the end of the day, you get your $790 CAD back.

Who is Pro for?

Founders, operators, nonprofits, SMBs and individuals inside larger organizations who need one clearly bounded production build. A whole department belongs in Team; governed organizational rollout belongs in Enterprise.

What does AEO/GEO mean?

Answer-engine and generative-engine optimization: structuring what we ship to be read, cited, and surfaced by AI engines. Visibility is architecture now.

What happens after the build day?

You leave able to run and extend what shipped. When the build is public-facing, that includes the AEO/GEO structure — semantic HTML, schema, verifiable claims — so it's ready to be read and cited by AI engines from day one. Internal apps and automations get the same rigour, pointed at your own systems instead.

Ship the software you actually need.

Fixed scope. Production delivery. Your code.

Reserve your seat