Reliability
Updated a critical mobile platform
Updated Android and iOS apps removed about 80% of Apex’s initial tech problems, by Dan’s estimate.
Case Study · Multi-Site Field Operations
How Apex Runs Field Work Across 60,000 Apartments From One Platform
Apex needed more than app maintenance. We learned their field operation. We made the tech choices. We stabilized the app. We expanded it to cover field work, customer records, HR, and payroll. We still support it.
About 5 minutes. No sales call required.
Built with Apex Trash, a doorstep trash and property service company serving apartment communities across eight states.
60,000
Apartments served
8 States
Work spread across 8 states
300+
300+ part-time field workers
1 Platform
One platform runs it all
These numbers describe Apex’s operation today. They show what the platform must support. They are not a claim that 21 Solutions caused this growth.
At a glance
Client
Apex Trash — doorstep trash and property checks for apartment communities.
Industry
Field services across many sites, mostly overnight workers.
The challenge
A key field app was outdated, unreliable, and hard for workers to trust.
What 21 Solutions did
We stabilized the system, kept it current, advised Apex on long-term tech choices, and expanded the platform as the business grew.
The business impact
Apex now runs on a more dependable platform for field work, management visibility, CRM, HR, and payroll. They can enter new markets without adding admin staff at the same rate.
When work happens across eight states, “Did we actually complete the service?” becomes a software problem
Apex Trash collects trash at apartment doorsteps and reports what crews find on the property. More than 300 part-time workers cover about 60,000 apartments in eight states. Most work five nights a week; some areas get seven-day service. Almost all work happens at night. Almost no manager sees it in person.
That is why every question Apex must answer the next morning is hard. A property manager calls about a missed pickup. Payroll must close. A resident keeps leaving trash out at the wrong time. None of those talks go well if the only proof is someone’s memory of a shift that ended at night, several states away.
Did the employee actually arrive at the right property?
Did the work happen during the required time window?
Was the service completed to the collection standard?
Was a reported missed pickup a real service failure?
Or was the resident outside the collection guidelines?
What else happened at the property that someone should know about?
Did the employee work the hours being claimed?
What should that employee be paid this period?
Can managers and customers both verify the answer?
Apex answers those questions with location-bound, time-stamped records from the field. The point is not a feature list. In a spread-out service business, software turns a night shift nobody saw into a record everyone can trust.
Apex calls the platform its “control tower”
The app started as a way to track time and document service. Now it is where field workers, the office, and customers meet. Assignments go out through it. Work gets verified in it. Managers review what happened. Customers see their properties. Payroll comes out the other side.
A large part of the company runs through one system. That is why reliability stopped being an IT issue and became an operating issue.
“I refer to the Apex platform as the control tower.”
The Apex platform
One record of what happened, shared by everyone who needs it
Field operations
- Employee assignments and attendance
- Service completion
- Geofenced, timestamped documentation
Management
- Review of what happened overnight
- Visibility across properties and markets
- Customer service history and records
Customers
- Property information
- Transparency into service delivered
- Historical reporting
HR & payroll
- Employee information
- Pay workflows
- Payroll automation, reporting, and exports
Asked what happens if the platform goes down for several days, Dan talked about service integrity and payroll. He ended with the phrase “bring my company to a grinding halt.”
The software became unreliable enough that workers stopped trusting it
21 Solutions did not inherit a system that was down. We inherited one that had quietly fallen behind. The app was built years ago and still ran, but fixes were only done when something broke. The gap between the software and the phones workers carried kept growing.
The mobile applications had fallen behind current Android and iOS device requirements.
Bugs and glitches accumulated instead of getting resolved.
Maintenance was reactive rather than planned.
Responsiveness from the previous provider had deteriorated.
Field employees and district managers began working around the application, because they no longer believed it would work when they needed it.
Critical software does not have to fully crash to hurt the business. Once field workers stop trusting it, they stop using it the way the operation expects — and the operation fails whether the servers are up or not.
First, make the system dependable again
The first work was not a rebuild. We updated the Android and iOS apps for the phones Apex workers actually use — and kept them updated. Not glamorous. By far the highest-value fix.
~80%
Dan estimates modernizing the mobile apps removed about 80% of Apex’s immediate tech problems.
With a dependable app again, Apex could do what no vendor can do for them: tell district managers and field workers the system is worth using again. Trust came first. Adoption followed.
Apex needed senior tech judgment, not another ticket queue
The difference shows in how work starts. Apex does not write tech specs. Dan brings a business goal — something the operation needs, or a problem the field keeps hitting — and 21 Solutions figures out what that means for the platform long term and how to build it.
- Regular planning talks so priorities get set before they become urgent.
- Same-day communication when needed. Dan says he can reach the team the day he needs them.
- A shared, clear definition of what counts as an emergency — agreed ahead of time, not during one.
- Direct talks about priorities and tradeoffs, without account managers in the middle.
- Business goals turned into tech choices by the people who will live with those choices.
- Short-term requests weighed against what they do to the platform two years from now.
“I don’t see you as a vendor. I see you as part of my team.”
Apex brings the business goal. Our tech team finds the responsible way to get there.
Sometimes the right tech choice is to say no
Apex asked us to build a multi-tenant feature a certain way. We looked at it and said no. The goal was fine. That path would have caused long-term problems in a platform Apex depends on every night.
That was paid work, ready to go. Saying no cost us revenue now and saved Apex a problem later.
“I’ve never had a partner say no, looking out for my best interest.”
A project vendor
Is usually hired to finish a defined scope. Deciding whether that scope is the right tech move often stays the client’s job.
A senior technology team
Looks at the platform in three years, not just the ticket this month. That long-term view sometimes means saying “not that way” — and explaining what to do instead.
A dependable tech team should recommend a simpler path or say no when a requested change would create more cost or risk later.
Once the foundation was dependable, Apex could build on it
A system people trust becomes a place to put more of the business. Once the field app was reliable, Apex started moving work that had lived in HubSpot, Google Sheets, Google Drive, and the gaps between them.
Where the platform started
- Time and attendance
- Service documentation from the field
What it coordinates today
- CRM tools for daily operations
- Customer and property records
- Customer-facing property access
- Notes, attachments, and historical records
- Employee and HR information
- Payroll workflows and automated exports
- Reporting across the operation
Still in progress
Apex has moved daily workflows out of HubSpot. Moving data and workflows that still live in Google Sheets, Google Drive, and other tools is ongoing — a planned step-by-step move, not one big switch.
This is not saying custom always beats bought. Apex’s workflows were unusual enough that forcing them into generic tools cost the operation more than building around them.
The business no longer has to reshape itself around somebody else’s software
Dan’s objection to generic platforms is not cost or capability. A packaged product follows someone else’s model of the business, and Apex then has to operate inside that model. Where the workflow is standard, that trade is fine. Where the workflow is part of how the company competes, it is not.
Service-verification requirements specific to doorstep collection
Resident violation tracking
Geofenced, timestamped field documentation
Attendance workflows built for overnight, part-time crews
Management review of what happened in the field
Customer transparency into their own properties
Compensation and payroll logic that matches how Apex actually pays people
Buy standard software where the workflow is standard. Build around the business when the workflow itself matters.
New markets without building a new management layer in every market
Apex has expanded into North and South Carolina. Historically, opening a market meant staffing it: field workers plus a part-time or full-time local manager on the ground to account for what was happening.
Reliable field visibility changed what that structure has to look like. When existing leaders can see whether crews arrived, whether service was completed, and where problems are building, more of a new market can run from the structure Apex already has.
$50K / year
Dan estimates Apex can avoid about $50,000 in manager salary per year when a new market runs without a dedicated local manager.
Client estimate based on Apex’s usual manager staffing.
The HR hire Apex did not have to make
As HR and payroll moved into the platform, Apex expected to hire another HR person. Dan says the new workflow let them skip that hire.
More geographic capacity. More operational visibility. Less pressure to solve every growth problem with another admin hire.
The results
Adoption
Rebuilt trust in the field
A dependable app let Apex rebuild trust with district managers and field workers.
Consolidation
Fewer systems holding the operation together
CRM, service records, HR data, payroll workflows, and reporting are increasingly moving into one operating platform.
Expansion
Growth without adding managers at the same rate
Apex entered new markets without automatically adding dedicated local managers.
Administrative leverage
Avoided an additional HR hire
New HR and payroll tools removed the immediate need to add admin staff.
Continued involvement
Senior support as the business changes
Apex still works directly with the senior team that understands both the operation and the platform.
Client testimonial
In the client’s words
“I don’t see you as a vendor. I see you as part of my team.”
“Without what you’ve done for me, my company would not be where it’s at today.”
Mission-critical software needs long-term attention
A custom app can quietly become one of the most important assets in an operating company. Nobody plans for it. It starts as a tool for one workflow. A few years later payroll runs through it and the customer relationship depends on it.
At that point, writing features is only part of the job. The team supporting it has to understand the operation, protect reliability, make honest tech tradeoffs, and keep adapting the platform as the business changes.
Keep the system current
Understand how the business actually uses it
Protect reliability
Evaluate technical tradeoffs honestly
Push back on bad short-term decisions
Translate operational goals into software
Support the people using it
Evolve the platform as the business changes
That is the role 21 Solutions plays for Apex.
Does your business depend on software that is falling behind?
We help operators figure out what is failing, make the right tech choice, update or extend the system, and support it long term.