Running on the desk
PC Financials · AI implementation firm for the back office
Services

What's inside the engagement.

Six lines of work, run as one operation. We build the AI and implement it against your systems, we fix what those systems can't do on their own, and we run what comes out: the data, the reporting, the books, the tax. You stay on the business. Start with the AI and the systems, or hand us the whole thing. Either way it begins with a written scope, signed before anything moves.

Directory · Six lines of work
Jump to · §1–§6
§ 1
AI & Automation.
AI tuned to your CRM, processes, and books, with the workflows automated around it.
§ 2
Systems & Custom Solutions.
Fixes, integrations, and custom solutions so your stack works together.
§ 3
Bookkeeping & Accounting.
Daily ledger, monthly close, AR/AP, payroll integration.
§ 4
Reporting & Intelligence.
Monthly board-ready statements, KPIs, 13-week cash flow.
§ 5
Financial Ops & Process.
Close calendar, AR/AP workflow, approval routing, expense.
§ 6
Tax.
Federal/state filings, year-round planning, sales-tax filings.
How to read this page
Not a menu

Each entry opens with the thing that hurts. Find yours and start there. Most engagements begin at §1 or §2, because that is where the difference is, and both are sellable on their own against a finance team you already have. §3 to §6 is the finance function that becomes possible once the first two are done, and the reason the automation can be trusted: point AI at books nobody has fixed and you get faster wrong answers.

If you'd rather skip the framework and talk it through, the intro is thirty minutes. Pick a slot →

§ 1
Intelligence

AI & Automation.

The same numbers get keyed into three systems. The close eats a week. Somebody rebuilds the same report by hand every month, and the automation you already bought never quite worked.

The rote work runs on a schedule instead of on a person, tuned to your chart of accounts and your actual processes, with a CPA reviewing the edge cases before anything reaches the ledger.

How § 1 runs, in full
§ 2
Engineering

Systems & Custom Solutions.

The CRM won't talk to QuickBooks. Somebody hand-massages the processor export before it will import. Two systems disagree about the same month and nobody can say which one is right.

The seams close. The tools you already run hand data to each other in code we wrote and maintain, not a no-code flow that breaks silently the day an upstream column gets renamed.

How § 2 runs, in full
§ 3
Accounting

Bookkeeping & Accounting.

The books are late. Or they're on time and you still don't trust them, so every question about last month starts with somebody reconstructing last month.

A general ledger that is current, accrual, and closed by business-day 7, kept by the same firm that built the automation watching it. Done by a CPA, not handed to a junior.

How § 3 runs, in full
§ 4
Reporting

Reporting & Intelligence.

The books are fine and nobody can see them. Every board meeting starts with an export to a spreadsheet and a deck somebody rebuilds by hand, and the cash question gets answered from memory.

One set of numbers, in a packet and on a dashboard, where every line traces back to an account and a period in the GL and the traced number matches.

How § 4 runs, in full
§ 5
Process

Financial Ops & Process.

The close keeps slipping and you can't tell why. Approvals sit with whoever is travelling, expenses trickle in for ten days, and the 1099 chase stalls every January.

The scaffolding around the GL, written down once with an owner and a date on every step, then maintained by the firm instead of by memory.

How § 5 runs, in full
§ 6
Tax

Tax.

The return is a translation exercise. Your books go in February to somebody who has never seen the business, and the decisions that would have moved the number were made ten months earlier.

Tax runs all year, by the same CPA who keeps the books, so filing becomes a recording exercise rather than a scramble.

How § 6 runs, in full
Colophon
What the work runs on
Built with
TypeScriptPythonPostgresSupabaseCloudflareInngestClaudeOpenAIEmbeddings
We work in yours
QuickBooksXero
Engagement

What the first
five weeks look like.

Most engagements run the same shape. The dates slip; the steps don't.

01
Intro call
Thirty minutes. We map your stack, the close calendar, and the two or three things that hurt most.
Week 0
02
Discovery
We sit inside your processes and systems (the old software, the new, the automation that never worked) and find what's actually broken.
Week 1
03
Written scope
A single-page scope after we've looked: fees, deliverables, what isn't included.
Week 1
04
Migration & implementation
Pulling data, mapping the chart of accounts, and standing up the first fixes and automations.
Weeks 2–3
05
First close
Your first clean monthly close, the board packet, and the cash forecast. Signed off by business-day 7 of the month; we post-mortem the day after.
Weeks 4–5
06
Steady state
Quarterly business review. Annual scope refresh. Software and books stay one engagement.
Ongoing
Questions
The ones that come up
Q. What's actually included, and where does your work stop?
The six lines above, in whatever combination the written scope names. Outside them: audit representation, cap-table and 409A work, ERP implementations like NetSuite or Sage Intacct, international tax, and full-stack product engineering for customer-facing apps. We refer those out rather than stretch into them, and the scope says which side of the line everything falls on before you sign it.
Q. Do you fix the books first, or put the AI in first?
Usually together, and never AI alone on books nobody has fixed: that produces faster wrong answers, which is why most finance AI pilots quietly stop after a quarter. If your books are already clean and the pain is purely tooling or visibility, §1 and §2 stand on their own without §3.
Q. Do we have to change our systems, or rip out QuickBooks?
No. We work in the stack you already run, QuickBooks or Xero, your CRM, your payroll and card providers, and fix the seams between them. A migration only happens if you want one and the scope says so. The default is that your systems stay and start behaving.
Q. What happens when the AI gets something wrong?
A CPA catches it, because nothing reaches your production ledger without a human approving it. Proposed entries are held for review, writes back to QuickBooks or Xero are explicit and logged, and the firm is on the hook for the result. That is the arrangement: the automation does the volume, the CPA owns the answer.
Q. What happens to the bookkeeper we already have?
That depends on which shape you buy. Engaged for the AI and the systems, we implement against your existing team's work and they keep the ledger. Hand us the whole back office and we take the ledger over. We will tell you which one we think you need after discovery, and we won't pretend it's the bigger one if it isn't.
Q. How does pricing work?
There is no rate card. Engagements start at $5,000 a month, and most run between $7,500 and $15,000, depending on entity count, transaction volume, and how much has to be built before it can be run. Discovery comes first, then a one-page written scope with the fee and the deliverables on it, signed before anything moves. It is a fixed monthly fee, and the build sits inside it rather than arriving as a separate invoice, so the month we do the most work is not the month you get the biggest bill. We do take hourly work, but fixed fee is the default, because hourly pays us to take longer. We work with companies doing over $5M in revenue; well below that, a standalone bookkeeping tool is usually the smarter buy and we will point you to one.
Q. If this doesn't work out, how do we leave, and what do we keep?
You keep the books, the data, the documentation, and the audit trail, and the systems work ends in either ongoing maintenance or a clean handoff, your call. We don't hold credentials you can't get back, and nothing is built so that leaving breaks it. An engagement you can exit is the only kind worth starting.
How to engage

Start with the AI and systems, or
let's scope the whole operation.

Thirty minutes. If we're a fit you get a written scope within the week. If not, we'll point you somewhere that is.