Skip to content
Creative Marketing AI

After checkout

You paid. Here is exactly what happens next.

Your portal opens within minutes of the payment clearing, and we book a project call. From there it runs in seven stages: we capture your current site, set the design direction, connect your domain, research your competitors, and you approve the plan and the content before anything goes live. Rebuilds are planned around a 30-day launch window when your information, assets, DNS changes and approvals arrive on time. Website care billing starts 30 days after signup — $99/month or $999/year, whichever you picked at checkout.

Timelines are estimates, and billing cycles run independently of delivery. We would rather say that here than surprise you with it later.

Stage 01

Your portal opens, and we get on a call

Your client portal is created the moment the payment clears — the welcome email with your login arrives within minutes, automatically. The portal is where billing, approvals, launch work and content requests all live, so nothing important ends up buried in an email thread. Then we get on a project call to go through the audit, the scope, your assets, the SEO direction, any integrations you need, and the timeline.

What we need from you: Show up to the call, confirm the scope, and hand over the access details.

Stage 02

We capture your current site

We pull your existing pages, images, logo, screenshots and copy so you can read your original text before we optimize anything. You see what we captured, and you tell us what carries over. Existing blog posts are kept as-is unless you ask otherwise.

What we need from you: Tell us what to keep and what to bin.

Stage 03

We set the design direction

We start from a design-system board, the reference patterns for your trade, or a custom direction that came out of your audit. If the logo we find on your current site is low quality, we will ask you for the best file you have.

What we need from you: Pick a direction, and send your highest-resolution logo — an SVG if you have one.

Stage 04

You connect your domain

We walk you through the changes at your registrar, configure Cloudflare, and preserve your email records where we can. This is the step that most often stalls a project, so it is worth doing the day we ask.

What we need from you: Update your nameservers as instructed. You have to do this part — we cannot do it for you.

Stage 05

We research you and your competitors

We compare your services, your wording, your local trust signals and your page structure against the competitors already beating you. That research is what the new site is built from, rather than a template with your name dropped in.

What we need from you: Nothing. This one is on us.

Stage 06

You approve the plan, then the content

You see a wireframe — the first site plan — and either approve the structure or tell us what to change, before any design and build work continues. Later, blog, social and service-area topics are shown to you before anything publishes. If it all looks right, you do not have to do anything.

What we need from you: Approve it, or send specific changes. Silence is the slowest answer.

Stage 07

Launch

Your old web addresses are pointed at the matching new pages with redirects, so existing links and bookmarks keep working instead of turning into dead ends. Rankings can still move around for a while after any rebuild while search engines recrawl the site — the redirect plan is designed to protect the value your current pages have, not to guarantee a position. Analytics goes on as part of launch, not as an afterthought, and publishing is tracked from there.

What we need from you: Final approval, and any last access we are missing.

What pushes the 30 days out

Almost every delayed launch we have had came from this list, and almost all of it is fixable in an afternoon. If you are quick on these, we are quick on the rest.

  • Slow replies — this is the number one cause, by a distance
  • Access we asked for that has not arrived yet
  • Nameserver or DNS changes not made
  • Approvals sitting unread
  • Missing photos, logos or content
  • Changes requested after the scope was approved