Running on the desk

qbo a/r app · the fast working surface over QuickBooks A/R: find it, fix it, print it, collect it · human-approved write-back ▸ discovery · inside your processes and systems, old and new, finding what's actually broken · week one ▸ implementation · fixes, integrations, and AI where it earns its place, until the pieces talk to each other · weeks two to three ▸ run · the data, the reporting, the books, and tax, run on what we built · ongoing ▸ stack · TypeScript · Python · Postgres · Supabase · Cloudflare · Inngest · Claude · OpenAI ▸ qbo a/r app · the fast working surface over QuickBooks A/R: find it, fix it, print it, collect it · human-approved write-back ▸ discovery · inside your processes and systems, old and new, finding what's actually broken · week one ▸ implementation · fixes, integrations, and AI where it earns its place, until the pieces talk to each other · weeks two to three ▸ run · the data, the reporting, the books, and tax, run on what we built · ongoing ▸ stack · TypeScript · Python · Postgres · Supabase · Cloudflare · Inngest · Claude · OpenAI ▸

An AI implementation firm for your back office

Your back office, run on AI.
We build it, we implement it, we run it.

PC Financials builds and implements the AI, fixes the systems underneath it, and runs what comes out: the data, the reporting, the books. You stay on the business; we run everything behind it.

For operators who know AI belongs in the back office and don't want to guess where it goes

Book a 30-minute intro →

The problem

One operation,
not three vendors.

Most growing companies don't have a books problem or a reporting problem. They have a fragmentation problem: a bookkeeper here, an outsourced "CFO" there, a CRM that doesn't talk to the GL, and no one accountable for the whole. The numbers are late, the reports are unreadable, and the seams are where the truth gets lost. They also know AI should be doing more of this, and can't tell you where it goes, who would implement it, or what breaks if they get it wrong, while the competitors who worked it out are pulling ahead. We replace that with one operation, accountable for the whole, built on AI we implement and systems we fix and own, so you can stay on the business.

The data never agrees

The CRM says one thing, the processor says another, the ledger says a third. Every number needs a person to reconcile it before anyone can trust it, so nothing is current and everything is contested.

II.

Nobody owns the seams

The bookkeeper owns the books. The CFO owns the reporting. Nobody owns the gap between them, and that gap is where the truth goes missing.

III.

AI has nothing to run on

Pointing a model at a chart of accounts that cannot answer the question produces faster wrong answers. This is why most AI pilots in finance quietly stop after a quarter.

IV.

You find out too late

By the time a bad month shows up in a report, it is two months old. The decisions that would have changed it have already been made.

The method

Nothing here is off the shelf.

Every engagement starts with discovery: we sit inside your processes and your systems (the old software, the new software, the AI experiment that never worked out) and find where it's actually broken. Then we implement: the fixes, the integrations, the automation and AI where it counts, until the pieces talk to each other. Then we run what we built, with every edge case going to a queue a human reviews. Nothing is resold, nothing is a bot you rent, and nothing gets configured once and abandoned.

Operating principle

"The model is the easy part. The hard part is the scaffolding around it: the checks that catch the failures, the queues that surface them, and the path back when something goes sideways at 3am."

Pin Cohen, CPA

Phase	What happens	When
discovery	inside your processes and systems, old and new, finding what's actually broken	week one
implementation	fixes, integrations, and AI where it earns its place, until the pieces talk to each other	weeks two to three
run	the data, the reporting, the books, and tax, run on what we built	ongoing

Everything we build is tuned to your systems, documented, and reviewed by a CPA before it touches your ledger.

In practice

What this looks like in practice.

Before

Two CRMs that didn't talk to each other, and neither talked to the ledger. On top of that, a bookkeeping firm that wasn't delivering and an outsourced CFO producing reports nobody could use. Money moved through the business and the owner couldn't say why. Nobody could say what was actually going on; every month ended in headaches instead of answers.

What we did

We made the two CRMs work and talk to each other, then wired one process running from the CRM through the ledger to reporting. Once the data had somewhere coherent to land, we built the AI in where it added leverage, not everywhere, only where it counted. Then we replaced the parts of the finance operation that weren't working and cut what wasn't earning its place.

After

The owner is back on what he does best: the product, the sales, the parts of the business he actually loves. Everything behind him is handled, and he can see it working. He knows why there's money in the bank.

How it runs

What the first
five weeks look like.

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

Intro call

Thirty minutes. We map your stack, the close calendar, and the two or three things that hurt most.

Week 0

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

Written scope

A single-page scope after we've looked: fees, deliverables, what isn't included.

Week 1

Migration & implementation

Pulling data, mapping the chart of accounts, and standing up the first fixes and automations.

Weeks 2–3

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

Steady state

Quarterly business review. Annual scope refresh. Software and books stay one engagement.

Ongoing

Before you call

Five answered

Q. Where does our data actually go?

Into a database this firm controls. No client's data is ever pooled with another's. We work against a copy of your books; anything written back to QuickBooks or Xero is explicit and logged, and proposed entries are reviewed by a CPA before they reach your production ledger.

Q. Who owns the code, and what do we keep?

PC Financials owns and maintains the code it writes. You get the outputs, the audit trail, and written documentation, not the source. Systems work ends in either ongoing maintenance or a clean handoff, your call, so the integrations do not become a hostage.

Q. Can we start with just the AI and systems work?

Yes. Those two lines are sellable on their own, and we'll implement them against your existing finance team's work. They're also the engine when we run the whole operation.

Q. Can you replace our controller?

Sometimes. If the controller is mostly running close and reporting, yes. If they're in a finance-leadership role doing FP&A, fundraising, or board-facing strategy, you want both.

Q. Do you sign an NDA?

Yes. Mutual NDA before the intro call if your stack requires it, standard otherwise.

Your back office, run on AI.
We build it, we implement it, we run it.

One operation,
not three vendors.

Nothing here is off the shelf.

What this looks like in practice.

What the first
five weeks look like.

What's inside the engagement.

Where we go deep.

Notes from the work.

QuickBooks is a fine ledger and a terrible window

Book a call.
Thirty minutes.

Your back office, run on AI. We build it, we implement it, we run it.

One operation,not three vendors.

Nothing here is off the shelf.

What this looks like in practice.

What the firstfive weeks look like.

What's inside the engagement.

Where we go deep.

Notes from the work.

QuickBooks is a fine ledger and a terrible window

Book a call. Thirty minutes.

Your back office, run on AI.
We build it, we implement it, we run it.

One operation,
not three vendors.

What the first
five weeks look like.

Book a call.
Thirty minutes.