Teamworks

1.1 Identity, founding arc, and operating-system positioning

Teamworks positions itself as "The Operating System for Sports," a unified software stack spanning talent acquisition, operations, athlete development, and performance workflows for elite sports organizations. The company’s current official pages anchor its roots in Durham, North Carolina and describe a mission to empower athletes and the coaches, administrators, and performance staff who support them with technology. Independent and investor-backed coverage ties that positioning to founder Zach Maurides’ experience as a Duke football player who saw how fragmented communication, scheduling, and athlete-support workflows were inside a major college program. Delta-v Capital’s Teamworks case study says Maurides set out to build Teamworks in 2006 after recognizing those workflow gaps, while a Forbes profile says he conceived the business in 2005 while playing at Duke. At the same time, one June 2025 SportsPro article described Teamworks as founded in 2004, which creates a narrow but real chronology discrepancy in the public record. This chapter therefore treats 2005-2006 as the company’s clear origin arc, uses 2006 as the best-supported operating founding year from current official and investor materials, and preserves the conflicting 2004 reference as an evidence gap rather than forcing false precision. What is not disputed is the business model direction: Teamworks has expanded from communication and scheduling roots into a broad vertical SaaS platform built specifically for professional, collegiate, Olympic, and tactical sports use cases.[CO001, CO002, CO003, CO004, CO005, CO006]

1.2 Leadership bench, governance signals, and founder dependence

Teamworks’ official full-text About page exposes a compact but credible executive bench around founder and chief executive Zach Maurides. The current public roster lists co-founder Mitch Heath, CFO Kyle Charters, COO Anna Resman, CTO Reed Shaffner, chief data scientist Doug Fearing, chief strategy officer James Coffos, and executive vice president of sales Corey Richardson. The combination matters for diligence because it shows the company now presents itself as more than a founder-led communications tool vendor: finance, technology, sales, and data-science functions all have named executive owners. Teamworks’ November 2021 leadership-update announcement also signals that the company deliberately professionalized its management layer well before the 2025-2026 AI acquisition wave, suggesting scale preparation rather than purely reactive hiring. Still, the public record is thin on board composition, committee structure, investor rights, and succession planning. Founder dependence remains material because Maurides is still both the clearest strategic voice and the public face attached to fundraising, M&A, and category positioning. Mitch Heath’s continuing public role as co-founder provides some continuity, but the governance picture remains materially less transparent than the company’s product and customer marketing. For later underwriting, the key question is not whether a management team exists — it clearly does — but how much decision-making, product vision, and key relationship management still concentrate in Maurides and a small leadership circle.[CO011, CO012, CO013, CO014, CO015, CO016]

1.3 Funding history, investor base, and acquisition-driven expansion

Public financing sources reconstruct a strong round-by-round capital story from 2020 onward. BusinessWire records a $25M Series C led by Delta-v Capital in April 2020, with new participation from Afia Capital and Stadia Ventures plus returning investors such as General Catalyst and Seaport Capital. Teamworks’ own Series D announcement then showed the company raising $50M in June 2022, again led by Delta-v and joined by Seaport, General Catalyst, Teamworthy Ventures, Blossom Street Ventures, Afia Capital, and a broad syndicate of current and former professional athletes. The next capital step was a $65M Series E in April 2023 led by Dragoneer Investment Group, announced alongside the acquisition of ARMS Software and bringing disclosed cumulative funding to $165M at that point. The inflection event came on June 17, 2025, when Teamworks announced an oversubscribed $235M Series F led by returning investor Dragoneer at a pre-money valuation above $1B. Current official company materials now state roughly $400M of funding, implying that undisclosed early rounds and later strategic additions bridge the gap between the publicly itemized 2020-2025 rounds and today’s cumulative total. Capital has not been used only to extend runway; it has visibly financed platform breadth. Between 2024 and 2026 Teamworks bought Zelus Analytics, Telemetry Sports, Opteamal, Sportlogiq, and PFF Enterprise, extending the company beyond workflow software toward a more ambitious data-and-intelligence stack. That acquisition cadence creates a plausible category-consolidation story, but it also means later diligence must separate organic module expansion from growth bought through M&A.[CO022, CO023, CO024, CO025, CO026, CO027]

1.4 Scale markers, customer reach, and global market presence

The strongest public proof of Teamworks’ commercial scale comes from the company’s own funding and acquisition releases rather than from audited financial disclosure. The June 2025 Series F announcement said Teamworks powered more than 6,500 elite sports teams globally and claimed preferred-technology status across 100% of NFL teams, 90% of MLB and Premier League clubs, 87% of NBA teams, 83% of MLS clubs, 81% of NHL teams, 99% of Division I NCAA athletic departments, and more than 65 Olympic federations across 24 countries. By March 2026, the PFF Enterprise acquisition release updated the scale language to more than 7,000 elite sports organizations globally, reinforcing the view that the company continued adding logos or counting additional entities after the Series F close. Teamworks’ current About page provides a different but complementary set of official maturity markers: 485+ employees, roughly $400M in funding, and a 17-country footprint supported by a 24x7x365 service model. The mismatch between the 24-country figure in 2025 financing coverage and the 17-country figure on the 2026 About page likely reflects a methodology change between "countries served" and countries with direct operating presence, but the discrepancy should still be acknowledged. What seems beyond serious dispute is that Teamworks has become deeply embedded in major North American professional leagues, elite college athletics, and Olympic/NGB environments. The open diligence question is whether those penetration metrics translate cleanly into durable multi-module ARR rather than a large installed base with uneven contract depth.[CO037, CO038, CO039, CO040, CO041, CO042]

1.5 Adverse signals, chronology conflicts, and unresolved diligence asks

