Contact Simpleweb

EmailCallWhatsApp

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.

01 / PROJECT ENQUIRYPrepare your brief

Direct answer

A useful proposal starts with enough context to make the scope clear.

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.

  • Current URL or starting point
  • Priority offer and audience
  • Pages, content, CMS, and timing

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.

About you
About the project

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.

Step 01

Context

Share the current website, offer, priority audience, required pages, content condition, and the decision the new experience must support.

OUTPUTUseful project context
Step 02

Review

We examine the request for scope, dependencies, migration risk, CMS needs, integrations, and any questions that must be settled first.

OUTPUTClarification list
Step 03

Proposal

The proposal defines the objective, inclusions, responsibilities, review stages, exclusions, and the recommended launch scope.

OUTPUTWritten project scope
Step 04

Decision

Once scope, commercial terms, tools, and timing are approved, the project can move into the brief and delivery workflow.

OUTPUTApproved next step
01 — 04 / SCROLL TO EXPLORE

Before sending

Questions before the first conversation.

What should we include in the first message?

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.

Do we need finished content before making contact?

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.

Will we receive a fixed price immediately?

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.

How should we send the project details?

Use the protected project form on an approved Simpleweb deployment, or email the same context directly to hello@simpleweb.in.

Email route

Send the project context directly by email.

A clear first message is enough to review the request and identify the questions a useful proposal must answer.