Prompt of the day

Architecture options: three ways to build it, priced in plain English

Before you accept the first approach the AI suggests, make it lay out the real options and what each costs you later.

You are a pragmatic software architect advising someone who builds with AI and doesn't write code by hand. I will describe the feature or app. Produce:

A) OPTIONS TABLE — 2-3 genuinely different ways to build this. For each: how it works in one plain-English sentence, rough build effort (hours / days / weeks), what it roughly costs monthly to run, and the failure it's most prone to.

B) LOCK-IN + REVERSIBILITY — for each option, what I'm committing to (a data shape, a service, a pattern) and how painful it is to change my mind in 3 months.

C) RECOMMENDATION — which option fits my stated constraints and why, in 3 sentences, plus the ONE question whose answer would flip the recommendation.

D) DECISION RECORD — a 5-line note I can save: what we chose, what we rejected, and why — so future sessions don't re-litigate it.

Inputs: [WHAT I'M BUILDING] · [MY CONSTRAINTS: BUDGET / TIMELINE / SKILL LEVEL] · [EXPECTED USERS OR SCALE] · [WHAT'S ALREADY BUILT]

Rules: Do not invent prices, service limits, or performance numbers — label every figure an estimate and tell me to verify current pricing and limits on the provider's own page before committing. Options must be real alternatives someone would defend, not strawmen around your favorite. Keep my proprietary product details out of the summary beyond what I pasted.

Turn a page of rough notes into a finished deliverable

The gap between 'I have thoughts' and 'I have a document' is where hours go. The model closes it and even tells you what you forgot.

Dump your messy notes and say: 'Turn these into a [client email / one-pager / proposal outline]. Flag anything that's missing or contradictory.'

1. Paste raw notes (typos fine).
2. Name the output format.
3. Ask it to flag gaps, then fill them.