The most visible adverse signal in the current public record is inherited from the Zelus Analytics acquisition. CourtListener and PacerMonitor show that The Phillies sued Zelus Analytics in March 2025, and local reporting from On Pattison plus broader summaries from Yahoo Sports and Athlon describe allegations that Zelus and Teamworks were preparing to market analytics products the Phillies believed they had contracted to use exclusively. A judge denied the Phillies’ request for emergency injunctive relief, but the broader contract dispute continued. That does not prove a material financial liability, yet it is exactly the type of data-rights and customer-trust issue that becomes more meaningful when a software platform acquires specialized analytics assets. Separate from litigation, Teamworks’ public materials leave several basic diligence items unanswered: exact incorporation date, full board composition, current cap-table terms, the bridge from team/org counts to paying customers, and how much of recent growth is organic rather than acquired. There are also data consistency issues worth preserving rather than smoothing away, including 2004 versus 2006 founding references and 17-country versus 24-country footprint claims. None of those issues undermine the reality that Teamworks is a scaled and well-financed category leader. They do, however, limit how aggressively later chapters should assume precision where the public record is still mostly marketing, financing, and transaction disclosure rather than audited operating evidence.[CO038, CO039, CO040, CO041, CO042, CO044]

1.6 Exhibits

2.1 Market Boundary and Status-Quo Substitutes

Teamworks should not be underwritten against a vague "all sports tech" market. The current official product set spans recruiting, operations, academics, athlete management, intelligence, and wallet-driven payment workflows, which together form a vertical operating system for elite sports organizations rather than a single analytics product. That means included spend in this chapter is software that coordinates athlete, staff, and department workflows: communication, scheduling, travel, recruiting, data centralization, academic support, decision-support analytics, and NIL or revenue-sharing administration. Excluded spend should include categories that appear in broad analyst reports but sit outside Teamworks' direct monetization path today, such as betting analytics, fan-engagement tooling, generic consumer team apps, and other media-adjacent categories. The status quo substitute is still fragmentation. Memphis explicitly described spreadsheets, emails, and manual workflows as inadequate once revenue sharing arrived, and Charleston's sole-source memo described why one department wanted a unified operational platform instead of disconnected systems. The market boundary therefore starts with workflow orchestration, not with every sports-data or sports-media budget line.[CM001, CM002, CM003, CM004, CM006, CM007]

2.2 Sizing Lenses and What Counts

The public evidence supports multiple market lenses, not one heroic TAM. MarketsandMarkets places global sports analytics at $2.29 billion in 2025 and above $4.75 billion by 2030, but its taxonomy explicitly includes fan engagement and social-media analytics that overstate Teamworks' direct opportunity. Verified Market Research offers a narrower adjacent lens in athlete management software, at $1.60 billion in 2025 rising to $3.40 billion by 2033, with sports teams as the dominant end user and North America around 40% share. College athletics adds a third lens. RallyFuel projects a $2.75 billion NIL market in the 2025-2026 cycle, while Opendorse reports network activity across 150,000+ athlete users, $250 million+ in compensation, and institutional penetration reaching 98% of NCAA, NAIA, and NJCAA members. These figures measure different things: broad category spend, narrower workflow-software demand, and transactional ecosystem activity. They are best read as upper bound, nearer-term proxy, and demand-signal layers rather than as interchangeable TAM numbers. The practical implication is that Teamworks' direct SAM is likely much smaller than the headline sports-analytics market but still meaningfully enlarged by NIL and revenue-sharing complexity.[CM004, CM005, CM012, CM013, CM014, CM015]

2.3 Buyer, User, Payer, and Adoption Path

The buyer map is multi-threaded. Recruiting staffs need prospect pipelines and communication; operations staffs need calendars, travel, messaging, and files; academics teams need appointment and study-plan workflows; performance staffs need centralized athlete data; and finance, compliance, and athletic-department leadership now increasingly own payment and governance decisions around NIL and revenue sharing. Public procurement evidence supports this cross-functional pattern. Texas A&M bought a bundled Teamworks package covering Hub, Academics, Video, INFLCR, and nutrition support for a discounted $235,000 annual fee, showing that budget ownership can be justified by several departmental pain points at once. Charleston's memo separately framed Hub as a proprietary center of gravity because it already connected compliance and academics. Teamworks' own pages reinforce the same land-and-expand pattern: Recruiting centralizes prospect data, Hub becomes the shared operating layer, AMS centralizes athlete performance data, Academics adds support workflows, Intelligence adds predictive decision support, and Wallet adds payment administration. In other words, the likely adoption path is wedge first, system of record second, and cross-sell into higher-stakes data or payment workflows later.[CM007, CM009, CM010, CM011, CM028, CM029]

2.4 Growth Drivers and Adoption Constraints

The strongest near-term demand driver is policy change in college athletics. NCAA's April 2025 rule package contemplated direct payments to student-athletes and elimination of more than 150 rules, while subsequent coverage framed the first revenue-sharing cap at $20.5 million for 2025-2026, tied to 22% of average Power Conference revenue and expected to step up over time. That turns budgeting, contracting, tax withholding, roster management, and cross-functional coordination from back-office friction into front-office urgency. Teamworks' own Wallet and Memphis materials are built around precisely that pain. But the same change is also a constraint. University Business and Oak View Group both emphasize that schools are under real financial pressure and are searching for new funding pathways, while SportsRecruits highlights hard roster trade-offs. The college market is therefore not a flat wave of demand. It is a budget-strained, opt-in market where the best funded departments move first, the mid-market hesitates, and product adoption will depend on whether software clearly reduces administrative burden rather than simply adding another line item.[CM021, CM022, CM023, CM024, CM025, CM026]

2.5 Valuation Relevance and Open Gaps

