{"product_id":"claude-code-agency-client-delivery-system","title":"Claude Code Agency \u0026 Client Delivery System","description":"\u003ch2 id=\"headline\"\u003eTurn Claude Code Into Your Client Delivery System.\u003c\/h2\u003e\n\n\u003cp class=\"sbs-lede\"\u003eA complete operating system for freelancers and agencies to discover, scope, propose, build, review, launch, hand off and retain website clients — as Claude Code commands that read one set of files per client and write into them, with a person between every draft and the client. Not a folder of proposal prompts: 21 modules, 37 commands, 29 templates plus a client-project skeleton, 17 checklists, 12 report shapes, 3 worksheets, four small scripts, and one complete fictional engagement to read before you run your own.\u003c\/p\u003e\n\n\u003ch2 id=\"problem\"\u003eThe problem\u003c\/h2\u003e\n\n\u003cp\u003eMost developers know how to build a website. The engagement around it is where the money and the reputation go: a proposal improvised the night before, a scope that said “and anything else needed”, an estimate that was a guess, revisions that never end because nobody counted the rounds, documentation that lives in a chat thread, a handoff that is a folder of files, and no process for turning a finished project into next month’s income. Each engagement starts from scratch; each one teaches the same lesson again.\u003c\/p\u003e\n\n\u003cp\u003eAsk a capable model to “write a proposal” and you get the other problem: confident prose with invented requirements, a budget the client never stated, a promise about rankings, and a signature block that looks like a contract. Speed without a system produces professional-looking documents that are not professional.\u003c\/p\u003e\n\n\u003ch2 id=\"solution\"\u003eThe solution\u003c\/h2\u003e\n\n\u003cp\u003eA structured delivery system that runs inside Claude Code:\u003c\/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eDISCOVER → SCOPE → PROPOSE → ONBOARD → BUILD → REVIEW → LAUNCH → HANDOFF → RETAIN\u003c\/code\u003e\u003c\/pre\u003e\n\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eOne set of files per client\u003c\/strong\u003e — \u003ccode\u003eclient-config.yaml\u003c\/code\u003e for the facts, \u003ccode\u003eCLAUDE.md\u003c\/code\u003e for the rules, the scope as the contract, and four logs (decisions, assumptions, changes, risks) as the memory. Every command reads them; none invents.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eClaude Code commands\u003c\/strong\u003e for every stage, each marked \u003cstrong\u003eINTERNAL USE\u003c\/strong\u003e or \u003cstrong\u003eCLIENT-FACING\u003c\/strong\u003e, each with its purpose, inputs, required context, steps, business rules, output format and validation — from \u003ccode\u003e\/lead-qualification\u003c\/code\u003e to \u003ccode\u003e\/retainer-opportunity\u003c\/code\u003e, with \u003ccode\u003e\/agency-project-status\u003c\/code\u003e as the one-block summary of any engagement.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eScope discipline as a habit\u003c\/strong\u003e: counts in the scope, an out-of-scope list before the price, acceptance criteria you can test, and \u003ccode\u003e\/scope-change-check\u003c\/code\u003e that classifies any new request in a minute with the reply drafted — calm, because it is arithmetic.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eEvidence over confidence\u003c\/strong\u003e: audits with evidence and a five-level priority system, estimates as ranges with assumptions, readiness with proof, reports where every number names its source and missing data says \u003cem\u003eunavailable\u003c\/em\u003e.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eThe ten operating rules\u003c\/strong\u003e in every command: work within scope, never invent client facts, identify uncertainty, preserve what works, expose no credentials, document changes, validate before done, flag scope creep, promise nothing the evidence does not support, stay professional.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch2 id=\"included\"\u003eWhat is included\u003c\/h2\u003e\n\n\u003cp\u003e201 files, 21 modules, 37 commands, 29 templates, 17 checklists, 12 report templates, 3 worksheets, 4 scripts — about 56,000 words. Every number here was counted from the bundle at build time.\u003c\/p\u003e\n\n\u003cdiv class=\"sbs-table\"\u003e\n\u003ctable\u003e\n\u003cthead\u003e\u003ctr\u003e\n\u003cth\u003eModule\u003c\/th\u003e\n\u003cth\u003eCovers\u003c\/th\u003e\n\u003c\/tr\u003e\u003c\/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e01-lead-qualification\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eFit score with reasons; the unknowns; the questions before unpaid discovery\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e02-client-discovery\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eSix areas — business, website, conversion, content, SEO, technical; the report the client confirms\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e03-client-intake\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eAssets and access with dates; the access inventory that holds no credentials by design\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e04-website-audits\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eTechnical, SEO and conversion audits; issue, evidence, impact, recommendation, effort, priority\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e05-project-scoping\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eThe scope document; counts; out-of-scope; acceptance; the scope check\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e06-estimation-pricing\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eLow \/ expected \/ high with assumptions; the price arithmetic; seven pricing models\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e07-proposals\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eSix proposal shapes; what a proposal must never do; Markdown to PDF without proprietary tools\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e08-client-onboarding\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eOne approver, one channel, the kickoff agenda, the day-for-day rule said out loud\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e09-requirements\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eTwelve sections with a source per requirement; TBD as a value; traceability\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e10-project-planning\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003ePhases, milestones as acceptance points, client inputs with dates, the risk register\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e11-claude-code-project-setup\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eThe workspace and the context Claude Code reads; never overwrites\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e12-build-delivery\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eRequirements → plan → implement → self-review → test → document → review; the definition of done\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e13-client-communication\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eStatus, questions, delays, review and approval requests in three registers; the weekly report\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e14-change-management\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eClassify, four impacts, approve, log — not every change costs money; every change is recorded\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e15-qa\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eSeven areas; PASS \/ PASS WITH ISSUES \/ FAIL; launch blockers named\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e16-client-review\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eBounded rounds; the package; feedback triage into six classes\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e17-launch\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eReadiness with evidence — GO \/ GO WITH WARNINGS \/ NO-GO; the launch report\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e18-handoff\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eThe plain-language document; access transferred, yours removed\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e19-reporting\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eMonthly reports where every number has a source and missing data says so\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e20-maintenance-retainers\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eServices from evidence; the retainer builder; response targets that are not guarantees\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e21-client-offboarding\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eThe clean ending; the retrospective that edits the system; honest testimonials only\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/tbody\u003e\n\u003c\/table\u003e\n\u003c\/div\u003e\n\n\u003cp\u003ePlus \u003ccode\u003e.claude\/commands\/\u003c\/code\u003e with 37 slash commands, \u003ccode\u003etemplates\/\u003c\/code\u003e with 29 templates and the client-project skeleton, 17 checklists, 12 report templates, 3 worksheets, a reference set (project-type overlays for ten kinds of project, Shopify \/ WordPress \/ static workflows, pricing reasoning with hypothetical examples, the client data policy, the communication rules, twelve troubleshooting entries), four standard-library scripts, and \u003ccode\u003eexamples\/example-client-project\/\u003c\/code\u003e — a fictional physiotherapy clinic’s redesign from enquiry to retainer, every file.\u003c\/p\u003e\n\n\u003ch2 id=\"commands\"\u003eThe commands\u003c\/h2\u003e\n\n\u003cdiv class=\"sbs-table\"\u003e\n\u003ctable\u003e\n\u003cthead\u003e\u003ctr\u003e\n\u003cth\u003eCommand\u003c\/th\u003e\n\u003cth\u003eAudience\u003c\/th\u003e\n\u003cth\u003ePurpose\u003c\/th\u003e\n\u003c\/tr\u003e\u003c\/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/lead-qualification\u003c\/code\u003e · \u003ccode\u003e\/client-discovery\u003c\/code\u003e · \u003ccode\u003e\/client-intake\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eInternal → client\u003c\/td\u003e\n\u003ctd\u003eFit score; the six-area discovery report; assets and access with secure methods\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/technical-audit\u003c\/code\u003e · \u003ccode\u003e\/seo-audit\u003c\/code\u003e · \u003ccode\u003e\/conversion-audit\u003c\/code\u003e · \u003ccode\u003e\/client-website-audit\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eInternal → client\u003c\/td\u003e\n\u003ctd\u003eEvidence-based findings; the combined report with an executive summary\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/client-scope\u003c\/code\u003e · \u003ccode\u003e\/scope-change-check\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eInternal → client\u003c\/td\u003e\n\u003ctd\u003eThe scope document; IN SCOPE \/ AMBIGUOUS \/ OUT OF SCOPE for any request\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/project-estimate\u003c\/code\u003e · \u003ccode\u003e\/generate-proposal\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eInternal \/ client\u003c\/td\u003e\n\u003ctd\u003eA range with assumptions; one of six proposal templates filled from the files\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/client-onboarding\u003c\/code\u003e · \u003ccode\u003e\/setup-client-project\u003c\/code\u003e · \u003ccode\u003e\/requirements-document\u003c\/code\u003e · \u003ccode\u003e\/project-plan\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eMixed\u003c\/td\u003e\n\u003ctd\u003eThe start: approver, channel, kickoff, workspace, requirements with sources, the plan\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/delivery-workflow\u003c\/code\u003e · \u003ccode\u003e\/client-project-qa\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eInternal\u003c\/td\u003e\n\u003ctd\u003eThe build loop against the definition of done; seven-area QA with blockers\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/client-status-update\u003c\/code\u003e · \u003ccode\u003e\/weekly-client-report\u003c\/code\u003e · \u003ccode\u003e\/client-question\u003c\/code\u003e · \u003ccode\u003e\/client-delay-notice\u003c\/code\u003e · \u003ccode\u003e\/client-review-request\u003c\/code\u003e · \u003ccode\u003e\/client-approval-request\u003c\/code\u003e · \u003ccode\u003e\/client-meeting-summary\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eClient-facing drafts\u003c\/td\u003e\n\u003ctd\u003eProfessional, concise, no blame, no promises; nothing sent automatically\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/change-request\u003c\/code\u003e · \u003ccode\u003e\/client-feedback-triage\u003c\/code\u003e · \u003ccode\u003e\/client-review-package\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eMixed\u003c\/td\u003e\n\u003ctd\u003eFour impacts and approval; six feedback classes; bounded review rounds\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/client-launch-readiness\u003c\/code\u003e · \u003ccode\u003e\/client-launch-report\u003c\/code\u003e · \u003ccode\u003e\/client-handoff\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eMixed\u003c\/td\u003e\n\u003ctd\u003eGO \/ GO WITH WARNINGS \/ NO-GO with evidence; the record; the plain-language handoff\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/monthly-client-report\u003c\/code\u003e · \u003ccode\u003e\/retainer-opportunity\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eClient-facing\u003c\/td\u003e\n\u003ctd\u003eSourced numbers; services the site needs, with evidence\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/client-offboarding\u003c\/code\u003e · \u003ccode\u003e\/project-retrospective\u003c\/code\u003e · \u003ccode\u003e\/project-estimate-review\u003c\/code\u003e · \u003ccode\u003e\/case-study-draft\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eMixed\u003c\/td\u003e\n\u003ctd\u003eThe clean ending; the lessons as edits; estimate vs actual; a draft from facts only\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e\/agency-project-status\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eInternal\u003c\/td\u003e\n\u003ctd\u003e\n\u003cstrong\u003eThe master summary.\u003c\/strong\u003e Phase, status, every stage, blockers, client actions, risks, next five actions; \u003ccode\u003eproject-status.json\u003c\/code\u003e\n\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/tbody\u003e\n\u003c\/table\u003e\n\u003c\/div\u003e\n\n\u003ch2 id=\"usecases\"\u003eUse cases\u003c\/h2\u003e\n\n\u003cul\u003e\n  \u003cli\u003eTurn discovery notes into a professional scope with counts, an out-of-scope list and acceptance criteria.\u003c\/li\u003e\n  \u003cli\u003eGenerate a proposal from a technical audit — findings become priority actions, priority actions become scope.\u003c\/li\u003e\n  \u003cli\u003eDetect whether a new request is scope creep, and reply in a minute without an argument.\u003c\/li\u003e\n  \u003cli\u003eCreate client status reports in minutes from the tracker, with the client’s actions and dates in their own section.\u003c\/li\u003e\n  \u003cli\u003eBuild a repeatable QA process that runs before every client review and again before launch.\u003c\/li\u003e\n  \u003cli\u003eCreate a professional client handoff in plain language, with every access transferred and none of yours left behind.\u003c\/li\u003e\n  \u003cli\u003eTurn completed projects into legitimate maintenance retainers built from what the site actually needs.\u003c\/li\u003e\n  \u003cli\u003eStandardise delivery across every client project, and improve it with each retrospective.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch2 id=\"who\"\u003eWho it is for\u003c\/h2\u003e\n\n\u003cp\u003eFreelance web developers; small web agencies; DevOps and technical consultants; Shopify developers; WordPress developers; AI-first agencies; solo technical founders; developers entering consulting. It assumes you can build the site. It does not assume you have run a client engagement before — the modules are written for a first one, and the example is a whole engagement you can read end to end.\u003c\/p\u003e\n\n\u003ch2 id=\"safety\"\u003eSafety and honesty\u003c\/h2\u003e\n\n\u003cp\u003eNo credentials in any file, ever: access is granted by platform invitation and recorded as present or missing. No invented client facts, budgets or metrics: TBD is a value, and a report says \u003cem\u003eunavailable\u003c\/em\u003e rather than guessing. No promised rankings, conversion increases, revenue, or launch dates while an input is outstanding. Nothing is sent to a client by a command; a person reads and sends. Testimonials are asked for honestly and never written for the client; case studies use only the facts in the files.\u003c\/p\u003e\n\n\u003cp\u003eAnd plainly: this is not legal, accounting or tax advice. Proposals are not contracts, scope documents do not replace agreements, retainer templates describe services rather than terms, and the pricing examples are hypothetical reasoning, not rates.\u003c\/p\u003e\n\n\u003ch2 id=\"compare\"\u003eHow it fits with the other six\u003c\/h2\u003e\n\n\u003cp\u003eThis is the engagement layer. The other products are the technical layers it sells and delivers with, and each is separate — buying one includes none of the others.\u003c\/p\u003e\n\n\u003cdiv class=\"sbs-table\"\u003e\n\u003ctable\u003e\n\u003cthead\u003e\u003ctr\u003e\n\u003cth\u003eWith\u003c\/th\u003e\n\u003cth\u003ePrice\u003c\/th\u003e\n\u003cth\u003eThe engagement it makes deliverable\u003c\/th\u003e\n\u003c\/tr\u003e\u003c\/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ca href=\"\/products\/claude-code-website-launch-system\"\u003eWebsite Launch System\u003c\/a\u003e\u003c\/td\u003e\n\u003ctd\u003e$19.99\u003c\/td\u003e\n\u003ctd\u003eBuilding client websites — the build inside the delivery workflow\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ca href=\"\/products\/claude-code-seo-website-audit-toolkit\"\u003eSEO \u0026amp; Website Audit Toolkit\u003c\/a\u003e\u003c\/td\u003e\n\u003ctd\u003e$19.99\u003c\/td\u003e\n\u003ctd\u003eSEO audit engagements — the deep audit behind the audit-and-build proposal\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ca href=\"\/products\/claude-code-conversion-revenue-optimization-toolkit\"\u003eConversion \u0026amp; Revenue Optimization Toolkit\u003c\/a\u003e\u003c\/td\u003e\n\u003ctd\u003e$19.99\u003c\/td\u003e\n\u003ctd\u003eConversion optimisation engagements\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ca href=\"\/products\/claude-code-website-operations-maintenance-system\"\u003eOperations \u0026amp; Maintenance System\u003c\/a\u003e\u003c\/td\u003e\n\u003ctd\u003e$39.99\u003c\/td\u003e\n\u003ctd\u003eMonthly maintenance retainers — the delivery side of the retainer you design here\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ca href=\"\/products\/claude-code-website-migration-replatforming-system\"\u003eWebsite Migration \u0026amp; Replatforming System\u003c\/a\u003e\u003c\/td\u003e\n\u003ctd\u003e$29.99\u003c\/td\u003e\n\u003ctd\u003eMigration projects — the technical work behind the migration project type\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ca href=\"\/products\/claude-code-shopify-automation-admin-api-toolkit\"\u003eShopify Automation \u0026amp; Admin API Toolkit\u003c\/a\u003e\u003c\/td\u003e\n\u003ctd\u003e$39.99\u003c\/td\u003e\n\u003ctd\u003eOngoing Shopify catalogue operations as a retainer\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/tbody\u003e\n\u003c\/table\u003e\n\u003c\/div\u003e\n\n\u003cp\u003eThe first three are also sold together as the \u003ca href=\"\/products\/complete-site-builder-stack\"\u003eComplete Site Builder Stack\u003c\/a\u003e. This product is not in any bundle; there is no automatic upgrade credit.\u003c\/p\u003e\n\n\u003ch2 id=\"delivery\"\u003eDelivery and licence\u003c\/h2\u003e\n\n\u003cp\u003eA single ZIP, delivered by download immediately after purchase. 201 files, about 240 KB — Markdown, CSV, YAML, JSON and four small Python scripts; nothing to install beyond Python 3, which your machine almost certainly has. A published SHA-256 checksum accompanies the download so you can verify what you received.\u003c\/p\u003e\n\n\u003cp\u003eLicensed to one person for unlimited clients, including branding the client-facing documents as your own. You may not redistribute or resell it, or sell the templates as a competing product. Full terms are in \u003ccode\u003eLICENSE.md\u003c\/code\u003e inside the archive.\u003c\/p\u003e\n\n\u003ch2 id=\"notpromised\"\u003eWhat is not promised\u003c\/h2\u003e\n\n\u003cp\u003eNo client, no signature, no renewal, no profit. The system makes each engagement clearer, more repeatable and better documented; whether a prospect says yes, what you charge, and how the project goes are yours — and it is built so that they stay yours and are written down.\u003c\/p\u003e\n","brand":"Site Builder Stack","offers":[{"title":"Default Title","offer_id":56283051753764,"sku":"SBS-CCACDS-V1","price":39.99,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0987\/3925\/7636\/files\/product-agency-system.png?v=1789354123","url":"https:\/\/sitebuilderstack.com\/products\/claude-code-agency-client-delivery-system","provider":"Site Builder Stack","version":"1.0","type":"link"}