Concrete does not wait, and neither does the phone
A flatwork crew's day has a hard deadline batched into it. The ready-mix truck shows up inside a delivery window, the load starts hydrating the second it leaves the plant, and you have a limited stretch of workable time before the mix stops cooperating. Everything about a concrete contractor's operation bends around that single fact. You do not pause a pour to take a call. You do not send a finisher to the truck to answer the office line while the bull float is still moving and the bleed water is coming up.
So the phone rings during the exact hours when nobody can possibly pick it up. Homeowners call between eight and eleven in the morning, which is when the truck is backing up. They call at lunch, which is when the crew is cutting joints and edging. They call at four, which is when you are washing out and loading. By the time anyone listens to voicemail, the person who wanted a driveway quote has already talked to two other contractors.
As of September 2026, the typical residential and light-commercial concrete shop is still running its entire front office out of one cell phone in a dusty truck, plus a text thread, plus a legal pad with measurements on it. That works right up until you are busy, and then it quietly costs you a large share of the bids you never knew existed.
This guide walks the whole path for a concrete, driveway, and flatwork contractor: what an inbound call actually contains, what to ask, why a phone quote is usually a mistake, how to protect the pour-day schedule, and how to get paid and reviewed afterward. It maps to the Run with Jarvis platform, which puts answering, booking, dispatch, invoicing, and follow-up under one subscription instead of five separate vendors.
What a concrete call actually contains
Flatwork calls are not one thing. They arrive in at least six distinct shapes, and each one wants a different response:
The tear-out and replace. A 30-year-old driveway is heaved, cracked, and sinking at the apron. The caller wants a number. The real job includes breaking out the old slab, hauling it off by the ton, re-grading, and possibly fixing whatever caused the failure in the first place.
The new pour on bare ground. A patio extension, a shop pad, an RV parking slab. No demolition, but now base prep, thickness, and reinforcement are all open questions.
The small repair or patch. A spalled step, a trip hazard at a sidewalk joint, a three-foot section at a garage entry. Often below your minimum, and the honest answer on the phone saves everyone a drive.
The decorative upgrade. Stamped, exposed aggregate, integral color, saw-cut patterns. Higher ticket, longer conversation, and a customer who has been looking at photos and has expectations about the finish.
The commercial or builder call. A GC needs a sidewalk, approach, or pad on a schedule that is already slipping. Different pricing, different paperwork, different urgency. The differences in how you intake and price those two sides of the business are covered in commercial versus residential service operations.
The tire-kicker who wants a per-square-foot number. Sometimes a real buyer, sometimes a homeowner assembling a spreadsheet. Worth qualifying, not worth a two-hour drive.
An answering setup that treats all six identically wastes estimator time on the ones that cannot close and loses the ones that could.
The intake questions that matter on a flatwork call
The point of the first call is not to price the job. It is to capture enough structured information that your estimator arrives at the property already knowing what he is looking at, and to get the visit on the calendar before the caller keeps dialing.
The questions worth asking every time:
- What is it? Driveway, patio, sidewalk, garage or shop pad, steps, curb, approach.
- Rough dimensions. Homeowners do not know square footage, but they know "two cars wide and about fifty feet long," or "the slab is roughly twelve by twenty." That is enough to size the job and decide whether it clears your minimum.
- Is there existing concrete? This is the single most important question on the call, because tear-out and haul-off can be a meaningful share of the total and it is invisible on a photo.
- New pour, replacement, or overlay? Three different scopes.
- Finish preference. Broom finish is the default. Stamped, exposed aggregate, or color changes the price band and the crew you send.
- Access. Can a ready-mix truck get within chute reach, or does this need a pump, a conveyor, or buggies across a lawn? A backyard patio behind a six-foot gate is a different job than a front driveway.
- Drainage and slope. Does water currently run toward the house? Any standing water after rain? This is where callbacks come from.
- Timeline and driver. Selling the house, hosting an event, tired of the crack, insurance claim, builder deadline.
- Address and best callback number.
That is a ten-question script, and it is exactly the kind of thing a human answering a call between truck loads never completes. An AI phone agent completes it every time, in the same order, and hands it to you as a structured record rather than a two-line voicemail.
Why you cannot quote a driveway over the phone
The instinct to give a number on the phone is understandable. The caller is asking for one, and the competitor who gives one sounds decisive. It is still usually the wrong move in flatwork, for reasons that are specific to concrete.
Square footage is the easy part. A two-car driveway at roughly twenty by fifty is a thousand square feet. At four inches, that is about twelve and a third cubic yards of concrete before any waste allowance, and most shops add a margin on top of that because you cannot run out mid-pour. Bump the slab to five inches for a vehicle load and the same footprint takes over fifteen yards. That arithmetic is straightforward and you can do it on the phone.
What you cannot do on the phone is everything else that moves the number:
Existing slab thickness and reinforcement. Old driveways get poured thick and get poured thin. Some have wire, some have nothing, some have a second slab underneath from a prior replacement. You find out when the hammer goes in.
Base condition. Whether you are adding two inches of compacted base or eight changes material and labor materially.
Grade and drainage. If water has been running back toward a foundation for a decade, fixing the slope is part of the job, and it may involve a drain, a swale, or a thickened edge you did not plan on.
Access and placement method. Chute-reachable is one price. A pump truck, a conveyor, or thirty buggy loads is another entirely.
Right-of-way involvement. If any part of the work touches the public sidewalk, the approach, or the curb, a permit and an inspection step enter the picture.
Thickness and reinforcement decisions. Mesh versus rebar, bar size and spacing, control joint layout, thickened edges at the apron. These are engineering-adjacent judgments a homeowner cannot describe and an estimator makes standing on the dirt.
So the right phone outcome for a concrete company is not a quote. It is a booked measurement with the scope captured, plus a clear range if you give ranges at all, plus an honest statement about what could move it. Your close rate on bids where you walked the site is a different number than your close rate on bids where you guessed, and the gap is your margin.
Booking the site visit and protecting the estimator's day
Once you accept that the site visit is the conversion event, the whole front office reorganizes around getting it booked and getting it kept.
GetTimePad holds real availability, so the AI books against actual open estimator slots instead of promising that someone will call back. A confirmation text goes out immediately and a reminder fires before the appointment. That matters more in concrete than in trades where the visit is short, because a flatwork measurement plus drive time is easily an hour, and a no-show at 9 AM cannot be resold.
Drive time is the underappreciated cost. An estimator who books four visits scattered across forty miles spends most of his day in a truck. Booking geographically, with the calendar aware of where the other appointments already are, turns four measurements into six. How to think about radius, drive time, and whether to price for distance is covered in the service radius and drive-time pricing guide.
There is also a segment of buyers who do not want to talk at all. They found you at ten at night after looking at a cracked slab all summer, and they would rather tap a Saturday morning slot than describe their driveway to a stranger. Self-scheduling running against the same calendar catches those people without creating a second conflicting schedule that somebody has to reconcile by hand.
Bid follow-up: the pile that decides your year
This is where concrete contractors lose the most money, and it is the most fixable thing on the list.
Here is illustrative arithmetic built only from clearly labeled assumptions. Assume you send thirty bids a month at an average job value of $6,800. If you close ten, that is $68,000 booked and twenty bids sitting in silence, representing roughly $136,000 of quoted work you already paid to produce. Each of those twenty cost you an answered call, a drive, a measurement, a takeoff, and a written proposal.
Recovering just two of those twenty through disciplined follow-up is $13,600 of additional revenue from work your estimator had already done. No new advertising, no new leads, no new crew. It is the highest-return activity available to a flatwork shop, and it is the one that reliably never happens, because working twenty open bids is a job and you already have a job.
The platform's AI outbound follow-up calls handle that list on a cadence you set. The system reaches the homeowner, asks whether a decision has been made, captures the actual objection, and books the pour when the answer is yes. Check /pricing for which tier includes outbound follow-up. Text follow-up runs alongside for the people who will not answer a call but will reply to a message.
The side benefit is structured objection data. If a third of your losses are "waiting until spring," that is a seasonal cash-flow reality you can plan around. If most are "went with someone cheaper," you have a positioning conversation with yourself. If several say "we decided to do pavers instead," that is a product question. Silence teaches you nothing.
Pour day is a scheduling problem with no slack
Concrete scheduling is unlike most trade scheduling because three independent constraints have to line up on the same morning: the crew, the ready-mix delivery window, and the weather.
Crew size is fixed by the pour, not by the office. A residential driveway wants enough hands to place, screed, bull float, edge, and broom before the slab gets away from you. Show up two people short and you are not slow, you are producing a bad slab.
The delivery window is not yours. The plant schedules trucks against every other job in the market that morning. Slide your start by two hours and you may lose the slot entirely, and a short load carries a fee that eats a small job's profit.
Weather owns the calendar. Rain within hours of finishing can ruin a surface. Cold slows set and risks the pour outright. Extreme heat accelerates it and invites plastic shrinkage cracking. Cure time then locks the site: foot traffic waits days, vehicle traffic waits longer, and design strength arrives weeks out. A customer who parks on a green slab creates a warranty problem that is nobody's fault but everybody's cost.
The operational consequence is that a weather cancellation is not a one-day slip. It is a cascade that has to be re-sequenced against truck availability and crew assignments, and every affected customer has to be told. Doing that by hand, from a truck, on a rainy Tuesday morning, is how shops end up with angry customers who were never called.
IntelliDrive carries the CRM, dispatch, and job records, so a pour is scheduled against the crew that will actually run it, and the customer record holds the deposit, the scope, the finish, and the permit status in one place. GPS tracking and route optimization keep the crew and the estimator from crossing the metro twice. Automatic ETA and arrival texts on pour morning cut the "are you still coming" calls that otherwise land on the one phone nobody can answer.
Permits, right-of-way, and sidewalk approvals
Flatwork has a paperwork layer that interior trades mostly escape. A driveway approach usually touches the public right-of-way. Replacing a city sidewalk panel often requires a permit and sometimes an inspection before you place. Approach width, apron slope, and where the drainage goes are frequently spelled out in local standards. Some jurisdictions want a bond or a licensed contractor on file for ROW work.
None of that should be answered by a phone agent improvising municipal code. The right posture is capture, not answer: record the address, whether the scope touches the sidewalk, curb, or approach, the specific question the caller asked, and route it to whoever handles your permits with full context attached. Your estimator calls back knowing the address and the exact approval question instead of rediscovering it from scratch.
The broader workflow for tracking which jobs need a permit, which need an inspection before pour, and how not to lose a week waiting on one is in the permits and inspections workflow guide. General small-business licensing and compliance orientation is available at sba.gov.
Tear-out, haul-off, and the change orders nobody priced
Demolition is where flatwork bids go wrong. You priced breaking out four inches and found six. You priced a clean subgrade and found a buried slab, a tree root mat, or saturated clay that will not compact. You priced one dumpster of debris and the old driveway weighed more than the estimate.
Two habits keep those from becoming arguments. First, write the assumption into the proposal explicitly: assumed slab thickness, assumed base depth, assumed disposal tonnage, and what happens if the field differs. Second, document the field condition with photos the moment the hammer exposes it, attached to the customer record, before anyone is upset. A change order supported by a timestamped photo of a six-inch slab with no reinforcement is a conversation. The same change order described verbally three days later is a dispute.
Chargeback defense is included on every plan, which is what you want when a deposit dispute surfaces months after a pour and nobody can find the signed change order.
Seasonality: weather owns your calendar
Concrete demand is not evenly distributed and neither is concrete capability. Spring brings the backlog of everyone who stared at a cracked driveway all winter, plus the rain delays that make placing unpredictable. Summer brings volume and heat management. Fall is often the best pouring weather and the busiest bid season. Winter, depending on your market, ranges from reduced to effectively shut down for flatwork.
That produces a phone problem with two distinct failure modes. In the busy stretch, call volume outruns anyone's ability to answer while also running production. In the slow stretch, every single call matters disproportionately because there are not many, and missing one is a larger percentage of the quarter.
Parallel AI answering removes the capacity ceiling in the busy months. Forty calls on the first warm Saturday in March get forty conversations, forty captured scopes, and forty booked measurements spread across the following three weeks, instead of one busy signal and thirty-nine voicemails. How to staff, price, and plan around demand that arrives in bursts is covered in the guide to seasonal call volume spikes.
Deposits, invoices, and getting paid
Concrete is a materials-heavy trade with an irreversible product. Once the truck discharges, you own the cost whether or not the customer pays. That is why a deposit before the pour is scheduled is standard practice and should be non-negotiable on residential work.
The operational version of that policy is simple: no deposit, no truck on the schedule. Enforcing it politely and consistently is easier when the deposit request is an automatic step in the workflow rather than an awkward phone call somebody has to remember to make. A payment link sent by text at proposal acceptance gets paid far faster than an invoice emailed as a PDF attachment, and the mechanics of that are in getting paid faster with payment links.
IntelliDrive handles invoicing with three payment providers plus bidirectional QuickBooks sync, so deposits and final balances land in your books without re-entry. Review automation to Google, Facebook, and Yelp fires after completion. Timing matters in concrete specifically: ask for the review after the slab has cured enough that the customer has walked on it and seen the finished color, not on the day of the pour when the surface is still dark and wet and looks nothing like the final product.
Manual handling versus an automated stack
| Moment in the job | Typical manual handling | Automated stack |
|---|---|---|
| Call arrives during a pour | Rings out to voicemail | Answered on first ring, English or Spanish |
| Scope capture | Two-line voicemail, maybe a name | Ten structured fields including access and existing slab |
| Site visit | "Someone will call you back" | Booked into a real calendar slot on the call |
| Visit reminders | None | Confirmation, day-before reminder, morning-of ETA |
| Estimator routing | Whatever order the calls came in | Booked with drive time and geography in view |
| Open bids | A folder and good intentions | Worked on a cadence by outbound call and text |
| Weather cancellation | Owner texts whoever he remembers | Re-sequenced in dispatch, customers notified |
| Pour-day arrival | Customer calls to ask if you are coming | Automatic ETA and arrival text |
| Field change order | Verbal, argued later | Photo-documented on the customer record |
| Deposit | Awkward phone reminder | Payment link at acceptance |
| Final invoice | Emailed PDF, chased twice | Invoiced with QuickBooks sync and a pay link |
| Review request | Occasionally, when someone remembers | Automatic after cure, to Google, Facebook, Yelp |
| Ad spend attribution | Best guess | Call tracking with campaign and keyword on Pro and above |
What to automate and what to keep human
Automate anything that is a repeated, structured, low-judgment step: answering, qualifying, booking, reminding, ETA notification, deposit collection, invoicing, follow-up cadence, review requests. Those are the things that fail because a person is busy, not because they are hard.
Keep human anything that requires standing on the dirt or exercising trade judgment: reading the grade, deciding thickness and reinforcement, calling the base prep, judging whether a customer's drainage expectation is achievable, pricing a decorative finish, and answering a code or right-of-way question definitively. A phone agent that tries to do those jobs will eventually promise something your crew cannot deliver, which is worse than a missed call.
The line is clean: automation owns the handoffs, the humans own the concrete.
Where to start
Start with answering and booking. That is where the largest measurable leak is, and it requires no change to how your crews work. Core at $500/mo covers the bilingual AI receptionist, smart job booking and calendar, GPS tracking and route optimization, ETA and arrival texts, POS and invoicing with three payment providers, QuickBooks sync, review automation, CRM and customer portal, the mobile app, and chargeback defense, with 500 AI call minutes included and $0.45/min after that.
Move to Pro at $750/mo when you are spending real money on Google Ads or Local Services Ads and need to know which campaigns produce poured driveways rather than which produce phone noise. Pro adds Dynamic Number Insertion, Google Ads and Meta attribution, AI transcription and lead scoring, sentiment and intent analysis, call recording, a power dialer with a browser softphone, and 1,000 minutes at $0.40/min overage.
Elite at $1,200/mo makes sense when you want campaign building, landing pages, ad creative, Google Business Profile management, AI review replies, LSA lead management, and the Jarvis AI Assistant handled inside the same platform, with 2,500 minutes at $0.35/min overage. All three plans are month-to-month with zero setup fees and unlimited users. Full detail at /pricing.
If you are currently deciding between buying five separate tools and buying one platform, the tradeoff analysis is in all-in-one versus point solutions. Speed of first response, which is the mechanism behind most of the gain described here, is broken down in the speed-to-lead guide.
Want to see this run against your own call volume and bid pile? Get in touch.
