Latest / AI Builds It: Easy Coding Tools / Sell 25 Tickets to a Local Breakfast With Replit Agent and Stripe

Transcript

Sell 25 Tickets to a Local Breakfast With Replit Agent and Stripe · AI Builds It: Easy Coding Tools

• 0:00
  SPEAKER_00: Build the ticket page in ReplitAsian if this is a repeat breakfast and you can send your email list straight to it.
• 0:07
  SPEAKER_00: Use Eventbrite when you need its event marketplace to help strangers find you.
• 0:12
  SPEAKER_00: Skip a custom build for a one-off event with no direct audience.
• 0:17
  SPEAKER_00: The choice is about reach.
• 0:19
  SPEAKER_00: Eventbrite is the easier button to press.
• 0:21
  SPEAKER_00: You can publish events for free, and it offers a Discovery Marketplace and marketing tools.
• 0:27
  SPEAKER_00: Fees apply when you sell paid tickets.
• 0:30
  SPEAKER_00: If you need new people to find your breakfast, those features may be worth more than the ticket fees.
• 0:36
  SPEAKER_00: Eventbrite's pricing overview.
• 0:39
  SPEAKER_00: But Maya already has an email list.
• 0:42
  SPEAKER_00: She does not need a marketplace to find her first 25 guests.
• 0:46
  SPEAKER_00: She needs a good event page, a checkout that stops at 25 seats, and an attendee list she can use again for the next breakfast.
• 0:55
  SPEAKER_00: That's when a small replit app earns its keep.
• 0:58
  SPEAKER_00: Maya can keep the page in her own style, send every email to one checkout link, and track which promotion brings buyers.
• 1:06
  SPEAKER_00: For repeated events, she can reuse the page and update the date, price, and seat count.
• 1:12
  SPEAKER_00: My ranking.
• 1:13
  SPEAKER_00: Replit agent plus stripe for repeat events with a list or another reliable way to bring buyers directly.
• 1:20
  SPEAKER_00: Evetbrite for a one-off event, an organizer who wants less setup, or a breakfast that needs marketplace discovery.
• 1:27
  SPEAKER_00: The$500 Breakfast Math.
• 1:29
  SPEAKER_00: Say Maya runs the fictional Riverside Builders Breakfast at Juniper Table in Columbus on December 10, 2026, from 8 to 9.30 a.m.
• 1:40
  SPEAKER_00: She has 25 seats and charges$20 per ticket.
• 1:44
  SPEAKER_00: A sold-out event brings in$500 before food, venue costs, and payment fees.
• 1:51
  SPEAKER_00: Here's the comparison.
• 1:53
  SPEAKER_00: It assumes 25 separate one-ticket domestic card purchases.
• 1:58
  SPEAKER_00: For a fair checkout price comparison, Maya absorbs Eventbrite's fees, so buyers pay$20 either way.
• 2:05
  SPEAKER_00: For the full table, please open this article on EasyCoding.tools.
• 2:11
  SPEAKER_00: For a$20 ticket, Eventbrite's U.S.
• 2:13
  SPEAKER_00: service fee is 3.7% plus$1.79 per ticket.
• 2:19
  SPEAKER_00: That's$2.53.
• 2:22
  SPEAKER_00: Add$0.58 for the 2.9% processing fee on a$20 order.
• 2:27
  SPEAKER_00: $3.11 per ticket.
• 2:30
  SPEAKER_00: Or$77.75 for$25.
• 2:33
  SPEAKER_00: Eventbrite normally adds fees to the buyer's checkout, but organizers can choose to absorb them.
• 2:39
  SPEAKER_00: Eventbrite's U.S.
• 2:41
  SPEAKER_00: ticket fees, Stripe's published domestic card rate, is 2.9% plus 30 cents per successful transaction.
• 2:48
  SPEAKER_00: On a$20 single ticket payment, that's$0.88.
• 2:52
  SPEAKER_00: Across 25 separate payments, Stripe takes$22.
• 2:57
  SPEAKER_00: Add one$20 month of Replit Core, and the known plan and payment subtotal is$42.
• 3:03
  SPEAKER_00: That leaves$458 before any extra Replit usage, a$35.75 difference from absorbing EventBrites fees.
• 3:13
  SPEAKER_00: Stripe standard US pricing and replit's core pricing.
• 3:17
  SPEAKER_00: If you already pay for Replit Core, don't count the subscription again as a new event cost.
• 3:22
  SPEAKER_00: And if buyers purchase several tickets in one Stripe checkout, the 30 cent fixed fee applies per payment, not per seat.
• 3:31
  SPEAKER_00: So Stripe's total can be lower.
• 3:33
  SPEAKER_00: The comparison changes if Maya passes EventBrites fees on to buyers.
• 3:38
  SPEAKER_00: She can keep more of the listed ticket price, but guests pay more than$20 at checkout.
• 3:45
  SPEAKER_00: Pick the setup that matches the price you want guests to see.
• 3:49
  SPEAKER_00: Build the small page Maya actually needs.
• 3:52
  SPEAKER_00: The page should answer the questions a buyer has before paying.
• 3:56
  SPEAKER_00: What is it?
• 3:57
  SPEAKER_00: Riverside Builders Breakfast with a short description of who should come and what the ticket includes.
• 4:03
  SPEAKER_00: When and where?
• 4:05
  SPEAKER_00: December 10th, 2026, 8 o'clock to 9.30 a.m.