For valuation, the key question is not whether sports software is a large theme; it is which slice Teamworks can repeatedly monetize with attractive contract depth and cross-sell. The public record points to a narrower but more actionable SAM in elite sports organizations with operational complexity, enough budget concentration to justify integrated software, and new payment or governance burdens that make manual processes untenable. That includes major college athletic departments, pro clubs, and Olympic or NGB programs with distributed staff and athletes. What remains missing is a clean bridge from public category headlines to Teamworks-specific revenue pools. Public sources do not disclose live Wallet or GM customer counts, the distribution of average contract values by school tier, the percentage of schools that will fully opt into revenue sharing, or how much current spending is replacing point tools versus expanding overall software budget. Those gaps do not negate the opportunity, but they do argue for underwriting Teamworks against constrained elite-workflow spend rather than the full sports-analytics headline market.[CM042, CM043, CM044, CM045, CM049, CM050]

2.6 Exhibits

3.1 Landscape shape: Teamworks is competing against wedges, suites, and infrastructure layers

Teamworks is no longer competing only against legacy scheduling tools or one direct clone. Its own product pages now describe an operating system that spans talent acquisition, daily operations, athlete management, performance, and intelligence. That breadth means the relevant landscape has to be split into classes: direct workflow wedges such as Front Rush in recruiting; performance and medical specialists such as Catapult, SportsWareOnLine, and CoachMePlus; adjacent athlete-monetization vendors such as Opendorse; and larger external-data and media-infrastructure companies such as Sportradar and Genius Sports. Status-quo substitutes also matter. The College of Charleston procurement record explicitly says athletics departments can remain stuck on multiple disconnected systems, while Teamworks argues that one identity layer, one hub, and shared calendars/tasks reduce that fragmentation. The key takeaway is that Teamworks’ buyer is often not choosing between Teamworks and one perfect like-for-like rival. The real choice is between adopting one broader suite, staying multi-homed across specialists, or delaying migration altogether.[CP001, CP003, CP004, CP005, CP008, CP010]

3.2 Module-level overlap: specialists still own credible wedges in recruiting, performance, and intelligence

At the workflow level, Teamworks’ breadth is genuine, but specialist alternatives remain credible because they sell depth where a staff can justify keeping a separate tool. Front Rush remains a real recruiting wedge in college sports because it talks directly to recruiting and roster management and discloses meaningful scale with more than 9,500 teams at 850-plus schools. Hudl pressures Teamworks from the game-preparation and video-analysis side, especially as Teamworks broadens through Telemetry and Intelligence. On the performance side, Catapult sells sports technology and analytics with public-company reporting discipline, while SportsWareOnLine remains tightly focused on athletic-training EMR and CoachMePlus keeps a lighter-weight human-performance and communication pitch. In intelligence, Sportradar and Genius Sports are not daily operations suites, but their scale, data infrastructure, and public disclosure make them credible adjacency threats if team decision-support converges further toward external data stacks. The implication is that Teamworks wins most cleanly when a buyer values cross-module workflow integration more than single-function depth.[CP011, CP012, CP013, CP014, CP015, CP016]

3.3 Pricing, packaging, and switching-cost dynamics favor suites but remain hard to benchmark publicly

Public pricing transparency is weak across this category. Most of the fetched peer pages talk about capabilities, packages, or contact-sales flows without exposing list prices. Teamworks is one of the few vendors in this source set where real contract evidence is visible. Texas A&M’s agreement shows a discounted annual Teamworks package at $235,000 plus overage mechanics for usage, while the College of Charleston’s sole-source justification shows a four-year Hub commitment and explicitly ties the purchase to already-installed Compliance and Academics modules. That matters competitively because it turns Teamworks’ integration story into something more concrete than homepage language: once a department standardizes on shared identity, shared calendars, and connected operations modules, replacement gets harder and procurement gets more strategic. At the same time, the absence of broad public peer pricing means investors still cannot tell from public evidence whether Teamworks wins by premium bundle value, by discounting, or by simply selling into higher-budget athletic departments than point-solution vendors target.[CP031, CP032, CP033, CP034, CP035, CP036]

3.4 Moat durability is strongest in workflow density, but intelligence expansion adds trust risk

The best-supported Teamworks moat is workflow density: one identity layer, connected products, and customer evidence that departments use Hub to tie together existing modules instead of keeping fragmented tools. That moat is real, but it is not invulnerable. Specialists still provide rational best-of-breed alternatives, especially where recruiting, video, athletic-training EMR, or human-performance teams want depth without a full-platform migration. Large adjacent data companies also matter because they have public scale and could move closer to team decision-support over time. The clearest adverse evidence is the Phillies dispute over Zelus/Titan exclusivity. Public reporting says the court denied emergency injunctive relief, yet the broader breach-of-contract fight continues and the allegations go directly to trust, exclusivity, and data-rights stewardship in Teamworks Intelligence. For diligence, that means Teamworks should be underwritten less as an unassailable monopoly and more as a broad suite whose defensibility depends on attach rates, integration depth, and clean governance of acquired intelligence assets.[CP038, CP040, CP041, CP042, CP043, CP045]

3.5 Exhibits

4.1 Revenue model breadth is real, and procurement documents prove Teamworks can sell enterprise bundles rather than only point products

