The stack
What it's actually built with.
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.
Platform
1 itemThe surface the kits run on. Everything else is connected tissue.
- Visit
Jotform
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.
Integrations
7 itemsServices the kits wire into. Used daily on real client builds, not theoretical.
- Visit
Stripe
Primary payment rails. Used for deposits, recurring billing, and single-transaction checkout across kits.
- Visit
HubSpot
CRM target for the sales lead capture and quote-request kits. Webhook-first, no middleware.
- Visit
Salesforce
Enterprise CRM target for larger sales and agency clients. Field mapping handled in the kit.
- Visit
Zapier
Used for glue, not for logic. If branching or scoring is involved it belongs in Jotform; Zapier only fires the cross-app event.
- Visit
Make
Alternative to Zapier when a client already lives in it. Same rule: glue only, never business logic.
- Visit
Google Sheets
The default "roster" target. Every events, registration, and intake kit ships with a live Sheet sync.
- Visit
Airtable
Used when a client wants a bit more structure than Sheets but not a full database. Good for CRM-lite and content ops.
Hosting & Infra
1 itemWhere the site and the newsletter live.
- Visit
Vercel
Where this site ships. Preview deploys, edge redirects, analytics.
Editor & Local
1 itemWhere the code actually gets written.
- Visit
VS Code
The editor. With Claude Code for pair-programming when the workflow warrants it.