• 4:09
  SPEAKER_00: at Juniper Table in Columbus.
• 4:12
  SPEAKER_00: How much?
• 4:13
  SPEAKER_00: $20 per ticket.
• 4:14
  SPEAKER_00: With any meal or drink details stated plainly.
• 4:17
  SPEAKER_00: Are seats left?
• 4:19
  SPEAKER_00: Show the remaining count and stop sales at 25.
• 4:22
  SPEAKER_00: What happens after checkout?
• 4:24
  SPEAKER_00: Show a clear confirmation and add paid guests to Maya's attendee list.
• 4:29
  SPEAKER_00: Keep the list useful too.
• 4:31
  SPEAKER_00: Store each attendee's name and email, ticket quantity, payment status, purchase time, and the source of the visit, such as Maya's email or an Instagram post.
• 4:41
  SPEAKER_00: Add a private organizer view with seats sold, seats left, and a CSV export.
• 4:47
  SPEAKER_00: The point is not to build a fancy dashboard, it's to know who is coming and which message brought them in.
• 4:53
  SPEAKER_00: Replit's event site guide describes a similar setup: a public event page, stripe checkout, attendees saved in Replit database, and an exportable list.
• 5:03
  SPEAKER_00: Replit's Paid Event Website Guide.
• 5:06
  SPEAKER_00: Copy these prompts into Replit Agent.
• 5:09
  SPEAKER_00: Start with a full stack app, not a static landing page.
• 5:13
  SPEAKER_00: Replit says its Stripe integration needs an app with back-end functionality, and the connector is available on paid plans.
• 5:21
  SPEAKER_00: Agent starts with a Stripe sandbox.
• 5:24
  SPEAKER_00: You connect a live Stripe account when you're ready to publish for real payments.
• 5:28
  SPEAKER_00: Replit's Stripe Integration Guide.
• 5:30
  SPEAKER_00: Prompt 1.
• 5:31
  SPEAKER_00: Build the page and ticket flow.
• 5:33
  SPEAKER_00: Prompt 2.
• 5:34
  SPEAKER_00: Add Stripe and the attendee list.
• 5:36
  SPEAKER_00: Prompt 3.
• 5:37
  SPEAKER_00: Test the parts that can cost you a seat.
• 5:39
  SPEAKER_00: One non-negotiable.
• 5:41
  SPEAKER_00: Able.
• 5:42
  SPEAKER_00: Don't mark someone paid just because they land on the thank you page.
• 5:46
  SPEAKER_00: Add them to the paid attendee list only after Stripe confirms the payment.
• 5:50
  SPEAKER_00: Budget an evening, then test before emailing the list.
• 5:54
  SPEAKER_00: I block three focused hours for the first version.
• 5:57
  SPEAKER_00: About and refine the page, an hour to test checkout and seat limits, and 30 minutes to enter the final event details and check the page on a phone.
• 6:07
  SPEAKER_00: That's a planning budget.
• 6:10
  SPEAKER_00: Not a promise that every build will take exactly three hours.
• 6:14
  SPEAKER_00: Use Stripe sandbox before you send the page to real buyers.
• 6:18
  SPEAKER_00: Replit's guide lists 4242-4242-4242 as a standard test card.
• 6:26
  SPEAKER_00: Run a test order, then confirm the attendee appears in the organizer list and CSV.
• 6:32
  SPEAKER_00: After that, connect the Live Stripe account in Replit's Publish Flow.
• 6:36
  SPEAKER_00: Replit Stripe testing and live payment steps for Maya's Event Month core is$20 per month and Stripe's fees are$22 under the 25 separate payment example.
• 6:48
  SPEAKER_00: Replit usage beyond included credits can add costs.
• 6:52
  SPEAKER_00: For the live app, Autoscale is the sensible deployment choice.
• 6:56
  SPEAKER_00: Replit says it sales down to zero while idle and charges while requests are being served.
• 7:02
  SPEAKER_00: The publishing pane shows the hourly cost for the machine settings you choose.
• 7:06
  SPEAKER_00: So treat$42 as the known plan and payment subtotal.
• 7:11
  SPEAKER_00: Not a fixed hosting quote.
• 7:12
  SPEAKER_00: Replit Pricing and Replit's deployment billing guide.
• 7:16
  SPEAKER_00: Put the email list to work.
• 7:18
  SPEAKER_00: Once the test passes, send one short email with the date, location,$20 price, and a single buy a ticket link.
• 7:25
  SPEAKER_00: Use a source tag such as SRC equals Maya email.
• 7:30
  SPEAKER_00: Use a different tag for social posts.
• 7:32
  SPEAKER_00: When tickets sell, Maya can see which link moved seats instead of guessing from likes.
• 7:38
  SPEAKER_00: In the next hour, open Replit, start a full stack app, and paste prompt one.
• 7:43
  SPEAKER_00: Then put the real date, venue, and ticket details into the draft before you build anything else.
• 7:51
  SPEAKER_00: All links to sources are available in the text version of this article.
• 7:56
  SPEAKER_00: You can find the full article at easycoding.toolslash blog.
• 8:00
  SPEAKER_00: Thanks for listening.
• 8:02
  SPEAKER_00: For more practical AI coding guides, tool comparisons, and resources for builders, visit easycoding.tools.
• 8:10
  SPEAKER_00: And if it's easier to remember, just go to aibuilds.it.
• 8:14
  SPEAKER_00: It redirects to easycoding.tools.