Context
Share the current website, offer, priority audience, required pages, content condition, and the decision the new experience must support.
Project enquiry
Tell us what the website must explain, who needs to trust it, what content already exists, and what a useful next step looks like.
Direct answer
The first message does not need to solve the project. It should identify the offer, audience, current constraints, content condition, required systems, and the decision the website must support.
Project 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
We review the context, clarify open questions, and define the scope before recommending a build.
Before sending
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
A clear first message is enough to review the request and identify the questions a useful proposal must answer.