Back

Business Intelligence

How Prosper Solutions Is Building a Data-Driven, Automation-Ready Service Desk with MSPbots

Farzan Amiri
CTO, Prosper Solutions
Profitability reports that used to take four hours now take 30 seconds to a minute to give me the whole picture.
About
How a Boston MSP turned its HaloPSA data into live profitability, owner-driven scorecards, and a clear plan for automation.
Website

From Break-Fix Shop to Business Service Provider

Prosper Solutions is a Boston, Massachusetts-based managed IT service provider delivering cybersecurity, cloud solutions, managed IT, and strategic technology consulting to nonprofits, government organizations, regulated businesses and more. Its service desk runs on HaloPSA, led by CTO Farzan Amiri, who has worked with MSPbots for about five years across two MSPs.

Prosper has already grown from a break-fix IT shop into a managed service provider. Now it is making its next move: becoming a business service provider that helps clients run better operations. For Farzan, technology isn't just about solving technical problems. It's about improving efficiency, strengthening client relationships, and making smarter business decisions.

For Farzan, that shift starts at home. To create more value for clients, Prosper first has to run a great operation of its own: a team that is happy, clients who get their money's worth, and savings passed on wherever possible. That means leadership needs a reliable view of the whole business, so problems are spotted and handled early instead of turning into long-term financial issues.

‍

The Challenge: All the Data, None of the Answers

Like most MSPs, Prosper had no shortage of data. Tickets, technician hours, invoices, and contracts all lived in the PSA. What it lacked was a way to turn that data into decisions.

  • Profitability was a manual math problem. To know if a contract made money, the team pulled data from several sources and calculated revenue against labor and other costs by hand.
  • Reporting meant CSV exports and cleanup. Raw data was exported, run through custom workflows, cleaned, then visualized and explained, again and again.
  • No live KPIs for daily huddles. There were no gauges, monitoring, or scorecards to see how the team was doing right now.
  • The PSA hit a ceiling. Halo offers more widgets than ConnectWise or Autotask, but its custom reporting still had limits.
  • Senior people were stuck on basic reports. A single profitability report took an operations supervisor about four hours to pull.

The biggest gap was financial. Leadership needed to know what each client actually cost to support, and how managed services compared with project work. Getting there meant exports, custom workflows, and hours of cleanup before anyone could even read the numbers.

"We've used SQL, we've used AI, we've used lots of different extraction methods, but nothing has been as effective."

The cost was not just time. Because the reports involved sensitive margin and cost data, Farzan kept them with his supervisors rather than T1 or T2 staff. That meant his highest-paid people were spending hours on routine report pulls instead of leading their teams.

‍

The Solution: Live Visibility, Starting with Profitability

Contract profitability for Halo. Prosper deliberately started with its biggest pain point. The contract profitability app pulls revenue, labor consumption, cost, and gross margin for every client agreement straight from Halo, with managed services separated from project and professional services, so no one has to rerun a query or rebuild a workflow.

"When reviewing an agreement, revenue alone doesn't tell us where we're making money. We need to understand how much labor is being consumed, what recurring issues exist, and whether the service being delivered aligns with the agreement." — Farzan Amiri, CTO

Product and project profitability. Each dashboard led to the next question. After contracts, Prosper added a product profitability dashboard to see which products are worth recommending. It is now building five project profitability dashboards with MSPbots' professional services team to compare budgeted hours, actual hours, cost, and margin on every project.

Reporting without the PSA's limits. Halo's custom reporting still has limits. When Farzan asked his operations team for a specific report or dashboard in Halo, they kept running into system roadblocks. Where Halo's reporting stops, MSPbots picks up: a deep library of template widgets and fully custom dashboards built on live PSA data, so the report Farzan needs is available at a glance instead of becoming a workaround project.

"Whenever there's system limitations for Halo, MSPbots takes that limitation away and I'm able to just see those reports at a glance."

‍

Building a Higher-Performing Service Desk

Financial visibility was the foundation, but Farzan is clear that it was never the whole point. Live operating data, including KPIs, staff management, and ticket flow, is what turns a service desk from busy to high-performing.

