Professional vs Enterprise: Which AI Spend Management Tier Fits Your Org?
TL;DR: minware's two plans share the same pre-built reports, custom metrics, and token spend regression. Professional costs $25/contributor/month, supports up to 100 contributors with no minimum, and bills month-to-month or annually. Enterprise costs $45/contributor/month with a 50-contributor minimum and an annual contract. It adds SAML SSO, on-premise ingest, custom data residency, enterprise AI tool APIs, and unlimited backfill. Upgrade when you pass 100 contributors, need one of those controls, use a self-hosted or Enterprise-only integration, or connect AI tools through their enterprise APIs.
Engineering leaders who need to show a board whether AI token spend is buying more delivery usually evaluate minware with one question still open: which plan. Both plans run the same AI return on investment (ROI) methodology on the same pre-built reports. The choice comes down to four constraints: contributor count, security controls, AI tool connections, and billing terms. This guide maps each constraint to the plan it requires and prices the difference at common team sizes.
Measuring AI ROI on either plan
AI ROI reporting on both plans rests on one method: a linear regression of a delivery outcome against token spend.
Reading the regression
The Lean AI Framework regresses roadmap value delivery, on-time delivery rate, and overhead cost against token spend, each in its own regression. The slope is the ROI readout: the change in the outcome per dollar of spend. With no explicit value field configured, roadmap value delivery defaults to story points completed, so a typical slope reads as story points completed per dollar of token spend.
Each regression output includes an R-squared value showing how much of the outcome's variation the spend explains. Regressions group by team and time period, normalizing each data point per person-day so team-size differences don't distort the slope. Each outcome's trend over time for the same team is the supporting check.
Accounting for confounders
A regression shows correlation, so a credible board readout names what else could move the numbers. Three confounders apply to AI adoption:
-
Task-level selection: engineers reach for AI selectively, using it on tasks where it is likely to help.
-
Person-level selection: early adopters are often already more active developers before they touch the tool.
-
Covariates: factors like code base age or code quality can shape both AI usage and delivery outcomes.
Naming these confounders when presenting the regression builds more credibility with a board than leaving them for someone else to raise.
Comparing what each plan includes
The two plans share their reporting. They differ in integrations, access controls, support, and hosting.
Features on both plans
Both plans include:
-
All pre-built reports, including AI impact, DORA, agile, and cost capitalization
-
Unlimited custom metrics and reports
-
Token spend regression against delivery outcomes
-
Comma-separated values (CSV) export, API access, and Model Context Protocol (MCP) access
-
SOC 2 Type 2 coverage
-
Role-based access control, plus SSO with Google or GitHub
Professional support runs through email or phone. Its historical backfill covers 1 year, with U.S. data residency on multi-tenant hosting.
I use Minware for our SDLC metrics and appreciate its ability to provide quality metrics throughout our SDLC... The initial setup was easy, integrating with Jira and our repository, and adding users. - George V. on G2
Enterprise additions
Enterprise costs $45/contributor/month on an annual contract and adds:
-
SAML SSO, System for Cross-domain Identity Management (SCIM), and human resources (HR) system team configuration
-
A multi-level org hierarchy for filtering reports by any division, sub-team, or cost center
-
The optional on-premise ingest agent, plus on-premise and custom integrations
-
The enterprise APIs for GitHub Copilot, Cursor, and Claude Code
-
Custom data residency and dedicated hosting
-
Unlimited historical backfill
-
Slack support, a service level agreement (SLA), a dedicated customer success agent, and a forward-deployed engineer
-
Regular training sessions and quarterly business reviews
-
Full-service report and metric customization
-
Bitbucket Pipelines, Outlook calendar, ServiceNow, plus custom CI/CD, webhook, REST, or GraphQL integrations
-
Direct minQL, SQL, and ODBC data access
AI tool connections
Token spend data reaches minware through vendor APIs or OpenTelemetry integrations, and the plan determines which vendor APIs connect. Professional supports GitHub Copilot's pro API, Cursor's Teams API, the Claude Code Analytics API, and OpenTelemetry from Claude Code, Codex, or a custom source. The enterprise APIs for GitHub Copilot, Cursor, or Claude Code require the Enterprise plan. An org that reports AI usage through one of those enterprise APIs needs Enterprise even below 100 contributors. AI commit and pull request authorship can also be read from your version control system, such as GitHub, GitLab, Bitbucket, or Azure DevOps, on either plan, with no AI tool integration required.
Metric customization
Custom metrics and reports are unlimited on both plans. Most customization happens by selecting existing metrics and breakdowns in a report configuration, which Professional customers do themselves. On Enterprise, minware's team handles full-service metric customization, usually within a single call and about 24 hours. Every metric's formula is visible in minQL, minware's formula language, so a leader can inspect the calculation before defending it in an executive review.
What I like best about minware is its flexibility. The platform comes with a great set of engineering reports out of the box, so you can start getting value immediately. - Verified user on G2
Sizing your plan by contributor count
Contributor count sets both the price and, above 100, the plan itself.
Contributor limits and cost
minware bills per contributor, defined as a person with recent activity in your data. You control which active contributors are included, and inactive historical contributors are free. Professional covers 1 to 100 contributors. Enterprise starts at 50 contributors with no upper limit, so an org above 100 contributors needs Enterprise regardless of its security requirements.
Enterprise's 50-contributor minimum matters most for small teams that need an Enterprise control. A 30-person team on Enterprise pays for 50 contributors.
| Contributors | Professional | Enterprise (billed annually) |
|---|---|---|
| 30 | $750/month | $2,250/month (50-contributor minimum) |
| 50 | $1,250/month | $2,250/month |
| 100 | $2,500/month | $4,500/month |
| 150 | Not available | $6,750/month |
Between 50 and 100 contributors, Enterprise costs 80% more than Professional. That difference pays for the Enterprise additions, so weigh them against your requirements.
Billing options
Both plans can bill annually, which gives finance a fixed line item. Professional also bills month-to-month with no commitment, so a team can evaluate the platform without a procurement cycle. The self-serve trial lets you connect your own data and explore the pre-built reports before talking to anyone on minware's team. minware accepts credit card or invoice payments on both plans.
Meeting security and compliance requirements
Security requirements are one of four upgrade triggers, alongside contributor count above 100, Enterprise-only integrations, and AI tools that report through an enterprise API.
Access controls
Both plans offer role-based access control, with data visibility scoped at the individual, manager, and executive levels. Professional supports password sign-in and SSO with Google or GitHub. Enterprise adds SSO with Security Assertion Markup Language (SAML), SCIM provisioning, and HR system team configuration for orgs that manage access centrally. An IT policy that mandates SAML SSO makes Enterprise the required plan at any team size.
On-premise ingest
The on-premise ingest agent is an optional Enterprise feature for security-sensitive teams, and most customers connect through standard integrations instead. The agent runs inside your environment and connects to source systems using your own credentials. API keys and direct access to tools like Jira or GitHub never reach minware. The agent uploads data files to a shared storage bucket you can inspect, which lets you confirm only the minimal information is included. The data collected matches a standard connection, so the agent's benefit is control over access. Setup requires Docker plus cloud storage credentials in your own environment.
Compliance reports and health data
minware is SOC 2 Type 2 compliant, with a report covering the security criterion only, audited for the most recent year ending in September. The report applies to both plans. minware is not ISO 27001 certified. For teams handling protected health information (PHI) under the Health Insurance Portability and Accountability Act (HIPAA), minware can sign a business associate agreement (BAA) for Enterprise customers. Custom data residency and dedicated hosting are also Enterprise-only, while Professional runs on multi-tenant hosting in the U.S.
Matching your org to a plan
Three thresholds decide the plan:
-
Up to 100 contributors with no enterprise requirements: Professional covers the full report set, with month-to-month or annual billing and no minimum.
-
Any size with an enterprise requirement: SAML SSO, on-premise ingest, custom data residency, a BAA, an enterprise AI tool API, a self-hosted or Enterprise-only integration, or direct SQL access each require Enterprise. Seats are billed at the 50-contributor minimum even for smaller teams.
-
More than 100 contributors: Enterprise is required, because Professional caps at 100 contributors.
| Plan detail | Professional | Enterprise |
|---|---|---|
| Price | $25/contributor/month | $45/contributor/month |
| Contributors | 1 to 100 | 50 minimum, no maximum |
| Billing | Monthly or annual | Annual |
| Historical backfill | 1 year | Unlimited |
| SSO | Google or GitHub | Adds SAML and SCIM |
| AI tool connections | Copilot pro, Cursor Teams, Claude Code Analytics, OpenTelemetry | Adds enterprise APIs |
| On-premise ingest | Not available | Optional |
| Data residency | U.S. | Custom |
| BAA | Not available | Available |
| Support | Email and phone | Adds Slack, SLA, customer success agent, forward-deployed engineer |
Choosing between the two plans
Both plans answer the board's question the same way, with token spend regressed against roadmap value delivery, on-time delivery rate, and overhead cost. Professional fits teams of up to 100 contributors who connect AI tools through standard APIs or OpenTelemetry. Enterprise fits orgs that cross 100 contributors, face a security mandate, or report AI usage through enterprise APIs. Price your contributor count against the 50-contributor minimum, then confirm the regression works on your own data during the trial.
Start a 14-day free trial, no credit card required, and connect your first data source.
FAQs
Can I switch from Professional to Enterprise mid-year, and how does annual billing work when I upgrade?
Yes. minware's Enterprise plan bills annually, so an upgrade moves your account onto an annual Enterprise contract.
What happens if we exceed 100 contributors on Professional?
minware's Professional plan supports up to 100 contributors. Beyond that, Enterprise is required, with no upper limit.
Does Enterprise include dedicated support?
Yes. minware's Enterprise plan includes a dedicated customer success agent, a forward-deployed engineer, Slack support, a support SLA, regular training, and quarterly business reviews.
Can we trial Enterprise features before committing annually?
minware's self-serve trial covers the pre-built reports on your own data, including the AI ROI regression. SAML SSO and the on-premise agent are Enterprise-only features, so raise them with minware's team during the evaluation.
How does pricing work for seasonal contributor fluctuations?
minware bills for active contributors, and you control which ones are included. Inactive historical contributors are free. Professional's month-to-month billing lets the bill follow team size from one month to the next.
Key terms glossary
Token spend: The dollar cost of AI tool usage, as reported by AI tool APIs or OpenTelemetry. On flat-rate, tiered, or discounted plans, reported spend may differ from the amount actually invoiced.
Roadmap value delivery: The expected value of completed work items. If no explicit value field is configured, it defaults to story points completed on tickets that are not bugs and have a parent epic or project ticket.
On-time delivery rate: The estimated roadmap item duration divided by the actual duration, capped at 100% per roadmap item.
Overhead cost: Personnel cost and AI token spend that goes toward work not counted in roadmap value delivery.
Linear regression: A statistical model charting the best-fit line between an outcome metric and an input variable. Each regression fits one metric pair.
R-squared: The share of the outcome metric's variation explained by the input variable, on a 0-to-1 scale.
SSO/SAML: Single sign-on using Security Assertion Markup Language. SAML-based SSO is an Enterprise feature. SSO with Google or GitHub is available on both plans.
SCIM: System for Cross-domain Identity Management, an open standard for automating user provisioning between an identity provider and an application.
On-premise ingest agent: An optional Enterprise agent that connects to your internal systems using your own credentials, so API keys and system access never reach minware.
BAA: The contract or written arrangement a HIPAA-covered entity requires from a vendor that handles its protected health information.
PHI: Individually identifiable health information held or transmitted by a covered entity or its business associate.
minQL: minware's patent-pending formula language, used to define every metric, with full visibility into the underlying logic.
MCP: An open-source standard for connecting AI applications to external systems. minware's MCP server lets AI agents query minware data directly.