Everyman Brand Archetype
Automotive
Workflow Automation
Fixify
Differentiated IT support by selling resolved outcomes rather than another ticketing seat, combining AI automation with human analysts, despite incumbent ITSM platforms owning the system of record.
• BUSINESS MODEL
• REVENUE
• MARKET TYPE
• MARKET ENTRY
• GROWTH MODEL
• MOAT
• EDGE
1
MODEL
Fixify tested whether AI-assisted IT support could scale without becoming a high-cost managed-service business. It automates routine Tier 1 and Tier 2 requests, uses human analysts for exceptions, and reports resolving about 75% of such tickets; its move to per-resolved-ticket pricing with a 100-ticket monthly minimum ties revenue and cost to completed work rather than seats or endpoints.
Question this model answers
We need to know whether our business model can scale.
BUSINESS MODEL
Managed Service
HOW THEY BUILT IT
'- Positioned Fixify as an AI-native help-desk layer that plugs into existing ITSM systems such as ServiceNow, Jira, Freshworks, ManageEngine, HaloPSA, and HappyFox.
- Automatically categorized incoming requests into more than 40 use cases, including customer-defined categories, using rules, AI, and customer-specific playbooks.
- Used AI Sidekicks to generate and execute multi-step automation plans, while human analysts handled exceptions and high-empathy interactions.
- Sold a managed outcome: customers selected which categories Fixify would resolve, retained visibility into status and metrics, and avoided replacing their existing ticketing system.
- Monetized through annual employee-based subscriptions initially, then moved to per-resolved-ticket pricing with a 100-ticket monthly minimum for MSPs; this aligned price with completed work and reduced adoption risk.
HOW TO ARCHITECT IT
1. Identify a high-volume operational workflow where customers already own a system of record but lack capacity, expertise, or automation.
2. Do not replace the incumbent system; integrate with it and become the execution layer that resolves work inside the existing workflow.
3. Start with a narrow set of repeatable use cases where success is measurable—password resets, access requests, software issues, or routine provisioning.
4. Build automation from customer-specific context, then keep humans in the loop for exceptions, judgment, and high-empathy interactions.
5. Price the completed outcome once you can predict resolution cost; outcome pricing aligns incentives but requires reliable unit economics.
6. Avoid promising broad automation before your resolution rate, escalation path, and cost per resolution are proven; otherwise service costs can scale faster than revenue.
DISTRIBUTION MODEL
Direct Sales, Outbound Sales, Partnerships, Product-Led Growth
HOW THEY OPERATIONALIZED
'- Direct and outbound sales to IT leaders at companies with roughly 75–2,000 employees, where internal help desks are under-resourced but too complex to fully outsource.
- Product-led integration: Fixify connects to the customer’s existing ticketing and productivity tools, reducing migration friction and enabling a limited-scope pilot.
- MSP channel: Fixify sells to managed service providers that can deploy its AI-assisted resolution layer across multiple client environments.
- Partnership-led credibility: integrations with ServiceNow, Jira, Freshworks, Slack, Microsoft Teams, and AI providers make the offering easier to adopt within existing IT stacks.
HOW TO REPLICATE WHAT WORKED
What Worked
Sell a contained pilot inside the customer’s existing workflow rather than demanding a platform replacement; this lowers switching risk and lets the buyer measure resolution quality before expanding scope.
Trap if Copied Blindly
Outcome-based pricing fails if the vendor cannot predict resolution cost or if customers hand over only low-value, high-effort tickets; without scope controls and a minimum commitment, the model can become unprofitable.
Insight on Untapped Business Model / Gaps / Pitfalls
GOLDMINE
GOLDMINE 1 — RESOLUTION-AS-A-SERVICE FOR BACK OFFICES. The same model can apply to HR, finance, procurement, legal ops, and customer support: customers pay for completed work, while AI handles repeatable steps and humans manage exceptions.
GOLDMINE 2 — PREVENTION LAYER, NOT ONLY RESOLUTION. The opportunity is to analyze recurring tickets and eliminate root causes—access design, onboarding gaps, asset issues, or confusing policies—rather than repeatedly resolving the same problem.
GOLDMINE 3 — MSP-MULTIPLIED AI DELIVERY. MSPs can distribute AI operations across many SMB clients; the platform gains diverse workflow data while the MSP gains margin without hiring proportional staff.
THE TRAP TO WATCH
THE PIT — UNBOUNDED OUTCOME PRICING. If customers can assign ambiguous or high-effort tickets at a fixed price, the vendor absorbs escalating labor cost; scope definitions and exclusions are essential.
THE SECOND PIT — AUTOMATION THEATER. Claiming AI resolution without measurable resolution rates, escalation quality, and auditability destroys trust once customers inspect the work.
MOVE WITH CAUTION
Do not compete with ServiceNow or Zendesk on system-of-record functionality. The durable position is the execution and outcome layer on top of the customer’s existing workflow.
2
MARKET
MARKET TYPE
Red Ocean
WHY THEY WON
IT service management is a Red Ocean with entrenched platforms, mature workflows, and many outsourcing alternatives. Fixify changed the buying criterion from “which ticketing system should we buy?” to “which work should we remove from our team?” Its structural opening was the gap between powerful ITSM systems and under-resourced IT teams: enterprises did not need another dashboard; they needed completed Tier 1 and Tier 2 work without hiring a full 24/7 help desk.
Fixify entered against ServiceNow, Zendesk, Freshworks, Jira Service Management, and traditional IT help-desk outsourcing firms. Its differentiation was not another ITSM dashboard but a managed resolution layer: AI plus human analysts resolving selected ticket categories inside the customer’s existing workflow.
Question this model answers
We need to differentiate from established competitors.
ENTRY STRATEGY
Brownfield Entry
EXECUTION
Fixify entered by modernizing existing IT help-desk workflows rather than creating a new category. It targeted companies already using ServiceNow, Jira, Freshworks, or similar systems but unable to staff or automate Tier 1 and Tier 2 support effectively. The critical bet was that customers would hand over selected ticket categories if Fixify could integrate without migration and deliver measurable resolution outcomes. This required ITSM integrations, AI playbooks, human analysts, and transparent performance reporting; it would fail if customers demanded full control over every workflow or if resolution quality could not meet internal SLAs.
FOOTHOLD STRATEGY
Wedge Strategy
THE HOW
Fixify’s initial wedge was routine Tier 1 and Tier 2 IT support for companies with roughly 75–2,000 employees. These teams had recurring ticket volume, limited staffing, and existing ITSM tools but lacked the capacity to automate and resolve work at scale. Once Fixify proved reliable resolution in selected categories, customers could expand the scope of work handed to the platform.
MARKET TYPE PLAYBOOK
RULE 1 — SELL THE RESOLVED TICKET. Price on completed outcomes rather than seats, endpoints or licences, because IT leaders are measured on resolution speed and cost.
RULE 2 — REFRAME THE COMPARISON. Move the buyer from “which ticketing system should we buy?” to “which provider resolves tickets for us?”.
RULE 3 — KEEP EXISTING SYSTEMS IN PLACE. Work inside ServiceNow, Jira or Freshworks so the entrenched platform is not a reason to refuse.
RULE 4 — PROVE QUALITY WITH HUMANS IN THE LOOP. AI automation must be backed by human oversight or the outcome promise will not hold.
In a Red Ocean, buyers already have systems and vendors.
Fixify’s advantage came from changing the unit of purchase: not seats, endpoints, or software licenses, but completed tickets.
This reframing mattered because IT leaders were measured on resolution speed, employee experience, and cost—not on owning another platform.
GENERAL RULES
WHAT HAPPENS IN THIS MARKET TYPE
RULE 1 — TARGET THE WORK THE INCUMBENT SYSTEM DOES NOT COMPLETE. ITSM platforms track tickets; Fixify resolves selected categories of work.
RULE 2 — INTEGRATE RATHER THAN REPLACE. Brownfield entry reduces migration risk and lets the customer retain existing investments.
RULE 3 — MAKE THE OUTCOME MEASURABLE. Resolution rate, SLA compliance, time to resolution, and escalation quality must be visible.
RULE 4 — REJECT BROWNFIELD ENTRY IF THE CUSTOMER’S DATA IS TOO MESSY. AI workflows depend on clean context; if tickets, permissions, and knowledge are inconsistent, automation will create more exceptions than value.
In a mature category, differentiate by changing the unit of value rather than adding marginal features.
A wedge is a narrow, repeatable workflow where the vendor can prove measurable outcomes before expanding scope.
HOW TO APPLY FOOTHOLD STRATEGY
RULE 1 — CHOOSE HIGH-VOLUME, LOW-AMBIGUITY WORK. Password resets, access requests, and common software issues are ideal because success is measurable.
RULE 2 — EXPAND BY CATEGORY, NOT BY FEATURE. Once one ticket category is reliably resolved, add adjacent categories with similar data and workflow patterns.
RULE 3 — MEASURE FOOTHOLD SUCCESS BY RESOLUTION RATE AND ESCALATION QUALITY. A foothold requires sustained completed work, not a successful demo.
RULE 4 — ADAPT TO OPERATIONAL MATURITY. Less mature teams need end-to-end support; mature teams need selective automation. Failure occurs when the vendor takes on ambiguous work before its AI and human workflow can handle it economically.
Fixify’s wedge was routine Tier 1 and Tier 2 IT support for companies of roughly 75–2,000 employees; failure occurs when the offer does not adapt to the customer’s operational maturity.
HOW TO APPLY MARKET ENTRY STRATEGY
Fixify modernised existing IT help-desk workflows for companies already using ServiceNow, Jira or Freshworks; failure occurs when customer data is too messy for AI workflows to resolve tickets reliably.
PATTERNS OF THIS MARKETING MODEL
PATTERNS IN OUTCOME-BASED AI SERVICES DISTRIBUTION:
1. RISK-REVERSAL OFFERS ACCELERATE PILOTS. “No bill until resolution” lowers adoption friction, but requires a minimum commitment to protect vendor economics.
2. INTEGRATION-led positioning reduces switching resistance. Customers adopt faster when the vendor works inside ServiceNow, Jira, Slack, or Teams rather than demanding migration.
3. MSP CHANNELS MULTIPLY SMB DISTRIBUTION. Managed service providers can deploy the same AI workflow across many clients, creating scale without direct enterprise sales.
WEAKNESS
Outcome pricing can attract adversarial scope behavior; customers may route difficult work to the vendor while retaining easy, high-volume work internally.
GROWTH CAMPAIGNS
'- “Resolve tickets, not seats” positioning, contrasting Fixify’s outcome-based model with seat-based ITSM pricing.
- AI help-desk campaigns claiming resolution of up to 75% of Tier 1 and Tier 2 tickets.
- Integration campaigns with ServiceNow, Jira, Freshworks, Slack, Microsoft Teams, and other existing IT systems.
- MSP-focused campaigns offering per-resolved-ticket pricing, a 100-ticket monthly minimum, and no platform or setup fee.
- Cost-comparison content positioning Fixify against the cost of building and staffing an internal help desk.
| So What
Fixify’s “no bill until we close our first ticket” and 100-ticket minimum reduce adoption risk while protecting minimum economics; the buyer can test value without a large platform commitment.
| Key Learning
Outcome-based offers work when the vendor can define a measurable unit of value and set a floor that prevents uneconomic pilots.
| How to Use
If you sell a managed outcome, define the completed unit precisely, exclude ambiguous work, and require a minimum volume or scope before offering performance-based pricing.
3
MONEY
REVENUE MODEL
Service Fee, Subscription, Usage-Based
Fixify’s economics depend on whether revenue per resolved ticket exceeds AI, analyst, integration, and support costs. Its MSP pricing is $15 per resolved ticket with a 100-ticket monthly minimum, while earlier enterprise pricing was employee-based—for example, $4,000 per month for 250 employees and $15,000 per month for 1,500 employees. The move toward resolved-ticket pricing makes unit economics explicit.
Question this model answers
We need to know whether our unit economics work.
PRICING STRATEGY
Usage-Based Pricing, Value-Based Pricing, Subscription Discount Pricing
WHY THEY WON
Customers pay for resolved IT tickets, either through employee-based annual subscriptions or per-resolved-ticket pricing. Revenue expands as customers assign more ticket categories, employees, or MSP client environments to Fixify. The vendor bears resolution cost, so margin depends on automation rate, ticket complexity, and human-analyst utilization.
TARGET AUDIENCE
IT leaders at mid-market companies (subscription or outcome-based; want to offload Tier 1 and Tier 2 support without hiring a 24/7 team); MSPs (per-resolved-ticket; want AI leverage across client help desks); Operations and employee-experience leaders (managed support; want faster resolution and better employee experience); Companies with existing ITSM systems (integration-led; want automation without replacing ServiceNow, Jira, or Freshworks).
Fixify prices MSPs at $15 per resolved ticket, with a 100-ticket monthly minimum, no platform fee, and no setup fee; triage and partial work are free. Enterprise pricing has historically been employee-based, with examples of $4,000 per month for 250 employees and $15,000 per month for 1,500 employees. The strategic consequence is that Fixify sells completed work rather than software access.
CUSTOMER BUYING BEHAVIOUR
A help-desk backlog, hiring constraint, after-hours coverage gap, or cost-reduction mandate triggers evaluation. IT leaders assess integration effort, resolution quality, security, and reporting; they often begin with selected ticket categories, then expand scope after measurable results. MSPs evaluate whether the per-ticket model improves margin across multiple clients.
WILLINGNESS TO PAY
CORE INSIGHT
IT leaders are not buying software; they are buying capacity to close routine work without hiring, training, and managing a 24/7 support team.
RULES OF ADOPTION
RULE 1 — PRICE THE COMPLETED OUTCOME. A resolved ticket is a clearer value unit than a seat, endpoint, or dashboard.
RULE 2 — PROTECT THE UNIT DEFINITION. The vendor must define what counts as resolved, exclude ambiguous work, and prevent customers from shifting high-effort cases into the fixed-price scope.
RULE 3 — USE AI TO LOWER COST PER RESOLUTION. Automation must handle repeatable work; human analysts should focus on exceptions and empathy, not routine execution.
RULE 4 — WATCH THE VOLUME-MINIMUM TRAP. A minimum ticket commitment protects revenue but can create resentment if the customer’s actual volume falls; contracts need renewal and scope-adjustment mechanisms.
The buyer is really buying IT capacity and employee-productivity protection, proven by IT operations, support, or managed-services budgets.
REVENUE RISK
Ticket-mix risk: Customers may assign complex, ambiguous, or poorly documented tickets, raising cost per resolution and compressing margin.
Automation-rate risk: If AI cannot resolve enough work reliably, human labor costs rise and the outcome-based promise becomes unprofitable.
Incumbent platform risk: ServiceNow, Zendesk, Freshworks, and Microsoft can add native AI agents and automation, reducing the need for an external resolution layer.
MSP concentration: MSP customers can aggregate many end clients; losing a large MSP can remove revenue across multiple accounts.
Scope disputes: Customers may dispute whether a ticket was truly resolved, creating revenue uncertainty and support burden.
Fixify is privately held; it raised $25 million in Series A funding in 2024, bringing total investment to $32 million, but ARR, revenue, and profitability are not publicly disclosed.
4
MOTION
Fixify built repeatable acquisition through direct outbound sales to IT leaders, product-led integrations with existing ITSM tools, and an MSP channel. Its per-resolved-ticket MSP offer creates a repeatable commercial motion: MSPs can test the service with a defined minimum and expand across client environments.
Question this model answers
We need to find a repeatable acquisition channel.
GROWTH EXPANSION MODEL
Land & Expand, Market Development
HOW THEY EXPAND
Fixify lands by resolving a narrow set of IT ticket categories inside the customer’s existing system, then expands as customers assign more categories, employees, or MSP clients. Market development extends the same AI-plus-human resolution model to MSPs and additional mid-market segments. Product-line expansion can move from ticket resolution into prevention, workflow analytics, and broader employee-support automation. The dependency is that each expansion must reuse the same integration, AI, and human-operations infrastructure.
COMPETITIVE STRATEGY
Sales-Led Growth
HOW THEY COMPETE
An IT leader gives Fixify a narrow ticket category → AI and analysts resolve work inside the existing ITSM system → the customer sees resolution rate, SLA performance, and reduced internal workload → more categories are assigned → MSPs replicate the model across clients → aggregated ticket data improves automation and playbook quality. The loop requires accurate categorization, reliable resolution, and clear cost-per-resolution economics.
GTM
Fixify runs an outcome-led, sales-assisted GTM.
$5–10M ARR
Direct and outbound sales target IT leaders at mid-market companies with under-resourced help desks. The product integrates with existing ITSM and communication tools, enabling a contained pilot. Customers expand by assigning more ticket categories after measurable results. MSPs provide a second route to market, using per-resolved-ticket pricing to deploy Fixify across multiple client environments. The primary motion is sales-led; product-led integration reduces friction and MSP distribution extends reach.
SUSTAINING MOATS
Data Advantage
The moat is Fixify’s accumulated resolution data, customer-specific playbooks, and human-AI operating system. As it resolves more tickets across companies and MSP environments, it improves categorization, automation, and exception handling; replacing it requires rebuilding both the AI workflow and the human delivery capability.
| Why This Moat Lasts
An AI-managed service moat lasts when resolution data, workflow integration, and human operations combine into a repeatable delivery system.
| Standard Rules
RULE 1 — RESOLUTION DATA CREATES AUTOMATION ADVANTAGE. Every resolved ticket improves categorization, playbook quality, and escalation logic.
RULE 2 — HUMAN-AI OPERATIONS CREATE SERVICE RELIABILITY. Automation alone cannot handle ambiguity; trained analysts make the outcome dependable.
RULE 3 — INTEGRATION CREATES WORKFLOW LOCK-IN. Once Fixify operates inside ServiceNow, Jira, Slack, or Teams, replacement requires changing both tooling and support operations.
| The Signal
Fixify reports resolving about 75% of Tier 1 and Tier 2 tickets and prices MSP work at $15 per resolved ticket with a 100-ticket minimum. The moat does not protect against native AI agents from ITSM incumbents or customers that retain only simple, high-volume work internally.
ARR
JOURNEY
Pre-$1M ARR
PROVE AI-ASSISTED TICKET RESOLUTION. Fixify focused on resolving routine Tier 1 and Tier 2 IT requests inside existing systems; the key move was demonstrating measurable resolution rather than selling another dashboard.
$1–5M ARR
WIN MID-MARKET IT TEAMS. The company targeted organizations with 75–2,000 employees and under-resourced help desks; the key move was integrating with existing ITSM tools to reduce migration risk.
$5–10M ARR
STANDARDIZE THE HUMAN-AI DELIVERY MODEL. AI handled repeatable work while trained analysts handled exceptions; the key move was making resolution quality and cost per ticket predictable.
$10–50M ARR
$10–25M ARR — BUILD AN MSP DISTRIBUTION CHANNEL. Per-resolved-ticket pricing and a 100-ticket minimum gave MSPs a repeatable way to deploy Fixify across clients; the key move was turning service capacity into a channel product.
$25M+ ARR — NOT PUBLICLY VERIFIED. Fixify raised a $25 million Series A in 2024 but has not disclosed ARR; its current emphasis is scaling AI-assisted resolution, MSP distribution, and broader workflow automation.
$50–100M ARR
NOT REACHED. Fixify has not publicly disclosed reaching this revenue scale.
$100M+ ARR
NOT REACHED. Fixify has not publicly disclosed reaching this revenue scale.
BREAKDOWN
THE STANDARD
Sell completed outcomes in a workflow where customers already own the system of record, using AI for repeatable work and humans for exceptions.
THE SEQUENCE
1. Pick one measurable, repeatable work category. Start with high-volume tasks where success can be defined, measured, and audited.
2. Integrate with the customer’s existing workflow before offering broad automation. Reduce switching risk by becoming the execution layer, not a replacement platform.
3. Move to outcome pricing only after unit economics are known. Define the completed unit, protect scope, and establish a minimum commitment before promising performance-based pricing.
Fixify’s integration-led approach and resolved-ticket pricing made the value proposition concrete: customers paid for work completed, not software seats.