3 THINGS TO AGREE ON BEFORE WORK BEGINS

Most web development projects do not fail because of bad code.

They fail because of unclear expectations.

The client assumes one thing.
The developer assumes another.
Nothing is written down.

By the time the website is done, both sides are frustrated — and neither feels satisfied.

Three simple agreements before work begins prevent most of this:

1️⃣ Agree on Exactly What Is Being Built
Not a general idea.

A clear breakdown:

✔️ Number of pages
✔️ What each page contains
✔️ Features included
✔️ Features NOT included
✔️ What counts as an extra/add-on

Vague requests create vague results.

“I want a professional website” means different things to different people.

Put everything in writing.

Let both parties confirm and agree before work starts.

That document becomes the project roadmap.

2️⃣ Agree on Timeline and Milestones
Do not just ask “how long will it take?”

Break it down:

✔️ When is the first design shared?
✔️ When is feedback given?
✔️ When is the full site ready for review?
✔️ When is final launch?

Without milestones:

❌ Delays go untracked
❌ Weeks turn into months
❌ Communication becomes reactive instead of structured

A timeline creates accountability on both sides.

3️⃣ Agree on What Happens After Launch
This is where most problems start.

Clarify:

✔️ Who handles updates?
✔️ How much do changes cost?
✔️ How are issues reported?
✔️ How fast are fixes done?
✔️ Is there maintenance support or not?

A project is not finished at launch — that is just the beginning of usage.

If this is not discussed early, disagreements are guaranteed later.

A professional developer will document all three without hesitation.

A problematic one will avoid writing things down.

So before you pay any deposit, ask yourself:

Have we clearly agreed — in writing — on what is being built, when it will be delivered, and what happens after launch?

© Bonnie Computer Hub
Empowering Through Technology