Generate Website Development Plan

Most website projects fail not because of bad design or bad code, but because they start without a clear plan. The scope expands, decisions get made without a framework, and what was supposed to take six weeks takes six months. A good website development plan does the strategic work upfront: defines what the site must do for the business, who it must convert, what pages and features are actually necessary, and in what sequence to build them. This prompt generates exactly that plan — phase by phase, with priorities and rationale — so you can execute with confidence rather than guesswork.

What It Does

Defines the strategic purpose and conversion goals of your website before touching design or development, so every decision that follows is grounded in business outcomes.
Produces a phased development roadmap — from must-have MVP to future enhancements — so you can launch faster and improve iteratively rather than waiting for perfection.
Delivers a complete specification including page structure, key features, technology recommendations, and timeline estimates appropriate for your team size and budget.

The Prompt

#CONTEXT:
I need to build or redesign a website for my business. I want a structured development plan that tells me exactly what to build, in what order, and why — so I can avoid scope creep, set realistic timelines, and ensure the site actually serves my business goals rather than just looking good. The plan should account for my specific audience, business model, and available resources.

#ROLE:
You are a senior web strategist and project manager who has led website builds for startups, SMBs, and established brands. You understand the difference between a brochure site, a lead generation site, and a sales-driven e-commerce experience — and you know how to scope the right type of project for each business situation. You know how to make hard prioritization decisions and push back on scope that does not serve the stated goal.

#RESPONSE GUIDELINES:
1. Start by defining the primary business goal the website must achieve — lead generation, e-commerce conversion, authority building, or another goal — and let this drive all subsequent decisions.
2. Define the target audience and their decision-making journey on the site: what they need to see, read, or do before they take the desired action.
3. Recommend a page structure with must-have pages for MVP launch and nice-to-have pages for a second phase.
4. Specify the top 3–5 features or functionality the site needs and rank them by priority.
5. Recommend a technology stack appropriate for my technical skill level and budget.
6. Provide a phased timeline with clear deliverables and gates between phases.

#WEBSITE PLANNING CRITERIA:
1. Every page must have a defined purpose and a primary call to action — decorative pages with no conversion goal should be cut or deferred.
2. The MVP launch must be achievable in the timeframe and budget I specify, even if that means deferring features.
3. Technology recommendations must match my technical capacity — do not recommend a custom React build if I need something I can maintain myself.
4. The plan must include at least one measurable success metric per phase so I know whether the site is working.
5. Mobile-first design and page load performance must be treated as non-negotiable requirements, not afterthoughts.

#INFORMATION ABOUT ME:
- My business and what I sell: [BUSINESS — product, service, or combination]
- My primary website goal: [GOAL — e.g., generate leads, sell products, build an audience, establish authority]
- My target audience: [AUDIENCE — who they are and what they need to see before they convert]
- My technical capacity: [SKILLS — e.g., comfortable with no-code tools, can manage WordPress, have a developer available]
- My budget range: [BUDGET — e.g., under $1,000 DIY, $2,000–5,000 with freelancers, $10,000+ with agency]
- My desired launch timeline: [TIMELINE — when do you need the site live]

#RESPONSE FORMAT:
Strategic Goal:
[One sentence defining what the website must achieve for the business]

Target Audience Journey:
[3-step description: what they arrive knowing, what they need to see, what action they take]

MVP Page Structure:
- [Page name]: [Purpose and primary CTA]
- [Page name]: [Purpose and primary CTA]

Phase 2 Pages (post-launch):
- [Page name]: [Why deferred]

Priority Features:
1. [Feature] — [Why essential]
2. [Feature] — [Why essential]
3. [Feature] — [Why deferred or optional]

Recommended Tech Stack:
- CMS/Platform: [recommendation and reason]
- Hosting: [recommendation]
- Key tools: [analytics, forms, email, etc.]

Phased Timeline:
Phase 1 (MVP Launch) — [X weeks]: [Deliverables]
Phase 2 (Optimization) — [X weeks]: [Deliverables]
Phase 3 (Scale) — [ongoing]: [Deliverables]

Success Metrics:
- Phase 1: [Metric and target]
- Phase 2: [Metric and target]

How to Use

Be specific about your primary goal — "get more customers" is too vague. "Generate 20 qualified leads per month for our B2B software product" gives the AI enough to make meaningful prioritization decisions.
Describe your audience's decision-making process, not just who they are. What questions do they need answered before they buy? What objections do they typically have?
Be honest about your technical capacity. A plan built on Webflow makes no sense if you have no web experience and no budget for a designer. The prompt works better when you are realistic.
Use the phased plan to set expectations with stakeholders — MVP on time beats a perfect site three months late in every business context.

Example Input

## Information about me

- My business: B2B consulting firm helping mid-size manufacturing companies reduce waste using lean methodology; we sell 3-day on-site workshops and a 6-month advisory retainer
- My primary goal: Generate qualified leads — decision-makers at manufacturing firms with 50–500 employees book a free 30-minute discovery call
- My target audience: Operations directors and plant managers who know lean exists but feel they lack internal expertise to implement it correctly
- My technical capacity: Comfortable with WordPress, no coding skills
- My budget: $3,000 total including design and setup
- My timeline: Live in 8 weeks

Tips

Design for the conversion, not the company. The homepage should answer the visitor's question — "can you solve my problem?" — within the first five seconds. Company history and team bios come later in the journey.
Write the copy before you design. The copy defines the page structure; the design serves the copy. Designing around placeholder text produces beautiful pages that fail to convert.
Launch ugly, improve fast. A live site with real traffic generating real data is worth ten times more than a beautiful site stuck in revision cycles. You cannot optimize what does not exist yet.
Track three metrics from day one: traffic source, conversion rate, and exit page. These three tell you where people come from, whether the site is working, and where the biggest drop-off point is.
Plan for content from the start. Most websites stall because content — copy, images, case studies — is not ready when development finishes. Build a content schedule alongside the development plan.