Most website projects don't fail because the designer was bad. They fail because nobody agreed on what was supposed to happen, in what order, and who owed what at each step. The owner thinks the web shop is handling everything. The web shop is waiting on photos and a list of services. Six weeks go by, both sides are frustrated, and the project quietly dies at 80 percent done.
We build websites for a living, and we've seen the inside of a lot of stalled projects that came to us for rescue. The pattern is almost always the same. So here's what a healthy project actually looks like, stage by stage, including the part nobody warns you about: the place where almost every project stalls is content, and the content usually has to come from you.
If you know the milestones going in, you can hold your builder accountable, hold yourself accountable, and spot trouble before it costs you a month.
The Milestones of a Healthy Project
Every legitimate website project, whether it takes a week or three months, moves through the same basic stages. The names change from shop to shop, but the sequence doesn't.
1. Discovery and kickoff
This is where the builder learns your business. What you do, who you serve, what services make you the most money, what your competitors look like, and what you want a visitor to actually do on the site (call, book, fill out a form). A good kickoff also covers logistics: who has access to your domain, your current hosting, your Google Business Profile, and your photos.
You owe: honest answers, access credentials, and a decision-maker in the room. If the person on the kickoff call can't approve anything, you've added a week to every future step.
They owe: a clear scope, a timeline with dates, and a list of exactly what they need from you, in writing.
2. Content gathering
This is the stage that kills projects, so I'll spend real time on it below. Short version: the builder needs your services list, your service area, your photos, your reviews, your license numbers, your story. Some shops write the copy for you from an interview. Others hand you a blank questionnaire and wait. Know which kind you hired.
You owe: photos, business facts, and timely answers.
They owe: a structured way to collect it from you. A shop that says "just send us whatever you have" is setting you up to stall.
3. Design and build
The builder turns content into pages. In an old-school agency process, this splits into wireframes, then mockups, then development, with an approval gate at each step. In a modern process, design and build often happen together, which is faster and gives you something real to react to sooner.
You owe: feedback that is specific and consolidated. "Make it pop" is not feedback. "The phone number should be bigger on mobile and the header photo should show our crew, not stock" is feedback.
They owe: working drafts you can actually click through, not just static pictures of a website.
4. Revisions
Every project needs a revision round. Healthy projects need one or two. Unhealthy projects need seven, usually because the first draft was built on guesses instead of real content, or because feedback trickled in one email at a time from three different people.
You owe: all your feedback in one batch, from one voice. If your spouse, your office manager, and your business partner all have opinions, collect them first and send one list.
They owe: a defined number of revision rounds in the agreement, and a fast turnaround on each one.
5. Pre-launch checks
Before the site goes live, somebody needs to verify the boring stuff: every form sends to the right inbox, the phone number is click-to-call on mobile, the site loads fast (you can check any site yourself with PageSpeed Insights), every page has a title and description, and the site is set up so Google can find and index it.
You owe: a final review. Click every link. Call the phone number from the site. Submit the contact form.
They owe: a launch checklist they actually run, and proof they ran it.
6. Launch and handoff
The site goes live on your domain. A healthy handoff includes: confirmation that the domain and hosting are in your name or accessible to you, login credentials, a redirect plan if you had an old site (so you don't lose the Google rankings you already earned), and clarity on what ongoing support costs.
You owe: nothing at this stage except attention.
They owe: everything above, plus a straight answer to "what happens if I stop paying you?" If the answer is "your site disappears," you didn't buy a website, you rented one. We wrote more about ownership traps in our piece on website contract red flags.
Where Projects Actually Stall: Content
Ask anyone who builds websites for small businesses where projects die, and you'll get the same answer: waiting on content.
It's not malice and it's not laziness. You're running a business. Writing your own "About" page, digging up photos from your phone, listing every service you offer with enough detail to build a page around, that's homework, and it lands on the busiest person in the company. The website is important but never urgent, so the email titled "Content questionnaire, please complete" sits unopened for three weeks while the builder's timeline quietly evaporates.
Here's the uncomfortable truth: when a project stalls at content, the timeline failure is usually shared. The owner didn't deliver, but the builder also chose a process that depends on a busy owner doing homework. A good process plans around reality instead of blaming the client for it.
There are three ways builders handle content, and they tell you a lot:
- The questionnaire model. They send forms, you fill them out, they build from your answers. Cheapest for them, slowest for you. This is where most stalls happen.
- The interview model. They get you on a call, ask questions, and write the copy themselves. Faster, because talking about your business for 30 minutes is easy and writing about it for six hours is hard.
- The pre-build model. They pull what already exists, your Google Business Profile, your reviews, your photos, your old site, and build a real draft from that first. Then you correct a draft instead of filling a blank page. This is what we do, and it's the single biggest reason our projects don't stall. Reacting is easier than creating.
Whichever model your builder uses, do this one thing before the project starts: spend 20 minutes collecting your 15 best real photos and a plain list of every service you offer. That one folder prevents more delays than anything else you can do.
Red Flags
- No written timeline with dates. "It usually takes a few weeks" is not a plan.
- No list of what they need from you. If they don't tell you what you owe, they're planning to use stock photos and filler text, or planning to blame you later.
- You can't see work in progress. Weeks of silence followed by a "big reveal" means there's no room to course-correct, and the reveal meeting becomes a negotiation.
- Unlimited revisions advertised as a perk. It sounds generous. In practice it means the first draft will be a guess, because revisions are where they expect to figure out what you want.
- Vague answers about ownership. Who owns the domain, the content, the site itself? If the answer takes more than one sentence, be careful.
- Payment structure with no milestones. 100 percent upfront with no defined deliverables, or a contract where you owe everything even if nothing launches.
Green Flags
- They ask about your business before they talk about design. Services, margins, service area, what jobs you want more of. A site built around your best work, like the trade-specific sites we build for HVAC companies and roofers, starts with those questions.
- They show you something real, early. A clickable draft in days, not mockups in week four.
- They have a content plan that doesn't depend on your free time. They interview you, or they build from what already exists.
- Specific, dated milestones and a defined revision count. Constraints are a sign of a real process.
- They put the launch checklist and ownership terms in writing without being asked.
- References you can actually check. Live sites, with phone numbers that get answered.
What This Looks Like When It Works
A healthy project, run well, doesn't need months. Discovery can happen in one call. Content can be pre-gathered from your public footprint. A first draft can exist in a day. Revisions can happen in real time on a screen-share instead of over two weeks of email. Pre-launch checks take an afternoon when the builder does them as a routine instead of an afterthought.
We've compressed that into a fixed process: first draft in 24 hours, then a build call where we finish the site live with you on the line, then launch within 7 days, guaranteed. Not because we skip stages, but because we removed the waiting between them. If you want the full breakdown of how a fast process compares to a traditional one, read Why Agencies Take Six Weeks (and Why We Don't).
Get a Site Built With You, Not At You
Omnyra builds done-with-you websites live on a call. You get a real first draft within 24 hours, we revise it together in real time, and your site is live in 7 days, guaranteed. Tiers start at $500, with pay-in-4 and Klarna financing available. We're veteran-owned and based in Wilmington, NC, with 1,500+ small business sites built in the last 90 days.