Teamworks is no longer a single communications tool monetized through a flat subscription. Current official pages show a portfolio spanning Hub, Operations, Academics, Recruiting, Intelligence, AMS, Performance, GM, and Wallet, which means the economic model is best understood as modular vertical software with multiple expansion paths. The clearest pricing evidence comes from procurement rather than a public rate card. A Texas A&M contract shows an Elite Package covering Hub, Academics, Video, INFLCR Verified, IN+ Local Exchange, and Notemeal at a $225,000 annual list price, plus a $12,500 INFLCR Plus add-on, before discounting to a $235,000 annual total. The same document also discloses usage-style charges for extra message credits and additional two-way users. That is materially different from simple seat licensing: it suggests Teamworks can combine recurring platform subscriptions, optional module upsells, and metered extras inside one institutional agreement. Wallet and GM widen the model further. Wallet is framed as a digital banking and payment workflow for NIL, per diem, and revenue-share disbursements, while GM is positioned as a budgeting, scenario-analysis, and athlete-earnings platform. Those launches imply a future mix that could include payment orchestration, compliance-related service load, and higher-value decision-support software alongside classic workflow subscriptions. Public evidence is therefore good enough to describe the revenue architecture, but not to quantify revenue mix, recognition policy, or realized gross profit by module.[CI001, CI002, CI003, CI004, CI005, CI006]

4.2 GTM evidence points to a land-and-expand sales motion with high switching costs, but public CAC and payback remain absent

The best publicly visible sales-efficiency clue is not a published CAC figure but the shape of customer contracts. The College of Charleston’s sole-source document says Hub was needed because the athletics department already used Teamworks Compliance and Academics, and it puts the estimated four-year cost at $446,800. That is a textbook expansion sale into an existing installed base. Texas A&M’s contract shows a three-year payment schedule stepping from $185,000 to $210,000 to $235,000 as early-adopter discounts roll off, which suggests Teamworks can raise realized annual contract value over time rather than rely on one-year discounting alone. The University of Maine’s 2026 athletics-solutions RFP results show that Teamworks is also competing in formal procurement processes against vendors such as Trackman, TruMedia, and Concourse Tech, reinforcing the idea that this is an enterprise procurement sale, not lightweight self-serve software. Memphis’ case study adds an operational angle. The school describes using GM and Wallet to manage budgets to the penny, coordinate high-volume contracts, and avoid late payments with a lean administrative team. That kind of workflow pain relief can produce strong retention and expansion if the product becomes embedded in daily finance and compliance operations. The tradeoff is that the same value proposition likely requires onboarding, support, implementation coordination, and customer success resources that pure bottom-up SaaS would not. Public sources therefore support a high- switching-cost, multi-product enterprise motion, but they do not expose CAC, payback, sales productivity, or attach-rate data directly.[CI014, CI015, CI016, CI017, CI018, CI019]

4.3 Teamworks increasingly sits between workflow SaaS, sports data infrastructure, and payment/compliance software

Teamworks’ product mix makes simplistic SaaS assumptions risky. Hub, Operations, Academics, Recruiting, and AMS read like familiar vertical-software modules whose economics should benefit from recurring contracts and workflow stickiness. But Intelligence explicitly markets predictive models, contract valuation, and sport-specific data science, while Wallet adds withholding calculations, W-8BEN collection, royalty-payment handling, and compliance safeguards for international athletes. Those capabilities may support premium pricing and larger budgets, yet they also imply specialized talent, support overhead, banking/compliance dependencies, and lower comparability to a pure seat-based workflow vendor. Public comps illustrate the spread. CompaniesMarketCap puts Sportradar at roughly $3.85 billion of market cap on about $1.55 billion of trailing revenue, while Catapult sits around $0.78 billion of market cap on about $0.11 billion of annual revenue. That yields a rough public market-cap-to- revenue anchor from about 2.5x to about 7.1x across relevant sports-technology businesses. Teamworks almost certainly lands somewhere on that wide spectrum rather than on a single clean software multiple. The problem is that no public Teamworks source discloses revenue, ARR, gross margin, services mix, or retention. The comp set is therefore useful for framing valuation possibilities and disclosure expectations, but not for confirming whether Teamworks’ >$1 billion private valuation is conservative or aggressive.[CI006, CI007, CI008, CI012, CI013, CI029]

4.4 Capital depth looks directionally strong, but public liquidity disclosure is far too thin for a real runway judgment

The visible funding story is a genuine strength. Teamworks’ current About page says the company has raised roughly $400 million, and the company’s June 2025 Series F announcement says it secured $235 million in an oversubscribed round led by Dragoneer at a pre-money valuation above $1 billion. The earlier 2023 Series E added $65 million and explicitly said the new capital would continue to fund M&A and expansion into new regions and elite human performance. Taken together with the acquisition pace from ARMS through Telemetry, Zelus, Opteamal, Sportlogiq, and PFF Enterprise, the public record suggests capital has been used both for organic product expansion and inorganic platform broadening rather than for mere survival financing. That said, “well funded” is not the same as “adequately capitalized.” Public sources do not disclose cash on hand, monthly burn, runway, debt facilities, seller notes, earn-outs, or integration reserves. Wallet and GM may also increase working-capital and compliance demands relative to core workflow software, especially as institutions move into revenue sharing and royalty withholding. The Zelus litigation is not obviously catastrophic, but ongoing legal and integration exposure is still a real contingent call on management attention and potentially on cash. The right financial judgment is therefore asymmetrical: Teamworks clearly has strong fundraising support, yet outside investors still lack the balance-sheet data needed to decide whether another financing round is optional or strategically necessary.[CI012, CI013, CI022, CI024, CI025, CI026]

4.5 Verdict: evidence supports enterprise pricing power and strategic breadth, but not yet revenue quality or capital-efficiency underwriting

