A web designer needs your real business content to build a credible site: a clear description of what you do and who you serve, your services with scope, your logo and brand material, real photos, accurate contact details, existing copy or brochures, logins to your domain and current site, and decisions on pricing and process. Delays in website projects are almost always content delays, not design delays.

One of the most common sources of friction in a website project is not the design. It is the content. The project that takes three months instead of three weeks is almost always waiting on the business owner to supply material only they can provide. This guide lists what a web designer actually needs from you, what tends to slow projects down, and what to do when you do not yet have everything.

Understanding this in advance protects both sides: the designer can plan around realistic content timelines, and the business owner is not surprised by requests that arrive mid-project.

Why content is usually the bottleneck

Design can be produced by the designer independently. Content cannot. The services, the descriptions, the photos, the contact details, the pricing decisions and the logins all live with the business. No designer can invent them honestly.

When a project stalls, the cause is almost always one of:

  • Content that was assumed to exist but does not.
  • Content that exists but is out of date or inconsistent.
  • Decisions that have not yet been made (which services to feature, how to describe the offer, what the call to action should be).
  • Logins or access that has to be retrieved from a previous provider.

The work that prevents these stalls happens before the project starts, not during it.

The content a web designer needs from you

The list below is what most credible small business website projects require. Not every item applies to every project, but most do.

Business identity and positioning

  • A clear statement of what the business does, in plain language.
  • Who the business serves (the types of customer or client).
  • What makes the business different or credible, stated honestly.
  • The business’s current logo and any brand guidelines.
  • Brand colours, fonts or existing visual material, if they exist.
  • Photographs of the team, premises, work or products.

If you do not have a logo or consistent brand material, say so early. Branding is often a separate scope from the website itself; the IDJoy Branding and Identity package exists for exactly this situation.

Service and offer content

  • A list of the services you want to feature on the site.
  • A short description of each service, including scope.
  • Any services you do not want to feature, or want to phase out.
  • Pricing approach: published prices, “from” prices, or quote-based.
  • Geographic areas served.
  • Typical process or working method, where relevant.

The strongest service pages describe what is included, not just the service name. The designer cannot invent that detail; it has to come from you.

Contact and operational details

  • The trading name exactly as it should appear.
  • The physical address (or a service-area description if you do not have a public premises).
  • Phone number(s), with country code.
  • Email address(es), preferably branded.
  • Operating hours.
  • Google Business Profile details (so the site and profile match).
  • Social profile handles, if relevant.

The article on Google Business Profile and your website explains why consistency between these details and the profile matters for local visibility.

Existing material

  • Current or previous website, if one exists.
  • Brochures, proposals,Capability statements or sales material.
  • Existing copy you want carried over or revised.
  • Testimonials or reviews you have permission to use.
  • Case studies or project examples.
  • Photos from previous work or projects.

Existing material is often the fastest source of accurate content. Even if it is out of date, it gives the designer a starting point that is more honest than placeholder text.

Access and logins

  • Domain registrar login.
  • Current hosting login.
  • Email provider login (if email is part of the project).
  • Analytics and Search Console access, if they exist.
  • Social profile admin access, if relevant.

If you do not have these, that is itself important information. Many projects discover mid-build that the previous provider holds the domain or hosting access, and retrieving it takes weeks. The article on the small business website launch checklist covers the ownership and handover side of this in detail.

Decisions only the business owner can make

  • Which services are the primary focus of the site.
  • The main call to action (enquiry, call, quote, booking).
  • How enquiries should reach the business (email, form, WhatsApp, phone).
  • Whether pricing is published or quote-based.
  • The tone of the site (formal, approachable, technical).

These decisions shape the project more than any design choice. A project that begins without them tends to drift, because each decision deferred becomes a decision made by default.

What tends to slow projects down

Some content is harder to supply than expected. Recognising the common sticking points helps you prepare.

Vague service descriptions

“We do everything” is not a service description. The designer needs each service named and scoped, even briefly. If you are unsure how to describe a service, a working conversation with the designer is faster than leaving it blank.

Photography that does not exist

Many businesses plan to use photos they have not yet taken. Either commission the photography before the project starts, or accept that the launch will use placeholder or stock images until real photos are available. The article on what makes a business website look trustworthy covers why real photography outperforms generic stock.

Decisions deferred

“The site can decide that later” usually means the decision is made under time pressure, by default, and not in the business’s interest. Make the primary decisions before the project starts.

Access held by a previous provider

If a previous designer, developer or IT provider holds your domain or hosting access, retrieving it can take weeks. Start that retrieval the day you decide to build a new site, not the day the new designer needs it.

What to do when you do not yet have the content

It is normal not to have everything ready. The right response is honesty, not delay.

Be explicit about what is missing

Tell the designer at the start what you have, what you are working on, and what you do not yet have. This lets the project plan around the gaps rather than discovering them mid-build.

Prioritise the decisions over the assets

If you cannot supply everything immediately, supply the decisions first (services, call to action, tone, contact path). The designer can shape the structure around the decisions while the assets are gathered.

Use existing material as a starting point

Even out-of-date brochures or a rough services list give the designer something to refine. A blank start is harder than an imperfect one.

Consider copywriting as part of the scope

If writing is not your strength, copywriting can be part of the project rather than a separate burden. The Digital Presence package includes content shaping for exactly this reason. Be honest about where you need help.

The conversation that prevents most delays

Before the project starts, have one honest conversation with the designer about content. Cover:

  • What you have ready now.
  • What you are working on and when it will be ready.
  • What you do not yet have and how you will handle it.
  • Who holds the access you will need.

This single conversation prevents most of the delays that turn three-week projects into three-month projects.

The conclusion

A web designer needs your real business content to build a credible site: business identity and positioning, service descriptions, contact and operational details, existing material, access and logins, and the decisions only the owner can make. Delays in website projects are almost always content delays, not design delays.

Prepare the decisions first, then the assets. Be explicit about what is missing. Start retrieving access from previous providers the day the project begins. And if writing is not your strength, treat copywriting as part of the scope rather than a separate burden.

If you are planning a website project and want a content checklist tailored to your business, describe the project and we will give you a specific list of what to prepare first.