Skip to content
Acorn Works

What we can do

Capabilities

Three things we do over and over, for businesses that look nothing alike. The systems change. The shape of the problem doesn't.

Three disagreeing systems feeding one reconciled recordA CRM window, a spreadsheet with a broken formula, and a point-of-sale receipt each report a different number. They feed into the Acorn Works operations app, which lists them as connected sources, shows the two conflicting totals side by side, flags the variance with an explanation, and resolves to a single reconciled record.CRM · DealsRiverside Lanes$4,800Delta Vending$5,200Summit Events$2,400tracking-v7-FINAL.xlsxABCDRt 12318$1,284Rt 4206$942#REF!POS — REGISTER 22× event pkg$9,400walk-in$2,490TOTAL$11,890Acorn Works · OperationsCONNECTED SOURCESCRMlivePoint of saleliveSpreadsheet · retiredimportedCRM says$12,400Register says$11,890Variance flagged — comp'd party, room 3$510.32One record, reconciledTHREE SYSTEMS THAT DISAGREE · ONE PLACE THE WORK ACTUALLY HAPPENS
01 · Integration

One place the work actually happens

Your CRM says one number and your point-of-sale says another, so once a month somebody sits down and reconciles the difference by hand. The systems aren't going anywhere — you pay for them and your team knows them. What's missing is something that sits across them.

We build the application your team actually works in, and it talks to the systems you already run. RCS Storage is the shape of it: a customer taps a button on their phone, the contract gets signed in the app, Stripe takes the payment, and the paid invoice lands in QuickBooks. Nobody retypes anything in the middle, and there's one record of what happened instead of three.

We're not selling you a middleware layer or a pile of custom APIs. Your systems already have APIs — the work is in the application that uses them properly, and in deciding what a customer, an event, or a dollar actually means when two systems define it differently. That reconciliation logic is where the time goes, and it has to be right before any of it is worth looking at.

Typically
  • the application your team works in·
  • secure links to the systems you already pay for·
  • one record instead of three·
  • reconciliation you can see·
  • a readable log when something goes wrong
From paper contracts to Stripe and QuickBooks
An invoice checked line by line against the contract it was billed underIncoming invoices enter a purpose-built vendor check application. Each line is compared against the supplier contract; a widget bracket billed at $62.50 against a contracted rate of $48.00 is highlighted as a mismatch, the overcharge is calculated, and the exception is queued for a person to rule on. Cleared invoices pass through.INVOICEVendor CheckInvoice #2214 · Acme SupplyFilter housing ×12$18.20Widget bracket ×34$62.50Freight$140.00Total$2,463.30unit price billed$62.50Contract · Acme Supply 2025Filter housing$18.20Widget bracket$48.00Freight cap$150.00contracted rate$48.00≠Billed above contract34 × $14.50 = $493.00Send to reviewclearedEVERY INVOICE CHECKED AGAINST ITS CONTRACT · A PERSON RULES ON THE FLAGS
02 · Purpose-built software

The tool that doesn't exist yet

Some problems don't have a product. They have a workaround with a person's name on it. When the thing you need isn't for sale, we build it — one workflow, shaped exactly to how the business already runs.

We built a vendor check application because nobody sells one. It parses each contract on intake, then checks every incoming invoice against the terms it was actually billed under, and flags the discrepancies for a person to rule on. It caught money that had been leaking quietly for years, because the only alternative was somebody reading every invoice against every contract, and nobody was ever going to do that.

That's the pattern. A repetitive check nobody has time to perform continuously, or a workflow that every vendor implements slightly wrong because it's specific to your business. We build the specific thing and nothing beyond it, with roles, an audit trail, and a record of every decision it made on your behalf.

Typically
  • internal tools·
  • document and invoice checking·
  • review queues·
  • role-based access·
  • audit logging
Replacing the legacy app that ran the money
A question answered from a legacy database without opening any inbound portA legacy SQL server sits inside the building, behind a firewall. A single outbound tunnel carries data out through one sealed opening; an inbound attempt is blocked. On the other side, a plain-language question in a chat window returns a real table of route collections, live from the tunnel.YOUR BUILDINGSQL · 2009-TODAYthe vendor's databaseyou were never given keys toFIREWALLOUTBOUND ONLYnothing gets inClaude — connected to your dataWhat did Route 12 collectlast month?Route 12 · June collectionsLOCATIONCOLLECTEDSPLITQuick Mart$1,284.50$642.25Gas & Go$2,102.00$1,051.00Lanes West$918.75$459.38live from the tunnel · 2 min agoYOUR NUMBERS, IN CHATGPT OR CLAUDE · WITHOUT OPENING A SINGLE PORT
03 · Legacy data

Ask your own data a question

The numbers you need are sitting in a database behind your firewall, in a system owned by a vendor with no commercial interest in helping you get at them. Every question costs a support ticket, or a person with database access and a free afternoon.

We move that data out and make it answerable — in ChatGPT, in Claude, or in whatever your team already has open — without opening a single port. The connection is outbound only: the tunnel originates inside your network, so there is nothing new listening on the internet and nothing new to attack.

Selective sync means only what you've agreed to share leaves the building. Per-location schema disambiguation means a row can always be traced back to the server it came from. And because it's a real connection rather than an export, the answer you get at 4pm reflects what was true at 4pm.

Typically
  • secure data sync·
  • outbound tunnels·
  • cloud replication·
  • reporting layers·
  • AI over your own data
What sales said versus what the register said

Systems we've connected

Twenty and counting

  • QuickBooks Online
  • Zoho CRM
  • Zoho Books
  • Stripe
  • CardConnect
  • Twilio
  • Plivo
  • Supabase
  • Microsoft SQL Server
  • Cloudflare Tunnel
  • ClubSpeed
  • Resend
  • Mailchimp
  • FreshBooks
  • ADP
  • JotForm
  • Home Assistant
  • Google Workspace
  • Anthropic Claude
  • OpenAI

A partial list. If you're running something we haven't touched, we'll find out quickly whether it has an API worth using.

Not sure which one you need?

Most engagements start as one of these and turn out to be another. That's what the diagnostic is for — a week or two, sat with the people doing the work, and a written answer about which of these actually applies. Sometimes the answer is none of them, and we'll say so.

Start a conversationDescribe your problem →