← Back

Skills · digital agency

Skills for the marketing agency.

The same method applied to a business with almost nothing operationally in common with a donut shop: departmental P&L, revenue recognition off a billing sheet, monthly billing and collections, and a partner deck every month.

Most of these now post straight to QuickBooks through an MCP connection, but only after I approve that specific entry. The skill shows me the draft, I say yes, it posts, and then it reads the entry back to prove it landed the way it was built. The one agent that writes to QuickBooks on its own can only create bills from invoices a teammate has already approved — it can’t edit, pay or delete anything.

Close & reporting

monthly-financial-package

Refreshes the monthly financials workbook from QuickBooks, then builds the ~31-slide partner deck out of it — every dependent tab updated, headcount reconciled against payroll, and four partner personas pressure-testing the deck before it reaches a real partner's inbox.

Replaced Five separate spreadsheets kept by hand, figures pasted into slides as screenshots, and commentary written from scratch — three to four hours of production work every month.
  • Produces The refreshed workbook and the partner deck, with a PDF preview to review before anything is shared
  • You step in A hard stop before the deck is built, until the workbook is confirmed final
  • Read more The full case study →
cash-basis-pl

Builds a monthly cash basis P&L with client ad spend taken out of both sides — the client money coming in and the media bills going out. It rebuilds every bank transaction from the ledger, one row per transaction per account, and each account has to tie to its own balance sheet change to the penny before a single row gets classified.

Written rules settle the judgment calls, because judgment that lives in someone's head gets applied differently in March than in August. Interest counts when the bank deposits it, so moving it later never counts it twice. Commission counts when it moves into operating, since until then it is sitting mixed in with client money.

Replaced A cash basis file where ad spend came out row by row or through hard-coded subtractions.
  • Fires on "do the cash basis P&L for October"
  • Produces The month's tab with a detail view, support tabs for ad spend and exclusions, and a year-to-date reconciliation that has to net to zero
  • Guardrails Closed months never change quietly. Before building a new month it re-checks every closed month against the ledger, and any late entry, edited amount or re-dated deposit comes to you as a table first, with the effect on that month's number
  • You step in Deciding whether to restate a closed month, and ruling on anything it flags

Journal entries

payroll-je

Builds the semi-monthly payroll journal entry as a QuickBooks import, pulling payroll straight from the provider's API rather than from a manual check entry. It reads paystubs, fees and member departments, converts cents to dollars, and aggregates earnings, deductions, employer contributions and workers' comp into a balanced entry that credits the operating bank account for the invoice total. Non-executive rows map to salary and wages by department; executive rows map to their own accounts and classes.

It exists because the native payroll-to-QuickBooks sync maps executive compensation wrong. The import format is a spec arrived at after six failed attempts — leaf account number plus full qualified path, currency on every row, fully qualified classes, and a plain numeric journal number repeated on every line.

Replaced A lot of Excel. Different ledger accounts and classes at the employee level, and the payroll provider's own overrides weren't deep enough to express it — so the mapping got rebuilt by hand each run.
  • Fires on "book payroll", "make the payroll JE", or naming a pay date with booking intent
  • Produces The posted entry, read back line by line, with a link to it and an Excel backup to attach — plus a tie-out summary and a list of everything it flagged rather than guessed at. The import CSV is now the fallback
  • Guardrails Non-negotiable tie-outs run before delivery: debits less expense credits must equal the company debit, salary buckets must equal gross pay, tax buckets must equal employer taxes, fees must tie to the fee list
  • You step in Every reimbursable expense, owner health premium, unknown deduction or earning type, changed department, and unrecognized executive is flagged before anything posts. Nothing posts until you say yes to that specific payroll. The first direct post was the 10/15/26 run
monthly-rev-rec-je

Turns the month's billing sheet into a balanced draft revenue-recognition entry, then converts that draft into an import file once it's been reviewed. It reads only the rows tagged for rev rec, finds columns by header name rather than position because they move between months, and reads the human-written finance notes to derive hours and rate per performing department. It debits where the revenue was billed and credits the department that did the work, carrying the client tag, a derived class, and the originating row numbers.

Replaced Hand-creating zero-dollar invoice records in QuickBooks to move revenue in and out of departments — one at a time, every month.
  • Fires on "build the rev rec JE for May", or pasting a billing-sheet link alongside any mention of revenue recognition
  • Produces Phase one, a two-sheet Excel draft — JE lines with flagged rows highlighted, a balance check, and a backup sheet tying every line to its source row. Phase two posts the entry and reads it back, with a names-to-verify list alongside it
  • Guardrails Scope is decided solely by the tag, even when other rows discuss rev rec at length — those flow through rev rec invoices and would double-count. One month is kept as a regression anchor with expected row, entry and line counts recorded, so a run that drifts is caught immediately
  • You step in The draft is the review gate. Phase two never runs until you've approved phase one, and one approval covers one month. The CSV is only for when the connection is down

Billing & collections

Billing week is where the money is either captured or quietly lost. These four cover the month's biggest billing run, the invoice before it goes out, the chase when it comes back late, and the cash when it finally arrives.

paid-media-billing

