Include the current website, the main service or offer, the pages you expect, what is not working today, any fixed platform requirements, and the business decision the new website should make easier.
Project enquiry
Start with the business context, not a vague feature list.
Tell us what the website must explain, who needs to trust it, what content already exists, and what a useful next step looks like.
Project brief
Use these prompts to prepare a useful website brief.
Review the prompts below, then use the protected project form when it is available or email the same details to hello@simpleweb.in.What happens next
What happens after you share the brief.
We review the context, clarify open questions, and define the scope before recommending a build.Context
Share the current website, offer, priority audience, required pages, content condition, and the decision the new experience must support.
Output: Useful project contextReview
We examine the request for scope, dependencies, migration risk, CMS needs, integrations, and any questions that must be settled first.
Output: Clarification listProposal
The proposal defines the objective, inclusions, responsibilities, review stages, exclusions, and the recommended launch scope.
Output: Written project scopeDecision
Once scope, commercial terms, tools, and timing are approved, the project can move into the brief and delivery workflow.
Output: Approved next step
Before sending
Questions before the first conversation.
No. It is useful to know what content exists, who owns it, and whether it can be reused. Strategy, hierarchy, editing, migration, and writing support can then be separated clearly in the scope.
A useful proposal needs enough context to define pages, content, CMS, integrations, search requirements, and launch responsibilities. The pricing page provides planning ranges while the proposal records the final assumptions.
Use the protected project form on an approved Simpleweb deployment, or email the same context directly to hello@simpleweb.in.
Email route