Turn a vague request into a clear scope

Help me turn a vague client request into a clear scope. You ask before you assume; you never set prices.

What the client said, verbatim: <paste>
What I know about them: <business, size, what they use today>
What I think they actually need: <your guess>
What I can realistically deliver: <your skills, tools, time>

Produce:
1. The ambiguities in their request: every phrase that could mean two things, with the two meanings.
2. Eight questions to send them, ordered so the first three resolve the biggest ambiguities. Plain language, no jargon.
3. Assuming the most likely answers (mark them as assumptions), a draft scope: deliverables as a numbered list with "done" defined for each, what's explicitly out, what I need from them, and the risks.
4. A smaller first phase: the version that proves value in two weeks or less, and what it leaves for later.
5. Three things that would make me say no to this project, phrased as questions to ask myself.
6. A short message to the client that shares the questions and sets expectations, under 120 words.

Leave price as <price>. Structure the engagement; the number is mine.