Runs the month-end paid media management fee billing end to end. It reconciles every client's ad spend against the spend source to the penny, independently recomputes every fee in code from the pricing rules — tiers, minimums, caps, and the aggregates where several brands bill as one family — and reports any row where its own calculation disagrees with the sheet.

Then it drafts each invoice by cloning that client's prior-month one, so terms, billing contacts, purchase order fields and line formatting carry forward instead of being retyped. It shows me a table and creates nothing until I approve it. After approval it creates the invoices, never sends them, writes each invoice back to the sheet as a link, and checks the posted result against what was asked for — date, amount, and description, line by line. The last step ties the fee income account to the sheet total within a penny.

The guardrail that matters most is a blank cell. Where a family of brands bills on aggregate spend, the parent row has to stay empty; a number there gets counted twice, which inflates total spend and — because the tiers run the other way — quietly drops the whole family into a cheaper rate. Nothing about the sheet would look wrong, so the skill checks for it every month.

Replaced The paid media half of the billing platform I spent sixty hours building and then killed. This is what that work turned into: not an application, just the process written down well enough to run.
  • Fires on "run paid media billing", "do the October paid media invoices", or a link to the billing sheet with month-end intent
  • Produces The spend reconciliation, an independent fee calculation, the drafted invoices for review, and after approval the created invoices linked back into the sheet
  • Guardrails It re-reads the sheet immediately before every write, because inserting or removing a client shifts every range below it. It will not move past a phase with an open discrepancy without a ruling from me
  • You step in Approving the draft table before anything is created, and sending. It never sends an invoice
  • Read more The app this replaced →
invoice-review-sweep

Reviews every invoice created during monthly billing against the billing sheet and the ledger, using a fifty-three point checklist built up from real billing runs and the bookkeeper's own rules. It reads the invoice lines, the project manager's notes, the linked estimate and last month's row, then redoes the hours math and shows the arithmetic inside each finding. Findings land on a review page in three tiers: block, fix before close, and advisory.

Before it calls anything a fix, it does one extra read that could disprove the finding. A reviewer who cries wolf gets ignored, which is worse than no reviewer at all.

Replaced A manual second pass after billing, re-checking every invoice against the sheet by hand.
  • Fires on "run the invoice review", "sweep the billing sheet", or the scheduled sweep that runs every two hours during billing week
  • Produces A review page showing invoices produced, left to create and waiting on PMs, the findings by tier with the math shown, the open rev rec worklist, and what changed since the last sweep
  • Guardrails It never touches the ledger, and the only edit it makes to the billing sheet is adding links. When a PM's stated hours and the invoice disagree, it names the PM and leaves the item open rather than reasoning its way to an answer from the sheet
  • You step in Every finding is yours to resolve or park. The skill never clears its own flags
ar-collections-email

Drafts a past-due chase for one client: a short email and a one-page statement of every open invoice. The email carries two numbers — total outstanding and amount overdue — and nothing else. It never says when an invoice passed terms, because invoices sometimes go out late and that framing starts an argument you cannot win. The statement ages each invoice against the due date printed on it, so it matches the document the client is actually holding.

Replaced Building each statement by hand off the aging report.
  • Fires on "chase this client", "draft a collections email", or picking a client on the collections dashboard
  • Produces A draft email with the bookkeeper copied, the statement attached, and a dated entry in the outreach log so the next chase starts from what was already sent
  • Guardrails The open invoices have to sum to the client's ledger balance before it drafts anything. It reads the figures back out of the finished statement, checks the aging buckets sum to the overdue total, and confirms the attachment is the same file it saved
  • You step in Nothing sends on its own. You read the draft and press send
remote-check-deposits

Records a batch of customer checks deposited by phone. It reads every check — payer, check number, the amount in numbers and again in words, memo, and any remittance stub — confirms the two amounts agree, and matches each check to open invoices. A check with no invoice number only gets applied when the open invoices on a single project add up to it exactly. Anything else gets flagged rather than guessed.

Then it stops and shows the plan. After I approve, it re-checks the invoice balances in case someone recorded a payment in the meantime, posts one payment per check, and reads each one back. It also crops each check out of the scan and names the image by invoice, payer, check number and amount.

Replaced Keying each check in by hand, hunting for the invoice behind the ones with no reference, and saving the images one at a time.
  • Fires on Sharing a scan of deposited checks, or "record these checks"
  • Produces Posted payments with links, named check images, and a tie-out of the check total to the applied total
  • Guardrails Short pays, overpays and anything that would leave money unapplied get flagged for you to decide. It looks for each check among recent payments first, so nothing is recorded twice
  • You step in Approving the application before anything posts, and attaching the images

Reconciliation

prepaid-reconciliation

Ties one month's column of the prepaid expenses amortization schedule to the general ledger and explains any variance transaction by transaction. It pulls month-end balances from the accrual balance sheet, compares the schedule against the ledger, and walks back through prior months to find where the break started — then queries journal entries, bills and purchases to isolate the lines that actually drove it.

The usual culprit is timing on new subscriptions: a renewal bill or card charge dated late in the month hits the ledger, but the schedule keeper parks the setup in the following month's column. A few cents of residual is normal penny rounding on the monthly amortization entries and isn't worth chasing.

