craft_digital
Playbook 05 · Interactive builder

SOP Decisions to Confirm

Settle every open default — in one pass.

Each item below shows the working default from the playbooks plus realistic alternatives. Pick the one that fits, or write your own. Your answers are saved automatically to this device — export when ready and the affected playbooks get updated to match.

Progress
0/28

Section 1

Pricing & Payment

How money moves in and what the qualification bar is.

1.1

Build payment structure

Current default50% deposit on signing, 50% on delivery/launch.
Why it mattersSets cashflow risk. Bigger deposit = less exposure if a client ghosts mid-build. Milestone splits keep clients engaged but add invoicing overhead.

Pick one

1.2

Build balance trigger — what the final invoice is due on

Current defaultDue on delivery / launch.
Why it mattersLocks down the moment the second invoice is enforceable. "Delivery" can be argued; written acceptance can't.

Pick one

1.3

Minimum engagement (qualification bar)

Current default~$30k (sometimes a ~$15k build + ongoing management).
Why it mattersFilters discovery time. Too low and the team is buried in tiny builds; too high and you miss good seed clients.

Pick one

1.4

Referral incentive

Current defaultNone specified (placeholder).
Why it mattersReferrals are our highest-converting channel. A formal incentive makes it easy to ask.

Pick one

Section 2

Sales / Front-End

2.1

Pre-engagement form reach

Current defaultSent to everyone; lighter version for warm referrals, full version for others.

Pick one

2.2

Internal proposal sign-off

Current defaultClinton signs off commercials; Derek confirms timeline/feasibility, before any proposal goes out.

Pick one

2.3

Follow-up cadence after SOW sent

Current defaultDay 0 send, Day 2 check-in, Day 5 nudge, Day 9 direct close.

Pick one

Section 3

SOW Contract Terms

3.1

Managed-infrastructure minimum term

Current defaultPlaceholder — needs setting.
Why it mattersProtects ROI on onboarding effort. Most agencies land at 6 or 12 months.

Pick one

3.2

Cancellation notice period (after minimum term)

Current defaultPlaceholder — needs setting.

Pick one

3.3

How the Kickoff Date is set

Current defaultScheduled "promptly after the deposit is received."

Pick one

3.4

Client response window

Current defaultPlaceholder — e.g. two business days.

Pick one

3.5

Client approval window (per milestone)

Current defaultPlaceholder — e.g. three business days.

Pick one

3.6

Legal review of SOW Standard Terms

Current defaultRecommended before first use.

Pick one

Section 4

Delivery

4.1

Response-time standards

Current defaultCritical 2h · High same business day · Medium next business day · Low within 3 business days.

Pick one

4.2

Change-order timing standards

Current defaultAcknowledge 4h · assess 24h · options 48h · written approval before work.

Pick one

Section 5

Client Health & Growth

5.1

External feedback scales

Current default1–5 value/expectations pulse during build; 0–10 NPS during managed infra.

Pick one

5.2

Feedback cadence

Current defaultBuild pulse at kickoff / mid-build / go-live; NPS at 30 days post-launch and each QBR.

Pick one

5.3

Internal account pulse cadence

Current defaultEvery two weeks during a build, monthly during managed infrastructure.

Pick one

Section 6 — New in v2

Operations & Access

Billing problem-handling and who holds admin on every tool.

6.1

Dunning timeline (payment-failure reminders)

Current defaultDay 1 friendly, Day 3 second, Day 7 firmer, Day 14 final.
Why it mattersTighter cadence recovers more invoices but risks burning goodwill; looser is gentler but lets bad debt accumulate.

Pick one

6.2

Service-pause threshold (unpaid managed infrastructure)

Current defaultPause at 14 days past due.
Why it mattersThe point at which we stop running their infrastructure for free. Needs to be written so it can actually be enforced.

Pick one

6.3

ACH grace window

Current defaultNot set — should ACH returns get longer grace than card declines?
Why it mattersACH returns can take days to settle; treating them like card declines may unfairly flag clients whose payment is still in-flight.

Pick one

6.4a

Tool admin — Craft Brain

Current defaultNot assigned.
Why it mattersEvery tool needs a named primary and backup so nothing locks up if someone is out.

Pick one

6.4b

Tool admin — cal.com

Current defaultNot assigned.

Pick one

6.4c

Tool admin — Lovable

Current defaultNot assigned.

Pick one

6.4d

Tool admin — Stripe

Current defaultNot assigned.

Pick one

6.4e

Tool admin — Mercury

Current defaultNot assigned.

Pick one

6.4f

Tool admin — Slack

Current defaultNot assigned.

Pick one

6.4g

Tool admin — Google Drive

Current defaultNot assigned.

Pick one