1. Redbook Software

How Redbook Software cut 30–45 day payment delays to zero

Location

United States

Industry

AgriTech SaaS

Company size

1-10 employees

A group of black and white cows in a muddy green field.

Redbook Software builds technology for the agriculture industry, a sector where customers are often out in the field, far from a computer, dealing with livestock, scales, and operational realities that have nothing to do with signing contracts or paying invoices. Selling SaaS to this audience means meeting customers where they are: on their phones, on the move, between tasks. For Jack Ruppert and his sales team, that context shaped every decision about how to run their sales process, including how they collected payment.

Before QwilrPay, that process wasn't working. Payment was slow, chasing was constant, and the tools Redbook were using weren't built for a customer base that rarely sits at a desk.


The challenges

Redbook's payment workflow relied on two separate tools: DocuSign for contracts and a manually sent Stripe payment link for collection. Getting agriculture customers to open a DocuSign email, navigate to the attachment, and sign on a desktop was its own friction point. But the payment side was the larger problem.

After a customer signed, Redbook's team would focus on onboarding them and expect payment to follow. It rarely came quickly. Stripe invoice emails went to junk mail, customers sent checks, or they simply couldn’t figure out how to pay. “AR was a huge issue for us,” Jack said. “Someone would sign up and we’d focus on getting them live. But it was, hey, I’m going to send you a check - and I didn’t want to take checks anymore. It’s just such a waste of time.”

The result was a consistent 30 to 45 day gap between a customer going live and Redbook receiving payment. For a small startup running lean with two salespeople handling a growing deal volume, every one of those days had a cost. Time spent chasing invoice payments, depositing checks, and texting customers back and forth about contract options was time taken directly from selling.


The solution

Redbook connected their Stripe account to QwilrPay in January 2026 and restructured their sales process around a single change: customers must provide payment information before they can sign. Proposals are now sent as mobile-friendly documents texted directly to customers who are out in the field, and the payment conversation is built into the acceptance flow rather than left as a trailing task.

Hardware charges are collected immediately at signing. Software subscriptions are configured to begin when the customer goes live, with HubSpot line items differentiating the two payment types within the same proposal. “We wanted the customer’s payment information so we could automatically charge it when they went live,” Jack explained. “That was really the impetus.”


The results

Payment at the point of signature

The most immediate change was when Redbook gets paid. Rather than waiting for customers to find and act on a Stripe invoice email, often weeks after going live, payment information is captured the moment a contract is signed. When a customer goes live, the charge runs automatically. The 30 to 45 day AR gap that had been a consistent pressure point has been eliminated entirely.

We’re not running into [payment delays] at all. Now it’s just obviously we’re getting the money when they go live.

Jack Ruppert, Co-founder & CEO, Redbook Software

A sales process built for field-based customers

Before QwilrPay, Redbook’s reliance on DocuSign created a structural mismatch with their customer base. Agriculture customers are often away from a desk and unreachable via desktop email flows. The ability to send a Qwilr proposal via text with payment built in removed that friction entirely. Customers can now sign and submit their payment information from their phone, at whatever moment is right for them, without needing to be in front of a computer.

Less internal back-and-forth

With payment chasing removed from the equation, Redbook’s two salespeople have recovered time that was previously spent managing AR and coordinating with customers on contract and payment options. The customer now owns more of the flow: choosing their contract type, entering their payment details, and completing the process on their own terms.

We’re not chasing payments. We’re not having to go text the customer back and forth and say, do you want an annual or monthly contract… it saves us clicks and effort and communication and allows the customer to own more of the flow.

Jack Ruppert, Co-founder & CEO, Redbook Software

The impact

For Redbook Software, QwilrPay has changed the structure of how the business collects revenue from the moment a deal is closed to when cash arrives. The 30 to 45 day delay is gone. The internal chasing is gone. And a sales process that was built around desktop tools now works for customers who are rarely at one.

It saves us clicks and effort and communication and allows the customer to own more of the flow.

Jack Ruppert, Co-founder & CEO, Redbook Software