The investable part of the story is easy to see. Teamworks can command six-figure annual contracts at large universities, monetize add-ons and overages, and extend beyond workflow software into analytics, athlete-earnings planning, and payment/tax orchestration. The surrounding market also looks favorable: sports analytics and athlete-management software are both growing at double-digit rates, while the post-House environment creates a new direct-payment budget line that Wallet and GM are explicitly designed to capture. In a best case, that produces a compound model with sticky core subscriptions, premium analytics, and budget-critical payment workflows. The underwriting blockers are equally clear. Public sources still do not show module-level ARR, gross margin, CAC, payback, net retention, customer concentration, backlog, cash balance, burn, runway, or debt and earn-out obligations. Procurement documents prove price points exist, but they do not reveal realized discounting across the broader customer base. Likewise, the public comp set helps bound valuation logic but cannot rescue a missing revenue denominator. The financial conclusion is therefore positive but incomplete: Teamworks looks strategically broad and well financed, yet the company remains materially under-disclosed on the specific inputs needed to judge revenue quality, margin path, and capital adequacy with confidence.[CI024, CI025, CI029, CI030, CI031, CI032]

4.6 Exhibits

5.1 Module map and customer-workflow coverage

The strongest product-level conclusion from the fetched Teamworks pack is that the company is no longer selling a single communications application. Current product pages divide the platform across Hub, Operations, Performance, Recruiting, and Intelligence, while older-but-still-useful product-breakdown material shows how legacy brands such as ARMS, Smartabase, Notemeal, INFLCR, Pulse, and Retain were pulled into that broader operating-system narrative. Hub remains the clearest anchor: Teamworks describes it as the unified command center for rosters, calendars, messages, travel, files, and other daily coordination workflows. Around that core, Operations handles logistics and inventory, AMS acts as the performance-data layer, Recruiting manages evaluation and onboarding, and Intelligence plus GM extend the stack into decision support. Customer procurement evidence from Charleston and Texas A&M makes this more than branding. Those documents show real buyers treating Teamworks as a multi-module suite that can centralize operational workflows and bundle adjacent products rather than as a narrow point solution.[CE001, CE002, CE003, CE004, CE005, CE007]

5.2 Architecture and integration workflows

Public materials repeatedly point to a shared architecture built around common identity, navigation, profiles, calendars, and tasks. The OSS integrations page explicitly says Teamworks has already integrated those shared components across products, while Hub and OSS materials together show one Teamworks ID, shared navigation, and customer-facing APIs for profile and calendar data. That pattern then appears in concrete workflow integrations. Recruiting can promote a recruit into Hub. ARMS and Whistle added hourly sync and unified recruiting boards. Hub-ARMS Tasks brought compliance actions into the same mobile surface. The 2024 integration wave deepened that pattern with one login, app switching, CARA logs in the app, and recruit creation in Hub. On the performance side, Teamworks says Nutrition uses an open API into AMS and that Smartabase or AMS can aggregate upstream feeds such as GPS, force plates, motion capture, S&C, and nutrition data. Taken together, the public architecture looks less like a monolith and more like a shared control plane sitting above specialist workflow modules and external data inputs.[CE006, CE009, CE010, CE014, CE015, CE016]

5.3 AI, analytics, and decision-support assets

The most important product expansion story is Teamworks' move from workflow software into data and decision support. Intelligence is marketed around machine learning and predictive models, and the recruiting launch argues that many college programs do not have the in-house engineering capacity to operationalize modern player-tracking and play-by-play data on their own. GM extends that logic into budgets and roster construction by centralizing athlete-earnings data, linking it to Compliance and Intelligence, and now surfacing football metrics such as Player Impact, Snap Count, Play Speed, and Change of Direction directly inside profiles. The acquisition trail gives substance to that strategy. Zelus brought the Data Engine and Titan Intelligence; Telemetry added coaching workflows and vision-linked football tooling; Sportlogiq added automated tracking and research depth; PFF added football data; and Opteamal extended athlete-monitoring reach in European football. The result is not yet a fully proven unified analytics stack in public, but the asset map is real and materially broader than simple marketing copy about AI.[CE011, CE012, CE024, CE025, CE026, CE027]

5.4 Trust, privacy, and operational-support signals

The public trust posture is real but thinner than the product map. Teamworks' privacy policy clearly states that the company acts as a processor for service data, discloses a subprocessor set that includes AWS, Twilio, and DocuSign, states that services are not intended for children under 13, and acknowledges both cross-border transfers and the inherent limits of digital-transmission security. Public technical and support surfaces also exist. Teamworks maintains public AMS and Recruiting Communications help-center entry points, a staff-resources page with sign-in and mobile-app links, and transition pages that explain how Smartabase and Whistle were rebranded into Teamworks AMS and Teamworks Recruiting Communications. Customer procurement material from Charleston adds another operational signal by describing single sign-on and direct integration between Hub and already-installed Compliance and Academics tools. What remains missing from the public pack is the deeper reliability and assurance layer enterprise buyers often expect: status evidence, uptime reporting, and certification detail do not appear with the same specificity as product marketing.[CE035, CE036, CE037, CE038, CE039, CE040]

5.5 Roadmap signals and open diligence gaps

Roadmap signals from 2023 onward point to a company prioritizing consolidation, cross-product workflow depth, and data-asset integration. PR Newswire framed the ARMS acquisition as a way to accelerate continued integrations across the operating system, while Forbes reported that Teamworks also needed several quarters to digest and integrate the wave of recent acquisitions. The 2024 integration releases around ARMS, Hub, and INFLCR show genuine workflow progress, and the 2024-2026 AI and analytics acquisitions give the platform more proprietary data and model depth. Even so, the public record still stops short of proving how completely those assets are unified in day-to-day operator workflows or how broadly customers buy across the stack. That leaves the core underwriting split unchanged: Teamworks has a credible module map, visible integration motion, and a real AI roadmap, but later diligence still needs operational proof on attach rates, uptime, API depth, and trust controls before treating the entire surface as mature and uniform.[CE020, CE021, CE022, CE024, CE026, CE030]

5.6 Exhibits

6.1 Segmentation, buyer map, and installed-base shape

