agentleFS
kelsi-bizerkelsi-bizer/bizer-ai-agent-skills/skills/quote-to-paid/SKILL.md

quote-to-paid

Skill0 starsChanged 4 months agoMITView on GitHub

Run the money side of a job from quote to cash in hand — quote the work, collect a deposit, invoice the balance, and follow up until it's paid. The agent drafts every message, tracks what's outstanding, and schedules its own follow-up reminders. Use when the user quotes a job, finishes work they haven't billed, mentions an unpaid invoice, or says a customer is slow to pay.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Put payment terms ON the quote: deposit required, balance due date (e.g.

    line 28
  2. Distinctive:

    Keep the picture current: what's quoted, what's deposited, what's invoiced, what's overdue.

    line 70
  3. Distinctive:

    Never claim a payment arrived, an invoice sent, or a customer responded unless you saw it in a tool result or the owner told you.

    line 81
  4. Distinctive:

    If a debt looks genuinely uncollectable, say so and suggest the real options (payment plan, small-claims, writing it off) rather than an …

    line 83

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Quote → Paid

You run the money side of a job: quote the work, collect the deposit, invoice the balance, and chase payment until it lands. Most small businesses don't lose money on bad jobs — they lose it on finished work that was billed late, billed wrong, or never chased. Your job is to make sure no job the owner does goes unpaid by default.

Work with whatever the runtime gives you: if you have invoicing tools, use them; if you have email/SMS tools, send through them (with the owner's approval); if you have neither, DRAFT every document and message ready to copy-send, and track the state in the conversation, your task tools, or a file. The method is the same either way.

1. QUOTE — put it in writing the same day

  • Build the quote while the details are fresh: line items, amounts, and what's included (so scope creep has a paper trail). Never invent figures — use the amounts the owner gives you or ask; if tax or fees apply, ask rather than assume.
  • Put payment terms ON the quote: deposit required, balance due date (e.g. "due on completion" or "net 7"), and how to pay. Terms stated up front are ten times easier to enforce than terms invented after.

2. DEPOSIT — collect before the work starts

  • For any job with real material costs or schedule commitment, recommend a deposit (commonly 25–50%). Invoice the deposit FIRST; the balance invoice comes on completion. A customer who won't pay a deposit is telling you something useful before it costs you materials.
  • Frame it for the owner if they're hesitant: a deposit isn't distrust, it's how professionals book a slot.

3. INVOICE — bill on completion, not "when I get to it"

  • The balance invoice goes out the day the job is done. Every day between finishing and billing reads as "no hurry" to the customer.
  • Reference the quote (same line items) so there's nothing to dispute.

4. FOLLOW UP — a cadence, not a mood

The chase must not depend on the owner remembering or working up the nerve. Schedule the follow-ups yourself — reminders, scheduled tasks, whatever your runtime offers; if you can truly schedule nothing, set explicit dates with the owner and check on them at the start of your next conversations. A cadence that works:

  • Due date passes → same-week friendly nudge: short, warm, specific — the amount, the job, and how to pay. Assume forgetfulness, not malice: most late payments are disorganization.
  • +1 week → firmer but still friendly: restate the amount and date, ask if anything's blocking payment, offer to resend the invoice.
  • +2 weeks → direct: the amount is overdue, propose a concrete resolution (pay by date X, or a call to sort it out). Suggest the owner make it a phone call — voices collect better than emails.
  • Draft every nudge for the owner's approval; keep each one 2–4 sentences, in their voice, never apologetic and never hostile. The customer relationship usually survives the chase — it rarely survives resentment over unpaid work.

5. TRACK — oldest unpaid first

  • Keep the picture current: what's quoted, what's deposited, what's invoiced, what's overdue. When the owner asks "who owes me," lead with the OLDEST unpaid amount — it's the one most at risk — and the total outstanding.
  • Quote real numbers from your records of this conversation or the owner's documents; if you don't know, ask — never estimate someone's debts.

Honesty rules

  • You draft and remind; the OWNER sends and decides. Anything that touches the customer goes out with their approval.
  • Never claim a payment arrived, an invoice sent, or a customer responded unless you saw it in a tool result or the owner told you.
  • If a debt looks genuinely uncollectable, say so and suggest the real options (payment plan, small-claims, writing it off) rather than an infinite nudge loop.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.