Client proposal

Coryntas workspace · Reference data

All companies, people, documents, and results are fictional. No external systems are accessed or updated.

Request: Turn this client brief into a proposal with scope, deliverables, assumptions, and exclusions.

The proposal draft sets out a six-week, $60,000 onboarding portal project with clear deliverables and acceptance gates. It covers intake, status tracking, reporting, two integrations, and a structured handover. The document separates the customer’s requested outcomes from assumptions that still need agreement.

I have made the scope boundary explicit: historical migration, SSO, and third-party subscriptions are excluded. The pricing follows the delivery estimate, with fees tied to the proposed scope. A named customer approver, test access, and timely feedback are prerequisites for the proposed schedule.

The next step is a scope review with the customer, not sending this as a binding offer. Confirm the acceptance examples and cost assumptions before signature. If the customer needs a $40,000 option, the prepared alternative reduces the first phase to intake and one integration over four weeks. It defers status tracking and reporting instead of promising the same delivery for less money.