Working together
From the first question to a working website.
Every project has its own starting point. These are the conversations that give the work a clear direction and keep everyone moving toward the same goal.
Start with the business.
Share where the business is today and what needs to change. A current website, a few examples and the questions customers ask can give the conversation a useful starting point.
A first website, an existing site that needs an upgrade, or a brand that no longer fits.
Agree on the work.
Define the pages, functionality and content the project needs. Discuss the platform, responsibilities, review points and what is included before the work begins.
Scope, deliverables, feedback arrangements, timing and the route to launch.
Bring the direction into focus.
Shape the page structure, words, imagery and visual identity together. Existing materials can be used where they serve the project; copy and content help can be included where they are needed.
A clear direction to review, with decisions connected to the business and its audience.
Build, review and refine.
Turn the direction into a working website and review it through open communication. Feedback helps refine the details; additional functionality or changes beyond the agreed scope are discussed before being added.
The review process and revision allowance are defined for the particular project.
Prepare for launch and handoff.
Review the agreed pages and important visitor paths, prepare the domain and hosting setup, and clarify the accounts and materials needed afterward. Handoff is arranged around who will use and maintain the website.
The launch responsibilities and any editing or maintenance needs are agreed as part of the scope.
Keep the site useful.
A website can need new content, updates and support after launch. Ongoing help is available, with the work and arrangement matched to what the business needs.
Support is discussed separately so the ongoing responsibilities are clear.
A shared understanding before a shared project.
Pricing and timing depend on what is being made, the content it needs and the review process. The scope should make the following clear:
- Pages, design and development deliverables.
- Who provides content, imagery and approvals.
- Feedback rounds and how changes are reviewed.
- Platform, integrations and hosting responsibilities.
- Launch, account ownership and handoff.
- Any support needed after launch.