/home / process
Mission control · live
Flight plan · every mission

The flight plan

Six stages, every time. Pick where you’re headed and the route re-plots: the stages stay the same, the work inside them changes.

T−6
Countdown to launch
Destination · Website
/destinations · 8 services

Pick a destination

Every service is a planet. Pick one and the rest of this page re-plots the route for it.

/trajectory · 6 waypoints

The route

Scroll to fly it. Each waypoint shows what happens, what you get and what I need from you.

T−6
On the pad
T−5 · Pre-flight
1 / 6

Discovery call

A call to learn your goals, your audience and what a win looks like.

For Website
Goals, audience and what the site has to do.
You get
Creative brief
Your part
Share your goals, sites you like and any brand files.
See a mission like this →
T−4 · Flight plan
2 / 6

Alignment

Scope, timeline and content plan agreed before any pixels move.

For Website
Sitemap, content plan and wireframes, signed off before design.
You get
Plan + dates
Your part
Sign off on scope and dates.
See a mission like this →
T−3 · Payload
3 / 6

Brand + assets

Logo, color, type, content and data, gathered or made, then turned into tokens.

For Website
Brand, copy and photos gathered, then turned into design tokens.
You get
Brand kit + tokens
Your part
Send what you have, or tell me to make it.
See a mission like this →
T−2 · Test flight
4 / 6

Prototype

The key pieces, working and clickable, reviewed together before the build.

For Website
Key pages designed in Figma and clicked through as a prototype.
You get
Clickable prototype
Your part
Two rounds of feedback, live or async.
See a mission like this →
T−1 · Assembly
5 / 6

Build

The real thing: built, wired to your content and tested on real devices.

For Website
Built in Webflow from the ground up: components, CMS, motion.
You get
Staging link
Your part
Load content and test on your own devices.
See a mission like this →
T−0 · Launch
6 / 6

Deploy

Go live, connect analytics and hand over a guide so your team owns it.

For Website
QA, a Lighthouse pass, launch day and a walkthrough for your team.
You get
Live + handoff
Your part
Celebrate. Then tell people.
See a mission like this →
/crew · who does what

Crew roles

Two seats in the cockpit. Here is who flies what, so nothing falls between them.

Mission control

Me
  • Plan the route and keep the dates
  • Design and build every piece
  • Write the code and host it on GitHub
  • Tell you early when something changes
  • Hand over the keys, the guide and the files

Crew

You
  • Share the brief and the sites you like
  • Pick one person to make the call
  • Send content, or tell me to make it
  • Give feedback at each checkpoint
  • Tell people when it launches
Comms
Updates at every waypoint
A shared board you can check any time
A real person on the other end
/eta · no guesses

What moves the timeline

Every mission gets real dates after the discovery call. These are the things that stretch or shorten the route.

Scope
How big is it?
A few pagesA full siteA platform
Content
Is the copy ready?
Ready to goPartly thereFrom zero
Brand
Is the brand set?
ReadyNeeds a refreshFrom scratch
3D + motion
Anything custom?
NoneA few momentsA signature piece
Data
Where does content live?
StaticIn a CMSSynced sources
Sign-off
Who makes the call?
One personTwo or threeA committee
Standard orbit

A full route with every waypoint. Most missions fly this one.

Not a quote · real dates come with the flight plan
Short hop

Fewer moving parts and fewer stops. The route goes almost straight from brief to launch.

Standard orbit

A full route with every waypoint. Most missions fly this one.

Deep-space mission

More stops, more people and more custom pieces. Worth it, and planned for from day one.

/faq · before we fly

Flight checks

The questions most crews ask before launch.

How long does a mission take?

It depends on the scope. After the discovery call you get a flight plan with a date for every stage, so you always know what’s next and when it lands.

How is pricing worked out?

Every mission gets a fixed quote once the scope is clear, broken down by stage. The mission planner shows the budget ranges most projects fall into.

What do you need from me?

A clear brief, one person who can make the call, your content (or a plan for it) and feedback at each checkpoint. The “Your part” line on every stage spells it out.

I don’t have copy or photos yet. Is that a problem?

No. That’s what the payload stage is for. I can write the copy, source or art-direct photos, or plan the build around what’s still coming.

How many rounds of changes do I get?

Two rounds of feedback on the prototype, live or async, plus fixes during the build. A bigger change of direction gets planned in, not squeezed in.

What happens after launch?

You get a walkthrough and a written guide, and your team owns the site, the files and the code. If you want help after launch, we plan that too.

/launch · plan this mission

Ready for launch?

Tell me where you’re headed. You’ll hear back with a time for the discovery call, and the countdown starts there.

01
Pick a destination (it follows the star chart)
02
Tell me what you’re launching
03
We book the discovery call
Mission request
Destination · Website
Destinations · up to three stops
Transmission received. Talk soon: the countdown starts with the discovery call.
Signal lost on the way out. Try again, or email me directly.