Invoices, payments and follow-up, while the books stay in QuickBooks Desktop
An established organization kept its books in QuickBooks Desktop and spent hours every week chasing payments by hand. The books stayed exactly where they were. FlexAR now handles everything around them.
Client An established organization that bills its customers directly
FlexAR · Home
A real screen from software we built. The business and the data in it are made up.
invoices managed
About 18,000
customers
3,000+
their QuickBooks Desktop books
Unchanged
The situation
Every bill went out by hand. Somebody had to know who owed what, put the bill together, send it, and then remember a week later that it still hadn't been paid.
It worked, because one person carried it. Which is another way of saying it stopped whenever that person was busy, away, or looking at something else. Replacing the accounting package was never on the table: the books live in QuickBooks Desktop and the bookkeeper knows it well.
What we built
Syncs with QuickBooks Desktop automatically, with no re-typing.
Sends invoices and statements by text message or email, each with a secure link to view and pay.
Takes card payments online or by phone and posts them straight back into QuickBooks.
Follows up on overdue balances on a schedule the office sets.
Matches incoming payments to the right invoice, and leaves anything uncertain for a person to confirm.
Every customer, one conversation
Invoices go out by text with a link to pay. Reminders follow on a schedule, and a reply lands in the same thread the office already has open.
FlexAR · Threads
A real screen from software we built. The business and the data in it are made up.
Ask it in plain English
The assistant reads the business's own invoices and messages. It answers questions and drafts messages, and a person approves anything before it is sent.
FlexAR · Assistant
A real screen from software we built. The business and the data in it are made up.
The bill comes from a number their customers already know
An invoice reaches the customer as a text message from the organization's own number, with a link to see it and pay it. What has been billed and what has been paid is one list, not somebody's memory. It runs under their name, in their own account, and they own the code and the information outright.
Their staff report a problem; we don't wait to be emailed
There is a report button inside the system. Somebody says what's wrong in their own words and it reaches us with the context already attached. We read the report against the actual code, and the office sees the change running on their own information before it goes live. That loop is how most changes to this system now happen.
The demo runs on an invented company's invoices, so you can open anything without looking at a real customer's account.
Applications came in on paper and by phone, bunks lived on a whiteboard, and nobody could say who still owed what.
Now
Families apply, sign and pay through one link; the office accepts in a few clicks, sees every balance and form, and reaches every parent with one message.
Every call, voicemail and email waited for one person, and the rest of the office waited for him.
Now
The assistant answers, takes messages, sorts and drafts; he approves every reply and takes the calls that are really for him.
Read the case study →
Start a conversation
Tell us how your business runs. We'll show you what we'd build.
We'll look at how you work, show you where time and money leak, pick the first piece worth building, and show you what it would look like.
A first conversation costs nothing. A real person replies within one business day.