How Metro Computer Networks Built Mobile Billing Around Flat-Rate Pricing

Metro Had a Flat-Rate Business. Its FSM Was Built for Hourly Work.

Metro’s business model is straightforward. Services have fixed prices. Parts have fixed prices. The company does not bill by the hour or itemize expenses. The problem was that its mobile billing screen was built around a different model.

Technicians were being asked to work through labor and expense steps on every job, even though Metro had no reason to use them. Jason Alford, owner of Metro Computer Networks, described the mismatch directly: “All my pricing is flat rate, from services and parts. My techs were adding labor and expenses we will never use.”

For a field team that is expected to finish a job, create the invoice, and get paid before leaving the customer’s site, those extra steps were part of a larger problem. The billing process was getting in the way of how Metro actually worked.

The Billing Screen Wasn’t the Only Gap

Once Jason looked closely at the workflow, the problem reached beyond labor and expenses.

Metro needed to mark invoice line items as taxable or non-taxable and show labor separately from parts. The system did not originally support either requirement.

Then QuickBooks started breaking. Work completed in the field was not reliably reaching accounting, creating a growing gap between what technicians had billed and what the office could see.

It started showing up in the field when Metro’s technicians did not simply complete the work and leave the billing for later. They invoiced and collected payment on site, using their phones. When that process did not work cleanly, a payment that should have happened at the door could instead become something accounting had to chase later.

Even website requests had their own gap. A customer could fill out Metro’s request form without there being a straightforward way to route the notification to the right person.

None of these issues was large enough to define the business on its own. Together, they were slowing down a workflow that needed to move quickly.

Two or Three Extra Minutes Was Happening 20 to 25 Times a Day

Metro’s field team was processing roughly 20 to 25 invoices a day, with technicians handling three to four on-site jobs each.

Every invoice carried the same unnecessary labor and expense steps.

At two to three minutes per invoice, the extra work added up to 4 to 6 hours of technician time every week. The missing taxable control was not an occasional edge case either. Because most IT jobs combine parts and labor, the issue touched close to every invoice Metro issued.

Meanwhile, the broken QuickBooks sync meant the accounting side could fall further behind as more work was completed and billed in the field. A system that was supposed to connect the field to the books was creating another gap for the business to manage.

For Metro, the question was no longer whether the billing workflow was inconvenient.

It was whether the software could keep up with the way the company actually charged and collected for its work.

Jason Didn’t Start With a Feature List

On Metro’s first call with Upvoit, Jason asked for one specific change: an invoice creation button on the mobile app’s home screen. It was committed during that call and shipped within days.

After that, the relationship followed the same pattern.

Instead of being handed a fixed process and asked to adapt Metro’s billing model to it, Jason could point to something that did not fit the way his technicians worked and work through a change around that specific need.

The button itself was not what mattered most. What mattered was that Jason saw Metro did not necessarily have to change its process just because the software had been designed differently.

The Mobile Billing Workflow Now Follows the Job

The mobile billing flow was rebuilt around Metro’s flat-rate model.

A technician can finish the work, create the invoice, edit the line items when necessary, capture the customer’s signature, and collect payment on site. The labor and expense steps that had nothing to do with Metro’s pricing model were removed from that flow. The initial rebuild took about a day from the request.

That same logic carries into the invoice itself.

Services and products can now have a default taxable or non-taxable setting, and that setting carries through to the work order. The technician does not have to recreate the same decision every time an invoice is prepared.

The result is a billing workflow that reflects the actual transaction: Fixed-price work → completed in the field → invoiced from the phone → signed by the customer → paid on site.

Customer Emails Were Still Creating Manual Work Orders

The billing problem happened at the end of the job. Metro had another gap at the very beginning.

Customers were already contacting the team by email, but those requests still had to make their way into the work-order process. Someone had to take the information from the email and turn it into something the field team could actually work from.

For Metro, that became another workflow worth fixing.

Upvoit built and launched AI Mailbox, which automatically turns incoming customer emails into work orders. Instead of letting a customer request sit in an inbox until someone manually recreates it, the request can move directly into the work-order process.

That gave Metro a more connected path from customer request → work order → technician.

And it reinforced the same thing Jason had already seen with billing: when the existing workflow did not match the way Metro operated, the answer was not necessarily to change the business. The workflow could change instead.

The Same Problems Showed Up in the Back Office

The custom work was not limited to technicians and dispatch.

Metro also needed a faster way to handle bulk payments for a large client. Staff needed to find PO entries while creating a bulk payment, so Upvoit added a PO number search directly into that workflow.

It is a small change, but it matters for the person doing the work. Instead of searching around a process that was not designed for Metro’s workflow, the information they needed was put where they needed it.

That became a consistent pattern across the account. The requests were not coming from a product roadmap. They were coming from people doing the work and pointing to the parts that were slowing them down. Pasted markdown.

Jason’s Test Was Whether the Product Would Move With the Business

Jason’s experience with the first request became the clearest proof point. And the response above says something important about what Metro needed from its FSM. The issue was not simply finding a platform with enough features. Metro needed a system that could respond when an existing workflow did not make sense for the business.

Jason put it even more directly when describing the experience to other MSP owners: “Ask what happens when the software doesn’t fit how you charge. Most of them will tell you to change how you charge. I asked for a billing screen built around flat rate, and I had it the next day. That’s not something you find on a feature list.”

Billing was not the end of the work.

Equipment and warranty tracking are now in progress, including model and serial numbers, installation dates, warranty-card photos attached to work orders, and renewal alerts for service contracts.

See What Upvoit Can Change for Your Team

Metro didn’t need more features. It needed software that could adapt when the way it worked didn’t fit the standard workflow. If your business has its own way of handling jobs, billing, payments, or service contracts, maybe your FSM should work around that too.

If you’re curious what that could look like for your business, book a demo.