Core PSA functions
Coordinate the service commitment and the work behind it.
Reduce disconnected tools by bringing service operations, customer workflows, billing, and specialized applications onto one SmartWorx foundation. Consolidate gradually around the way your MSP works.
Build it internally, deliver it through a partner, or adopt a publisher-built application.
A better portal, quoting process, onboarding workflow, or billing process shouldn’t always mean another product to manage. Run those applications on a common foundation with a consistent application experience.
Shared page, navigation, and component patterns give applications a common UI foundation, with room for each publisher’s design. They can share platform services and administration where supported.
A publisher can build a PSA-class application for service desk, projects, assets, agreements, and customer records, then extend it without adding another platform beside it.
Coordinate the service commitment and the work behind it.
Bring customer and commercial work into the same model.
Review subscriptions and charges in customer context.
Build around the managed services that distinguish your business.
Applications can be owned, branded, supported, and commercialized by the organizations that build businesses around them.
An MSP can configure an application around its own operating model.
An implementation partner can design and operate an MSP solution for customers.
A publisher can own its application offering, brand it, package it, price it, support it, and commercialize it on SmartWorx.
SmartWorx provides the platform. Application publishers can build businesses on top of it.
Build an application businessConnect subscriptions, usage, customer agreements, and billing review in an application designed around your service model.
Illustrative process. Connections depend on the upstream systems and available data.
Consolidate where it makes sense. Integrate where another system should remain. SmartWorx supports API definition import and endpoint configuration to plan those connections around supported operations and permissions.
Explore APIs & connectivitySee how service queues, onboarding, documentation, commercial work, cloud reconciliation, and reporting could fit into a publisher-built application.
Explore the sample applicationIllustrative Marketplace package by Example Publisher. Not commercially available.

Bring service operations, customer workflows, billing processes, and specialized applications onto a common foundation—and keep the external systems that still make sense.