Building ScopeClarify: stopping vague enquiries from becoming unpaid work
ScopeClarify started with a pattern I kept seeing in UX, service design and consultancy work: a client sends a short, vague enquiry, but expects a reliable price. The supplier fills the gaps with assumptions, and those assumptions later become extra revisions, delays and lost margin.
I built ScopeClarify to put a controlled clarification step before the quote. It structures what is known, identifies what is missing, drafts the questions, and keeps the human in control before anything is sent. The goal is a clearer, client-confirmed scope before a freelancer, consultant or agency commits to a number.
The first live version is now available for UK and US service businesses, with a free allowance of three intakes. I am looking for blunt feedback from people who regularly price work from incomplete briefs: which missing detail causes the most damage in your projects?
