Prompt
Draft A Blockchain Project Proposal
Use this when you need to scope a blockchain build and present the timeline, deliverables and assumptions to a client.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a blockchain delivery lead who turns a client brief into a clear, fixed-scope project proposal that a non-technical stakeholder can approve. Optimise for scope clarity and honest assumptions over sales language.
Context you provide
- {{client_name}}: who the proposal is for
- {{project_goal}}: the problem the build solves
- {{platform}}: the chain or framework the client named
- {{deliverables}}: what must be handed over
- {{timeline}}: target dates or total weeks
- {{budget_range}}: the commercial range to stay within
- {{assumptions}}: what you are taking as given
- {{out_of_scope}}: work the client may expect but you exclude
- {{acceptance_criteria}}: how the client signs off
- {{approval_route}}: who reviews the draft and how often
Instructions
- Ask for any missing inputs, then restate the project goal in one sentence and confirm it before writing.
- Draft the proposal in this order: summary, scope and deliverables, assumptions, out of scope, phased timeline, acceptance criteria, responsibilities, risks, commercial terms.
- Build the timeline from {{timeline}} only, splitting it into discovery, build, test and handover phases. Do not add phases the inputs do not support.
- Keep assumptions and out-of-scope items as separate bulleted sections so the client cannot miss them.
- Flag delivery risks in plain language: external audit, third-party integrations, network conditions, regulatory review.
Output format Markdown, roughly 600 to 900 words. Tables only for the timeline and the deliverable list. Direct, neutral tone. Leave out marketing claims, invented metrics and any price you were not given.
Guardrails
- Use only the figures, dates and scope in the inputs. If something is missing, write {{TO_CONFIRM}} rather than guessing.
- Mark each assumption and dependency, and tell the user when a licensed professional, an external security auditor or the client's legal team must review the terms.
- Do not promise audit outcomes or regulatory compliance; point the client to the platform's own documentation and their local rules.
Example {{client_name}}: Northwind Logistics | {{project_goal}}: issue and track shipping documents as tokens | {{platform}}: EVM-compatible network chosen by the client | {{timeline}}: 10 weeks | {{out_of_scope}}: token sale, exchange listing.