Blog · · 7 min read

Ask your AI for the comparison as a table

#The situation

You run a small physiotherapy clinic and you need a new website. You asked around and got three quotes: a small agency at 6,800 euros, a freelance designer at 3,900, and a bigger agency at 11,500. Each one is written differently, promises different things and leaves out different things.

So you paste all three into an AI assistant and ask which is the better deal. What comes back is five tidy paragraphs. The first agency "offers a solid WordPress build with a reasonable timeline". The freelancer "is the most budget-friendly and flexible". The big agency "provides the most complete package". Each sentence sounds fair. None of them puts the three quotes side by side, and you still can't see the one thing you need to know: which of them meets your conditions.

Or you ask for a table, and it looks fine in the chat. Then you copy it into an email or a note, and it turns into rows of pipes and dashes.

A comparison is a table. Ask for it as one, ask for the gaps to be marked instead of guessed, and keep it as a file, because you'll be back to it when the answers to your questions arrive.

#Ask the AI

Paste your options first (the quotes, the product pages, the offers), say what matters to you, then add this. It works in ChatGPT, Claude, Gemini, or an agent that can write files directly, and for any choice between a few options: suppliers, tools, laptops, job offers, venues.

Help me compare these options. Write the comparison as a file I can keep and
come back to.

Name it: decision-<topic-slug>-<today's date YYYY-MM-DD>.md

The file:
- Frontmatter: title, date, decision (the question in one line), options
  (their names), status: open.
- A # heading, then "## Recommendation": which option fits what I told you,
  in two or three sentences, inside a > [!important] callout. If it depends
  on something I haven't told you, say what, instead of picking.
- "## Comparison": one table, with the options as columns and the criteria
  as rows. Start with what I said matters, then cost up front and over the
  first year, then anything else that really separates them. Put a number or
  a short fact in each cell, never a judgement word like "good" or
  "flexible".
- If an option doesn't say something, write "not stated" in that cell.
  Never fill a gap with a guess.
- "## How the numbers were worked out": one line for each cell you had to
  calculate, showing the sum.
- "## What would change the answer": two or three things that, if they
  turned out differently, would change the recommendation.
- "## Ask before deciding": a checklist (- [ ]) of questions to send each
  option, one for every "not stated" or doubt in the table.

Rules: use only what's in my message. Write money with a currency code or
symbol. Keep the table short enough to read on one screen and move detail
into the sections below it. No advice beyond the recommendation.

Reply with the filename only, then the file in one code block fenced with
four backticks.

Four lines do most of the work.

"Never a judgement word like good or flexible." This is the line that turns paragraphs into a comparison. "Flexible" can't be checked; "3 rounds of revisions" can. With numbers and short facts in every cell, you read across a row and see the difference yourself.

"If an option doesn't say something, write not stated." Quotes are written to sound complete. They're not. Without this rule an assistant fills the silence with what's likely, and a likely answer is a guess. With it, the gaps show up in the table, where they belong.

"Show the sum." A first-year cost is a calculation: the price plus twelve months of hosting. One line per sum means you can redo it, and spot it if the assistant counted something twice.

"A checklist of questions, one for every gap." This is what you actually do next: send each option its questions. The file writes them for you.

#What comes back

We tried it in a fresh chat. The clinic, the conditions and the quotes are made up, but here they are exactly as we pasted them before the prompt:

I run a small physiotherapy clinic (two physios, one receptionist) and I need a new website. What matters to me: launch before 1 March, about 5,000 EUR to spend up front, my receptionist must be able to change opening hours and prices herself, and Spanish + English would be nice but isn't essential. We already pay for an online booking system and want to keep it.

Studio Norte (small agency): WordPress, 8 pages, embeds your booking system, 8 weeks, two rounds of design revisions, 6,800 EUR fixed (40% / 40% / 20%). Hosting not included, about 25 EUR/month. Optional care plan 90 EUR/month. You supply text and photos. One-hour training at handover.

Marta Ruiz (freelance designer): Webflow, 6 pages, booking system embedded, 5 weeks, three rounds of revisions, writes the home and services copy. 3,900 EUR (50% / 50%). Webflow plan paid by you, around 23 EUR/month. You can edit text, prices and hours yourself; a short how-to video.

