Knowledge Base / Management

Management Guide

Keeping promises at scale: the timelines we commit to, how we talk to clients at every stage, and what to do when something goes sideways.

Roles and who owns what

RoleOwnsIs the only one who may…
SellerThe relationship until handoff; add-on conversations at deliveryQuote prices, promise dates (from the SLA table, never invented)
Production managerThe pipeline: schedules, stage gates, QA sign-offDeclare a site ready for client review or launch
Designer / developerThe build meeting the standards, flagging blockers earlyRequest scope clarification (through the PM, in writing)
Owners (the co-founders)Pricing, positioning, exceptions, refunds, strategyApprove discounts, refunds, out-of-policy promises, firing a client
The one-owner rule

Every project has exactly one person the client emails. Clients with two contacts play them against each other; clients with none churn. The seller hands the baton to the PM at kickoff, visibly, in the kickoff email.

Timelines & SLAs (what we may promise)

CommitmentSLANotes
Quote after qualification call24 hoursPublic promise on the website. Never miss it; a late quote kills trust before the project starts.
Starter build (up to 3 pages)5–8 business daysFrom assets-in-hand, not from signature.
Growth build (up to 7 pages)10–15 business daysIncludes booking/lead-capture wiring.
Premium build2–4 weeks, quoted per scopePM sets the date at kickoff after scoping.
Client emails (business hours)Same dayEven if the answer is "looking into it, reply tomorrow".
Care-plan fix (site down / broken)4 business hours to respondDown sites jump every queue.
Care-plan routine edits2 business daysMonthly content edits batch on a set day.
Revision round during review2–3 business daysOne consolidated batch per round.

The delay rule: the moment a date is at risk, the client hears it from us with a new date and a reason. A client who learns about a delay from the calendar instead of from you is a client writing a bad review in their head.

Client communication

The cadence (minimum touchpoints per build)

Client hears from us at least five times per project
KICKOFFday 0 IN PROGRESSmid-build PREVIEWreview day LAUNCHgo-live CHECK-INday +7

Copy-paste templates

Template 1: Kickoff (send within 24h of deposit)

"Hi [name], deposit received, and we're officially building. Here's the plan so you always know where things stand:

What we're building: [package, pages, vibe]. Your preview date: [date]. Launch target: [date].

What we need from you by [date]: [logo / photos / business details]. That's the only homework you'll get.

Your contact for everything from here is [PM name] (this email). Talk soon."

Template 2: Mid-build pulse (no action needed)

"Quick update, no action needed: [site] is in the design/build stage and on schedule for your preview on [date]. Sneak peek attached. More soon."

One screenshot attached. Clients forward these to friends; make the screenshot the coolest section so far.
Template 3: Preview request

"Hi [name], your website is ready to see: [preview link]

Two favors: open it on your phone first (that's where most of your customers will be), and collect all your feedback in one reply if you can. We'll fold in your changes and confirm launch for [date]."

Template 4: Launch

"[domain.com] is LIVE. Go look at it, then send it to someone.

What's already done for you: Google has been notified (Search Console + sitemap), SSL is active, analytics are running, and your contact form has been test-fired.

One question while everything's fresh: want us to keep it fast, secure, and updated for you each month? That's the Care Plan, $99/mo. If yes, you never think about this website again except to answer the leads."

Template 5: Day-7 check-in

"One week live. Quick numbers from your analytics: [visitors] visitors, [leads] form submissions/calls. [One-line observation.]

Anything you'd like adjusted now that it's had real traffic? And if you're happy with how this went: who do you know with a business that needs this? An intro is the best thank-you we can get."

Tone rules for every client message

Escalation: when things go sideways

SituationFirst moveEscalate to owners when…
Project slipping >2 daysPM re-plans, informs client with new date + reason before the old date passesSlip exceeds a week, or it's the second slip on the same project
Scope creepPM logs the request, replies "great idea, here's the quote", keeps building the agreed scopeClient insists the extra work was "included"; disagreement about the written scope
Unhappy client at reviewListen fully, restate their concerns in writing, propose one concrete revision plan with a dateSecond failed review round, refund language, or public-review threats
Non-payment of final 50%Polite reminder at +3 days with the invoice attached; site stays on preview URL until paid+14 days silent, or client disputes the deliverable itself
Site down (care client)Acknowledge within 4 business hours, all hands until restored, post-mortem note to client afterDown >24h, data loss, or a security breach (owners immediately, before the client reply)
Abusive clientStay professional, move everything to writing, do not match toneImmediately. Only owners may fire a client, and they will.
The refund stance (owners' standing policy)

We would rather fix a site twice than argue once. If a client is genuinely unhappy after two honest revision rounds, owners decide between one more round, partial refund, or full refund and part ways. Sellers and PMs never promise refunds themselves; they promise "I'll get you an answer today" and escalate.

Weekly operating rhythm