Before quoting a service request on X, write down what the post actually specifies, then ask for the few details that would change the work or price. Give a conditional range only if you can name what it includes. If a major cost driver is still unknown, request details instead; if a firm constraint makes the job impossible, decline. A short post can start a scope conversation, but it is rarely a complete brief.
Separate the request from your assumptions
Start a short scope note with two headings: “Stated” and “Unknown.” Under “Stated,” copy the requested outcome and any explicit deadline, budget, platform or deliverable. Under “Unknown,” put everything you would otherwise have to assume to estimate the job. “Need a landing page soon” does not tell you whether the client needs design, copy, implementation or all three; “soon” is not a delivery date.
Check the current thread before spending time on an estimate. A later reply may supply the missing brief or show that the person has already hired someone. Treat a public request as an opening to clarify the work, not permission to present a price for an imagined version of it.
Ask for the details that change the work
Your intake should be short enough for someone to answer, but specific enough to reveal the main cost drivers. You do not need every implementation detail before deciding whether a project is worth discussing. Ask about the fields below, adapting them to the service: an editor might ask for word count and source material, while a developer might ask which system the work must fit into.
- Deliverable and boundary: What exactly should be handed over? How many pages, pieces or workflows are involved? Is implementation included, or only a design or plan?
- Deadline: What date does the work need to be usable, and is there time for the client to provide inputs and review drafts?
- Budget: Is there a target range or a ceiling? Ask to test fit, not to replace your own estimate of the work.
- Inputs and decisions: Who supplies copy, assets and access? Who approves the result, and what requirements—such as accessibility, integrations or stakeholder reviews—might expand the job?
Turn a vague post into a provisional scope
Consider this fictional X post: “Need someone to redo our landing page soon. What would it cost?” A designer can record one fact—someone wants a landing-page redo—and leave price blank. The first useful questions are: Which page? Do you need design only, or copy and implementation too? What date is “soon”? Do you have a budget range? These questions separate potentially different jobs without demanding a full creative brief in public.
Suppose, in this fictional example, the buyer answers: “Our existing product page; one page only. We have final copy and brand assets. We need a design file, not a built page, by June 30. Budget ceiling is $1,500.” The provisional scope note is now: redesign one existing product page; client supplies final copy and assets; deliver a design file by June 30; implementation excluded; ceiling $1,500. Still confirm the file format, expected screen sizes, revision rounds and who can approve work on time. Those details define what “done” means and whether the date is feasible.
If the buyer instead says the page needs new copy, a working build and several stakeholder reviews, do not price it as the design-only version. Rewrite the scope note around those additions and decide whether you can estimate them. For guidance on composing the initial public response, see the separate guide to replying to a product recommendation request on X; the scoping decision here is what information you need before naming a price.
Choose a range, another question or a decline
The next step depends on what your scope note can support. A range communicates a bounded estimate, not a promise to complete any version of the request for that amount. A firm quote should wait until you have agreed on the deliverable, exclusions, timeline and revision or approval assumptions.
| Scope condition | Next action | What to say |
|---|---|---|
| You can define the included work, but some details remain. | Offer a conditional range. | State the range, inclusions, exclusions and what could change it. |
| An unknown could substantially change the work. | Request the deciding detail. | Ask whether that item is included before estimating. |
| A firm budget, deadline or requirement rules out your offer. | Decline the job as stated. | Name the mismatch without suggesting you can meet it. |
Apply that choice to the page request
For the fictional design-only version above, suppose the designer’s own provisional estimate is $1,100–$1,400 USD. They could say: “For one existing page using your final copy and assets, a design file would likely fall around $1,100–$1,400 USD, assuming desktop and mobile layouts and up to two revision rounds. That excludes copywriting and implementation. I’d confirm the file format, approval process and June 30 schedule before quoting firmly.” This is an illustrative seller estimate, not a market price. If the designer cannot meet June 30 or the buyer’s $1,500 ceiling once the real work is clear, the appropriate answer changes to a decline or a smaller scope the buyer actually wants.
If copy or implementation remains unresolved, ask which is required rather than attaching that range to an undefined project. The test is simple: could the buyer tell what work your number buys, and could you tell what would count as a change? If not, keep scoping.
Keep discovery separate from the quote
ReachFast presents public X requests with the post, author, date and buying-intent score, and prepares a suggested reply that opens in the X thread for the seller to decide whether to send. That can bring a relevant request to your attention; you still need to read the live conversation, ask for requirements and make the pricing decision yourself.
Continue the scope conversation when the buyer responds, and let their answer determine the next question or estimate. If they do not respond, leave the thread alone rather than treating silence as a reason to send another pitch. The separate follow-up guide covers those conversation boundaries.
