The voicemail is warm, which is what makes it awkward.
"Hi, this is Carol Beaudry. You did our roof, must be three years ago now? On Ashworth? We loved how it turned out. Anyway, we're finally doing something about the garage, and we didn't even consider calling anyone else. Give us a ring."
A repeat client, calling you, pre-sold, three years later. This is the best phone call in the trades (the one every "how to grow your business" article says to engineer) and it just arrived free. Then you try to remember the Beaudry roof and find fog. Ashworth. Three years. Was that the one with the two-layer tear-off? Or was that the other street over? What did it come to? Fourteen something? Sixteen? Did you do the garage flashing then or did they say leave it? Was there a skylight?
You will call Carol back, and she will assume you remember her roof the way she does, vividly, because it was the biggest check she wrote that year. You will perform warm recognition while knowing almost nothing, and then you will go quote her garage the way you would quote a stranger's: from scratch, from guesses. The relationship is three years old. Your knowledge of it is three minutes old.
Three questions decide whether a callback client gets stranger treatment or family treatment, and none of them can be answered from memory at three years' distance: What exactly did we do? What did we charge? What did it look like?
Where the old systems go to die
Most crews technically have this information. Somewhere. The question is whether it survived three years of real life, and the usual archives fail in characteristic ways.
The phone. The photos of the Beaudry roof are on the phone you had three years ago: the one with the cracked screen, now either traded in or sitting in a drawer with a dead battery and a charging port full of drywall dust. Even if the photos migrated through backups, they are ten thousand photos deep, unlabeled, between lumberyard receipts and somebody's birthday.
The binder, the folder, the box. Paper systems are usually one person's discipline, and they die when that person gets busy. The binder that was immaculate through the first two years has a gap starting the summer you took on the second crew. The Beaudry file might be there. It might be the one that rode on the dashboard for a month.
The email thread. Searchable, in theory. In practice: which address did Carol use, was the final quote the attachment called v3 or the numbers you agreed to by phone after v3, and is the photo set in the thread or was that a text? Reconstruction from email is an afternoon, and you have an hour.
Memory. The cruelest one, because it feels reliable. You remember the Beaudry job: you can picture the street, the weather, some guy's dog. What memory does not keep is the numbers: squares, hours, the surprise that ate a day, the price. Memory keeps the movie and loses the ledger, and the callback needs the ledger.
The archive that doesn't rot
In Zeus, the Beaudry roof is not in a drawer. Finished jobs stay searchable forever. Closing a job archives it. It does not shred it. Type "Beaudry" or "Ashworth" and the whole record stands back up:
The scope, as built. The line items that were actually quoted and invoiced: tear-off, two layers, ice-and-water to code, the skylight flashing kit (so there was a skylight), the vents. Not your reconstruction of the scope; the scope.
The money, as charged. Quote, invoice, payments: $15,400, as it happens, so both of your guesses were wrong. And within it, the pricing structure you used then: what the tear-off ran per square, what you billed the flashing at.
The pictures, in place. Job photos GPS-matched to the job at capture time, meaning the tear-off progress shots, the sheathing surprise on the north face and the finished roof from the street are all attached to Beaudry, not adrift in a camera roll. Three years later this is the difference between "we have photos somewhere" and "here are the photos."
The day-by-day. Day logs and per-job time records: it took the crew four days, not the three you would have sworn, because day two rained out and day three found soft sheathing. That sheathing note is now the most valuable sentence in the file: it is the north-face warning for the garage.
The paper they saw. The Sent Documents archive holds the actual PDFs that went to Carol: the exact quote she accepted, the exact invoices she paid, with the signature still on the signed one. Not a re-render from current data; what you sent, as you sent it. If Carol says "I thought last time the flashing was included," you are both looking at the same page she is remembering, in seconds.
None of this required an act of archiving. It is the exhaust of having run the job through the system: the quote you sent, the photos the crew took, the hours they clocked, the logs they wrote. The filing happened because the working happened. That is the property paper systems never had. The archive builds itself out of the job, so it has no gap starting the summer you got busy.
How do you price a repeat job from the old one?
Now run the callback properly, because this is where the archive pays cash.
Five minutes at the curb before you knock: open the Beaudry job. Roof was $15,400 for 24 squares, so call it $640 a square, all-in, 2023 pricing. Four crew-days including a rain day and the sheathing repair, which you billed as a change order at $700 (there is the record of how you handled surprises with this client: smoothly, in writing, and she signed it same-day, which tells you plenty about Carol). The garage is maybe 6 squares, same shingle, one simple plane, no skylight.
The wrong move is the one that feels loyal: quote the garage off 2023's $640 a square because "that's what they paid last time." Three years have moved your shingle cost, your labor, your insurance, your everything. History is the baseline, not the price. The right move takes ten minutes: start from the 2023 structure, which you know worked (it was accepted, built, and paid without a fight), and reprice the components at today's rates. Say materials are up a fifth and your labor rate has moved: the garage pencils out around $4,300, and you can see every step from the old number to the new one.
That visible bridge does more than settle your own math. It is the quote conversation, handed to you:
"Carol, I pulled up your roof file before I came over: 2023, twenty-four squares, we found some soft sheathing on the north side and fixed it as we went, you signed off same day, good memory. Garage is about a quarter the roof in size. Same shingle's still available. Prices have moved since '23, materials mostly, so it lands around $4,300 where it'd have been about $3,850 back then. And I'll check that garage sheathing before we start, since the house had that soft spot."
Every sentence in that is doing work. I pulled up your file says she is a client, not a lead. The sheathing detail says you know her house better than any competitor bidding blind. The old-price-to-new-price bridge kills the "you're charging more than last time" objection before it forms, because you raised it first, with a reason. And the whole thing took fifteen minutes, standing on knowledge, instead of an evening of guessing followed by a week of hoping you guessed high enough. The two classic callback failures are quoting low out of misremembered loyalty, and quoting a nervous stranger-price to someone who expected family.
The habit that pays in three years
Honest limit, and it is the load-bearing one: the archive is only as good as what the crew put in it. Zeus keeps everything forever, but "everything" is defined on the job site, in the moment. A job that ran through the system with no photos and empty day logs archives into a skeleton: scope and money, which is still far better than fog, but no north-face warning, no progress shots to show Carol at her kitchen table.
Which reframes the capture habits every owner nags about. Photos at each stage, a one-line day log, hours clocked to the job. Pitched as today's discipline, they feel like overhead for a job you will finish either way. Pitched as a deposit in the archive, they are the difference, three years out, between the contractor who says "I think it went fine" and the one who says "here's what we did, here's what we found, here's what it looked like the day we left." Every job you close well is a quote you will barely have to write later, because the repeat call always comes, always years later, always after memory has quietly sold the file.
Carol's garage, by the way, is how it compounds: that job is now in the archive too. When she calls in 2029 about the porch, the file will be twice as deep.
Frequently asked questions
Do finished jobs ever get purged or age out?
No. Finished jobs stay searchable indefinitely; closing a job moves it out of your active boards, not out of existence. The three-year-old file and the three-week-old file are equally retrievable, by client name or address. The practical limit is the one above: retention is forever, but it can only retain what was captured.
What if the callback client was never in the system because the job predates it?
Then that job is fog, and nothing retroactively fixes fog; you quote it the honest way, as new work with fresh eyes. The actionable version of this question points forward: the archive starts paying at year one and compounds after that, so every job that runs through the system from today is a future callback you will answer from records. The best time to have started was three years ago. The available time is this job.
Is showing a client their old pricing asking for trouble?
Mostly the opposite, if you drive the conversation. The old price is the anchor the client half-remembers anyway. Controlling it beats being ambushed by it. Bridge it out loud: what it was, what moved (materials, labor, three years), what it is now. Clients accept "prices changed since 2023" without friction; what they punish is the feeling that the number is arbitrary. A visible bridge is the least arbitrary a number can look. The exception is a job you badly mispriced back then. In that case the file just warned you, which is also the archive doing its job.
We're a small crew. Is per-job photo and log discipline realistic?
Keep the bar low and mandatory rather than high and optional: photos at start, at anything surprising, and at finish; one sentence per day in the log; hours clocked to the job. That is under five minutes a day and it is the whole deposit. The crews that fail at this are the ones that aim for beautiful documentation and quit in a busy week. Three photos and a sentence, every job, survives busy weeks, and three years later it is the file that answers Carol.
ZEUS