OnShore replaced Friday invoicing with one Slack message.

Before LedgerUp, every invoice at OnShore was handmade. Amelia Engen, who runs customer success at OnShore, would pull up a deal in Salesforce, switch to Stripe, click through the invoice builder, double-check every field, and hit send. Ten to twenty minutes per invoice. She'd batch the whole thing into a single Friday block.

And invoicing was only half the problem. The other half lived in her inbox. Customers emailing for W-9s, asking about payment status, requesting receipts—routine stuff, but each one meant stopping what she was doing, finding the right document, writing a reply, and sending it off. None of it was hard. All of it added up.

Then there was the bookkeeping after the invoice went out. OnShore runs their reporting and dashboards out of Salesforce—revenue by client, billing status, collections aging. But Stripe doesn't talk to Salesforce on its own. So after creating an invoice in Stripe, someone had to go back into Salesforce and update the record manually. One more screen. One more step that's easy to skip when you're busy.

And when payments came in, someone had to match them to the right invoice. Straightforward for card and ACH payments through Stripe. But nearly 70% of OnShore's invoices are paid by check— and reconciling checks means manually matching a deposit in the bank account to an open invoice, often with no clear reference number to go on.

OnShore brought in LedgerUp and Ari, the AI agent that connects Salesforce, Stripe, and Slack. The old workflow—check Salesforce, build in Stripe, update Salesforce again—collapsed into a single Slack message. Amelia sends Ari a study result name. Ari creates the invoice, sends it to the customer, and posts the invoice data back to Salesforce automatically. No toggling. No manual record updates. The dashboards stay current without anyone thinking about it.

The real unlock was the Study Results feature: a single-line approval flow inside Slack that replaced the manual field-by-field review. Invoicing went from a dedicated Friday block to something Amelia does between calls.

Invoicing was the first problem Ari solved. The second one happened almost by accident.

OnShore has received 125 customer emails since going live with LedgerUp. Ari has answered 39 of them—1 in 3— before Amelia ever had to read them. A customer asks for OnShore's W-9? Ari drafts the reply, attaches the document, and sends it to Amelia for approval. She clicks approve. Done.

Receipt requests, “where's my invoice” follow-ups, payment questions—same thing. Ari reads the email, drafts a response with the right information already attached, and waits for a one-click sign-off. The message is already written. The document is already there. Amelia's job went from “find the thing, write the email, send the thing” to “approve.”

Once invoices are sent and payments start coming in, someone has to close the loop. For card and ACH payments through Stripe, that's relatively simple. But nearly 70% of OnShore's invoices are paid by check, and matching a bank deposit to the right open invoice—often without a clear reference number—is the kind of tedious, error-prone work that quietly eats hours.

Ari reconciled 100% of OnShore's paid invoices to their bank account. Every card payment. Every check. Automatically matched, marked as paid, and reflected in Salesforce. No one on the team had to open a bank statement and squint at deposit amounts trying to figure out which client sent what.

That's the full loop: invoice created, sent to the customer, data posted to Salesforce, payment matched when it lands. One Slack message starts it. Ari finishes it.