Teamworks’ public customer record is unusually concentrated in elite-sports institutions rather than in mass-market teams or consumer sports apps. The buyer and payer is rarely the same person as the end user: athletic directors, operations executives, finance leaders, and NGB administrators appear to buy the system, while athletes, coaches, medical staff, league officials, and even family members are the daily users. The product footprint also segments clearly by job-to-be-done. Hub and Operations material anchor Teamworks as the system of record for rosters, calendars, travel, messages, and files; AMS appears where performance and medical data need to be centralized; Memphis adds a newer NIL and revenue-sharing buyer; and public procurement shows college athletics buyers can purchase broad bundles rather than single features. Scale claims are large enough to matter: Teamworks says it served more than 6500 elite teams in 2025 and more than 7000 organizations by March 2026, while its own financing materials claim deep penetration in the NFL, NCAA Division I, Olympic federations, and other major leagues. The important nuance is that these are installed-base claims, not revenue-quality disclosures. They prove reach and category relevance, but they do not by themselves prove durable multi-product ARR across the whole footprint.[CU001, CU002, CU003, CU004, CU008, CU010]

6.2 Named proof, deployment depth, and international breadth

The strongest evidence in this chapter comes from named deployments that go beyond logos and identify actual workflows or stakeholders. Melbourne City used Hub and AMS during a move into a new training facility and described an in-season implementation across two professional and six academy teams. Aquatics GB and Swim England adopted Hub and AMS for athletes, coaches, medical teams, and performance staff, explicitly tying the rollout to data-driven performance decisions ahead of LA 2028. Bates is a useful lower-resource proof point because it had already implemented Hub and Compliance plus Recruiting before making AMS the next step in its roadmap, framing the purchase as a way to reduce staff burden rather than add another system. Team Netherlands shows Olympic customization, with sport-specific data and workflow views by federation. In North America, the Penguins provide the longest visible durability signal, Austin FC adds current AMS proof in MLS, Memphis shows Teamworks moving into NIL and revenue-sharing administration, Baylor shows daily Hub usage in women’s college basketball operations, and the NWSL story claims near-leaguewide Hub penetration. Bristol City adds a second international club-soccer logo, helping confirm that Teamworks’ customer proof is not just North American or college-centric. The chapter therefore supports real multi-segment adoption, with especially strong proof in pro clubs, NCAA departments, and Olympic or NGB environments.[CU019, CU020, CU021, CU022, CU023, CU024]

6.3 Durability signals, land-and-expand motion, and procurement economics

Teamworks looks more durable where the public record shows either long tenure or module expansion. The Penguins’ use of Hub since 2014 is the cleanest long-duration proof. Bates moved from Hub and Compliance plus Recruiting into AMS, Memphis added General Manager and Wallet for the revenue-sharing era, and Charleston’s sole-source justification explicitly said Hub was needed because Compliance and Academics were already in place. Texas A&M’s contract suggests that at least some collegiate customers buy Teamworks as a broad bundle with six-figure annual value rather than as a narrow point solution. That is important because it implies Teamworks can deepen wallet share inside existing accounts, not just count more logos. At the same time, public evidence also shows that expansion is not frictionless. The Maine RFP shows Teamworks still appears in competitive procurements alongside Trackman, TruMedia, and Concourse, and PFF Enterprise illustrates that some customer expansion is arriving through acquisition rather than purely organic cross-sell. The practical conclusion is that Teamworks appears to have a credible land-and-expand engine, but the balance between organic module attach, acquired customer base, and procurement win rate is still opaque.[CU016, CU017, CU018, CU025, CU030, CU032]

6.4 Retention visibility, evidence-quality gaps, and customer trust risk

The biggest diligence gap is not a shortage of named customers; it is the lack of public evidence on customer quality. No reviewed source disclosed NRR, GRR, churn, contract length, customer concentration, or segment-level ARR mix. Even the strongest case studies are overwhelmingly vendor-authored, which means they do a good job of illustrating workflow fit but a weak job of proving renewal economics or independently measured outcomes. Public proof therefore supports a conclusion that Teamworks is deeply embedded in elite-sports workflows, but not that its installed base is uniformly high-value or equally durable across segments. This matters more because Teamworks is moving further into sensitive data and decision-support use cases. The Phillies and Zelus dispute is not a broad churn event, but it is a real customer-trust signal attached to an acquired analytics asset and raises the possibility that exclusivity, data-rights governance, and acquired-customer obligations can become meaningful in later diligence. Investors should read the customer chapter as strong on segmentation and deployment proof, decent on expansion logic, and still underpowered on retention math, independent satisfaction evidence, and concentration analysis.[CU047, CU048, CU049, CU050, CU053, CU054]

6.5 Exhibits

7.1 College demand tailwinds are real, but NCAA budget pressure can still squeeze spend

Teamworks' most urgent growth wedge is now tied directly to the most financially stressed buyer cohort in U.S. sports. The company says General Manager serves 98% of Division I NCAA institutions and that Wallet is already trusted by more than 700 NCAA institutions, which means Teamworks is not just adjacent to the House-era transition; it is selling directly into it. NCAA rule changes now allow schools that opt in to provide up to $20.5 million in direct financial benefits to student-athletes and require technology platforms for payment monitoring and third-party NIL agreement reporting. That creates obvious product demand for GM, Wallet, and adjacent compliance workflows. The risk is that the same sources describing the opportunity also describe buyer stress. University Business, OVG, SportsRecruits, Opendorse, and RallyFuel all depict a market where schools are adding new athlete-payment obligations, searching for sponsorship and auxiliary revenue, and coping with continuing rule uncertainty. For Teamworks, this can produce a two-speed customer outcome: stronger urgency for planning and payments software at the top of the market, but slower procurement, tighter budgets, and more ROI scrutiny across the rest of Division I. If revenue-sharing costs are treated as non-discretionary while software budgets remain contestable, college demand may stay large but become more cyclical and politically visible.[CR001, CR002, CR003, CR004, CR005, CR006]

