twelve documents covering the first two weeks of a freelance project, the part where
scope gets decided. Written by someone three years into solo work, in the order the jobs
arrive.

What’s inside: a client intake form (8 sections, 40+ fields, plus the access checklist
that sets your real start date), a one-page scope statement with numbered deliverables,
exclusions, five assumptions and a 7-day acceptance clause, a project brief in 12
sections, a 45-minute kickoff agenda in six timed blocks, a 28-question questionnaire
with a table for reading answers as project risk, a revision policy with the two-round
rule and a pushback script, a payment schedule comparing five structures with a worked
three-milestone example and a reminder calendar, six email templates (lead reply, quote,
paperwork, pre-due nudge, late payment at day 1, 7 and 14, wrap-up with the referral
ask), an offboarding checklist covering money, repo hygiene, access transfer, a
12-column client tracker CSV with 5 filled example rows, and a 28-page printable PDF
binding it all together.

Plain Markdown, so you edit the wording in any text editor and paste it into a proposal
in a minute. No app, no subscription, nothing to install. Amounts and rates stay out:
yours change, the structure does not. Templates, not legal advice. Check deposit and
late-fee rules where your client is registered.

Rules:
- Translate the DESCRIPTIVE words of the title. Leave a token in English only when
it is an actual trademark or invented brand, a published work’s title, or a
technical format such as PDF or SVG.
- A title made of ordinary words describing the item ("Summer prints", "Instant
Download") is NOT a brand — translate it.
- Do not return NAME unchanged unless every one of its tokens is one of the above.
- Preserve all HTML tags and structure in the description
- Keep technical terms in their commonly used form in the target language
- Maintain the same tone and style