← PorchLight free sample · Client Ops Starter Kit

PorchLightFree sample · Client Ops Starter Kit

Free Sample — Client Ops Starter Kit

From: PorchLight · Sample of: Client Ops Starter Kit ($29, one-time) · Version: sample 1.0

This free sample contains two pieces taken directly from the paid kit:

  1. Invoice chase sequence in three tones (Friendly → Firm → Final), with subject lines, a suggested cadence, and an internal log. Source: templates/05-invoice-chase.md.
  2. Proposal AI prompt, a copy-paste prompt that turns discovery-call notes into a structured proposal draft. Source: prompts/proposal.md.

Both are shown as they appear in the kit. The only edit: file references that point to other parts of the kit are labelled as such.

How to use it: replace every [bracketed placeholder] with real details, send one tone at a time, and check names, amounts, and dates before anything goes out.

Not legal advice. These are business drafts. Laws and payment rules vary by jurisdiction. If you rely on a document as binding, have qualified counsel review it. AI-generated drafts are still drafts: you are responsible for what you send. Don't paste confidential client data into AI tools unless your client agreement and the tool's terms allow it.

Part 1 — Invoice chase sequence (from the kit)

Invoice Chase Sequence — [Invoice #] / [Project Name]

To: [Client Name]
Invoice: #[number] · Amount due: $[amount] · Original due date: [YYYY-MM-DD]
Pay link: [URL]
Internal status: [X days past due] · Last contact: [date / note]

Use one tone at a time. Escalate only after your grace window. Never invent legal threats you won’t follow through on.

Suggested cadence (adjust to your SOW):

1. Friendly (nudge)

Subject: Quick nudge — invoice #[number] for [Project Name]

Hi [Name] —

Quick nudge on invoice #[number] for $[amount], due [due date].

Pay here: [pay link]

If it’s already in progress, just reply with the expected payment date and I’ll note it.

Thanks,
[Your name]

2. Firm (clarify + deadline)

Subject: Invoice #[number] is [N] days past due — need a payment date

Hi [Name] —

Invoice #[number] ($[amount]) for [Project Name] is now [N] days past due (original due date [due date]).

Please either:

  1. Pay here: [pay link], or
  2. Reply by [firm deadline date] with a confirmed payment date

I want to keep delivery and support on track; a clear date helps me plan.

Thanks,
[Your name]

3. Final (facts + next steps you will take)

Subject: Final notice — invoice #[number] ($[amount]) before [next step]

Hi [Name] —

This is a final notice regarding invoice #[number] for $[amount], originally due [due date], now [N] days past due.

Pay link: [pay link]

Per our agreement, if payment is not received (or a written payment plan confirmed) by [final deadline date], I will [next step you will actually take — e.g. pause remaining work / withhold final files / close the engagement per SOW].

If there’s a blocker on your side, reply before that date and we can document a short payment plan in writing.

—
[Your name]
[Studio] · [email]

Internal log (do not send)

Date Tone sent Reply / outcome Next action
Friendly
Firm
Final

Pause work? [Y/N — date]
Payment plan notes: [ ]

Part 2 — Proposal AI prompt (from the kit)

AI Prompt — Proposal Draft

Copy everything below the line into ChatGPT, Claude, or similar. Paste your notes in the INPUT block. Review the draft against the proposal template and pre-send QA checklist before sending (both are in the full kit: templates/01-proposal.md, templates/06-pre-send-qa.md).

You are helping a solo freelancer draft a client proposal from discovery notes.

## Tone rules
- Confident, plain English. No hype, no buzzwords, no “synergy / leverage / world-class.”
- Write as the freelancer (first person singular or “I”).
- Be specific. Prefer concrete deliverables over vague promises.
- Never invent metrics, case studies, or timelines the INPUT does not support.
- If INPUT is missing a critical field (price, timeline, or deliverables), insert a clearly marked [NEED FROM YOU: …] placeholder instead of guessing.

## Length cap
- Target under 450 words for the body (sections 1–7). Acceptance block may add a few lines.

## Output format (use these exact headings)
1. Understanding
2. Recommended approach (include a 3-row phase table if phases are implied)
3. Deliverables (bullets) + “Not included” (3 bullets max if known)
4. Timeline (markdown table: Milestone | Target)
5. Investment (markdown table) + payment schedule
6. Working together (contacts, tools, response time, change-order one-liner)
7. Next steps (numbered)
8. Acceptance (short signature / “Approved — please send the SOW” line)

Also output a one-line **Subject suggestion** for the email that carries the proposal.

## INPUT (replace between the markers)
<<<INPUT
Client name:
Company:
Discovery date:
Project / problem (their words):
Goals / success criteria:
Constraints (timeline, budget posture, stakeholders):
Deliverables discussed:
Explicit exclusions (if any):
Proposed timeline / milestones:
Fee / package:
Payment terms (deposit %, milestones):
Your name / studio:
Your email:
Tools you’ll use:
Other notes:
>>>

What's in the full kit

This sample is 2 of the kit's 22 Markdown files. The full Client Ops Starter Kit ($29, one-time) adds:

Format: one ZIP of 22 plain Markdown (.md) files, including the prompt library. Open them in any text editor, or paste the text into Notion, Google Docs or Word. No Notion template, Docs, Word or PDF files are included.

Get the full kit ($29, one-time) on the PorchLight site: https://porchlightkit.pages.dev/?ref=sample-pdf&utm_source=sample-pdf&utm_medium=pdf&utm_campaign=free-sample

Free sample for your own client work. Please don't resell or redistribute it. © 2026 PorchLight. Questions: AddJustin2@gmail.com