The fourth stage in our Build Week series is development. This is when the approved designs are turned into a real, working website. For business owners, it can be a quieter stretch. Much of the work happens behind the scenes, and progress may not look dramatic from the outside until the pieces come together.
Setting up the environment
Development usually begins on a private development or staging site, not the live website. This lets the team build freely without affecting the current site or exposing unfinished work. The staging site is typically protected with a password and blocked from search engines.
At this point, decisions made earlier are put into action: the platform, the hosting environment, the theme approach and any plugins or integrations the site will need.
Building templates and components
Rather than building each page by hand, developers generally build templates and reusable components based on the design system. A header, a footer, a hero section, a card grid, a testimonial block and a contact form each get built once and then reused. This approach makes the site consistent and easier to edit later.
Careful developers build with phones in mind from the start, check color contrast and keyboard navigation as they go, and keep page weight under control by handling images and scripts thoughtfully.
Connecting the working parts
Many websites depend on features beyond static pages. During development, the team connects and configures them:
- Contact and quote forms, including where submissions are sent and stored.
- Booking, scheduling or reservation tools.
- Online store features, payments in test mode and shipping settings.
- Email newsletter signups.
- Maps, videos and other embedded content.
- Analytics and any consent tools required.
Each integration is a potential point of failure, so each one gets tested on its own before the whole site is reviewed.
Setting up the editing experience
A good build is not just pleasant for visitors. It should also be manageable for the people who will update it. Developers often configure the content management system so common tasks are simple, such as editing hours, adding a staff member or posting news, while protecting the parts of the design that should not be accidentally broken. User roles are set up so each person has the access they need and no more.
What the business sees
Near the end of development, the business typically receives a link to the staging site to click around. At this stage, pages may still have placeholder text or temporary images. That is normal. The goal of this preview is to confirm that the site works and feels as expected, not to proofread every word.
Meanwhile, the business should be finishing content. Final text and photos are needed for the next stage, Build Week 5, when content is loaded into the site and reviewed page by page.
What Good Development Looks Like From the Outside
Because so much of this stage happens out of view, it helps to know what signs suggest the work is on track. You do not need to understand the code to notice these:
- Regular updates. A short note on what was built this week and what is next keeps everyone aligned, even when there is little to see.
- Questions about details. Developers often ask where a form should send its messages, what the confirmation should say or who should receive booking alerts. These questions mean the work is being done carefully.
- A clear list of what is still placeholder. Knowing which pieces are temporary prevents confusion when you first see the staging site.
- Test-mode notes. For stores and payments, the team should explain that transactions on staging are test transactions and will not charge real cards.
Decisions the Business May Be Asked to Make
Development raises practical questions that only the business can answer. Having answers ready keeps things moving:
- Who should receive form submissions, and should more than one person get a copy?
- What should the confirmation message say after someone submits a form or books an appointment?
- Which staff members need logins to the website, and what should each be able to do?
- Which email address should automated messages come from?
- For stores: which shipping options, tax settings and payment methods should be enabled? Your accountant can help with tax questions.
- Which analytics or consent tools should be installed, and who should have access to the reports?
How to Explore the Staging Site
When you receive the staging link, a purposeful walk through the site is more useful than random clicking.
- Start on the homepage on your phone and try to complete the site’s most important task, such as booking or contacting the business.
- Open the main menu and visit each top-level page.
- Submit each form once using your own details, and confirm the message arrives where it should.
- Try any special features, such as filters, galleries or maps.
- Note anything that feels broken, confusing or slow, along with the page and device you were using.
Remember that the staging site may be slower or behave slightly differently from the finished site, and that some content is still temporary. Focus on how it works rather than on final wording.
Mistakes to Avoid During Development
- Adding features mid-build without discussion. A new integration can affect timelines and testing. Raise it as a request so the team can tell you how it fits.
- Sharing the staging link widely. Unfinished work seen out of context can cause confusion. Keep it to the people who need to review.
- Letting content slip. Development often finishes before content does. When that happens, the launch waits on content, not code.
- Making changes to the old site’s setup. If the domain, email or hosting settings need changes, coordinate them with the web team so launch plans stay accurate.
Questions Owners Ask
Can we start editing the new site ourselves now?
Sometimes, once the templates are ready. Ask your team when it is safe to start entering content and whether there are any areas you should avoid until development is complete.
Will we be trained on how to use it?
Ask. Many projects include a training session or written guides. It is easier to learn on the staging site, where mistakes cannot affect real customers.
How will we know development is finished?
Your team should tell you when every template, feature and integration on the plan is built and ready for content and testing. A short written list of what was completed, and anything still outstanding, makes that handoff clear for everyone.




