A clear process. One person carrying the context.
From the first conversation through launch, every phase has a clear purpose, decision, and next step. You always know what is moving and what needs your input.
See all six phases ↓- Structure
- Six defined phases
- Communication
- Direct with Briann
- Progress
- Milestone-based
You work directly with the person designing and building your website.
The business context does not disappear into a handoff. Briann leads the strategy, design, development, and launch, so decisions stay connected from one phase to the next.
How does a website project move from brief to launch?
Arc uses six phases: Understand, Strategy, Design, Build, Launch, and Support. Each phase closes with a defined decision, keeping discovery, approvals, and production from blending into one unclear stretch of work.
-
01
Listen before planning
Understand
We learn what changed in the business, what the website needs to accomplish, who it needs to serve, and what material already exists.
- Decision point
- Shared project brief
-
02
Turn context into direction
Strategy
We set the site architecture, visitor journey, content direction, project scope, responsibilities, and milestones before visual work begins.
- Decision point
- Approved direction and scope
-
03
Give the direction a system
Design
The visual system and key pages are designed around the business, its brand, and the actions visitors need to take.
- Decision point
- Approved design direction
-
04
Move from direction to product
Build
Arc develops the approved direction into a responsive production website, adds the agreed content, and prepares the complete experience for testing.
- Decision point
- Testable production build
-
05
Check the complete experience
Launch
We complete browser, performance, and accessibility checks, confirm the agreed technical setup, configure deployment, and take the approved site live.
- Decision point
- Launch approval
-
06
Define what happens next
Support
Post-launch fixes follow the agreed project terms. Ongoing maintenance or future expansion continues through a separate support plan when needed.
- Decision point
- Confirmed support plan
What is agreed before production begins?
The proposal confirms the exact pages, functionality, responsibilities, timeline, payment milestones, approval points, and post-launch support before the build starts.
- What Arc will deliver
- What you need to provide
- When feedback and approval are needed
- What is included after launch
Start with what changed in the business.
The first brief does not need to be polished. Share where the business is now and what the website needs to support next.