Sell, Schedule, Capture: Embeds Without Owning the Checkout

Sitelas does AI website generation, forms, and analytics. It does not run a checkout, a calendar, or a broadcast email engine. Site owners use their own Stripe, Calendly, and email-provider accounts; Sitelas embeds those as first-class primitives in the page tree.

stripe-payment-link

A button or link that opens the site owner's Stripe Payment Link URL.

• Site owner creates a Payment Link in their Stripe dashboard → copies the URL.
• Pastes it into the primitive's paymentUrl prop, or asks Claude: "Add a buy button on the product page for $35, link to buy.stripe.com/xyz".
• Renders as a styled button. Click → Stripe-hosted checkout on the site owner's own account.

Props: paymentUrl, text, openInNewTab, variant, size, borderRadius.

Sitelas never touches money. No Stripe Connect, no marketplace obligations, no chargebacks routed through Sitelas, no PCI surface.

calendly-embed

An inline Calendly booking widget.

• Site owner creates a Calendly event → copies the URL.
• Pastes into calendlyUrl.
• Renders Calendly's widget inline — visitor books without leaving the site.

Props: calendlyUrl, height, hideEventTypeDetails, hideGdprBanner, backgroundColor, primaryColor, textColor.

Sitelas never sees the calendar. Calendly owns the scheduling, reminders, rescheduling, time-zone math, and everything else they've built over a decade.

The form primitive

One primitive covers every form on every site — differentiated by data.formType (an open string: contact, newsletter, rsvp, quote, anything). Submissions land in your Sitelas inbox and contact list, with an optional per-form webhook for anything that takes an HTTPS POST; file uploads are stored privately by Sitelas. Want the data in a spreadsheet? Claude's own Google Sheets connector handles that (see below). Covered separately — see Where Your Form Submissions Actually Go.

Why this is the right boundary

Specialist tools do it better

Stripe, Calendly, Mailchimp each have 10+ years of depth Sitelas isn't going to replicate. Building Sitelas-side commerce would mean a thinner Stripe, a worse Calendly, and a feature-anemic Mailchimp — all maintained by a small team that should be writing templates instead.

Zero marketplace obligations

No Stripe Connect chargebacks routed through us, no CAN-SPAM compliance for broadcast email, no GDPR subject-access requests for transaction records we never stored.

Site owner owns the relationship

They control their Stripe account, their customer list, their calendar. Leaving Sitelas doesn't break the business — the money keeps flowing to their Stripe account regardless.

What's explicitly not on the roadmap

• Stripe Connect / marketplace billing — stays direct to the owner's own Stripe.
• Native commerce (carts, inventory, orders) — Sitelas owns the catalog page, not the checkout.
• Native scheduling (round-robin, availability rules, reminders) — Calendly territory.
• Native broadcast email — Mailchimp / ConvertKit / Beehiiv.
• Shopify integration — deep ecommerce is a different product.

Cross-tool orchestration is Claude's job, not ours

Claude already has connectors for Gmail, Calendar, Drive, Sheets, GitHub, Linear, Notion. With Sitelas installed as another connector, you can chain across them in one chat:

"Export this month's submissions to a new Google Sheet."

Claude reads Sitelas's list_submissions, then writes to Sheets via its own Sheets tool. We don't maintain a Sheets connector for this — Anthropic does. Every new Claude connector becomes transitively available to Sitelas users at zero cost to us.