Pixel & Oak (agency): custom design, 10 pages, Spanish and English, their own booking module replacing your current tool, 12 weeks, unlimited design revisions, basic SEO and a half-day photo shoot. 11,500 EUR in three monthly payments. Hosting and maintenance 140 EUR/month, 12-month minimum.

(The quotes we pasted were a little longer, written as each studio would write them; this is the same content, shortened.) The assistant replied with the filename, decision-physio-clinic-website-2026-11-15.md, and this file, shown here in full.

---
title: Physiotherapy clinic website, three quotes compared
date: 2026-11-15
decision: Which of the three website quotes should the clinic accept?
options:
  - Studio Norte
  - Marta Ruiz
  - Pixel & Oak
status: open
---

# Physiotherapy clinic website: which quote?

## Recommendation

> [!important]
> Marta Ruiz fits what you told me best. She is the only quote under your 5,000 EUR up-front budget (3,900 EUR), her 5-week timeline leaves the most room before 1 March, and she states that your receptionist can edit text, prices and hours herself. She keeps your booking system. The open point is Spanish + English, which her quote does not mention, so confirm that before you sign (see "Ask before deciding").

## Comparison

| Criterion | Studio Norte | Marta Ruiz | Pixel & Oak |
|---|---|---|---|
| Time to build | 8 weeks | 5 weeks | 12 weeks |
| Latest kick-off to launch by 1 Mar 2027 | 4 Jan 2027 | 25 Jan 2027 | 7 Dec 2026 |
| Build price | 6,800 EUR | 3,900 EUR | 11,500 EUR |
| Build price vs 5,000 EUR budget | +1,800 EUR | -1,100 EUR | +6,500 EUR |
| Receptionist edits hours and prices herself | not stated (1-hour training; care plan covers "small edits") | Yes, in the Webflow editor, plus a how-to video | not stated |
| Spanish + English | not stated | not stated | Yes |
| Keeps your booking system | Yes, embedded | Yes, embedded | No, replaced by their module |
| Running cost per month | 25 EUR hosting (+90 EUR optional care plan) | 23 EUR Webflow plan | 140 EUR hosting and maintenance, 12-month minimum |
| First-year total | 7,100 EUR (8,180 EUR with care plan) | 4,176 EUR | 13,180 EUR |
| Pages | 8 | 6 | 10 |
| Design revisions | 2 rounds | 3 rounds | Unlimited in design phase |
| Who writes the text | You supply text and photos | Marta writes home and services pages | not stated |
| Payment schedule | 40% / 40% / 20% (start / design sign-off / launch) | 50% / 50% (start / launch) | 3 monthly payments |
| Also included | Nothing else stated | Nothing else stated | Basic SEO, half-day photo shoot |

## How the numbers were worked out

- Latest kick-off, Studio Norte: 1 Mar 2027 minus 8 weeks (56 days) = 4 Jan 2027.
- Latest kick-off, Marta Ruiz: 1 Mar 2027 minus 5 weeks (35 days) = 25 Jan 2027.
- Latest kick-off, Pixel & Oak: 1 Mar 2027 minus 12 weeks (84 days) = 7 Dec 2026.
- Build price vs budget, Studio Norte: 6,800 - 5,000 = +1,800 EUR.
- Build price vs budget, Marta Ruiz: 3,900 - 5,000 = -1,100 EUR (1,100 EUR left under budget).
- Build price vs budget, Pixel & Oak: 11,500 - 5,000 = +6,500 EUR.
- First year, Studio Norte: 6,800 + (12 x 25) = 6,800 + 300 = 7,100 EUR.
- First year, Studio Norte with care plan: 7,100 + (12 x 90) = 7,100 + 1,080 = 8,180 EUR.
- First year, Marta Ruiz: 3,900 + (12 x 23) = 3,900 + 276 = 4,176 EUR ("around 23 EUR/month" in her quote, so approximate).
- First year, Pixel & Oak: 11,500 + (12 x 140) = 11,500 + 1,680 = 13,180 EUR.
- All first-year totals assume 12 months of running costs and ignore any months before launch, because the quotes do not say when hosting or plan fees start.
- The latest kick-off dates assume the studio can start on that date. None of the quotes states availability.

## What would change the answer

