How to ask

Reply to the proposal email. That's it. Don't accept the proposal in the portal first; the acceptance is final, and we can't undo it cleanly to swap in a new version.

Write whatever you'd write to a colleague. There's no template to follow. If a phone call is faster than typing, call us — the contact details are in the email signature, or on How to reach us.

Common changes we see

You can ask for any of these without it being awkward:

• Scope adjustments. Drop a line item, add one, swap one for something different.
• Cost questions. Why is X priced the way it is, can we bundle Y, is there a cheaper alternative for Z.
• Payment terms. Spreading payments over more instalments, shifting the start date, asking about discounts for upfront payment.
• Timing. Pulling delivery forward, pushing it back, locking it to a specific date (a launch event, a fiscal deadline).
• Wording in the terms. If a clause doesn't fit how you work, flag it — we'd rather rewrite than have you sign something you're uncomfortable with.

What happens next

For most questions, we reply with a clarification on the same email thread and you carry on with the original proposal.

For changes that affect what's in the proposal — scope, prices, terms — we issue a revised proposal. You'll get a new email with a new link and a new code. The old proposal becomes obsolete; ignore it.

"We're waiting for your confirmation"

You may see a line in our email along the lines of "we'll wait for your confirmation before moving to acceptance." That just means: tell us by email that the proposal is good before you click the accept button in the portal. It gives both sides a chance to catch any last-minute mismatch.

A quick "yes, looks good, proceeding to accept" reply is plenty.

When you should pause

If at any point you're unsure whether the proposal still matches what you actually want, don't accept it. Accepting is the trigger for invoicing and project kickoff — it's harder to walk back than to send one more email asking us to revise.