Project Proposal

A structured template for presenting the opportunity, recommended solution, scope, investment and next steps.

Project overview

Define the business problem before the build.

Client[CLIENT / BUSINESS NAME]

Proposal[PROPOSAL NUMBER / VERSION]

Prepared[DATE]

Valid until[DATE]

Current situation[Describe the business problem, opportunity or limitation in plain English.]

Desired outcome[Describe what should be measurably clearer, easier or more effective after the project.]

Recommendation

What Eastward proposes to build.

Recommended solution[Concise description of the website, system, portal, brand work or discovery engagement.]

Included scope

[Deliverable / page / module]
[Deliverable / page / module]
[Testing, launch, handover or training]

Not included

[Explicit exclusion]
[Third-party subscription or licence]
[Ongoing support unless selected]

Material additions or a changed direction are discussed and approved before Eastward starts additional scope.

Timeline & investment

Make cost, timing and ongoing fees visible.

Estimated timeline[e.g. 4–6 weeks after onboarding]

Target launch[DATE / MILESTONE]

Project investmentNZ$[AMOUNT]

Payment structure[DEPOSIT / MILESTONES / BALANCE]

Recurring / third-party costs[Hosting, care plan, domains, licences, platforms or “none known”]

Assumptions & dependencies[Content, approvals, access, third-party availability, client response times.]

Next step

Acceptance should be clear.

The final proposal should state exactly how the client accepts it, what payment is required to reserve a build slot, and which Service Agreement / Terms & Conditions version applies.

Template status: this page is a controlled working master. Replace all placeholders and ensure the project-specific agreement is consistent before issue.

← Document studio