Sperber Replaced Payroll File-Watching Scripts With Files.com Expectations

Sperber Landscape Companies was built fast, and built by acquisition. Founded in 2019 as a private-equity-backed platform, the national commercial landscaping group assembled a portfolio of regional operators stretching from Hawaii to Florida, each brand keeping its own name and local standing while Sperber supplied the resources behind it. By its third year of operation it had climbed into the top ten of the industry's LM150 ranking, with more than 1,500 employees serving resorts, corporate campuses, municipalities, and commercial properties across the country.

A company assembled that way runs its back office centrally, and the part of the back office that can never be late is payroll. At Sperber, paying more than 1,500 people across all of those brands depends on a daily rhythm of payroll check files produced by the Innova payroll system, delivered over SFTP, and read downstream by NetSuite. The entire chain rests on one fact no SFTP server can report on its own: whether today's file actually showed up.

When a Payroll File Didn't Arrive, Nothing Happened

SFTP has a blind spot. A server does something when a file lands and nothing at all when it doesn't. A transfer that fails throws an error; a transfer that never starts throws nothing. When a file didn't show up, nobody knew until someone checked.

That someone was Sperber's help desk. The team monitored arrivals by hand and wrote its own scripts to fill the gap: scripts to test whether the expected file had landed, scripts to move files to archive after processing, and a manual alarm when a file sat unread too long. Detecting absence is structurally harder than reacting to arrival. The scripts had to know what was expected, check on a schedule, and tell "not yet" apart from "never coming." A payroll-critical file could still sit missing for hours before anyone looked, and the monitoring existed at all only because a small team kept rebuilding it by hand.

The arrangement stopped being tenable when the pattern needed to grow. The help desk was standing up a new SFTP endpoint to receive check files, and the choice in front of the team was plain: wrap the new endpoint in another layer of the same custom scripting, or find a receiving platform that treated a missing file as a failure in its own right. It needed to know which files were due each day, raise an alert when they did not come, and handle the archival lifecycle after they were read, all without custom code to maintain.

“If that doesn't happen, create a report that shoots an email ... that says we didn't receive the files as expected.”

Sperber selected Files.com to be that endpoint.

An Endpoint That Expects the File

Daniel Vasquez, a system engineer on the help desk team, built the workflow end to end and carried it into production himself. Daily payroll check files from Innova were configured to land on Files.com over SFTP.

The monitoring the team used to script became configuration. Using Files.com Expectations, the site held a standing definition of what a correct delivery looked like: the daily file, in its folder, by its deadline. When the file arrives, the window closes clean. When it doesn't, Files.com generates an email alert to the help desk because the platform itself knows a file was due.

The same error path covers the second half of the lifecycle. A Files.com Automation moves read files into dated archive folders and copies them onward into Sperber's SharePoint sites. If a file remains unread within the day, the alert fires again. The help desk is told about both failure modes—the file that never came and the file that came and sat unread—while manual archiving and SharePoint copying are removed from the daily process.

A Missing File Is an Alert, Not a Discovery

With the workflow in production, Sperber replaced hand-monitored arrivals and in-house arrival-checking scripts with alerts the platform raises itself.

• A missing payroll check file is now an email to the help desk, raised the day it happens, instead of something someone discovers by opening a folder.
• A file that arrives but goes unread trips the same alert, so a stalled downstream step surfaces as quickly as a missing upstream one.
• The daily chore is gone. Files are classified, archived into dated folders, and copied into SharePoint with nobody touching them, and there are no scripts left to maintain.

The pattern also compounds. An Expectation is configuration, not code, so the next scheduled feed Sperber takes in is another arrival definition and another archive rule on the same platform, not another script for the help desk to write and keep alive. What was a bespoke build the first time is now a standard the team can repeat.

The Help Desk Stopped Watching the Folder

Before Files.com, the reliability of Sperber's payroll file feed was a property of people. It held up because a help desk team kept checking and kept its scripts running. Now it is a property of the platform.