the process

a fixed-scope build with decisions at every gate.

You never disappear into a months-long agency process and wait for a reveal. Strategy, direction, build, and launch are approved in sequence, with the scope, price, and definition of done agreed up front.

1. stage 01

   scope the outcome.

   Define the audience, the business result, the required pages and workflows, and what is explicitly outside the build. New ideas that surface mid-build are captured for a follow-up engagement instead of stretching this one.

   deliverable

   A documented SOW: fixed price, fixed scope, a clear timeline, and a definition of done both sides agreed to.

   next · stage 02

2. stage 02

   set the foundation.

   Establish positioning, message hierarchy, identity, and voice — the operating context the site and systems will share. Everything built after this stage inherits from it, which is what keeps the brand, the pages, and the tooling from drifting apart.

   deliverable

   The brand foundation: positioning, identity, and voice, approved before anything is built on top of it.

   next · stage 03

3. stage 03

   design and build together.

   Copy, interface, and tooling are built as one versioned system. You review at defined gates instead of at the very end — no disappearing into a months-long agency process and waiting for a reveal.

   deliverable

   Working increments at every gate, reviewed in a shared engagement workspace where progress, decisions, and deliverables live in the open.

   next · stage 04

4. stage 04

   test the real paths.

   Forms, routing, permissions, analytics, mobile behavior, edge cases, and handoffs get tested — not only the visual polish. The paths your customers will actually take are the ones that get exercised.

   deliverable

   A tested system: every capture form submits, every workflow routes, every analytics event fires.

   next · stage 05

5. stage 05

   launch and transfer ownership.

   Go live on your domain and your accounts, with the engineer who built it on the line during the cutover window. Nothing is held hostage: the credentials, the code, and the content are yours.

   deliverable

   A live system plus documentation, recorded walkthroughs, and full access — owned by you from day one.

   next · stage 06

6. stage 06

   run it yourself or stay on care.

   Operate the system independently, use Content OS to run the weekly content and campaign loop, or keep Floeberg on a month-to-month Care plan for ongoing maintenance and iteration. All three are real options — the build does not depend on a retainer.

   deliverable

   A working system you can run without us — and a standing option for help when you want it.