CREA.MBAThe landing is done. The legal is done. The Discord is live. Here's what v1.0.0 of CREA.MBA actually ships with — and what I decided to cut.
I've spent the last ten days shipping the final push of CREA.MBA v1.0.0. Today the landing is done, the Terms of Service are bulletproof, the Discord server is up, and the Polar checkout is wired to automatic GitHub and Discord access. The product is ready to sell — the store opens in two weeks once the waitlist emails go out.
This is a build-in-public post, not a marketing page. If you're working on your own boilerplate, SaaS, or founder launch, I think the useful parts are here: the section structure that actually converts, the legal language that stops the four reselling attack vectors, and the decisions I cut for lack of time.
I analyzed six competitors — ShipFast, MakerKit, Supastarter, IndieKit, SaaSBold, NextBase — and mapped every section each one uses. Then I cut the ones that looked like filler and combined the ones that said the same thing twice.
The final structure:
The decision that mattered most: putting the changelog on the landing instead of the blog. A blog makes sense for SEO, but for a boilerplate the signal a potential buyer needs is "this is actively maintained." The changelog delivers that at a glance; a list of blog posts from six weeks ago does not.
A boilerplate is software that begs to be redistributed, white-labeled, resold, and templated into a marketplace. The Terms of Service close those paths explicitly, with two distinct licenses:
Individual License: unlimited personal projects. Build your ideas — as many as you want, commercial or not, no cap.
Company License: one license = one project. Freelancers, consultancies and agencies always fall under Company — every client project requires its own license, no exceptions.
The four restrictions that harden the Company License:
Defining who counts as "individual" and who counts as "company" objectively cost me three drafts. Solo founder building their own products → Individual. Freelancer billing hours to a client → Company. No ambiguity = no future disputes.
A lawyer reviewed the full text. After the feedback, the Company License was reinforced with four additional clauses. Without that review, three of the four reselling vectors would have been wide open. If you don't know a lawyer, budget around €300 for a basic ToS review — that's cheap compared to the cost of a dispute.
The privacy policy follows GDPR literally. Real providers named: Polar, Stripe (fallback), GitHub, Discord, Resend, Google Analytics. Real retention windows. Real rights explained (access, rectification, erasure, portability, opposition, consent withdrawal). AEPD as the Spanish data protection authority for complaints.
Zero friction from click to code. Here's the flow:
/api/webhooks/polar route runs./thank-you with three next steps: check email for the GitHub invite, join Discord, watch the 3-minute quick-start screencast.No account on crea.mba. No login. No signup. The decision was to keep the buyer flow radically simple — the landing, the checkout, the delivery, and nothing in between.
Three prices for three distinct moments of the launch:
The founder window runs a few weeks as a goodwill payback for the people who trusted me when the product was vaporware. The early bird is the launch price that gets CREA.MBA ranking against the competitive median ($349) at 38% below it. The standard price activates later, when the product carries its own weight with case studies.
Not everything made the v1.0.0 cut:
If you're reading this from a future post-launch point, assume the real numbers and decisions are in the next changelog entry. Build in public only works if the numbers are real.
Two things I'd repeat. First, close the legal back doors before the first euro comes in. Every ambiguity in your ToS is a future dispute. My fourth draft is the one I published; the first draft would have left three of the four reselling vectors wide open.
Second, cut hard before you ship. Testimonials, launch video, blog section on the landing, Skool evaluation, custom newsletter platform — all wanted a slot, none earned one. v1.0.0 is the minimum version that can carry the promise of the product without lying. Everything else is v1.1, v1.2, v1.3.
Next week: founder emails, the first real conversions, and the first real data. Stay tuned.
Subscribe for more tutorials and tips on building products with AI