# How to plan a website project so it stays the size you agreed By Chris Gatherer, CDO · Published November 13, 2026 · Shuffle Studio > A plain guide to keeping a website project on budget and on time: write down what's in, decide who signs off, and give new ideas a home. Original: https://shufflestudio.io/blog/how-to-plan-a-website-development-project-without-scope-creep --- It usually starts with a good idea. Halfway through a build, someone on the board asks for a donor page. A provider wants a second intake form. The new hire suggests a chatbot. Each one is reasonable on its own. Together, they're how a six-week website turns into a five-month one with a bigger invoice and a tired team. That's scope creep, and it's rarely anyone's fault. It happens when nobody wrote down where the project ends. Here's how we plan builds so the website you agreed on is the website you get, and the good ideas still have somewhere to go. ## 1. Write down what's in, and what's for later Before anyone opens a design file, we put the project on one page: the goal, the pages, the features, and the connections to your other tools. Next to that list goes a second one, just as important: what's *not* in this build. A short example for a nonprofit site: - **The goal: **More volunteer sign-ups - **In this build: **10 pages, a sign-up form that lands in your CRM, event listings - **Saved for later: **A member login area The "later" column isn't a no. It's a parking spot. Writing it down early means nobody has to argue about it in week four. At Shuffle Studio this page becomes your Statement of Work, the SOW. You read it, you sign it in your client portal, and from then on everyone is working from the same list. ## 2. Decide what "done" looks like at each step "The form works" means different things to different people. "A test sign-up shows up in the CRM within a minute" means one thing. We write a short checklist like that for each stage: - **Design:** page layouts and the content plan are approved. - **Build:** every page in the SOW works on phones, tablets and desktops. - **Launch:** forms, tracking, redirects and logins all pass a final check. We also agree on one person on your side who gives the final yes, and how long reviews take. That keeps sign-off fast and clear. ## 3. Give every new idea the same four questions New ideas will come up. That's a good sign; it means people care about the site. When one does, we ask: 1. What problem does this solve, and for whom? 2. Is it already in the SOW? 3. What does it change in time, cost or testing? 4. Who on your side approves it? If it's already covered, we do it. If it's new and worth doing now, it becomes a **change order**: a short document that says what's being added (or swapped out), what it costs, and how it moves the date. You sign it in your portal before the work starts, so there are no surprises on the invoice. If it can wait, it goes on the "later" list. One helpful distinction: a change order covers new work during a build. Once your site is live and on a [Continuous Support](/services) plan, keeping what we built working is part of the plan. Outside a plan, fixes and changes are scoped and quoted like any other request. ## 4. Check the site against the plan before launch Right before launch we walk the site against the signed SOW, item by item: done, waiting on something, or moved to later. Anything waiting gets a name and a date next to it. ## 5. Turn the "later" list into the next season of work Launch isn't the finish line. The ideas you parked during the build become the starting list for what comes next. With Continuous Support, your site stays hosted, updated and secure on one monthly plan, and that "later" list turns into steady improvements instead of a second big project. New requests go through **Your requests** in your client portal, so nothing gets lost in an email thread. ## Questions we hear a lot **What is scope creep?**Work that gets added to a project after it starts without anyone agreeing to the extra time or cost: new pages, new features, extra rounds of review. **Does saying "later" mean saying no?**No. It means the idea gets a proper home and a proper estimate, instead of being squeezed into a deadline it wasn't planned for. **What happens if something breaks after launch?**On a Continuous Support plan, keeping your site working is part of the plan. Without one, we scope and quote the fix first, so you know the cost before any work starts. **What if we realize mid-build that we need something important?**Then it's worth doing. We'll write a change order with the cost and the new date, and you decide. ## Ready to plan yours? If you're planning a new site or a rebuild, we'd be glad to help you map it out. [Book a call](https://shufflestudio.io/get-started) or call us at (609) 337-6488.