After you buy

Everything you need is waiting.

The moment your Build Pack is delivered, you get access to your client portal — documentation, MCP server setup, the community, live events, the Classroom, and a direct line to Gus. Here's exactly what that looks like.

From purchase to live in minutes Your accounts. Your code. Your platform. No servers to rent. No DevOps required.
01 · The first 24 hours

From purchase to first build session.

01

You buy

Choose a platform. Checkout through Stripe. Takes 90 seconds. The moment your purchase confirms, your deployment is ready to start.

02

Connect three accounts

GitHub stores your code. Vercel publishes your platform. Neon holds your data. One click each. All free to start. Takes about three minutes.

03

Name it and press Deploy

Pick your platform name. Press Deploy. Behind the scenes: a private GitHub repo is created, a fresh database is spun up, the full schema is applied, and your live site is published — all inside your own accounts.

04

You get three links

Your live URL. Your private code repository. Your database. The platform is yours — run it, rebrand it, extend it however you like. Then open it in Claude Code and say "read CLAUDE.md" to start building on top of it.

02 · Inside the portal

Everything in one place.

Your client portal has six sections. Here's what each one does.

Fig. 01 · Client portal — dashboard

Your dashboard

Everything starts here. Your purchased Build Packs are listed with download buttons — always the current version, updated whenever we ship improvements to the stack.

For Lifetime Deal members, the full catalog is here. Filter by vertical, complexity, or profit potential and download whichever platform you're ready to build.

  • Current Build Pack versions always available
  • Lifetime members see the full 145+ catalog
  • Download history and session notes
Fig. 02 · Client portal — resources & MCP setup

Resources & MCP setup

The Resources page is the first thing to read after downloading your Build Pack. It has two jobs:

First — human-readable docs. The Get-Started Walkthrough takes you from unzipping the folder to a live Vercel deployment in 13 steps. The Build Pack structure guide explains every file and why it's there. Gotchas documents every known trap before you can hit it.

Second — MCP server setup. One terminal command connects your AI agent to PushButtonPlatforms' documentation server, so mid-build questions get answered by the server, not by you googling error messages.

  • Get-Started Walkthrough (Mac & Windows, 13 steps)
  • MCP server: connects agent to live PushButton docs
  • Neon, Vercel, GitHub, Context7 MCP setup — all in one place
  • Gotchas, deployment guide, database patterns
Fig. 03 · Client portal — technical documentation

Technical documentation

The docs section is for when you want to understand what you're building, not just execute commands.

Every doc is written in two voices — plain English first, then the technical detail for those who want it. The Build Pack structure guide explains the MWP layer system. The auth doc explains exactly why Better Auth was chosen over NextAuth or Clerk. The gotchas page has every known trap with wrong, right, and why.

Technical buyers get the depth they need. Non-technical buyers can follow the plain-English sections and skip the rest.

  • Build Pack structure & MWP protocol
  • Better Auth setup and patterns
  • Environment variable reference (every variable, where to get it)
  • Deployment guide: GitHub → Vercel → custom domain
  • Gotchas: stack-specific and platform-specific traps
Fig. 04 · Client portal — community feed

Community

A buyers-only community lives inside the portal — questions with accepted answers, build shares, and announcements from people running the same stack you are.

Posts and replies can carry video and audio, so "here's a screen recording of what I'm stuck on" is a first-class question — and those get answered fastest.

The Events calendar runs alongside it: live build sessions, office hours, and walkthroughs. RSVP and you get a reminder email 24 hours before start.

  • Q&A with accepted answers — solved questions stay findable
  • Video & audio attachments on posts and replies
  • Events calendar: live sessions, office hours, build-alongs with RSVP
  • Early Drops category — Lifetime members see new platforms first
Fig. 05 · Client portal — classroom

Classroom

The Classroom is where the permanent learning lives: courses, walkthroughs, and every live session recording — organized into lessons with your progress tracked as you go.

Miss a live session? The recording publishes straight into the Classroom and everyone who RSVP'd gets notified. Nothing disappears into a chat scroll.

Some courses are open to every buyer; others are Lifetime-member exclusives.

  • Courses with lessons, video, and progress tracking
  • Live session recordings publish here automatically
  • Pick up exactly where you left off — completion is saved
  • Lifetime-exclusive courses alongside the open catalog
Fig. 06 · Client portal — ask-anything assistant

Ask Anything

Every portal has an AI assistant that knows your Build Pack — the stack, the patterns, the docs, and the platform you're building.

Ask it anything mid-build. "How do I add Stripe to this?" "What's the right way to add a new database table?" "Why is my Neon connection timing out?" It answers from the context of your specific platform, not generic documentation.

This is the support layer that means you're never stuck.

  • Knows your specific Build Pack and stack
  • Answers stack questions, pattern questions, deployment questions
  • Available 24/7 — no waiting for a support ticket
  • Falls back to "book a call with Gus" for anything it can't answer
03 · You're not building alone

Community access included with every purchase.

Every Build Pack purchase includes access to the PushButtonPlatforms community — built directly into the portal, on the same stack the Build Packs teach. Questions get accepted answers that stay findable. Posts and replies carry screen recordings, not just text.

Around the feed: a live events calendar with RSVP and email reminders, member groups by platform and cohort, and a Classroom where every session recording lands as a trackable lesson. Lifetime members get the Early Drops category — new platforms announced there before they go public.

Q&A with accepted answers

Ask with a screen recording attached; the accepted answer floats to the top and stays findable for the next builder who hits the same thing.

Live events + Classroom

Build sessions, office hours, and walkthroughs on the calendar — RSVP, get a 24-hour reminder, and catch the recording in the Classroom if you miss it.

Early platform drops

New platforms announced in the members-only Early Drops category before they go live on the site. Lifetime members get first access.

GS

04 · If you get stuck

Book a call. I'm here.

The portal, the docs, the MCP server, and the community handle 95% of questions. For the other 5% — the edge case nobody's hit yet, the business question that isn't in the docs, the "is this the right platform for my specific situation" conversation — I'm available.

Every Build Pack includes the option to book a 30-minute call directly with me. No support queue. No ticketing system. If you're stuck on something real, we'll figure it out.

— Gus Skarlis, Founder

Book a call with Gus
05 · What this replaces

Support that doesn't cost more per month.

Without PushButtonPlatforms

  • Build from scratch: 3–6 months, $15k–$65k
  • Stack questions: StackOverflow, GitHub issues, outdated blog posts
  • Deployment errors: google the error message, hope someone had the same issue
  • Architecture decisions: make it up as you go
  • No gotchas reference: hit every trap cold
  • Support: file a ticket, wait 2–5 business days

With a Build Pack + Portal

  • Production-ready platform: live in minutes, $899
  • Stack questions: Ask Anything (knows your exact stack)
  • Deployment errors: Vercel MCP + deployment guide
  • Architecture decisions: already made, documented with reasons
  • Gotchas: documented before you can hit them
  • Support: Ask Anything → community → book a call with Gus

Everything you need is in the portal.

Connect and deploy. Open the portal. Your first build session is closer than you think.

Connect GitHub, Vercel & Neon → Name it → Deploy. Done.

Talk to Gus first →