CrispLinen Case Study Home Customer Stories CrispLinen CrispLinen Saved $72,000 in Annual Fuel Costs with Upper A Baltimore-Washington linen and uniform rental company rebuilt 8-year-old routes from memory-based driver runs into documented, optimized zones, cutting fuel expenses by 25%, achieving 96% on-time delivery, and ensuring zero customer losses during driver transitions. In Conversation with Nathan Briggs, Route Manager, CrispLinen Key Results $72K/yr Fuel cost savings 96% On-time delivery rate Zero Customer losses during driver transitions 3 Previously canceled customers returned The Challenge When Nathan Briggs took over as Route Manager at CrispLinen, he inherited a routing system that existed almost entirely inside the heads of 22 drivers. Routes had been passed down and modified over 8 years of management changes. No master document described who delivered where, on which days, or in what order. Drivers ran their routes from memory, and each had developed their own sequence, shortcuts, and customer relationships over years of repetition. The system worked, barely, as long as every driver showed up every day. The moment one didn’t, the fragility became obvious. Driver #8 had been with CrispLinen for six years and ran a route covering 85 accounts across the Baltimore harbor area. Restaurants, hotels, and a marina resort all depended on his Tuesday and Thursday deliveries. When Driver #8 resigned with two weeks’ notice, Nathan faced an immediate problem: nobody else knew the route. There was no written record of which accounts were on it, what day each received service, or what the receiving instructions were. Three customers canceled within two weeks of Driver #8’s departure: Nathan scrambled to rebuild the route from billing records, but billing data didn’t include delivery days, stop sequences, or the specific instructions customers had given Driver #8 over six years. A hotel that required delivery through the service entrance before 7am received its linens at the front desk at 10am. A restaurant that accepted deliveries only between 2pm and 4pm got a 9am knock on a locked door. The confusion drove three accounts to competitors. Drivers crossing each other’s paths daily: Without centralized route planning, drivers’ territories overlapped extensively. Nathan tracked two drivers one morning and found they passed within a block of each other four times during the day, each visiting different customers in the same neighborhood. Across 22 drivers, the wasted mileage was enormous. Fuel costs 25% above industry benchmarks: CrispLinen spent $288,000 annually on fuel. Nathan benchmarked this against industry averages for a fleet of similar size and geography and found CrispLinen was overspending by roughly $72,000 per year. The excess cost came directly from unoptimized routes and territorial overlap. New driver onboarding took 2-3 weeks: When a new driver was hired, they rode along with an experienced driver for 5 to 7 days, then ran the route solo while calling the office repeatedly for directions and receiving instructions. Full independence took 2 to 3 weeks. During that period, service quality suffered and customer complaints spiked. When Driver #8 quit, his route went with him. Six years of customer knowledge, receiving instructions, building access codes, preferred delivery times. All of it was in his head. I spent two weeks calling 85 customers asking them to tell me how their own deliveries worked. Three of them didn’t wait around for me to figure it out. Nathan Briggs Route Manager, CrispLinen Nathan recognized that the tribal knowledge problem wasn’t unique to Driver #8. Every one of CrispLinen’s 22 drivers carried the same risk. If any driver left, retired, or was injured, their route became a guessing game. Nathan needed to extract the institutional knowledge from 22 heads and put it into a system that anyone could operate on day one. The Solution Nathan chose Upper after testing it with a single zone of 4 drivers and 320 accounts. The optimization results were clear enough that he committed to a full fleet rebuild within a month. The migration started with data extraction. Nathan spent two weeks working with drivers to document every account: delivery days, receiving instructions, access codes, contact names, preferred times, and special handling notes. He compiled everything into a master spreadsheet with 1,800 rows. Using Upper’s CSV import, he loaded the entire customer database in one session, with all receiving instructions saved as stop notes attached to each account. The spreadsheet took two weeks to build, but it was the most valuable two weeks I’ve spent at this company. For the first time in eight years, we had a complete record of every customer, every delivery day, and every special instruction. That document didn’t exist before. Nathan Briggs Route Manager, CrispLinen A Complete Route Rebuild by Geography and Volume Nathan didn’t try to optimize the existing route structure. He started from zero. Using Upper’s route optimization, he divided the Baltimore-Washington corridor into 5 geographic zones and assigned 4 to 5 drivers per zone. The algorithm distributed accounts within each zone to minimize drive time while respecting delivery day assignments and time preferences. The new routes looked dramatically different from the old ones. Drivers who had been crisscrossing the same neighborhoods now operated in tight geographic clusters. The overlap that had been wasting fuel for years was eliminated. Two drivers who had been passing each other four times daily now served adjacent, non-overlapping territories. Every route was saved as a recurring template in Upper’s scheduling system. Monday routes, Tuesday routes, and so on, each optimized for that day’s specific set of accounts. The templates meant routes were consistent week to week but could be adjusted when new accounts were added or existing ones changed their delivery schedule. Documented Routes That Any Driver Can Run The stop notes feature solved the tribal knowledge problem. Every account in Upper carried detailed receiving instructions: which entrance to use, who to ask for, where to leave deliveries if the contact wasn’t available, access codes for gated facilities, and any special handling requirements. When a new driver opened their route in the Upper app, every piece of information they needed was attached to each stop. Nathan tested the system two months in when a driver called in sick on a Wednesday morning. He assigned the route to a substitute driver who had never visited any of the accounts. The substitute opened Upper, saw the optimized sequence, read the stop notes at each location, and completed the route without a single phone call to the office. No customer noticed the change. I used to dread the phone call at 5am telling me a driver was sick. It meant my whole morning was spent putting out fires. Now I reassign the route in Upper, the substitute driver opens the app, and the day runs itself. The customers don’t know and don’t care who’s driving. They just get their linens on time. Nathan Briggs Route Manager, CrispLinen Real-Time Visibility Across the Corridor With 22 drivers covering territory from Baltimore to Washington, D.C., Nathan had historically relied on phone check-ins to know where drivers were. That meant he knew each driver’s approximate location twice a day: once at the midpoint call-in and once when they returned to the facility. Upper’s live fleet tracking gave Nathan a real-time view of the entire fleet on a single map. He could see which drivers were ahead of schedule, which were running behind, and whether any route needed adjustment. When a major client in Arlington called requesting an early pickup, Nathan identified the nearest driver, added the stop to their route, and confirmed a 30-minute ETA without making a single phone call to a driver. The Impact CrispLinen’s route rebuild produced measurable results across every operational metric, but the most significant change was structural. The business no longer depended on any individual driver’s knowledge to function. Routes, customer instructions, and delivery schedules existed in a system that was accessible to anyone, documented, and optimized. Fuel costs dropped $72,000 annually. The 20-25% improvement came from eliminating territorial overlap, tightening geographic clusters, and letting Upper’s algorithm sequence stops by proximity rather than by driver habit. Nathan tracked fuel consumption monthly and saw the reduction stabilize after the first six weeks, confirming it was a permanent efficiency gain rather than a one-time adjustment. On-time delivery performance jumped from 84% to 96%. The improvement came from two sources: optimized routes that accounted for service times and delivery windows, and the elimination of sequence errors that occurred when drivers ran from memory. Customers who had experienced inconsistent delivery times for years noticed the change. Three previously canceled customers, including one of the accounts lost during Driver #8’s departure, returned after hearing from other businesses that CrispLinen’s service had improved. Performance Metrics MetricsBefore UpperAfter Upper Annual fuel costs$288,000$216,000 ($72K savings) On-time delivery rate84%96% Customer losses during driver transitions3 in one incidentZero New driver readiness2-3 weeks (ride-alongs + training)Day one (app + stop notes) Route documentationNone (driver memory only)Full stop notes, recurring templates Driver territorial overlapExtensive (drivers crossing paths daily)Eliminated (5 geographic zones) Canceled customers recoveredN/A3 returned New driver onboarding became a non-event. CrispLinen hired four new drivers over the following year. Each completed a half-day orientation covering the Upper app, vehicle procedures, and customer service expectations. On their second day, they ran a full route solo using Upper’s app and stop notes. None required a ride-along. The longest any new driver took to reach full proficiency was three days, compared to the previous 2 to 3 weeks. Nathan restructured his own role as well. Before Upper, he spent most of his day managing route emergencies: covering for absent drivers, resolving delivery disputes, and fielding customer complaints about timing. After the rebuild, his focus shifted to account growth and service quality. He used Upper’s data to identify underperforming routes, optimize zone boundaries as new accounts were added, and prepare accurate bids for prospective clients using real route and time data. CrispLinen now operates a delivery system that is resilient to the one thing every service business faces eventually: people leaving. Routes are documented, optimized, and transferable. The knowledge that used to walk out the door with every departing driver now stays in the system, accessible to whoever runs the route next. We used to be one resignation away from chaos. Now we’re a route management company that happens to deliver linens. The routes run the business. The drivers execute. And when someone leaves, the route stays. Nathan Briggs Route Manager, CrispLinen
CrispLinen Saved $72,000 in Annual Fuel Costs with Upper A Baltimore-Washington linen and uniform rental company rebuilt 8-year-old routes from memory-based driver runs into documented, optimized zones, cutting fuel expenses by 25%, achieving 96% on-time delivery, and ensuring zero customer losses during driver transitions. In Conversation with Nathan Briggs, Route Manager, CrispLinen
The Challenge When Nathan Briggs took over as Route Manager at CrispLinen, he inherited a routing system that existed almost entirely inside the heads of 22 drivers. Routes had been passed down and modified over 8 years of management changes. No master document described who delivered where, on which days, or in what order. Drivers ran their routes from memory, and each had developed their own sequence, shortcuts, and customer relationships over years of repetition. The system worked, barely, as long as every driver showed up every day. The moment one didn’t, the fragility became obvious. Driver #8 had been with CrispLinen for six years and ran a route covering 85 accounts across the Baltimore harbor area. Restaurants, hotels, and a marina resort all depended on his Tuesday and Thursday deliveries. When Driver #8 resigned with two weeks’ notice, Nathan faced an immediate problem: nobody else knew the route. There was no written record of which accounts were on it, what day each received service, or what the receiving instructions were. Three customers canceled within two weeks of Driver #8’s departure: Nathan scrambled to rebuild the route from billing records, but billing data didn’t include delivery days, stop sequences, or the specific instructions customers had given Driver #8 over six years. A hotel that required delivery through the service entrance before 7am received its linens at the front desk at 10am. A restaurant that accepted deliveries only between 2pm and 4pm got a 9am knock on a locked door. The confusion drove three accounts to competitors. Drivers crossing each other’s paths daily: Without centralized route planning, drivers’ territories overlapped extensively. Nathan tracked two drivers one morning and found they passed within a block of each other four times during the day, each visiting different customers in the same neighborhood. Across 22 drivers, the wasted mileage was enormous. Fuel costs 25% above industry benchmarks: CrispLinen spent $288,000 annually on fuel. Nathan benchmarked this against industry averages for a fleet of similar size and geography and found CrispLinen was overspending by roughly $72,000 per year. The excess cost came directly from unoptimized routes and territorial overlap. New driver onboarding took 2-3 weeks: When a new driver was hired, they rode along with an experienced driver for 5 to 7 days, then ran the route solo while calling the office repeatedly for directions and receiving instructions. Full independence took 2 to 3 weeks. During that period, service quality suffered and customer complaints spiked. When Driver #8 quit, his route went with him. Six years of customer knowledge, receiving instructions, building access codes, preferred delivery times. All of it was in his head. I spent two weeks calling 85 customers asking them to tell me how their own deliveries worked. Three of them didn’t wait around for me to figure it out. Nathan Briggs Route Manager, CrispLinen Nathan recognized that the tribal knowledge problem wasn’t unique to Driver #8. Every one of CrispLinen’s 22 drivers carried the same risk. If any driver left, retired, or was injured, their route became a guessing game. Nathan needed to extract the institutional knowledge from 22 heads and put it into a system that anyone could operate on day one. The Solution Nathan chose Upper after testing it with a single zone of 4 drivers and 320 accounts. The optimization results were clear enough that he committed to a full fleet rebuild within a month. The migration started with data extraction. Nathan spent two weeks working with drivers to document every account: delivery days, receiving instructions, access codes, contact names, preferred times, and special handling notes. He compiled everything into a master spreadsheet with 1,800 rows. Using Upper’s CSV import, he loaded the entire customer database in one session, with all receiving instructions saved as stop notes attached to each account. The spreadsheet took two weeks to build, but it was the most valuable two weeks I’ve spent at this company. For the first time in eight years, we had a complete record of every customer, every delivery day, and every special instruction. That document didn’t exist before. Nathan Briggs Route Manager, CrispLinen A Complete Route Rebuild by Geography and Volume Nathan didn’t try to optimize the existing route structure. He started from zero. Using Upper’s route optimization, he divided the Baltimore-Washington corridor into 5 geographic zones and assigned 4 to 5 drivers per zone. The algorithm distributed accounts within each zone to minimize drive time while respecting delivery day assignments and time preferences. The new routes looked dramatically different from the old ones. Drivers who had been crisscrossing the same neighborhoods now operated in tight geographic clusters. The overlap that had been wasting fuel for years was eliminated. Two drivers who had been passing each other four times daily now served adjacent, non-overlapping territories. Every route was saved as a recurring template in Upper’s scheduling system. Monday routes, Tuesday routes, and so on, each optimized for that day’s specific set of accounts. The templates meant routes were consistent week to week but could be adjusted when new accounts were added or existing ones changed their delivery schedule. Documented Routes That Any Driver Can Run The stop notes feature solved the tribal knowledge problem. Every account in Upper carried detailed receiving instructions: which entrance to use, who to ask for, where to leave deliveries if the contact wasn’t available, access codes for gated facilities, and any special handling requirements. When a new driver opened their route in the Upper app, every piece of information they needed was attached to each stop. Nathan tested the system two months in when a driver called in sick on a Wednesday morning. He assigned the route to a substitute driver who had never visited any of the accounts. The substitute opened Upper, saw the optimized sequence, read the stop notes at each location, and completed the route without a single phone call to the office. No customer noticed the change. I used to dread the phone call at 5am telling me a driver was sick. It meant my whole morning was spent putting out fires. Now I reassign the route in Upper, the substitute driver opens the app, and the day runs itself. The customers don’t know and don’t care who’s driving. They just get their linens on time. Nathan Briggs Route Manager, CrispLinen Real-Time Visibility Across the Corridor With 22 drivers covering territory from Baltimore to Washington, D.C., Nathan had historically relied on phone check-ins to know where drivers were. That meant he knew each driver’s approximate location twice a day: once at the midpoint call-in and once when they returned to the facility. Upper’s live fleet tracking gave Nathan a real-time view of the entire fleet on a single map. He could see which drivers were ahead of schedule, which were running behind, and whether any route needed adjustment. When a major client in Arlington called requesting an early pickup, Nathan identified the nearest driver, added the stop to their route, and confirmed a 30-minute ETA without making a single phone call to a driver. The Impact CrispLinen’s route rebuild produced measurable results across every operational metric, but the most significant change was structural. The business no longer depended on any individual driver’s knowledge to function. Routes, customer instructions, and delivery schedules existed in a system that was accessible to anyone, documented, and optimized. Fuel costs dropped $72,000 annually. The 20-25% improvement came from eliminating territorial overlap, tightening geographic clusters, and letting Upper’s algorithm sequence stops by proximity rather than by driver habit. Nathan tracked fuel consumption monthly and saw the reduction stabilize after the first six weeks, confirming it was a permanent efficiency gain rather than a one-time adjustment. On-time delivery performance jumped from 84% to 96%. The improvement came from two sources: optimized routes that accounted for service times and delivery windows, and the elimination of sequence errors that occurred when drivers ran from memory. Customers who had experienced inconsistent delivery times for years noticed the change. Three previously canceled customers, including one of the accounts lost during Driver #8’s departure, returned after hearing from other businesses that CrispLinen’s service had improved. Performance Metrics MetricsBefore UpperAfter Upper Annual fuel costs$288,000$216,000 ($72K savings) On-time delivery rate84%96% Customer losses during driver transitions3 in one incidentZero New driver readiness2-3 weeks (ride-alongs + training)Day one (app + stop notes) Route documentationNone (driver memory only)Full stop notes, recurring templates Driver territorial overlapExtensive (drivers crossing paths daily)Eliminated (5 geographic zones) Canceled customers recoveredN/A3 returned New driver onboarding became a non-event. CrispLinen hired four new drivers over the following year. Each completed a half-day orientation covering the Upper app, vehicle procedures, and customer service expectations. On their second day, they ran a full route solo using Upper’s app and stop notes. None required a ride-along. The longest any new driver took to reach full proficiency was three days, compared to the previous 2 to 3 weeks. Nathan restructured his own role as well. Before Upper, he spent most of his day managing route emergencies: covering for absent drivers, resolving delivery disputes, and fielding customer complaints about timing. After the rebuild, his focus shifted to account growth and service quality. He used Upper’s data to identify underperforming routes, optimize zone boundaries as new accounts were added, and prepare accurate bids for prospective clients using real route and time data. CrispLinen now operates a delivery system that is resilient to the one thing every service business faces eventually: people leaving. Routes are documented, optimized, and transferable. The knowledge that used to walk out the door with every departing driver now stays in the system, accessible to whoever runs the route next. We used to be one resignation away from chaos. Now we’re a route management company that happens to deliver linens. The routes run the business. The drivers execute. And when someone leaves, the route stays. Nathan Briggs Route Manager, CrispLinen
The Challenge When Nathan Briggs took over as Route Manager at CrispLinen, he inherited a routing system that existed almost entirely inside the heads of 22 drivers. Routes had been passed down and modified over 8 years of management changes. No master document described who delivered where, on which days, or in what order. Drivers ran their routes from memory, and each had developed their own sequence, shortcuts, and customer relationships over years of repetition. The system worked, barely, as long as every driver showed up every day. The moment one didn’t, the fragility became obvious. Driver #8 had been with CrispLinen for six years and ran a route covering 85 accounts across the Baltimore harbor area. Restaurants, hotels, and a marina resort all depended on his Tuesday and Thursday deliveries. When Driver #8 resigned with two weeks’ notice, Nathan faced an immediate problem: nobody else knew the route. There was no written record of which accounts were on it, what day each received service, or what the receiving instructions were. Three customers canceled within two weeks of Driver #8’s departure: Nathan scrambled to rebuild the route from billing records, but billing data didn’t include delivery days, stop sequences, or the specific instructions customers had given Driver #8 over six years. A hotel that required delivery through the service entrance before 7am received its linens at the front desk at 10am. A restaurant that accepted deliveries only between 2pm and 4pm got a 9am knock on a locked door. The confusion drove three accounts to competitors. Drivers crossing each other’s paths daily: Without centralized route planning, drivers’ territories overlapped extensively. Nathan tracked two drivers one morning and found they passed within a block of each other four times during the day, each visiting different customers in the same neighborhood. Across 22 drivers, the wasted mileage was enormous. Fuel costs 25% above industry benchmarks: CrispLinen spent $288,000 annually on fuel. Nathan benchmarked this against industry averages for a fleet of similar size and geography and found CrispLinen was overspending by roughly $72,000 per year. The excess cost came directly from unoptimized routes and territorial overlap. New driver onboarding took 2-3 weeks: When a new driver was hired, they rode along with an experienced driver for 5 to 7 days, then ran the route solo while calling the office repeatedly for directions and receiving instructions. Full independence took 2 to 3 weeks. During that period, service quality suffered and customer complaints spiked.
When Driver #8 quit, his route went with him. Six years of customer knowledge, receiving instructions, building access codes, preferred delivery times. All of it was in his head. I spent two weeks calling 85 customers asking them to tell me how their own deliveries worked. Three of them didn’t wait around for me to figure it out. Nathan Briggs Route Manager, CrispLinen
Nathan recognized that the tribal knowledge problem wasn’t unique to Driver #8. Every one of CrispLinen’s 22 drivers carried the same risk. If any driver left, retired, or was injured, their route became a guessing game. Nathan needed to extract the institutional knowledge from 22 heads and put it into a system that anyone could operate on day one.
The Solution Nathan chose Upper after testing it with a single zone of 4 drivers and 320 accounts. The optimization results were clear enough that he committed to a full fleet rebuild within a month. The migration started with data extraction. Nathan spent two weeks working with drivers to document every account: delivery days, receiving instructions, access codes, contact names, preferred times, and special handling notes. He compiled everything into a master spreadsheet with 1,800 rows. Using Upper’s CSV import, he loaded the entire customer database in one session, with all receiving instructions saved as stop notes attached to each account.
The spreadsheet took two weeks to build, but it was the most valuable two weeks I’ve spent at this company. For the first time in eight years, we had a complete record of every customer, every delivery day, and every special instruction. That document didn’t exist before. Nathan Briggs Route Manager, CrispLinen
A Complete Route Rebuild by Geography and Volume Nathan didn’t try to optimize the existing route structure. He started from zero. Using Upper’s route optimization, he divided the Baltimore-Washington corridor into 5 geographic zones and assigned 4 to 5 drivers per zone. The algorithm distributed accounts within each zone to minimize drive time while respecting delivery day assignments and time preferences. The new routes looked dramatically different from the old ones. Drivers who had been crisscrossing the same neighborhoods now operated in tight geographic clusters. The overlap that had been wasting fuel for years was eliminated. Two drivers who had been passing each other four times daily now served adjacent, non-overlapping territories. Every route was saved as a recurring template in Upper’s scheduling system. Monday routes, Tuesday routes, and so on, each optimized for that day’s specific set of accounts. The templates meant routes were consistent week to week but could be adjusted when new accounts were added or existing ones changed their delivery schedule.
Documented Routes That Any Driver Can Run The stop notes feature solved the tribal knowledge problem. Every account in Upper carried detailed receiving instructions: which entrance to use, who to ask for, where to leave deliveries if the contact wasn’t available, access codes for gated facilities, and any special handling requirements. When a new driver opened their route in the Upper app, every piece of information they needed was attached to each stop. Nathan tested the system two months in when a driver called in sick on a Wednesday morning. He assigned the route to a substitute driver who had never visited any of the accounts. The substitute opened Upper, saw the optimized sequence, read the stop notes at each location, and completed the route without a single phone call to the office. No customer noticed the change.
I used to dread the phone call at 5am telling me a driver was sick. It meant my whole morning was spent putting out fires. Now I reassign the route in Upper, the substitute driver opens the app, and the day runs itself. The customers don’t know and don’t care who’s driving. They just get their linens on time. Nathan Briggs Route Manager, CrispLinen
Real-Time Visibility Across the Corridor With 22 drivers covering territory from Baltimore to Washington, D.C., Nathan had historically relied on phone check-ins to know where drivers were. That meant he knew each driver’s approximate location twice a day: once at the midpoint call-in and once when they returned to the facility. Upper’s live fleet tracking gave Nathan a real-time view of the entire fleet on a single map. He could see which drivers were ahead of schedule, which were running behind, and whether any route needed adjustment. When a major client in Arlington called requesting an early pickup, Nathan identified the nearest driver, added the stop to their route, and confirmed a 30-minute ETA without making a single phone call to a driver.
The Impact CrispLinen’s route rebuild produced measurable results across every operational metric, but the most significant change was structural. The business no longer depended on any individual driver’s knowledge to function. Routes, customer instructions, and delivery schedules existed in a system that was accessible to anyone, documented, and optimized. Fuel costs dropped $72,000 annually. The 20-25% improvement came from eliminating territorial overlap, tightening geographic clusters, and letting Upper’s algorithm sequence stops by proximity rather than by driver habit. Nathan tracked fuel consumption monthly and saw the reduction stabilize after the first six weeks, confirming it was a permanent efficiency gain rather than a one-time adjustment. On-time delivery performance jumped from 84% to 96%. The improvement came from two sources: optimized routes that accounted for service times and delivery windows, and the elimination of sequence errors that occurred when drivers ran from memory. Customers who had experienced inconsistent delivery times for years noticed the change. Three previously canceled customers, including one of the accounts lost during Driver #8’s departure, returned after hearing from other businesses that CrispLinen’s service had improved.
Performance Metrics MetricsBefore UpperAfter Upper Annual fuel costs$288,000$216,000 ($72K savings) On-time delivery rate84%96% Customer losses during driver transitions3 in one incidentZero New driver readiness2-3 weeks (ride-alongs + training)Day one (app + stop notes) Route documentationNone (driver memory only)Full stop notes, recurring templates Driver territorial overlapExtensive (drivers crossing paths daily)Eliminated (5 geographic zones) Canceled customers recoveredN/A3 returned
New driver onboarding became a non-event. CrispLinen hired four new drivers over the following year. Each completed a half-day orientation covering the Upper app, vehicle procedures, and customer service expectations. On their second day, they ran a full route solo using Upper’s app and stop notes. None required a ride-along. The longest any new driver took to reach full proficiency was three days, compared to the previous 2 to 3 weeks. Nathan restructured his own role as well. Before Upper, he spent most of his day managing route emergencies: covering for absent drivers, resolving delivery disputes, and fielding customer complaints about timing. After the rebuild, his focus shifted to account growth and service quality. He used Upper’s data to identify underperforming routes, optimize zone boundaries as new accounts were added, and prepare accurate bids for prospective clients using real route and time data. CrispLinen now operates a delivery system that is resilient to the one thing every service business faces eventually: people leaving. Routes are documented, optimized, and transferable. The knowledge that used to walk out the door with every departing driver now stays in the system, accessible to whoever runs the route next.
We used to be one resignation away from chaos. Now we’re a route management company that happens to deliver linens. The routes run the business. The drivers execute. And when someone leaves, the route stays. Nathan Briggs Route Manager, CrispLinen
