Signing the contract with a real estate website design agency feels like the hard part. It isn’t. The hard part is the three to six months that follow — and whether you emerge from them with a site that performs, or with a site that looks like a compromise and feels like one to use.

Most guides on hiring a web design agency stop at the moment of selection. This one starts there. Here’s what actually happens after you sign, what your agency needs from you at each stage, and how to behave as a client in ways that  produce better work. 

Discovery: the phase most clients underestimate

The first few weeks of a web design project don’t look like much from the outside. No designs. No pages. No visible progress. Just meetings, questions, and documents.

This is discovery, and it’s the most important phase of the project — not because of what it produces, but because of what it prevents. Bad briefs, misaligned expectations, and design directions that don’t fit the business almost always trace back to discovery that was rushed or skipped entirely.

Your job in discovery is to be specific. Not about what you want the site to look like — that comes later — but about what you need it to do. Which buyers are you trying to reach, and what do they need to feel before they’ll contact you? What does the current site fail at? Who inside your organisation will have opinions about the design, and when should they be involved?

The agencies that do this well will ask questions you haven’t thought about. Answer them honestly, including the uncomfortable ones. If your current enquiry rate is low, say so. If a previous redesign didn’t work, explain what happened. The more your agency understands about the real situation — not the aspirational version of it — the better their brief will be.

One thing worth doing yourself before discovery kicks off: talk to recent clients. Ask how they found you, what they looked at on your current site before contacting you, and what nearly made them go elsewhere. That information is more useful to a design agency than any amount of internal discussion about your brand values.

Strategy and architecture: agreeing on the skeleton

After discovery, most agencies will present a site architecture — a structural map of the pages, how they connect, and what content each one needs to contain. This isn’t the design. It’s the skeleton the design will be built on.

Review this carefully, because structural changes are cheap at this stage and expensive later. Does the navigation reflect how your buyers and sellers actually think about their problem, or does it reflect your internal organisation? Is the listing page given the prominence it deserves, or is it buried under corporate content? Is there a logical sequence that moves a visitor from first impression to contact, or do the pages exist as separate islands?

This is also when content decisions get made — and this is where many real estate website projects start to go wrong. Agencies need content to design around: not placeholder text, but real headings, real photography, real descriptions of what you do and who you do it for. If that content doesn’t exist yet, now is the time to start creating it, not after the design is presented.

The most common cause of project delays isn’t the agency. It’s the client failing to deliver content on time. If copywriting isn’t included in your contract, either hire someone or assign the work internally with actual deadlines. Treating content as something that gets sorted out later is a decision that will extend your timeline by weeks.

Design: how to give feedback that actually helps

The first design presentation is the moment most clients either become good clients or difficult ones. The difference is almost entirely in how they give feedback.

Unhelpful feedback sounds like this: “I don’t really like the blue.” “Can we make it feel more premium?” “My colleague thinks the font is too small.” “I showed it to my wife and she prefers a different layout.”

Helpful feedback sounds like this: “The homepage doesn’t communicate that we specialise in luxury properties — a buyer arriving for the first time wouldn’t know that from this screen.” “The listing page feels like a data sheet. We need it to feel more aspirational.” “The contact form is too prominent on the first visit — buyers at this stage aren’t ready to enquire, they’re still exploring.”

The distinction is between feedback that describes a preference and feedback that describes a problem with how well the design achieves a specific goal. The first kind forces the agency to guess what you actually need. The second kind gives them something concrete to solve.

Before any design review, go back to the objectives you agreed in discovery. Ask whether each screen achieves what it’s supposed to achieve for the visitor it’s supposed to serve. If it doesn’t, describe the gap specifically. If it does, say so — positive feedback is just as important as critical feedback, because it tells the agency which decisions to protect.

A few things worth knowing about this stage: design is easier to change now than at any other point in the project. A layout that isn’t working can be rethought in hours. After development starts, the same change takes days. If something isn’t right, say so clearly now. Leaving feedback for the next round, or hoping it resolves itself, is how projects end up with designs that nobody’s entirely happy with.

