Intelligence layer for ready-mix
Price, forecast and collect on every yard you produce.
Peryard reads your batch, dispatch, ledger and receivables and returns one operating picture — what a yard costs, what it earns, and when the cash actually lands.
Illustrative. Not a customer's numbers.
The problem
You price by the yard. You find out by the quarter.
The cost you quote is last quarter's cost.
Cement moved. Freight moved. The mix got adjusted on a Tuesday to hit a slump. The price sheet didn't move with any of it.
The money is fine until the month it isn't.
Your customers pay in 60-plus days. Your cement is due in 30. You find the gap when the statement arrives, not when it was created.
The answer exists — in a spreadsheet, on one person's laptop.
Somebody in your office rebuilds it every month by hand from four exports, and it's right up until the day they're on vacation.
None of this is a discipline problem. It's a plumbing problem. The data exists — in dispatch, in batch, in the ticket, in the AR ageing. Nothing connects it.
How it works
Connect what you already run.
Batch and dispatch records, material invoices, payroll hours, and your AR ageing. Peryard reads them. It does not replace your dispatch system or touch your batching controls.
Peryard builds the per-yard picture.
Landed material cost by mix design. Labour and truck cost by load. Delivery cost by distance. Revenue by ticket. Rebuilt every day, not every quarter.
You see it before it's history.
Margin per yard, per mix, per customer, per job. Cash projected forward on the receivables you actually have. Alerts when a mix, a customer or a month goes upside down.
Peryard sits alongside your batch and dispatch system. Read-only by default. Nothing about how you batch changes.
The core product
The Stack
Your plant, live. Every number with the decision attached.
Your accounting system knows what you spent. Your batch system knows what you poured. Your bank knows what landed. None of them talk, so the answer only exists after somebody spends a week building it by hand. The Stack connects them and keeps the answer current.
Turn rate
Average last quarter was 1.8. With 13 trucks and 8 drivers, optimal fleet size is 11 trucks.
Margin / yd
Cost per yard rose $4.10 since March while price held flat.
A / R
$84,200 crosses 60 days next Friday. Two accounts hold all of it.
Margin by mix design — worst first
Days on hand
Receivables ageing
Integrates withQuickBooks · your batch and dispatch system · your bank· More systems — next
Illustrative figures. Not a customer's numbers.
Attachments
Two products attach to it.
Collect
Get paid without spending the relationship.
An invoice passes 60 days and routes itself to your lien dashboard. No decision, no awkward call. The debtor is informed the job is approaching lien exposure, and the clock keeps running. Most of the time that's the whole intervention — in the case we've run, a 97-day invoice was paid seven days after the notice went out. No call was made. No lien was filed.
Informational, never a threat. Peryard executes a calendar — it isn't a law firm and doesn't give legal advice.
JointPay
Supplier terms you can't get alone.
Peryard holds partnerships with material suppliers. Qualified producers get pricing and terms through those partnerships that a single plant can't negotiate on its own. The mechanism is simple: one customer payment comes in, and the supplier's share and yours are calculated invoice by invoice and paid out the same week. You stop fronting material, and your supplier stops carrying you.
Same week. No delay. Illustrative.
By application. Qualification depends on the partner and on your operating data. Peryard is not a bank. We calculate the split. Your bank moves the money.
Marked section — for suppliers
If you supply the plant
Your first hard signal that a customer is in trouble is a late invoice. By then the exposure is already unsecured and the only choices left are collections or a write-off. The signals were in the producer's operating data for months before that — you just had no way to see them, because credit gets extended against a price sheet.
Peryard gives you a view into the accounts that agree to share it, and gets you paid out of collections rather than out of credit. No new capital. No security interest. No priority contest with anybody.
Visibility today
None beyond your own invoices
Warning time
Zero — the signal is the loss
Differentiation left
Price, once quality and freight are matched
Who it's for
Fit, stated plainly.
Peryard fits you if:
- You run one to five ready-mix plants
- Your customers take 45 days or more to pay
- You're on a commercial and job-site mix, not residential COD
- Somebody in your office already builds a version of this in Excel
- You're in the Dallas–Fort Worth metro — we're onboarding here first
Peryard isn't for you yet if:
- Your customers pay in under 20 days — the cash side of this is worth much less to you
- You're a single-plant operation doing under 5,000 yards a year
- You need a dispatch or batching system. That's not what this is.
- You're outside North Texas. Get on the list — we'll expand, and we'll tell you when.
Why DFW first
We're starting in Dallas–Fort Worth on purpose. Material costs, haul distances, permitting and lien rules are regional, and a cost model that averages across the country isn't a cost model — it's a guess. We're building Peryard against real North Texas plants, real Texas lien deadlines and real local cement and aggregate pricing. When the numbers hold here, we'll take them somewhere else.
Where we are
Peryard is pre-launch. We're building it with a working North Texas ready-mix producer and a cement supplier, against their real batch records, real invoices and real receivables — not a demo dataset. Early access members get the model run on their own numbers before they're asked to pay for anything.
See your real cost per yard.
Send us a month of batch records and invoices. We'll run your actual numbers and walk you through what we find. No cost, no commitment, and your data stays yours.