Webyfied.
Start a project

How we work

Seven steps, in order. The uncomfortable ones are near the top on purpose, because that is where projects are usually lost.

The shape of it

Nothing here is a surprise

Projects rarely fail because somebody wrote bad code. They fail because nobody agreed what success meant, and the disagreement surfaced at launch.

So the awkward conversations happen in week one. What number are we moving. What happens if it does not move. What do we need from you, and what happens when it arrives late. All of it goes in writing before anyone opens a design file.

01

Listen

One hour, no slides. We ask what the business actually sells, who buys it, and what is currently going wrong. Most of this call is you talking.

Week 0. Free, and you keep the notes.
02

Look at the evidence

We read your analytics, your search console, your ad accounts, and your competitors. Opinions come after data, not before.

Week 1. You get the audit whether or not you hire us.
03

Agree the number

Before any design or code, we agree on one primary metric. Enquiries, sales, cost per lead. Everything is judged against it.

Week 1. Written into the proposal.
04

Design in the open

Wireframes, then design, reviewed with you as they happen. Nothing is revealed as a finished surprise, because surprises are how projects die.

Weeks 2 to 3. Two rounds of revision included.
05

Build and instrument

We build it fast, accessible, and measured. Tracking is verified before launch, not bolted on after somebody asks a question.

Weeks 3 to 5. You see it on a staging link throughout.
06

Launch quietly

We launch, watch, and fix. The first week after launch is when real users find the things testing missed.

Week 5. Rollback ready at all times.
07

Measure and report

A monthly note that leads with the number we agreed on. If it did not move, that is the first paragraph, along with what we are changing.

Ongoing. Cancel with thirty days notice.
What we need from you

The project is only half ours

Agencies love to blame clients for delays, and clients are rarely told clearly what was needed. So here it is, in advance:

  • One decision maker who can approve without a committee
  • An hour a week, reliably, for the first five weeks
  • Access to analytics, ad accounts, and hosting on day one
  • Content and photographs by the date we agree, or a decision to have us produce them
  • An honest answer to "who is your customer," even if the honest answer is "we are not sure"

When these arrive on time, we hit the dates. When they do not, we will tell you the same week, not at the end.

Honest limits

Things we will refuse

We will not buy followers, publish AI generated filler under your name, promise a search ranking, or run ads to a page we know does not convert.

We will not take on a rebrand for a business whose real problem is that nobody knows it exists. And we will not sign a retainer when a one time project is what you actually need.

Each of these has cost us money. Each is why the clients we do have stay.

Next step

Let us look at what you have, and say something useful about it.

Send us your site or your idea. You will get a straight answer about what is working, what is not, and what it would take. No pitch deck.