Bringing stakeholders in at the right moment

One of the most reliable ways to derail a web design project is to introduce stakeholders at the wrong stage. The pattern is familiar: design is presented, the primary client approves it, then it gets shared internally and someone who wasn’t in the discovery meetings has strong opinions about the colour scheme, the photography style, or the navigation structure.

None of those opinions are necessarily wrong. The problem is timing. When new requirements arrive after design is underway, they don’t just change the design — they reopen questions that were already settled, introduce contradictions with decisions that have been built on, and consume revision rounds that were budgeted for refinement rather than rethinking.

The way to avoid this is to establish, at the start of the project, who has approval authority and who has input. People with approval authority need to be present at discovery and at the first design presentation. People with input can be consulted, but their feedback should be filtered through whoever is managing the project on the client side — not delivered directly to the agency at different stages in different formats.

Tell your agency at the beginning who they’re designing for and who will be signing off. If that list includes people with strong aesthetic opinions who haven’t been involved so far, get them involved in discovery rather than waiting for them to see the design.

Development: what’s happening and what you need to do

Once design is approved and development starts, the visible pace of the project changes. There may be weeks where you don’t see much. This is normal — the site is being built, which looks less dramatic than design but is significantly more work.

Your main responsibilities during development are content delivery and responsive feedback when the agency has questions. If you’re providing photography, copy, or any other assets, deliver them on the agreed schedule. A development team waiting on a hero image or a set of agent bios is a development team that’s either paused or working around gaps that will need to be filled later.

When test builds become available to review, test them properly. Not just on your desktop in your office — on your phone, on a slow connection, in the conditions your buyers will actually be using. Navigate through the site the way a first-time visitor would. Try to find a property. Try to contact an agent. Note everything that creates friction, not just things that look wrong.

Pay particular attention to the content management system you’ve been set up with. This is the tool your team will use to update the site after launch. Is it intuitive enough for the people who’ll be using it? Can you update a listing, publish a blog post, or change an agent’s photo without asking a developer? If not, raise it before launch, not after.

Launch: the preparation most clients skip

The week before launch is usually frantic, and the temptation is to focus entirely on getting the site live. The clients who handle this phase well prepare for what happens immediately after launch, not just for launch itself.

Before the site goes live, make sure you have access to everything you’ll need: the hosting account, the domain registrar, the analytics setup, the content management system. These should be in accounts you control, not accounts controlled by the agency. Confirm this explicitly — don’t assume.

Establish a process for reporting and fixing post-launch issues. Bugs surface after launch. Links break. Content formatting goes wrong in ways that weren’t visible in testing. Having a clear process for how these get reported, prioritised, and fixed prevents the post-launch period from becoming chaotic.

And set aside time in the first few weeks to review how the site is actually performing. Is the search function being used the way you expected? Are visitors reaching the contact page? Are they dropping off at a specific point in the journey? The data from the first month of real traffic is more useful than any amount of pre-launch testing — and it tells you what to optimize next.

The client behaviour that produces the best work

The agencies that consistently produce strong results tend to say the same thing about the clients they produce them for: they’re decisive, they give specific feedback, and they deliver what they promised when they promised it.

Decisiveness doesn’t mean rushing. It means making clear decisions at each stage and not revisiting them without good reason. Every time a decision is reopened, the project slows and the budget shrinks.

Specific feedback doesn’t require design expertise. It requires being clear about what a screen needs to achieve and honest about whether it does. That’s something any client can do.

Delivering on commitments — content, approvals, access — respects the agency’s time and keeps the project moving. Agencies structure their schedules around client dependencies. When those dependencies arrive late, the knock-on effects are rarely contained to a single week.

The best real estate website projects aren’t the ones where everything went smoothly. They’re the ones where problems were identified and resolved quickly, feedback was honest and constructive, and both sides felt like they were working toward the same outcome. That’s a collaboration worth having — and most of it is within the client’s control.