A clear website build process from strategy to launch.
The Cosmic Build website build process is designed to reduce uncertainty, keep decisions moving, and prevent the project from expanding without control. Every stage has a defined purpose, clear inputs, and an agreed next step.
1. Strategy · 2. Structure · 3. Build · 4. Launch
Before the project begins
A short application and fit review confirm whether the project matches the studio, the available budget, and the proposed timeline. Suitable projects then move to a focused discovery call and written proposal.
The proposal confirms
- The agreed pages, deliverables, and exclusions.
- The project schedule and feedback windows.
- The investment, currency, and payment stages.
- Required access, content, and client responsibilities.
- How revisions and additional requests are handled.
1. Strategy
We begin by defining what the website must do. That means understanding the offer, the ideal client, the most important objections, the available proof, and the action a qualified visitor should take.
Key decisions
- Who the primary audience is.
- Which offer or service deserves priority.
- What a visitor must understand above the fold.
- Which proof builds confidence.
- What counts as a meaningful conversion.
Typical output
A concise strategic direction covering audience, positioning, page goals, conversion priorities, and any important technical constraints.
2. Structure
Before visual design is polished, we map the information architecture and section sequence. This keeps the website focused on customer decisions rather than decorating an unclear page.
What is planned
- Navigation and page hierarchy.
- The purpose of each page.
- Headline, proof, objection, and CTA placement.
- Internal links between relevant pages.
- Content gaps that must be resolved before build.
Typical output
A page-by-page structure or working content framework that can be reviewed before the build becomes expensive to change.
3. Build
The approved structure becomes a responsive WordPress website. Reusable styles, sensible components, and a lean technical setup help the site remain consistent and maintainable.
Build standards
- Responsive layouts for common screen sizes.
- Clear heading structure and readable content widths.
- Compressed, appropriately sized media.
- Practical plugin selection and reduced complexity.
- Forms, calls to action, and tracking foundations.
- Priority-page metadata and internal links.
Feedback approach
Feedback is collected at agreed checkpoints and returned as one consolidated response. This protects the schedule and prevents contradictory changes from different channels.
4. Launch
Launch is a controlled handover rather than a last-minute upload. We complete the agreed checks, confirm ownership and access, and make sure the client understands the immediate next steps.
Launch checks may include
- Desktop and mobile layout review.
- Navigation, button, and form testing.
- Metadata, indexing, and sitemap checks.
- Basic analytics and conversion-event checks.
- Performance and image review.
- Backup, security, and maintenance pathway.
- Final access and handover notes.
Typical timelines
| Engagement | Typical delivery |
|---|---|
| Landing Page Sprint | 7–10 days |
| Website Build — Launch Sprint | 3–5 weeks |
| Performance Tune-Up | 5–10 days |
Timelines begin when the agreed payment, content, access, and approvals are in place. Delayed feedback or missing material can move the launch date.
What we need from you
- A clear explanation of the offer and ideal client.
- Access to existing website, hosting, analytics, and brand assets where relevant.
- Approved images, legal details, and business information.
- One decision-maker or one consolidated feedback channel.
- Feedback within the agreed review window.
How scope stays controlled
Every project has agreed deliverables. New pages, integrations, major content changes, or requests outside the original scope are assessed separately. This keeps the core project predictable while leaving room for useful additions when they are genuinely needed.
After launch
A website is not finished forever on launch day. Offers change, proof grows, software updates, and customer behaviour becomes clearer. Clients can manage the site independently, return for focused improvements, or move onto a suitable Care Plan.
Frequently asked questions
How many revision rounds are included?
The proposal states the included review points and revision allowance. Consolidated feedback is required so the project can move efficiently.
What happens when content is late?
The schedule may move or the project may be paused until the required material is available. This prevents rushed decisions and avoidable rework.
Can the site launch in phases?
Yes, when a phased release is strategically useful. A focused landing page can launch before a wider site, or lower-priority pages can follow after the core conversion path is live.
Do you provide training?
A practical handover is included at the level agreed in the proposal. Deeper team training or documentation can be added when required.
Start with a clear project application
Share the current problem, the result you need, your preferred timeline, and the budget range allocated. We will confirm fit and recommend the most suitable engagement.