Tech Stack
Providers chosen by workflow, not hype.
I use a provider-agnostic stack across voice AI, LLMs, CRM, automation, data, hosting, payments, analytics, and communications. The right stack depends on cost, latency, reliability, data ownership, and what the operator actually needs to run.
01
AI Voice
Provider choices for outbound, inbound, qualification, transfer, and call-summary workflows.
02
LLMs
Models selected by task cost, reliability, latency, tool use, and reasoning depth.
03
CRM
Systems of record for contacts, pipelines, ownership, reporting, and follow-up.
04
Automation
No-code, low-code, and custom integration layers for moving data safely.
05
Data
Storage, data quality, reporting, and enrichment layers for systems that need trustable inputs.
06
Hosting
Deployment, observability, and delivery infrastructure for web apps and marketing sites.
07
Analytics
Measurement and monitoring tools for traffic, speed, errors, and funnel decisions.
08
Payments
Billing, invoice, subscription, and contract-to-payment workflows.
09
Communications
Channels for alerts, reminders, human handoff, and client communication.
Stack recommendation
The current website stack is good and does not need a replacement: Next 16, React 19, Tailwind 4, Supabase, Resend, Upstash, Sentry, and Vercel are a solid fit. The improvements are organization, proof media, lazy SDK initialization, route structure, performance checks, and clearer package surfaces.
Stack audit
Want the right providers for your workflow?
Book a build call for implementation, or request a system audit to compare providers before you commit.