How to Build a Website in a Week: The 7-Day Launch Plan
A practical one-week website launch plan covering scope, copy, design, CMS, SEO, analytics, forms, QA, and launch day.
Most one-week website projects don't fail because the team moved too fast. They fail because nobody treated speed as a scoping exercise.
At Metamatter we ship marketing sites in seven days. Not brochureware: sites with working forms, editable content, crawlable pages, and conversion tracking that actually fires. The trick is deciding what you're not building this week, not heroic overtime.
Why a one-week launch is worth attempting
Founders and marketing leads usually come to us with the same pressure: a fundraise, a product launch, a sales push, or an embarrassing current site. Waiting twelve weeks for a traditional agency cycle isn't an option. Neither is launching something that looks fine in Figma but can't capture a lead.
A tight timeline forces good decisions. You stop debating seventeen homepage variations. You write copy for one buyer, not five personas. You pick a CMS based on who edits tomorrow, not who might edit in 2027.
Google still rewards useful pages, clean metadata, and fast load times, as the SEO Starter Guide makes clear. AI search adds another layer: your content needs clear answers and verifiable claims. A rushed site can still rank if the structure is sound.
Who this plan is for
This works best if you match one of these profiles:
- Founder-led B2B with a defined offer and at least rough proof (logos, metrics, a case study).
- Marketing lead replacing WordPress or an AI-generated site before a campaign goes live.
- Operator who can approve copy in 24 hours and won't reopen design on day five.
It's a bad fit if you need custom product integrations, a full rebrand with stakeholder committees, or legal review on every paragraph. Those are real needs. They just don't fit seven days.
The seven-day framework
| Day | Focus | Output |
|---|---|---|
| Mon | Scope + sitemap | Page list, conversion goal, CMS decision |
| Tue | Copy draft | Homepage, 2–4 core pages, FAQ block |
| Wed | Design approval | Real screens, component set, image list |
| Thu | Build | Templates, forms, analytics hooks |
| Fri | CMS + SEO | Metadata, sitemap, structured data |
| Sat | QA | Mobile, forms, redirects, accessibility spot-check |
| Sun | Launch | Search Console, monitoring, first traffic review |
We've seen teams try to flip design and copy. It rarely works. Copy first, design second, build third. Design should solve hierarchy problems copy already identified.
Practical rules we enforce on every sprint
One conversion goal. Demo request, contact form, or waitlist: pick one primary action per page. Secondary links are fine; competing hero CTAs are not.
Fixed page count. For a week-one launch, think homepage, 2–3 service or product pages, about, contact, and legal. Blog can come week two.
Named owners. Someone owns copy, someone approves design, someone tests forms. If "the team" owns it, nothing ships.
No net-new research. Use customer calls, sales decks, and existing docs. This isn't the week to run a positioning workshop.
Day-by-day process
Monday: scope like a product manager. List every URL, its job in the funnel, and whether it needs CMS fields. Decide integrations now: CRM, email routing, analytics. Changing HubSpot vs. plain email on Thursday costs you launch.
Tuesday: write for a skeptical buyer. Open with the outcome, not your founding story. Every service page needs proof: logos, numbers, a quote, or a specific process. Generic "we partner with you" copy is what AI site builders spit out. Replace it.
Wednesday: design with constraints. Approve desktop and mobile for homepage plus one inner page. That's enough to build the system. Moodboards are where one-week projects go to die.
Thursday: build the acquisition layer. Forms must deliver to the right inbox or CRM. Wire GA4 events for CTA clicks and form submits per Google's event guidance. Don't defer tracking to "phase two."
Friday: SEO that's operational. Unique title tags and meta descriptions per page. sitemap.xml, sensible robots.txt, canonical URLs. Submit the sitemap in Search Console. Check Core Web Vitals on mobile: oversized hero images are the usual culprit.
Saturday: QA like revenue depends on it. Because it does. Submit every form. Click every phone and mailto link. Scan for lorem ipsum. Test on a real phone, not just Chrome devtools.
Sunday: launch and watch. Turn on monitoring. Check realtime analytics within the first hour of traffic. Have one person responsible for fixing broken paths fast.
Search visibility without overthinking it
You don't need a 40-page SEO strategy in week one. You need crawlable HTML, honest metadata, internal links between related pages, and content that answers real buyer questions. Add FAQ sections where they reflect actual sales objections. They help humans and search snippets alike.
If you're planning a content hub later, leave URL patterns and CMS models ready. Migrating /blog/post-title after launch is annoying.
Common mistakes
- Scope creep on day three. "Can we add a resources section?" Not this week.
- Design perfectionism. Shipping 90% beats polishing 60% for another month.
- Untested forms. We've debugged "contact us" forms that silently failed for two weeks post-launch.
- No content owner after launch. Someone needs to update pricing, dates, and proof blocks.
What to do next
If seven days fits your situation, block the calendar and lock scope today. If you need help compressing decisions, Metamatter runs fixed-scope sprints with senior builders who have fintech and enterprise backgrounds, with no junior handoff.
Week two is for blog posts, case studies, and refinement. Week one is for becoming credible enough to send traffic.
FAQ
Can you really launch a credible marketing site in seven days?
Yes, with fixed scope and fast approvals. Open-ended design is what breaks the timeline.
Do I need a CMS from day one?
If marketers will publish without developers, yes. Otherwise static core pages are fine initially.
What should happen on launch day?
Sitemap submission, form tests, analytics verification, and mobile performance spot-checks.
When does it make sense to hire an agency?
When the deadline is fixed and you can't risk weak tracking, wrong CMS choices, or generic AI copy.
