Choose a tech stack for your project

This prompt acts as a practical CTO for a small team. It recommends a frontend, backend, database, auth, hosting and payments setup, prefers tools your team already knows and flags choices that are hard to undo.

text-code-choose-tech-stack — claude — 83 words

Act as a pragmatic CTO advising a small team.

Project: [WHAT YOU ARE BUILDING]
Team: [e.g. 2 developers who know JavaScript and a little Python]
Needs: [e.g. mobile-friendly web app, payments, 5k users in year one]
Budget: [e.g. under ₹5,000 a month for hosting]

Recommend a stack for frontend, backend, database, auth, hosting and payments. For each, give one alternative and the reason to pick it. Prefer boring, well-documented tools my team already knows. Flag anything that will be hard to change later.

Edit in the builder Copy & open Claude ↗Copy & open ChatGPT ↗Copy & open Gemini ↗

The best stack is usually the one your team already knows. Say honestly what everyone is comfortable with.

Get a better result

What you will get

A recommended stack for frontend, backend, database, auth, hosting and payments, each with one alternative and a reason, favouring well-known tools your team can use, with hard-to-change choices flagged.

Common mistake

The suggestions are fashionable but new to your team.

Fix: State what each person knows and say “prefer these unless there is a strong reason”. Learning time is a real cost.

Also watch for

Hosting costs are missing or too optimistic. Give your monthly budget, and ask for a rough cost at launch and at ten times the users. Check the providers’ current prices.
Every choice is presented as equal. Ask for “the three decisions that would be costly to reverse and what to do to keep them flexible”.

Try a variation: add an exit plan

Ask for “how I would move away from each choice later, and what data I should be able to export from day one”. Lock-in is easier to avoid at the start.

Still not right? Reply with this

Cut the recommendation to the fewest tools that work. Give me one backend language, one database and one host, with a reason for each.