1. **Spanish + English becomes a must-have.** If Marta cannot or will not do both languages, Pixel & Oak is the only quote that states them, but at 11,500 EUR it is 6,500 EUR over budget and replaces your booking system.
2. **Your budget can stretch to about 6,800 EUR and Studio Norte confirms your receptionist can edit hours and prices herself.** Then Studio Norte (2 design revision rounds, 8 pages, you supply the text) becomes a real alternative.
3. **The booking system turns out to be a problem.** If your current tool has costs or limits you did not mention, Pixel & Oak's built-in module changes the comparison. Today you want to keep it, so it counts against them.

## Ask before deciding

**Studio Norte**
- [ ] Can my receptionist change opening hours and prices herself, without the care plan? What does the 1-hour training cover?
- [ ] Can the site be in Spanish and English? What would it add to the price and timeline?
- [ ] Is the 8-week timeline from kick-off, and when could you start?
- [ ] Is anything else included beyond the 8 pages (SEO setup, photos)?
- [ ] Which managed host do you recommend, and does the 25 EUR/month start at launch?

**Marta Ruiz**
- [ ] Can the site be in Spanish and English? What would it add to the 3,900 EUR and the 5 weeks?
- [ ] Is the Webflow plan exactly 23 EUR/month for this site, and does it start at kick-off or at launch?
- [ ] Is SEO setup included, or not?
- [ ] Do you write the text for the other pages, or do I supply them? When could you start?
- [ ] Who can I contact for edits or problems after launch, and is that covered in the price?

**Pixel & Oak**
- [ ] Can my receptionist change opening hours and prices herself? How?
- [ ] Who writes the text for the 10 pages?
- [ ] Can I keep my current booking system instead of your module? What would that change in the price?
- [ ] What happens to my existing bookings and data when you replace the current tool?
- [ ] What does the 140 EUR/month cover, when does it start, and can I leave after the 12-month minimum?
- [ ] What are the dates of the three monthly payments, and when could you start?

We checked every sum and every date by hand, and every "not stated" against the quotes. They're right.

It's a better answer than the paragraphs, and not because the recommendation is surprising. It's better because you can see why it holds, and where it could still fall over.

Your conditions come first. The top half of the table is the things you said matter: launch date, budget, editing it yourself, two languages, keeping the booking system. Reading down, you can already see that only one quote states all of your must-haves, and that none of them confirms everything you asked for.

The gaps are visible. Studio Norte never says whether your receptionist can change the hours herself. In the paragraphs, "a solid WordPress build" quietly covered that. In the table it says not stated, and the first question on Studio Norte's list asks it.

The first-year row changes the picture. By build price alone, Pixel & Oak costs about three times Marta's quote. Over the first year, with its 140 euros a month and a 12-month minimum, it's 13,180 against 4,176. That number was in none of the quotes; it's a sum, and the sum is on the page.

It names the condition that would flip it. Two languages are "nice to have" today. If that changes, the recommendation changes, and the file says so before you sign anything.

One thing to change for your own use: the latest kick-off row assumes each studio could start the day you sign. Ask each one when they could actually start, and put the answer in the table.

#Save it as a file

Save it as decision-physio-clinic-website-2026-11-15.md in a decisions folder, and connect that folder in MD Flow (what browsing a folder of Markdown looks like).

#Why that matters next week

The table reads as a table. Open the file in a plain text editor and the comparison is fourteen rows of pipes and dashes, with the long cells pushing everything out of line. In MD Flow it's a real table again, as it was in the chat: the frontmatter becomes a header with the decision at the top, the recommendation is a coloured callout, and the questions are a checklist. If the table is wide, it can use more of the pane in Wide or Full mode. On a Mac, pressing Space on the file in Finder shows the same rendered preview without opening anything.

The answers go into the same file. Send each studio its questions. Say Marta replies that a second language adds 900 euros and a week: paste her answer back to the assistant with "update the file", or edit the cell yourself and tick the box in your editor. MD Flow's preview follows each save, so the new row, and maybe a new recommendation, is on screen the moment the file changes.

It survives being sent. Your business partner wasn't in the chat and doesn't read Markdown. With Pro, export the file as a PDF: the table, the callout and the checklist come through as they look in the app.

The folder becomes a record of what you chose and why. Next year, when the website needs work or a new quote arrives, you'll want to know what you compared, what you asked and what you assumed. Each decision has its date in its name. Search by filename is free in MD Flow; with Pro, search also reaches inside the files, so status: open finds every decision you haven't closed yet.

The chat gave you an opinion. The file gives you the comparison, with its gaps showing, which is what you'll need when the answers come back.