After 40 years of combined experience building websites for schools, not-for-profits, and service organisations across Perth and Western Australia, we can tell you exactly where every project stalls. It’s not the design or the code. It’s the part where feedback and approval are needed.
There’s typically one client contact holding everything together. They’re capable, thorough, and managing the website project on top of a demanding full-time role. We’ve worked with hundreds just like them.
These are the five moments where we’ve seen projects grind to a halt, and what fixes them.
1. Blank-page paralysis
The site map gets approved, everyone’s excited, the project’s moving. Then we send over the content documents, and there’s silence on the other end because they’ve just been handed fifteen blank pages that all need to sound “official”, “right”, and “approved by leadership.” That kind of pressure on top of an already packed week means the content task quietly slides to next week and the week after.
The longer it sits, the harder it is to start because now there’s guilt on top of overwhelm.
It’s one of the most common things we hear from clients who’ve been through a previous website project. The scope of what was needed from them wasn’t clear upfront, so they didn’t plan for it.
The fix is structure, both in the writing and in the scheduling. We have those conversations early: what does content creation look like in your workload? What support do you need? What are realistic due dates? But the biggest shift is giving clients content briefs to write to instead of blank pages to fill. Rather than “write the About page,” it becomes “answer these five things, in this order.” The blank page disappears.
If you’re facing this right now, AI can help build that scaffold. Not to write your content, but to turn a blank page into a structured brief with the right questions in the right order. Give it your page name and your audience, and ask it to generate the questions your content needs to answer. You still write in your voice. AI removes the paralysis of staring at nothing. We’ve included the exact prompt for this in our free template pack below.
2. The wall-of-text review
The website’s been built, and the content is in. We send the final website link over for one last look, and while it’s initially met with enthusiasm, there’s silence. Again.
So, what happened? They saw about 40 pages of content to review and thought, “I need a solid block of time to tackle this,” but that time never came — because it rarely does when you’re the one who keeps the entire organisation running.
The fix is breaking it down, which sounds simple, but we support our clients in carving out time in their schedule to review. How much support depends on the client — sometimes it’s a rough estimation of hours, sometimes it’s going through it together on the phone every day.
One thing we love is taking your page list, dropping it into AI, and asking it to create a review schedule — thirty minutes a day across two weeks, prioritised by most important pages first. Export it as calendar events (.ics file you can import into your calendar). Suddenly, “review the whole website” becomes “Tuesday 2pm: check the About page.” We’ve included the exact prompt for this in our free template pack below.
3. The fear of breaking everything
The site’s been reviewed, the content’s been approved, training has been done, and now it needs to be uploaded into the backend. But it sits empty for weeks.
This is the classic fear of getting it wrong. What if I break the layout? What if I accidentally delete something? What if it looks different from what the designer intended?
That fear, alongside every other responsibility they’re carrying, means the backend sits unused as the launch date gets pushed out. This is one of those friction points that doesn’t show up in any project plan but can quietly add weeks.
The fix is a simple, page-specific checklist that asks:
- Is the heading correct?
- Is the content correct?
- Do the images display?
- Do the links work?
- Does it look right on your phone?
Paste your page list into AI and ask it to generate a review checklist for each page with those five questions. It turns a scary open-ended task into a series of yes-or-no questions. Much less room to feel like you’ve done it wrong. We’ve included the exact prompt for this in our free template pack below.
4. The feedback pile-up
Design concepts have been presented, and we leave them with the client for review. The person we’re working with loves them, but they need a sign-off from the principal, the marketing lead, maybe even the board chair.
So they forward the designs with a quick “let me know what you think.” Feedback trickles in over two weeks across dozens of emails. Half of it contradicts the other half, and maybe someone replies to the wrong thread. One staff member sends two words (“Looks good!”) but then follows up with multiple dissertations over the next week. And the person in the middle has to somehow turn all of that into one coherent response to send back to us — while still doing their actual job. This is where projects lose weeks, sometimes months, without anyone realising.
The fix starts before the feedback, not after it. Give stakeholders a set of structured questions tied back to the original brief — not “do you like this?”
Things like:
- Does the design reflect how we want people to feel when they first land on our site?
- Does the most important information stand out first?
- Is there anything here that doesn’t feel like us?
- Is there anything missing that our community would expect to find?
- Could our team realistically keep this updated?
- Is there anything here we’d want to be able to change easily in future?
When stakeholders are answering specific questions, you get usable feedback. Pair that with a clear list of who needs to approve, what they’re approving, and when it’s due, and the feedback round goes from a sprawling open-ended exercise to a structured task with a deadline. If you’re managing this yourself, paste all the feedback into AI and ask it to group by theme, flag any contradictions, and summarise into a single list you can send back to your agency. We’ve included the exact prompt for this in our free template pack below.
5. Not knowing what’s expected
This one is the core of the previous four, and it’s a big one. The client didn’t know how much of their time this project would need, or that they’d be responsible for writing content, or sourcing photography, or getting board approval at a specific milestone. Nobody told them upfront what their role involved or built tools and processes to support them.
We’ve seen this more than any other issue, and it’s the responsibility of the website agency to guide the client through what’s coming, when, and how much time to set aside.
The fix happens at the very start. Client involvement is clearly mapped out — what’s needed, when, and how much time to set aside. And it doesn’t stop at kickoff. We keep clients updated throughout the project on what’s coming up on their side, so nothing lands as a surprise.
The common thread
Every one of these moments has the same shape: a capable but busy person getting handed a task that feels huge without the clear structure or tools to tackle it.
40 years of frontline knowledge in complex website projects has given us the experience to build tools and support structures that deliver websites our clients are happy with — without adding stress to their plate.
And with AI tools improving since you started reading this blog post, you can use them to support your workflow through a website project. They can make any project easier if you know where to use them.
We’ve put together a free template pack with the prompts for each of these five moments. It works whether you’re working with us or not, and it’ll save you weeks of delay on your next website project.
If you’re planning a website project in 2026 and want a team that’s already built these approaches into the way they work, we’d love to chat →
Download the Website Project Toolkit
