We plan a project the way you plan a day in the mountains: know the objective, pack for the conditions, set save points and keep someone on belay.
These are the nine stages, from the first call to the work after launch. Scroll to follow the trail, or pick a point on the map.
Stage 01EL. 0 M
Origin Point
The discovery call
Every map and every artboard starts at zero, zero. So does every project: one conversation about where you are trying to get to, what is in the way and what you have already tried. You ask us anything. Nobody presents slides.
What happens
- A conversation about goals, constraints and timing
- A first look at the site, store or brand as it stands
- Honest questions in both directions
You leave with
- A direct answer on whether we are the right team
- The rough shape of the route
- A clear next step
Map termTrue north. The single outcome the project steers by. If a decision does not move toward it, it waits.
Stage 02EL. 520 M
Blueprint Base Camp
Research and the route plan
Base camp is where a climb is won or lost before it starts. We unpack everything: the brand, the audience, the competitors, the analytics and the technology you already run. Then we draw the blueprint.
What happens
- Stack check: an audit of the site, platform, content and data
- Brand, audience and competitor review
- Risks and unknowns named early
You leave with
- The topo: scope, phases and timeline in writing
- An estimate tied to that scope
- Agreement on how the result will be measured
Map termStack check. An honest inventory of what you already run, what still works and what will not survive the climb.
Stage 03EL. 1,040 M
Moodboard Meadow
Creative direction
Open ground before the trail steepens. This is where the look, the voice and the feel get explored while changing direction is still cheap: references, palettes, type, tone and first concepts.
What happens
- Moodboards, palettes and type studies
- Brand voice and messaging directions
- First concepts for the key screens, labels or panels
You leave with
- A creative direction you have seen and chosen
- The visual rules the build will follow
Map termSightline. What the eye lands on first. Every layout, label and screen is planned around it.
Stage 04EL. 1,560 M
Wireframe Switchbacks
Structure and prototype
The trail starts to zigzag. User flows, wireframes and architecture diagrams go back and forth until the structure holds, and the hardest part gets prototyped first.
What happens
- User flows and wireframes for the key journeys
- Architecture and data model sketched before code
- The crux identified and prototyped
You leave with
- A structure you have clicked through, not only heard described
- Sign-off at a save point before the build begins
Map termCrux. The hardest move on the route. We find it early and solve it first, because everything above depends on it.
Stage 05EL. 2,080 M
Commit Ridge
The build
The long ridge to the top. Design becomes artwork and code, committed in stages you can see. From here the route is chosen and the work is to follow it well.
What happens
- Build in phases, each ending in something you can review
- A midpoint check against the route plan
- AI used where it speeds the work, with a human on belay
You leave with
- A changelog after each phase: what changed and what is next
- Working software or finished artwork, not a status slide
Map termHuman belay. The person holding the rope on every AI-assisted step: reviewing, correcting and signing off.
Stage 06EL. 2,600 M
Staging Camp
Test and review
The last camp before the top, and the place to find out what is not ready. Everything runs on staging, on real devices, with real content.
What happens
- Cross-browser and device testing
- Accessibility, performance and SEO checks
- Content loaded and proofed, print files checked against the dieline
You leave with
- A punch list, worked to zero
- A release plan with a rollback
Map termFalse summit. The point that looks like the top and is not. Staging camp exists to find them before launch day does.
Stage 07EL. 3,040 M
Launch Window
The summit stretch
The final push is short and deliberate. Redirects, tracking, backups and sign-offs are lined up, and we pick the moment.
What happens
- Redirects, analytics and structured data verified
- Final approvals from the people who own them
- Launch timed around your season, not ours
You leave with
- A go or no-go you can trust
- Everyone knowing their part on the day
Map termFixed line. A release process that works the same way every time: staging, checklist, rollback.
Stage 08EL. 3,417 M
Go-Live Summit
Launch
The work goes live. We watch it closely in the first hours and days, fix what the real world turns up and confirm that what we planned to measure is being measured.
What happens
- Release to production
- Monitoring and checks on live traffic
- Fast fixes for anything launch reveals
You leave with
- A live site, store or platform, or a package on the shelf
- A release register: what shipped and how it is being measured
Map termRelease register. The record at the top: what shipped, when, and what we are measuring from here.
Stage 09EL. 2,890 M
Iteration Traverse
After launch
The summit is the halfway point. What comes next is where the value shows: handover, measurement, improvement and the next peak along the ridge.
What happens
- Training and handover for your team
- Documentation left in place
- Measurement against true north, then tuning
You leave with
- Cairns: the docs, style guides and runbooks that mark the way
- A list of next peaks, in priority order
Map termCairn. A stack of stones that marks the route for whoever comes next. Ours are documentation.
Sixteen terms we use on every project, and what each one means in plain words. You will hear them on calls and see them in status reports.
- Origin point
- Where every route starts: zero, zero, and one conversation.
- True north
- The single outcome the project steers by.
- Stack check
- An audit of the site, platform, content and data you already have.
- The topo
- The route plan: scope, phases, timeline and estimate, in writing.
- Rope team
- Your people and ours, tied together, with named contacts on both sides.
- Sightline
- What the eye lands on first. Layouts are planned around it.
- Save point
- A review where you sign off and the progress is locked in.
- Crux
- The hardest problem on the route, found early and solved first.
- Bezier bend
- A round of revision. The trail curves back on itself and comes out higher.
- Human belay
- The person holding the rope on every AI-assisted step.
- Changelog
- The report after each phase: what changed and what is next.
- Tech-debt scree
- Loose rock that slows every step. We clear it as we climb.
- API pass
- Where two systems meet. Integrations get their own plan and their own tests.
- False summit
- Something that looks finished and is not. Testing is how we find them.
- Fixed line
- A release process that works the same way every time: staging, checklist, rollback.
- Cairn
- Documentation left to mark the route for whoever comes next.
01.
Your people and ours, with named contacts on both sides and one place where decisions are written down.
02.
AI speeds up the climb. A person reviews, corrects and signs off on every AI-assisted step.
03.
Changes are decided at a review, where their cost in time and budget is visible.
04.
After each phase you get a short report: what changed, what is next and what we need from you.
Dana Point, Orange County, California • hello@creartful.com