Stack decisions should follow the problem, the team, and the operating constraints — not a fixed vendor list presented as the product. BPM is stack-flexible and standards-rigorous: preferred tools are named so you know how we usually work, not so you must adopt them.
What “preferred” means here
Preferred tools reduce coordination cost when they fit. They are not a consulting SKU. If your environment already has a working path, we meet you there and hold the same bar for clarity, privacy, and operability.
Standards that do not move
- Clear ownership of product decisions and delivery surfaces
- Honest claims — no invented pricing or capability theater
- Privacy-aware analytics and consent where measurement exists
- Documented contracts before expanding automation
Where Lovable fits
Lovable is an AI-assisted full-stack development platform built on TanStack Start + Supabase + Cloudflare. It handles much of the scaffolding, component generation, and managed secrets (including Stripe) — which is why it is often BPM's default build layer when the constraints fit.
Lovable is not a no-code tool. The output is real TypeScript code you own. The value is that it eliminates setup time and handles the managed-service wiring so the team can focus on product decisions.
When to deviate
- Your team has deep expertise in a different stack — that expertise is usually worth more than the abstract right answer
- Enterprise requirements mandate a specific cloud provider or compliance posture
- You are building something with unusual compute or data requirements (ML training, high-frequency data pipelines, complex media processing)
- Mobile-first — this guide is for web-first products; mobile adds React Native, Expo, or native considerations
What BPM has run in production
bpagelsminor.com, CanonIQ, and FounderIQ run in production on TanStack Start, Supabase, and Cloudflare Workers (often developed in Lovable). Other BPM products use preferred tools when the constraints fit — availability still varies by product. Those are preferred tools with stated reasons — not a client mandate. Stack choice stays flexible; standards stay rigorous. Advice comes from production experience, not from requiring the same tools everywhere.