A two-week website starts with a clear brief

A small business website can be a fairly straightforward build. The harder part is often getting everything around the build ready at the same time.

The copy needs an owner. Someone has to choose the photographs. Access to the domain or existing website needs to be available. And there needs to be a person who can review the work and make decisions.

That's the context behind a promise like “a website in two weeks.” It can be a sensible target for an agreed scope, provided everyone understands what the timeline includes.

When I discuss a website project, I want to understand what has to work on launch day. A service website with a contact form is a different project from one that takes payments, manages appointments and sends information to a CRM.

Even the number of pages only tells part of the story. Five pages of supplied content and approved designs require a different amount of work from five pages that still need research, copy, structure and design direction.

That is why a useful brief starts with the visitor and the action they need to take. For a contractor, that might mean exploring the right service and sending enough project details for an estimate. For a salon, it might mean understanding the services, finding the location and reaching the booking step.

From there, we can decide what belongs in the first release. Which pages are essential? What information needs to be collected? Which integrations are required immediately? What can sensibly wait?

Content needs the same attention. If a client is supplying the copy and photographs, those should have an agreed delivery date. If I'm helping prepare them, that work should be included in the scope. Leaving that responsibility unclear makes the launch date difficult to rely on.

Integrations also bring their own dependencies. A booking provider may need an account configured. A payment service may require verification. A CRM connection may need access and a decision about which fields go where. These details belong in the plan before the project is described as ready to start.

Then there is feedback. A clear approval owner helps keep decisions consistent. Useful review points might be the page structure, the design direction, a working preview and the final launch checks. The purpose is to give the client a chance to respond while changes are still manageable.

Finally, “finished” needs a shared meaning. For a straightforward service website, that could include readable layouts, correct content, working links, checked forms and a successful handover. If tracking or automation is included, its behavior should be checked too. A button looking right does not tell us whether the information reached the intended destination.

This is how I approach planning website work through Hitudios: establish the scope, make the dependencies visible and agree on what will be checked before launch.

For suitable projects, delivery within weeks is a practical aim. The brief, content and approvals are part of making that possible.

If you're planning a business website or looking for an agency delivery partner, share the work you need and the date you're aiming for. You can explore my work at https://www.hiteshmahay.com/.