Skip to content
Skip to the session recap

Office Hours #75 · 7 October 2026

Ask anything.
We'll try.

An hour of real builder questions: Claude, Stripe, branches, handoffs, and one free cap.

Wednesday drop-in

Fast questions,
real answers.

Sam runs a Wednesday drop-in with a long queue of questions. He sets expectations early: AI is not gospel, so correct it with sources and guardrails. Factual one-liners are faster to search than to ask in a live session.

He shows how to connect Claude Code to Base44 through the connector in under a minute, recommends webhooks for keeping Stripe subscription status in sync, and points builders to his video guide on mixing public pages with staff-only dashboards. He explains why an identical prompt can fail one evening and work the next morning: try a different model, use Compare, and avoid peak hours.

Other topics include branches with test data for colleagues, partner handoffs between workspaces, act-as-user privacy and your own Terms of Service, the cost of backend functions that run but do nothing, and a bring-your-own-OpenAI-credits idea modelled on remove.bg. Becca wins a Base44 cap in a wheel spin run by Lily, and Sam previews Thursday's community awards.

Recorded
7 October 2026
Hosted by
Sam
Format
Open Drop-In

Handing work to others

Clients, colleagues,
users, agents.

  1. 01

    Clients

    Contract first, then make them admin, move workspaces, and transfer ownership.

  2. 02

    Colleagues

    Branches with test data keep production safe.

  3. 03

    Users

    Act-as-user is powerful, so cover it in your policies.

  4. 04

    Agents

    Claude or ChatGPT can drive Base44 through the connector.

6 lessons

Small habits,
big saves.

  1. 01

    Connect Claude to Base44 in one message

    Open Claude Code and ask it to connect to Base44 using the Base44 connector, then log in once. Give it an existing app's URL, or a blank app's URL, and prompt away. The same flow works with ChatGPT.

  2. 02

    Keep subscriptions in sync with webhooks

    For monthly and yearly Stripe plans, use webhooks to keep premium status in step with renewals, failures, cancellations, and refunds. A lighter alternative is to fetch the latest status when the subscription page loads.

  3. 03

    When a prompt fails, change the model

    Revert the failure and resend on a stronger model, then use Compare to try two more. LLMs also degrade at peak hours, roughly 17:00–20:00 UK time, so the same prompt may work fine the next day.

  4. 04

    Write a PRD before the first prompt

    Planning the full product requirements up front, with any tool, consistently produces a better app.

  5. 05

    Give collaborators a branch with test data

    Create a branch, enable test data for it, and a colleague can redesign freely without touching production records. Review and merge when it is ready.

  6. 06

    Cover admin powers in your policies

    Act-as-user lets owners see what a user sees. That is normal for any app you control, but your privacy policy and Terms of Service must cover it, and sensitive data such as private messages should be encrypted.

Security week,
awards first.

As stated on 7 October 2026.

  • Update 01

    Security Week is next week

    Sam and Robert will cover RLS basics on Tuesday, a security drop-in on Wednesday, and go-live readiness on Thursday.

  • Update 02

    Community celebration tomorrow

    Thursday's Office Hours is the September awards show with Community Pillar roles, community strategy, and a spoiler for a huge end-of-month event.

  • Update 03

    Game Jam closes in 24 hours

    About 23 hours remained to submit a game to the Launchpad.

  • Update 04

    App folders are coming back

    Sam says folders were moved as part of a large upcoming launch and will return in a better form.

Every question,
answered.

Every substantive question from the hour, including answers the hosts could not confirm.

18 of 18 answers

Watch the original

An hour
of Q&A.

7 October 2026 · Sam

Open on YouTube

Billing questions the hosts could not resolve in public are summarised briefly. The bring-your-own-credits feature was described by a chat member and is not confirmed by Base44.

Bring this to your next build

Keep
building.

  1. 01

    Correct AI with sources and guardrails instead of trusting it blindly.

  2. 02

    Use Stripe webhooks for subscription status.

  3. 03

    On a failed prompt, revert and switch models, and avoid peak hours.

  4. 04

    Hand colleagues a branch with test data.

  5. 05

    Make sure your policies cover admin powers like act-as-user.

Keep learning

Further reading.

Official documentation is supplemental reading, not a claim that the hosts shared each link.

  • Public pages plus staff-only areas video guide (Dec 2025)linked in chat; exact URL not in the captions.
  • Base44 feedback boardfeedback.base44.com
  • Base44 merch storelinked in chat.
  • Unofficial Office Hours archivethis site.

Unofficial community archive · All Office Hours