The point where work gets scattered
Client work becomes hard to inspect when a proposal total is treated as a payment request, a payment is treated as agreement to new terms, or a revised file silently replaces the version a client reviewed.
Use the proposal to make the work understandable
A useful proposal connects the client’s problem to a concrete approach: deliverables, responsibilities, exclusions, timing and price. For a website, ‘five pages’ is incomplete without the actual page list, content owner, review rounds and launch responsibilities. Unknowns should be visible so the client knows what still needs a decision.
Sample proposal wording: ‘This phase covers Home, Services, About, Work and Contact. You supply approved copy and images. Two consolidated design review rounds are included. Hosting migration and new photography are excluded. The proposed total is $3,000, subject to the scope review below.’ This is an offer to inspect, not evidence of acceptance.
Use the agreement to review the working terms
An agreement can address the accepted scope, responsibilities, payment schedule, handling of changes, review process, delivery and other terms appropriate to the engagement. Identify the parties and the exact version under review. Check that attachments and linked scope descriptions are the ones the parties actually intend to use.
Sample review request: ‘Please review Website Agreement v2 dated 12 March, including Scope A. The changes from v1 are the photography exclusion and the launch date. Please raise questions before confirming your decision.’ This is an operational review pattern, not a claim about legal effect. Required terms and formalities depend on the situation.
- Name the exact document and its attachments.
- Resolve inconsistent prices, dates or deliverables.
- Use appropriate qualified help for legal terms you do not understand.
Use the invoice to explain the requested payment
An invoice should identify the supplier, customer, work or agreed milestone, amount, currency, reference and relevant payment timing. Include the business and tax details required for your circumstances. For the website example, the first invoice might request the agreed $900 initial payment and state that it is part of the $3,000 project total.
Sample line: ‘Website project W-104, initial payment under the accepted 12 March scope: $900 USD. Remaining project balance before later agreed changes: $2,100.’ Do not describe the invoice as paid until the actual payment is confirmed. If it is a request for an upcoming milestone, label that milestone accurately.
Choose the right next action
If the client is comparing approaches, improve the proposal. If both sides want to proceed but terms remain open, review the agreement. If the relevant payment is due under the agreed arrangement, prepare the invoice or payment request. A scope increase may need a revised proposal or agreement before a different amount is requested.
Maintain a short reference chain: project W-104, accepted scope dated 12 March, agreement v2, invoice W-104-01 and the eventual payment result. The references make the story inspectable. They do not collapse the decisions into one: document review, personal consent and payment approval each have their own purpose.
Keep the context with the conversation
Messages can help you prepare wording from the project context you select. Keep the complete proposal and agreement in your current document process, with their reviewed versions identifiable. Use the existing payment experience when there is an agreed amount to request or pay, then inspect its confirmed result and return to the conversation with the context connected.
Understand your Twin · See Business access and metered AI usage