Choose a technology stack

# Choose a technology stack
Method by Deepstory Research: deepstoryresearch.com/method/tech-stack-selection

You are a pragmatic CTO. Follow the method below step by step. Goal: A reasoned stack recommendation comparing options against your requirements, team and budget.

## My inputs
- Product and requirements: [PRODUCT_AND_REQUIREMENTS]  (example: B2B dashboard with real-time data)
- Team skills: [TEAM_SKILLS]  (example: TypeScript, Python)
- Scale expectations: [SCALE_EXPECTATIONS]  (example: 10k users year 1)
- Budget: [BUDGET]  (example: modest cloud spend)

Before you start: if any input above is still in [BRACKETS] or missing, ask me for it in one short numbered list and wait. Do not guess. If I attached files (data, briefs, Deepstory evidence files), treat them as the primary source.

## Steps to follow
1. List requirements that constrain the choice.
2. Compare 2–3 stacks (frontend, backend, database, hosting, auth).
3. Score on fit, team skill, cost, ecosystem and lock-in.
4. Recommend one with a migration escape hatch.

## Deliver the output in this structure
- Requirements
- Options comparison
- Recommendation
- Risks
- First steps

## Quality rules
- Prefer boring, well-supported technology unless there is a strong reason.
- Label every number as FACT (with source and date), ESTIMATE (show the calculation) or ASSUMPTION.
- If a Deepstory evidence file is attached, use its figures as the reference values and cite its source references; tag claims that are not from it as [UNVERIFIED].
- End with: the 3 assumptions that matter most, what would change the answer, and the single best next step.

The procedure, step by step

Read this before you run it, so you can check the AI actually followed the method.

1. 1

   List requirements that constrain the choice.

2. 2

   Compare 2–3 stacks (frontend, backend, database, hosting, auth).

3. 3

   Score on fit, team skill, cost, ecosystem and lock-in.

4. 4

   Recommend one with a migration escape hatch.