The owner's plan is the spec

Many business owners who rebuild a website already know what they want. They have written it down: the pages, the order, the tools, what each part is for. Then they hand it to a vendor, and the plan starts to change shape. Some sections get “improved”. Some quietly disappear. New ones show up that nobody asked for. A few weeks later the owner can no longer tell which parts of the site are his plan and which are the vendor’s taste.

We recently rebuilt a directory and review website whose owner had written his own plan for the new site, in 20 sections. This is how we worked with it, and what you can ask your own vendor so you never lose sight of yours.

We build the plan, not our version of it

Before the rebuild we had audited the old site from its own data, and the audit had its own view of what to do first. Then the owner wrote his plan. From that point the rule was simple: the owner’s plan is the spec. We follow it section by section. We don’t grade it, and we don’t swap in a plan we like better.

That does not mean switching off the data. It means putting the data to work for the plan. When we sized the content, we sorted 13,252 searches into the pages his plan named, not into a structure of our own. When we sorted a further 1,005 searches one by one, each got an action and a reason, and 61 new pages came out of it, inside the sections he had already defined.

Where the data disagrees, write it down

Sometimes the numbers point another way. A plan is written before all the data is in, so that is normal. What matters is what happens next.

Our rule: the difference is written down as an open question, and the plan stays as it is. The question says what the data shows, what it might mean for that section, and what we need from the owner to decide. Until he answers, we build what the plan says. The owner decides when he has the facts in front of him, not when a vendor has already built around him.

And nothing gets built before the plan for it is agreed. Agreeing first is slower for a day. It saves weeks of “that’s not what I meant”.

One list, every section, its state

The plan became a stage checklist. Every one of the 20 sections is on it, always, with one of three states:

• Done. Live, with where to look.
• Held: waiting on your answer, ready on our side. The work is ready; it waits on a decision or a fact only the owner can give. The wording matters. “Held” alone sounds like a delay on our end. This says whose move it is, without blame.
• Ongoing after launch. Sections that never finish, like news and guide updates, with the routine that keeps them going.

No section leaves the list in silence. It is the same rule we hold for every commitment in our weekly reports: done, replaced with a reason, or still there.

“Extra” is its own label

Along the way we did things the plan didn’t ask for: checks, safeguards, small tools that made the launch safer. Those are useful, but they are not the plan. So every one of them is marked “Extra”, on a separate line from the agreed work.

This protects both sides. The owner can see what he agreed to, and what came on top, and never has to wonder whether an extra was quietly traded for a section he wanted. Scope stays sharp because the two are never mixed. It is the same honesty behind fixing the hours, not promising everything: you should always be able to see exactly what was done.

A demo page with a screenshot for every item

A checklist tells you a section is done. It doesn’t show you. So we built a demo page that walks the owner through every item on the list, each with a screenshot and a link to the live page. He can check the whole plan in one sitting, at his own pace, without a call and without knowing where anything lives on the new site.

Alongside it, a written report went to the owner every week: what moved, what is held and on whom, what comes next. Reports and checklist tell the same story, because they come from the same list.

The result

20 of 20 sections built. Live in 18 days, from kickoff to the site answering on its own domain. Every held item was ready on our side, waiting on one answer. Every extra was labelled as one.

The speed came partly from the clarity. When nobody argues over what the plan says, and every open question has a home, the team spends its days building.

What to ask your own vendor

You don’t need special tools to get the same clarity. Ask for these:

• A list of every section of my plan, with its state today. Not a summary. Every section, every time.
• For anything held: what exactly is it waiting on, and from whom? If it waits on you, you should know which answer.
• Where the data disagreed with my plan, where is that written down? You want the question and the evidence, not a decision already taken.
• Which work was beyond what we agreed, and how is it marked? Extras should be visible and separate.
• Can I see each finished item, with a screenshot or a link, without asking you to walk me through it?

A team that works from one list can answer all five the same day. If yours can’t, your plan may already have turned into theirs.