Live KPIs for every role. Farzan's teams use dashboards built for managers, dispatchers, financial reporting, and vCIOs, comparing this week against the past periods. That makes it possible to spot trends and trace problems back to their root cause.

A name next to every number. Prosper's scorecards measure each metric against a goal, and every metric has an owner. Those scorecards run the weekly EOS Level 10 leadership meeting, including a view of each engineer's hours against an 80% target. If something is off track, it isn't just a line in a report. It's someone's job to fix by next week.

"Most companies have that data, but Prosper actually runs the business on it." — Leonard Narvaza, MSPbots

Automation that takes over dispatch. In Farzan's experience, NextTicket assigns tickets automatically based on priority, severity, and contact importance such as VIP status, so the system effectively acts as the dispatcher. Prosper is now looking at SOP automation and AI in its dashboards as next steps.

Next up: visibility for every staff member. In 2027, Prosper plans an enhanced service desk dashboard that fills the reporting gaps Halo can't cover, giving the whole team, not just leadership, the same live view.

‍

The Vision: Automate the Routine, Elevate the People

Farzan's view of AI and automation is practical. Its job is to remove repetitive work, and its value depends on whether leadership knows what it wants first.

Vision comes before tools. Prosper's approach runs in a set order: know the outcome you want, then integrate the data, then implement the automation. Farzan stresses that no vendor can supply the vision for you.

"We had the vision, and MSPbots helped us integrate and implement it. You have to know the vision of what your business outcome should look like."

Define the process before you automate it. Dashboards show what's working and what isn't. The next step is writing down the procedures a person would follow, because automating an undefined process only speeds up the mess. This is where MSPbots' SOP agent fits in, turning documented procedures into automated execution across technicians, sales, and other teams.

"If you insert automation in your business without understanding your procedures, you're automating chaos." — Leonard Narvaza, MSPbots

AI elevates people instead of replacing them. Farzan compares today's fear of AI to fears about the internet in 1995. In his experience, automation removes routine tasks and frees people to move into higher-value work. When NextTicket automated 40 hours a week of dispatch, the coordinator moved into DevOps with better pay. His supervisors, freed from report pulls, now spend that time on one-on-ones and coaching.

"It doesn't eliminate your job. It creates new opportunities, and it saves time from valuable resources."

‍

The Results: Faster Reports, Cleaner Data, Better-Priced Contracts

Before MSPbotsAfter MSPbots
About 4 hours for a supervisor to pull a profitability report30 seconds to a minute on a live dashboard
40–80 hours to design and build each reporting procedureReady-made dashboards, built with MSPbots professional services
2–3 hours to run each reportData available at a glance, refreshed automatically
40 hours a week of manual dispatch (Farzan's NextTicket experience)Dispatch automated; that coordinator moved into a better-paid DevOps role

Hidden billing gaps, found. While validating the profitability dashboard, Prosper spotted discrepancies that led it to travel charges, discounts, and invoices that weren't recorded the way the team expected. It also found co-managed technician time that had to be excluded from internal labor costs. Fixing those issues improved both its reporting and the quality of its data inside Halo.

"Those may sound like small details, but when you're calculating profitability across numerous contracts, those details matter."

Pricing based on facts, not assumptions. Some clients Prosper believed were profitable were actually costing more to support. Now pricing and scoping decisions rest on real labor consumption, recurring issues, and whether delivered service matches the agreement. On projects, historical cost and labor data is starting to sharpen estimates and catch budget overruns earlier.

Leaders back to leading. With reports available on demand, supervisors spend their time on one-on-ones and coaching instead of data pulls. In Farzan's NextTicket example, the dispatcher whose role was automated was redeployed, not replaced.

"40 hours was saved, and a new job was created, and that person has elevated into a better position."

For Farzan, the real result isn't a dashboard. It's an organization that connects its everyday technical work to business outcomes, with the visibility and clarity to act before problems grow.

"MSPbots isn't simply about creating dashboards. That's what business intelligence should do: not just tell you what happened, but help you make better decisions about what happens next." — Farzan Amiri, CTO, Prosper Solutions
Farzan Amiri
CTO, Prosper Solutions