Skip to article
← Back to the notebook
Guides / 01

Before you ask for a website, prepare these five things.

You do not need a twenty-page document. You do need a clear problem, a list of what is ready and an idea of what can wait.

In this article

Start with what should happen

“I need a modern website” leaves too many decisions open. “I want people to understand my services and contact me on WhatsApp” gives the project a useful starting point.

Choose a primary action: enquiries, bookings, purchases or explaining an offer. A first release can have several sections without having to solve every part of your business.

Gather the content you already have

Content is not something to add at the very end. Service descriptions, available photographs and customer questions shape the page. Knowing what is missing helps make an estimate realistic.

  • Available logo and brand files.
  • Clear descriptions of services or products.
  • Images you have permission to use and current contact details.
  • Common customer questions and examples of your work.

Separate references from a finished design

A website you like can explain a layout, tone or interaction. It is not a substitute for an implementation-ready design, and it is not an instruction to copy it.

If you already have Figma files, include mobile screens, form states and components. If you need design too, say so. Luby can scope and quote design separately from development.

Separate launch requirements from the next release

Make two lists: what you cannot launch without, and what can follow later. Booking calendars, payments, languages and admin tools all need definition and testing.

For every feature, explain who uses it, what information they need and what happens next. That is more useful for estimating than a list of technologies.

Agree on budget, timing and approval

Share a budget range and explain whether the launch date is tied to a real event. This makes it possible to adjust scope before committing to delivery.

Decide who gathers feedback and who gives final approval. Put deliverables, included revisions, payments, access and maintenance in writing. Your domain and service accounts should remain under your control.

A brief you can copy

“My business offers __ to __. The website should help people __. I already have __ and still need __. To launch, I need __; later we can add __. My budget range is __ and my target date is __. The person approving the work is __.”

You do not need every technical term to start the conversation. A useful brief explains the problem and makes the remaining decisions visible.

Let’s bring it back to your project.

Tell us what you need to build