7.2 Payments, privacy, and data-rights exposure now sit inside the product surface

Teamworks' risk surface is broader than legacy communications or scheduling software. Wallet pushes the company into payment timing, withholding, IRS remittance, and international-athlete tax workflows; the privacy policy reserves wide rights to collect data from schools, governing bodies, partners, and data providers, to combine data sets for analytics, and to transfer data in legal processes or acquisitions; and the Phillies-Zelus dispute shows how quickly analytics products can become entangled in exclusivity, IP, and customer-trust fights. The Wallet material is especially important because it shows Teamworks taking on operational steps that are closer to regulated financial plumbing than pure workflow automation: W-8BEN collection, withholding calculations, 1042-S issuance, and remittance when the institution appoints Teamworks as withholding agent. At the same time, the privacy policy openly contemplates subprocessor use, business-partner sharing, FERPA handling, CPRA rights, and data transfers in a sale or merger. That means every new product and acquisition adds governance work around access controls, data provenance, and institutional consent. The Zelus case is the clearest adverse manifestation of that risk. Even without an injunction, a live dispute over who can commercialize analytics components to rivals is exactly the kind of issue that can unsettle customers deciding whether to centralize roster valuation and contract strategy inside Teamworks.[CR017, CR018, CR019, CR020, CR021, CR022]

7.3 Acquisition-led expansion raises dependency, integration, and founder-execution risk

Teamworks is no longer a single-product operating tool vendor. The reviewed official materials show a rapid acquisition cadence across analytics and performance infrastructure: Zelus, Telemetry Sports, Opteamal, Sportlogiq, and PFF Enterprise in roughly eighteen months, plus continuing product stitching work such as ARMS-Hub integrations. That breadth can be strategically powerful because it lets Teamworks sell recruiting, roster valuation, payment, operations, compliance, and video/data products into the same sports organization. It also means the execution burden has shifted toward integration quality, data consistency, UX coherence, and contract harmonization across acquired assets. Recent Teamworks communications still revolve heavily around founder-CEO Zach Maurides, who is the visible voice on Wallet, GM, and the major analytics acquisitions; that makes key-person concentration a genuine issue even if the company has deeper functional leaders behind the scenes. Teamworks does have evidence of demand outside the NCAA ecosystem, including Hub penetration in the NWSL, but those wins do not eliminate the core concentration fact that its end markets are still sports organizations whose budgets rise and fall with media, donor, sponsorship, ticket, and institutional support cycles. Underwriting therefore has to assume that integration and customer-spend sensitivity matter together: if acquired analytics units are slow to unify or if sports buyers retrench, Teamworks could face a harder path to converting platform breadth into durable, high-quality ARR.[CR034, CR035, CR036, CR037, CR038, CR039]

7.4 The investable posture depends on observable triggers rather than broad category optimism

The right way to underwrite Teamworks is to watch the junctions where external pressure and internal complexity meet. If college programs keep opting in to revenue sharing but athletic departments show rising deficits, procurement slowdowns, or a heavier dependence on sponsorship backfill, the company may still win logos while seeing tougher budget negotiations. If Wallet keeps expanding, diligence should look for payment errors, withholding exceptions, complaint volume, and the depth of privacy or security assurance behind the policy language. If the Phillies-Zelus dispute produces adverse rulings, restrictive settlement terms, or discovery that exposes broader customer-rights tension, the analytics-upside narrative should be marked down immediately. And because recent growth is tied to acquired analytics assets, migration milestones, cross-sell evidence, and platform rationalization matter more than headline deal volume. The kill criteria below therefore focus on events that management cannot spin away: customer budget strain, compliance failures, litigation setbacks, integration misses, and any sign that founder-centered execution is becoming a bottleneck rather than an edge. Public evidence is good enough to rank those risks now, but not good enough to clear them without deeper customer, legal, and systems diligence.[CR046, CR047, CR048, CR049, CR050, CR051]

8.1 Investment thesis, anti-thesis, and why price sensitivity dominates the call

The long case for Teamworks is straightforward to articulate. Teamworks has assembled a broad vertical operating stack across Hub, Recruiting, AMS, Intelligence, Wallet, Academics, Influencer, and adjacent workflow tools, which is exactly the type of product breadth that can justify a premium multiple if customers truly buy multiple modules and renew them over time. Public contracts show that departments can spend well into six figures annually for a bundled Teamworks deployment, while the NCAA's post-House rules create more reporting, revenue-sharing, and payment complexity inside athletic departments. That combination means Teamworks is not just selling software seats; it may be selling workflow consolidation at a moment when schools and elite teams need fewer vendors and better data integrity. The bull case is therefore less about raw team-count marketing and more about whether Teamworks has become the system of record for operational, performance, and payment workflows across elite sports organizations. The anti-thesis is equally important because valuation is already non-trivial. Public evidence still does not disclose the revenue base, margin profile, net revenue retention, or cap-table terms that would let an outside investor test whether the >$1B mark is conservative, fair, or aggressive. Public comps such as Genius Sports and Sportradar disclose audited revenue and still trade closer to 2x-3x EV/revenue, while Catapult trades at a higher premium but does so with visible public-market marks and formal reporting. Teamworks also carries integration and contract-execution risk through the Zelus analytics dispute and the broader challenge of monetizing acquired products instead of merely assembling them. The recommendation therefore has to be explicitly price-sensitive: Teamworks may be strategically strong, but the current public record is not strong enough to support a buy at any price above the last disclosed private round without further diligence.[CV001, CV003, CV005, CV006, CV007, CV008]

