Loading…
Loading…

The stack
Every platform, integration, and tool that goes into the kits. No sponsorships (Jotform partner code disclosed), no resume-padding, no theoretical tooling. If it's listed, a real client build touched it.
The surface the kits run on. Everything else is connected tissue.
The form + workflow engine every kit installs into. Conditional logic, webhooks, payment flows, HIPAA plan. Five years building this thing; one partner code (burakilter) for a plan discount.
Services the kits wire into. Used daily on real client builds, not theoretical.
Primary payment rails. Used for deposits, recurring billing, and single-transaction checkout across kits.
CRM target for the sales lead capture and quote-request kits. Webhook-first, no middleware.
Enterprise CRM target for larger sales and agency clients. Field mapping handled in the kit.
Used for glue, not for logic. If branching or scoring is involved it belongs in Jotform; Zapier only fires the cross-app event.
Alternative to Zapier when a client already lives in it. Same rule: glue only, never business logic.
The default "roster" target. Every events, registration, and intake kit ships with a live Sheet sync.
Used when a client wants a bit more structure than Sheets but not a full database. Good for CRM-lite and content ops.
What keeps the workshop running behind the scenes.
The AI assistant the workshop runs on for drafting, document review, intake checks, and encoded processes. Moved here from ChatGPT this spring. Projects per client, Skills for repeatable tasks. ChatGPT stays in rotation for image generation and voice.
Transactional email for this site (contact form replies, newsletter welcomes). Cheap, reliable, good DX.
The site itself - App Router, React 19, Tailwind v4. Static-first, JSON-driven content.
Where the site and the newsletter live.
Where this site ships. Preview deploys, edge redirects, analytics.
Where the code actually gets written.
The editor. With Claude Code for pair-programming when the workflow warrants it.