ForX

How it runs

Discipline is the deliverable.

Every ForX engagement runs the same five steps, with written approval gates between them — so you always know where the build stands and what ships next.

The five steps

The same five steps, every build.

Discover, plan, build, launch, support. The scope changes with the package; the order and the gates don't. Here's what each step covers and what you approve before the next one starts.

Step 01 · Discover

We learn the business before we open a tool.

Discovery covers the business itself — what you offer, the goals behind the launch, the audience you're trying to reach, the assets you already have, and what your launch actually needs. Nothing is designed here. The point is to make every later decision smaller.

  • business + goals
  • audience
  • current assets
  • launch needs

Step 02 · Plan

Nothing is designed until the plan is on paper.

We map the website, the systems and tools behind it, the vendors involved, the content plan, and the launch path — one document you can read and question. The step closes at the sitemap approval gate: you sign off on what the site is before design begins.

  • sitemap
  • systems + tools
  • vendors
  • content plan
  • launch path
  • gate: sitemap approval

Step 03 · Build

You approve the design before it becomes the build.

We design and build the site, forms, automations, and integrations the plan calls for. The design approval gate sits inside this step — you approve the direction before we commit it to code, and changes after that point go through a written change order.

  • design
  • site build
  • forms
  • automations
  • integrations
  • gate: design approval

Step 04 · Launch

Nothing goes live without your written go-ahead.

We prepare the presence, connect the tools, and walk the finished build with you in a final review. Go-live happens only after final review approval and your written launch authorization — and we stay on hand through the launch itself.

  • presence prep
  • tool connections
  • gate: final review
  • gate: launch authorization
  • go-live support

Step 05 · Support

Go-live is a step, not the end of the work.

After launch we keep improving, updating, and optimizing — new pages, campaign help, CRM and automation improvements, and ongoing strategy from a partner who already knows how your business is built.

  • updates
  • new pages
  • optimization
  • ongoing strategy

Approval gates

Why nothing ships by surprise.

Four gates run through every build, and each one is yours to open. Work pauses at a gate until you approve it in writing — so the site that launches is the site you signed off on.

  • +Written, not remembered — every approval is recorded, so both sides can point to exactly what was agreed.
  • +Written change orders — when scope changes, the change is documented and priced before the work happens. No silent additions, no surprise invoices.
  • +One decision maker — one person on your side owns approvals, which keeps the build fast and the accountability plain.
  • +Decisions sit where change is cheap — a sitemap is easier to revise than a design, and a design is easier to revise than a build. Each gate puts the decision at the point where changing your mind costs the least.

The four gates

  1. Sitemap approval
    You approve what the site is — pages, structure, purpose — before design begins.
  2. Design approval
    You approve the design direction before it becomes the build.
  3. Final review
    You review the finished build, end to end, before launch prep completes.
  4. Launch authorization
    Your written go-ahead. Nothing goes live without it.

The division of labor

What you bring. What we carry.

A build moves at the speed of its inputs. This is the honest split — what only you can supply, and what we take off your plate.

What you bring

  • +Content — the words, photos, and facts only you have: what you offer, who it serves, what makes it credible. We shape it into pages; you supply the raw material.
  • +Decisions — timely answers when a choice is yours to make. Open questions stall builds faster than hard problems do.
  • +Approvals — sign-off at each gate, from your one decision maker.
  • +Access — domain, hosting, email, and any existing tools. We tell you exactly what we need and when.

What we carry

  • +Strategy — the plan, the sequence, and the reasoning behind both.
  • +The build — design, development, forms, automations, and integrations.
  • +Coordination — vendors, tools, and handoffs to qualified professionals when legal, tax, or filing decisions come up.
  • +The checklist nobody enjoys — DNS, redirects, form tests, tracking, backups, and the other small items launches tend to forget.

Timelines

How long it takes.

As a working range, essential builds often run about 3–6 weeks and larger builds 6–10 weeks or more — depending on content, approvals, and access, the things only you can supply.

Those are patterns, not promises. Your proposal states your scope, your gates, and your dates.

Want to try the process first?

A ForX Launch Audit is the Discover step as its own engagement — a focused read on your idea, presence, tools, and launch needs, with a recommended next step. No obligation to build.

Start With a Launch Audit