8.2 Current valuation context and explicit price discipline

The best public valuation anchor remains the June 2025 Series F: Teamworks raised $235M at a pre-money valuation above $1B, and public coverage now points to roughly $400M of total funding since inception. That is enough to confirm that Teamworks has graduated from a niche workflow vendor into a scaled, institutionally financed private sports-tech platform. It is not enough, however, to validate the current price. The same public record that gives investors a headline valuation withholds the inputs that matter most for underwriting: revenue, gross margin, operating leverage, customer concentration, debt, and the liquidation waterfall. Public procurement evidence helps, because it proves Teamworks can land annualized contracts ranging from roughly $112k for a Hub-led deployment to $235k for a broader multi-module package. But those contracts do not solve the central problem: one department-level deal can span many teams and many modules, so the company's 6,500-team / 7,000-organization scale claims cannot be translated cleanly into ARR. That opacity drives the entry rule. If Teamworks deserves only the 2x-3x revenue multiples that public comps such as Genius Sports and Sportradar receive, then a >$1B valuation would require roughly $333M-$500M of revenue. If Teamworks deserves a more premium Catapult-like 5x-7x multiple because it is closer to a vertical operating system with sticky workflow ownership, the mark still implies roughly $143M-$200M of revenue. Public evidence does not tell the market which world is real. The right discipline is therefore not to accept the private mark at face value, but to insist on audited revenue, retention, and cap-table proof before treating the current price as more than a sponsor-backed reference point.[CV001, CV002, CV005, CV006, CV022, CV023]

8.3 Comparable set and what public markets imply about supportable valuation

The comparable set has to do two jobs at once. First, it needs to bracket Teamworks against public sports-tech operators that actually disclose revenue and market values. Second, it needs to incorporate pricing evidence from Teamworks' own public contracts, because Teamworks is private and the public-market data alone cannot tell investors how much revenue its workflow stack might already generate. Catapult is the cleanest premium comp for Teamworks' performance-and-operations angle: it sells sports performance technology directly to teams and currently trades around 5x-7x revenue depending on whether one uses Yahoo's EV/revenue or CompaniesMarketCap's market-cap framing. Genius Sports and Sportradar are less directly comparable on product mix, but they matter because they are scaled public sports-data platforms with audited reporting, and both currently trade much closer to 2x-3x revenue. That spread is the essential valuation frame for Teamworks. Public Teamworks contracts then provide the missing monetization anchors. Texas A&M's Elite package reached $235k annually by year three, and College of Charleston's Hub-only sole-source memo implied roughly $112k annually for a narrower deployment. Those are not enough data points to build a precise ARR model, but they do establish that Teamworks can monetize at institutional ACVs that matter. The key limitation is that the public record does not reveal how many customers look like Texas A&M versus Charleston, how many entity counts represent full athletic departments versus single teams, or how much attach rate exists for analytics and Wallet products. That is why the comparable analysis points to a valuation band, not a single fair-value answer.[CV005, CV006, CV014, CV015, CV016, CV017]

8.4 Bull, base, and bear scenarios with explicit triggers

The bull case requires Teamworks to prove that the operating-system story is monetizing faster than public evidence currently shows. Underwriting that outcome means assuming Teamworks has already crossed into roughly $200M+ of revenue-equivalent scale, that Wallet and GM capture a meaningful share of the post-House payment/compliance workflow, and that the Intelligence / Zelus / PFF stack becomes a durable premium analytics layer rather than an integration project. In that world, the company can plausibly support a $1.8B-$2.4B valuation by 2028, especially if public sports-tech multiples stabilize and Teamworks can show strong retention plus multi-product penetration. The base case is much more conservative and is the right public-only default today. It assumes Teamworks is real, scaled, and strategically well positioned, but not yet publicly proven enough to command an aggressive premium. If audited revenue lands in the roughly $150M-$200M zone, if attach rates are mixed across the stack, and if public multiples remain in the current range, then the present >$1B mark can be justified only as roughly fair rather than obviously attractive. The bear case emerges if revenue is materially below the Catapult-implied threshold, if litigation or customer-confidentiality disputes slow analytics adoption, or if the Series F preference stack heavily subordinates a new entrant. In that outcome, Teamworks could still be a good company and a bad price, which is exactly why kill criteria and diligence asks matter more here than broad product admiration.[CV008, CV010, CV023, CV028, CV029, CV030]

8.5 Diligence blockers, exit readiness, and final recommendation

The decisive blockers are all products of private-company opacity. Public sources do not disclose audited revenue, gross margin, EBITDA, net revenue retention, cohort expansion, module attach rates, customer concentration, debt, or the preference stack created by the Series F. Those are not cosmetic omissions. They determine whether the >$1B mark is a disciplined private round, a sponsor-friendly marketing mark, or a price that only works because insiders hold better downside protection than a new investor would. The same problem affects exit readiness: Teamworks may well be strategically interesting to a buyer because it spans operations, recruiting, analytics, and payments, but the public record does not prove the type of audited scale and governance maturity that would normally justify broad IPO-style underwriting. That leaves a narrow but defensible conclusion. Teamworks deserves to stay on the buy list because the product breadth, contract evidence, and market tailwinds are real. It does not deserve a buy recommendation at the last disclosed price until management discloses enough financial and cap-table detail to bridge public evidence to the current valuation. The correct recommendation today is research-more / track: proceed only if diligence proves that Teamworks is already at least a high-end private vertical-SaaS revenue scale with clean renewal dynamics and investor terms that do not transfer hidden downside to new money. Without that proof, the company remains compelling while the entry remains under-justified.[CV024, CV025, CV026, CV030, CV031, CV037]

8.6 Exhibits