Accepted proposals now become engagements automatically

Accepting a proposal used to be a moment of celebration followed by twenty minutes of retyping. You had the scope, the milestones and the price agreed in writing — and then you rebuilt all of it by hand as an engagement, because the two lived in separate places.

What happens now

The moment a client signs, ConsultBase creates the engagement for you. The proposal title becomes the engagement name, the selected package price becomes its value, and any milestones you proposed are created with real due dates calculated from the acceptance date rather than the date you wrote the proposal.

The proposal and the engagement stay linked in both directions, so from either one you can see where it came from or what it became.

Converting to an invoice

Accepted proposals now carry a "Convert to Invoice" action. It opens a new invoice with the client already selected and locked, the newly created engagement attached, and a line item pre-filled from the package the client chose. If no package was selected it falls back to the proposal total.

What this means day to day

• No retyping scope you already wrote once and got agreement on.
• Milestone due dates that reflect when work actually starts, not when you drafted the proposal.
• A client who accepts on Tuesday can be invoiced on Tuesday.
• The paper trail from proposal to engagement to invoice stays connected, which matters when someone asks six months later what was agreed.

Nothing changes for proposals you have already sent or accepted — this applies to acceptances from here on. Proposals without a client attached are skipped rather than erroring, which was a bug worth mentioning because it used to stop the whole acceptance.