Every website project has a moment where it either gets easier or harder, and it usually happens on the discovery call. This case study walks through a website build from that first call in December 2025 to launch in February 2026: what I asked, how I planned around content that was already written, how the build ran, and how revisions fit inside a one-month timeline.
This project is under NDA, so the client’s name, branding and live URL are not shared. The visuals in this post are sample layouts that show my process, not the client’s actual site.
Key takeaways
- Discovery call in December 2025, build started the 2nd week of January 2026, launched the 2nd week of February 2026. About one month, revisions included.
- The client handed over finished, SEO-optimized content with all links included, so the job was presenting it correctly, not writing it.
- The site covers a Homepage, About Us, Contact Us, Blog, Privacy Policy, Terms of Use and Local Pages.
- Reviewing the content before designing anything is what kept the build fast.
- A reusable local page template kept the design consistent and makes future local pages quick to add.
The Project at a Glance
| Detail | Info |
|---|---|
| My role | Web designer and developer |
| Client | Confidential (under NDA) |
| Discovery call | December 2025 |
| Build window | 2nd week of January 2026 to 2nd week of February 2026 |
| Total duration | About 1 month, revisions included |
| Content | Provided by the client, SEO-optimized, links included |
| Pages | Homepage, About Us, Contact Us, Blog, Privacy Policy, Terms of Use, Local Pages |
The Challenge
The client wanted a website built to rank locally and turn visitors into inquiries. The content side was already handled: their team had written SEO-optimized copy for every page, with internal and external links mapped out.
That changed what the job was. This was not a “figure out what to say” project. It was a “present what has already been said, correctly and fast” project. The real challenges were:
- Turning finished, SEO-driven content into a layout that reads well and converts, without disturbing the heading structure, links or keyword placement.
- Building a site structure that supports multiple local pages without feeling repetitive or thin.
- Delivering everything, including revision rounds, inside one month.
Phase 1: The Discovery Call (December 2025)
Every build I take on starts with a discovery call, because the decisions made there save days of rework later. On this call I focused on five things:
- Business goals: What does a win look like? Phone calls, form fills, quote requests?
- Audience: Who lands on the site, what are they looking for, and how ready are they to buy?
- Content status: What is finished, what is missing, and who owns each piece? Here, all copy was ready and SEO-optimized, with links included.
- Site structure: Which pages are needed, and how do the local pages fit into the navigation?
- Look and feel: Brand assets, reference sites they liked, and anything they wanted to avoid.
I closed the call by confirming scope, timeline and how revisions would be handled, so expectations were set before a single page was built.
Phase 2: Planning and Content Handoff (Late December to Early January)
Between the call and kickoff, the client handed over the finished content. Before designing anything, I went through it page by page to:
- Map each page’s heading structure (H1 to H3) so the design supports it instead of fighting it.
- Check that every internal and external link was accounted for and pointed where it should.
- Flag anything that affects layout, such as long sections, lists, FAQs and calls to action.
- Define a reusable template for the local pages, so each one stays consistent while keeping its own unique content.
This planning step is why the build phase moved quickly. There were no surprises hiding in the copy.
Phase 3: Design and Build (2nd Week of January to Early February)
The build started in the 2nd week of January. I worked in a deliberate order, starting with the pages that carry the most weight, then moving to templates and supporting pages.
1. Homepage
The homepage is the main conversion point: a clear value proposition up top, a visible call to action, trust-building sections, and pathways into the service and local pages.
Sample homepage layout (fictional brand, for illustration only. Not the client’s site.)
2. About Us
Built to give the business a face and a story, with the client’s copy structured for easy scanning and a clear next step at the end.
3. Contact Us
Kept simple on purpose: a clean form, clear contact details, and no friction between a visitor and an inquiry.
4. Local Pages
These are the SEO workhorses of the site. I built a flexible template so each local page carries its own unique content while sharing a consistent structure. That kept the design cohesive and made future local pages quick to add.
5. Blog
A clean, readable blog layout, set up so the client’s team can publish new content on their own without touching the design.
6. Privacy Policy and Terms of Use
Legal pages are easy to overlook but matter for credibility and compliance. They were styled to match the rest of the site and linked in the footer.
Phase 4: Revisions (Early to 2nd Week of February)
Revisions were planned into the timeline, not treated as an afterthought. After the first full review, the client sent consolidated feedback, and I worked through it in organized rounds. One list of changes per round kept edits clean and avoided the back-and-forth that usually pushes a project past its deadline.
Phase 5: Final QA and Launch (2nd Week of February 2026)
Before going live, I ran a full pre-launch checklist:
- All internal and external links tested and confirmed.
- Headings, page titles and meta details checked against the SEO content provided.
- Mobile, tablet and desktop testing across the whole site.
- Forms tested end to end, including submission and notification delivery.
- Speed and image optimization pass.
- Final walkthrough with the client, then launch.
The site went live in the 2nd week of February 2026, roughly one month after kickoff.
The Timeline at a Glance
| When | What happened |
|---|---|
| December 2025 | Discovery call, scope and goals confirmed |
| Late December to early January | Content handoff, content review and structure planning |
| 2nd week of January | Project kickoff, design and build begins |
| Mid to late January | Core pages, local page template and blog built |
| Early February | Client review and revision rounds |
| 2nd week of February | Final QA and launch |
The Outcome
The client went from finished copy to a live, launch-ready website in about a month, revisions included. The final site gives them:
- A complete site structure covering every page a local service business needs.
- A scalable local page template they can keep expanding.
- Their SEO content preserved as written, with links and heading structure intact.
- A blog they can run on their own.
What I Would Tell Anyone Planning a Website
- A strong discovery call shortens the whole project. Most timeline problems are scope problems that were not caught early.
- Ready content speeds everything up. When copy arrives finished, design and development can stay focused.
- Templates make local SEO scalable. One well-built local page layout means new pages take minutes to add, not days.
- Planned revisions protect the deadline. Building feedback rounds into the schedule keeps the launch date realistic.
Frequently Asked Questions
How long does a website like this take to build?
This one took about one month from kickoff to launch, revisions included, with the content already written and SEO-optimized. If content still needs to be written, plan for more time.
Do I need my content ready before the build starts?
It is not required, but it helps a lot. Finished content lets me plan the layout around your real headings, links and calls to action instead of placeholder text, which is a big part of why this project stayed on schedule.
How are revisions handled?
Revisions are agreed on the discovery call and built into the timeline. Feedback is collected into one list per round, which keeps changes organized and the schedule on track.
Can the client add more local pages later?
Yes. The local pages were built from a reusable template, so new locations can be added without redesigning anything.
The Short Version
A clear discovery call, a careful review of the content before design starts, a reusable template for local pages and revisions planned into the schedule turned finished copy into a live website in about a month.
Need a website built the same way? If your content is ready, or you need help getting there, book a call.
About the author: Rolijon Clemenia is a web designer and WordPress developer based in Iligan City, Philippines, with 5+ years building websites and online presence for freelancers and businesses across the US, UK and Australia. Read more about Rolijon.