Replaced Comparing two Excel files by hand with lookups.
  • Fires on "reconcile the May column", "tie out the prepaid schedule", "why doesn't column O match"
  • Produces A report giving the schedule balance, the ledger balance, the variance, the specific transactions driving it, and the recommended correction — or a written reconciliation memo on request
  • You step in It reports and recommends; it only writes corrected figures into the schedule if you ask
balance-sheet-reconciliation

Builds the monthly balance sheet reconciliation. It copies last month's workbook, loads the balance sheet in its export format, and reconciles each supporting tab: receivables and payables aging, undeposited funds, fixed assets, accrued expenses, and unearned revenue by customer and project. It ties the linked schedules for prepaids, PTO and the ad spend liability without editing them.

It checks completeness the hard way: every account carrying a balance has to have a row on the summary, because a lookup that defaults to zero will quietly hide one that doesn't. Unearned revenue gets a year-to-date check row by row, since an entry on the wrong project still leaves the total tying. The last step compares every account to the trial balance in code.

Replaced Rolling a twelve-tab workbook forward by hand every month.
  • Fires on "do the September balance sheet rec", or last month's file with roll-forward intent
  • Produces The month's workbook with every tie-out cell at zero, plus a short list of what needs a decision — aged receivables, undeposited items, missing accruals, negative unearned rows
  • Guardrails It never posts, so adjusting entries come back as proposals. Every number is verified in code and every variance gets named, rounding included
  • You step in Approving any adjusting entry, and deciding what to do about what it surfaces
ad-spend-tracker-monthly-roll

Rolls the client ad spend liability reconciliation into a new month inside the main workbook. It duplicates last month's tab, pulls the month-end balance sheet into a companion tab, and rebuilds the invoice lists, the vendor bills coded to the liability accounts, and each client's balance from their own spend tracker. Before writing anything it simulates the tracker lookups in code, so it knows what every cell should say before it says it.

The tab explains its own cash variance. It lists tracker spend not yet billed and client payments still sitting in operating, and keeps going until the line labelled unexplained reads zero.

Replaced Building each month's tab by hand, then re-downloading and pasting a fresh balance sheet every time something changed.
  • Fires on "roll the ad spend tracker to November", or the first days of a new month
  • Produces The new month tab and its balance sheet tab, variance explained to zero, and a short report of what changed since last month
  • Guardrails It never edits last month's tab or a client's own tracker. It reports problems in either one and leaves them alone
  • You step in Anything that doesn't tie — a tracker whose balance formula was never extended into the new month, for instance

Variance analysis

Two skills, deliberately split. The expense one drills to vendor; the revenue one drills to client. If the account is income, the revenue skill supersedes.

flux-analysis

Runs a month-over-month flux on any expense account or account group, drilled to vendor and transaction level. It maps a plain-English category to real accounts, pulls the P&L for both periods to set the reconciliation target, then queries all three sources that post to expense accounts — card charges, AP bills, and journal entries carrying the monthly amortization of annual prepaid software. It handles the credit flag on purchases, signs journal entries by posting type, and infers vendors for journal entries from line descriptions.

The hard rule is that nothing is produced until all three sources reconcile exactly to the P&L. Amortization entries are the source most easily forgotten, which is why the reconciliation is a hard gate rather than a check.

Replaced Side-by-side Excel comparisons stitched together with lookups.
  • Fires on "what changed in professional fees last month", "what changed in marketing spend in Q2", "compare hosting costs October vs November"
  • Produces A four-tab workbook — summary with a written narrative and top-ten preview, full vendor detail sorted by absolute delta, every underlying transaction as an audit trail, and a methodology tab documenting scope and caveats
  • Nuance A vendor appearing as both a cash charge and an amortization entry gets two rows so the distinction stays visible. Vendors with no prior-period baseline are marked NEW rather than showing an infinite percentage. Renewals are timing, not real change
  • You step in Scope confirmation up front — which accounts the category means, which two periods, accrual or cash basis
revenue-flux-analysis

The income counterpart, drilled to client rather than vendor. It maps plain-English revenue terms to account families, sources by-customer revenue from a transaction-detail export, pulls client names out of commission journal-entry descriptions where the name field is blank, and rolls sub-jobs up to the parent client against a canonical list. It can corroborate a movement with logged hours rather than leaving it as a guess.

Each period has to tie to the penny before the workbook gets built. A zeroed-out client isn't automatically a loss and a new one isn't automatically a win — the hours tab is there so you can tell which.

Replaced The same side-by-side Excel lookups, on the income side.
  • Fires on "explain the change in analytics income", "which clients drove the development revenue change"
  • Produces A four-tab workbook plus an optional fifth putting logged hours beside revenue by client, with project-level detail underneath
  • Nuance A service team logs across project types, so total team hours per client won't be one-to-one with a single income account — which is why project-level detail stays visible instead of being rolled away
  • You step in Scope confirmation when the account group is ambiguous, and supplying the period exports. Genuinely new, unmatched clients are flagged rather than invented

The other side of the same method — seventeen skills for a nine-location food business →