The copy challenge
A project is priced, then grows one small request at a time: a second landing page, a third revision round, a deliverable promised on a call. Nobody updates the proposal, so weeks later the team has delivered work the price never covered and the only record sits in separate inboxes. The copy has to make the cost of unrecorded changes concrete before it can present ScopeDeck as the record of what was agreed and everything that changed after.
My role and key writing decisions
I wrote all the landing-page copy for this concept project. No client was involved.
- I built the headline on the client's own phrase. "One more small thing" is what a client says when asking for extra work. The headline gives that phrase the three things the product produces: a price, a deadline and an approval. The worked example later on the page delivers all three (+$900, delivery moves 3 working days, Approve or Decline), so the headline is a promise the page keeps.
- I showed the product as one worked change request instead of describing it. The Solution section sets out the work, an hour estimate, a fee, the effect on delivery and the client's two choices. The request is the same one that opened the Problem section: a second landing page. The reader sees the identical ask twice, first as an unpriced favour and then as a priced change.
- I answered the objections through the details ScopeDeck keeps with each extra request: its fee, deadline impact and client approval. The PDF answer acknowledges that a document can record the original scope and later updates. Both that answer and the DocuSign answer explain how ScopeDeck keeps each request's decision with the project. The answer about annoying the client uses the eight-hour example and treats refusal as useful information before the extra work starts.