Pckgr

Automate recurring application management for IT teams and managed service providers.

Monthly and annual device-capacity subscriptionsSoftware
Visit website
Reported revenue> $1,000,000ARR · Unspecified $Over 1M ARR reported in the July 14, 2026 interview; exact accounting cutoff unspecifiedOriginal disclosure
Business modelMonthly and annual device-capacity subscriptionsSoftware
Profile depthResearched profileProduct facts and editorial breakdown
Source checkedOct 20, 2026Observation date, not revenue cutoff

Business overview

Public positioning

Application packaging, deployment and patching for Microsoft Intune, with a separate standalone endpoint-management offering. The July interview describes mostly solo initial development and a small current team. The official About page read for this review lists four people: Tom (founder/CEO), Miranda, Bri and Mitch. This is a public team roster, not a verified payroll total.

How it makes money

Intune plans scale by managed-device bands; the newer RMM offer has separate device-based beta pricing.

Business breakdown

Researched Oct 20, 2026

Source-linked product facts, followed by MRRTrace analysis of the customer problem, workflow, trade-offs and questions to test.

The customer problem

Pckgr automates application packaging, deployment and patching for IT teams and MSPs. Its current site distinguishes an Intune companion from standalone RMM. Editorial interpretation: the paid problem is keeping routine software maintenance repeatable as the fleet grows. A useful small-business opportunity can exist where a broad platform leaves administrators doing repetitive preparation, exception handling and verification. Buyers may value a narrow reliable workflow even when their primary management suite already contains many features.

Core workflow

  1. Choose the Intune companion or standalone RMM based on where endpoints are managed.
  2. Connect the appropriate environment, select applications and configure the intended deployment or update.
  3. Review results on representative devices before expanding a rollout; investigate failed installations and retain a recovery route.

What customers pay for

The current plans use device capacity as the commercial unit. Editorial hypothesis: evaluate the offer using administrator hours saved per month, successful update coverage and time spent recovering failed deployments. The relevant alternative includes manual preparation and ongoing maintenance, not simply the price of another subscription. A buyer could test a fixed set of common applications across a small representative fleet, documenting exception rates before and after adoption. A builder should also track support cost per supported package, because difficult installers may consume more effort than the nominal fleet size suggests.

Distribution signals

Observed channels and entry points; their performance is not inferred.

  • Administrator communities and ecosystem specialists

    Mahony describes an initial free launch in Intune communities, followed by paid demonstrations through Microsoft MVPs. The source does not establish controlled attribution.

    Evidence

Trade-offs

  • Editorial risk: specializing in one ecosystem gives clear buyer language and integrations, while upstream product changes can weaken differentiation or break a previously reliable workflow.
  • Editorial risk: device-based pricing is legible, but actual delivery cost may depend on package complexity, customer permissions and support needs rather than device count alone.

Open questions

  • Which recurring application task costs the target administrator enough time to justify a subscription?
  • What evidence would demonstrate that automation improves reliability as well as reducing manual effort?

A MRRTrace reading of public product material. Trade-offs and questions are editorial analysis.

Revenue evidence

Founder disclosure in interview
> $1,000,000ARR · Unspecified $ · Over 1M ARR reported in the July 14, 2026 interview; exact accounting cutoff unspecified
Reporting period
Over 1M ARR reported in the July 14, 2026 interview; exact accounting cutoff unspecified
Figure as of
Not provided
Reporting method
Founder disclosure in interview
Source checked
Oct 20, 2026
Source published
Jul 14, 2026

Strict lower bound, not exactly 1M. Uses the founder ARR statement, not the editorial 83K monthly header. Historical self-report, not audited receipts or profit. The interview concerns the established Intune product and introduces RMM as a next venture; no income is allocated to RMM or inferred from current packaging.

Thomas Mahony first-person interview, July 14, 2026
This historical disclosure is separate from any current Stripe connection shown on this page. MRRTrace has not audited the business. Revenue is not profit, and historical figures are not current earnings guarantees.

Pckgr for Intune: Starter $49/month for up to 100 devices, Professional $99/month for up to 1,000, Business $149/month for up to 2,500; larger fleets quoted. RMM beta is separate, free up to five devices and Pro from $10/month. Dollar currency is not explicitly identified on the read page.

The source page may change its prices, limits, or offer after the recorded check date.

What founders can learn

Editorial notes

Build a recurring service around one costly administration task inside an established software ecosystem.

Before you build something similar

  • Intune integration depends on Microsoft platform permissions and compatibility.
  • A package that works in one device configuration can fail elsewhere; production rollout needs environment-specific validation.
  • Historical ARR is a run rate and a strict lower bound; current RMM pricing does not establish separate RMM revenue.

These are MRRTrace observations, not statements by the founder or proof of a repeatable outcome.

Source material

4 sources
  1. Founder income and bootstrap interview Public source · Checked Oct 20, 2026
  2. Official product, rendered SPA Public source · Checked Oct 20, 2026
  3. Official pricing, rendered SPA Public source · Checked Oct 20, 2026
  4. Official team, rendered SPA Public source · Checked Oct 20, 2026