AI sites & automation
Launch without stacking AI tools.
- Selection
- 18 8 optional
- Target budget
- $112 per month
- Profile
- Structuring business stage
Which tool does what?
Core workflow
Lovable
Useful in this role workflow to produce, approve, or deliver more cleanly.Core workflow
Cursor
Useful in this role workflow to produce, approve, or deliver more cleanly.Core workflow
Replit
Useful in this role workflow to produce, approve, or deliver more cleanly.Production
Vercel
Useful in this role workflow to produce, approve, or deliver more cleanly.
ProductionSupabase
Useful in this role workflow to produce, approve, or deliver more cleanly.
ProductionAirtable
Useful in this role workflow to produce, approve, or deliver more cleanly.
ProductionMake
Useful in this role workflow to produce, approve, or deliver more cleanly.Production
Zapier
Useful in this role workflow to produce, approve, or deliver more cleanly.
Support / finishn8n
Useful in this role workflow to produce, approve, or deliver more cleanly.
Support / finishWebflow
Useful in this role workflow to produce, approve, or deliver more cleanly.Support / finishIf needed
Framer
Useful in this role workflow to produce, approve, or deliver more cleanly.
Support / finishIf neededStripe
Useful in this role workflow to produce, approve, or deliver more cleanly.Support / finishIf needed
PostHog
Useful in this role workflow to produce, approve, or deliver more cleanly.Support / finishIf needed
Plausible Analytics
Useful in this role workflow to produce, approve, or deliver more cleanly.Support / finishIf needed
Google Search Console
Useful in this role workflow to produce, approve, or deliver more cleanly.
Support / finishIf neededChatGPT
Useful in this role workflow to produce, approve, or deliver more cleanly.Support / finishIf needed
Claude
Useful in this role workflow to produce, approve, or deliver more cleanly.Support / finishIf needed
Perplexity
Useful in this role workflow to produce, approve, or deliver more cleanly.
Why these tools together?
This stack serves a precise role: Tools, websites, prototypes, automations, agents, AI workflows, payments, SEO, analytics and launch. The right choice is not to own every tool, but to keep a clear chain between research, production, approval, and delivery.
A good fit if…
Tools, websites, prototypes, automations, agents, AI workflows, payments, SEO, analytics and launch.
Look elsewhere if…
You do not yet have a recurring deliverable or client workflow to structure.
Source of truth
The brief, source files, exports and decisions have to stay connected.
Reliable production
The core tools should cover 80% of the work without piling up duplicates.
Clear sign-off
The client has to be able to approve a version, a budget or a direction without ambiguity.
What should you budget?
Lovable$25
Supabase$25Replit$20
Zapier$20
Cursor$20
Vercel$20
Airtable$20
Webflow$14
Make$9
n8nVariesFrameroptional$10
StripeoptionalUsage-basedPostHogoptionalFree
Plausible Analyticsoptional$9
Google Search ConsoleoptionalFree
ChatGPToptional$20Claudeoptional$20
Perplexityoptional$20
The target budget is the recommended starting envelope. The list price adds up each core tool's first paid plan, excluding 1 tool without a fixed price. Optional tools are not included.
What to watch out for
Stacking creative tools without connecting brief, production, approval, delivery, and billing.
Dormant subscriptions
A premium creative tool should map to something you invoice.
Scattered assets
Without organisation, references and source files become impossible to maintain.
AI without intent
AI should speed up a direction, not replace professional judgement.
Recurring volume
The stack pays for itself once the deliverable comes round several times a month.
Several stakeholders
Add collaboration, feedback or a DAM once feedback and assets start scattering.
Questions to ask yourself
Is the final deliverable clearly tied back to the original brief?
If not, the project has no single source of truth.
Does each tool play a distinct role in the chain?
If two tools do the same job, one of them should be conditional.
Does the client know what to approve, and where?
If not, feedback will generate avoidable back and forth.