Q1 2026 revenue 01
989 USD M [CO005] Diligence report
EquipmentShare
EquipmentShare remains a buy-and-monitor story: a scaled rental platform with a credible software layer, rising guidance, and improving liquidity, but still dependent on cyclically exposed capital-heavy operations.
Cover facts
Company profile
EquipmentShare (Nasdaq: EQPT) is a Columbia, Missouri-based construction technology and equipment rental company founded in 2015 by Jabbok Schlacks and Willy Schlacks. It combines equipment rental, sales, service, and the T3 connected-jobsite platform to serve large contractors, industrial customers, infrastructure projects, and data-center builders. The refreshed Q1 2026 reporting set showed 407 operational locations, $989 million of quarterly revenue, $1.605 billion of liquidity, and raised full-year 2026 guidance, reinforcing the view that the company is still scaling with disciplined execution.
- Website
- www.equipmentshare.com
- Founded
- 2015-01-01
- Founders
- Jabbok Schlacks, Willy Schlacks
- Founding location
- Columbia, MO
- Headquarters
- Columbia, MO
- Product
- Equipment rental, equipment sales, parts and service, and T3-connected jobsite software that combines telematics, fleet visibility, access control, and workflow tools.
- Customers
- Large contractors, industrial operators, infrastructure developers, and complex-jobsite customers that value uptime, visibility, and fleet control.
- Business model
- A hybrid model with equipment rental as the core revenue engine, supported by sales, service, OWN program economics, and software-enabled workflow control.
- Stage
- Public
- Funding status
- Public company after its January 2026 IPO; still supported by prior venture capital, asset-backed lending, and OWN-program financing.
Executive summary
Top strengths
- Scaled branch network and strong Q1 2026 execution support continued growth
- T3 gives the company a differentiated operating layer across connected jobsites
- Liquidity and leverage improved enough to keep the financing story manageable
- OWN-program economics reduce some of the fleet-capex burden
Top risks
- Construction cyclicality can quickly compress utilization and margins
- Software monetization remains opaque relative to the rental business
- Safety, uptime, and branch execution are core operating risks
Open gaps
- Standalone T3 revenue or ARR is still not separately disclosed
- Customer concentration and retention metrics remain opaque
- Segment gross margins are still not fully transparent
Contents
01Company Overview
1.1 Identity, ownership, and what the company actually sells
EquipmentShare is now a public company trading on Nasdaq under EQPT, but the business still looks like the vertically integrated model it built privately: equipment rental, equipment sales, parts and service, plus T3 software and connected-jobsite tooling. The official website frames the company as a construction productivity platform rather than a pure rental broker, and the public filings / press releases show that the company uses the rental fleet to seed adoption of the technology layer. The result is a business with two linked engines — physical branch density and software-enabled fleet visibility — that share the same customer relationship and operating backbone.[CO001, CO002, CO003, CO006]
| metric | value/status | date | confidence | gap |
|---|---|---|---|---|
| Founded | 2014 | 2014 | high | Exact incorporation vs. operating launch date varies by source |
| Headquarters | Columbia, Missouri | current | high | None |
| Public listing | Nasdaq: EQPT | 2026-01 | high | None |
| Locations | 407 | 2026-03-31 / 2026-05 | high | Latest public quarter; branch count may move each quarter |
| TTM revenue | $4.652B | 2026-03-31 | high | Derived from Sacra / Q1 release |
| FY2025 revenue | $4.379B | 2025 | high | Historical base year |
| Employees | 7,768 | IPO filing period | medium | Later public-current headcount not consistently disclosed |
| T3-managed equipment | 325,000 pieces | IPO filing period | high | Public filing-period disclosure |
| Total raised | $1.599B | IPO + prior disclosed rounds | medium | Includes IPO proceeds and disclosed equity/debt raises; not all private financings |
Public, source-backed snapshot; where dates differ, the row uses the latest explicitly disclosed period.
[CO001, CO004, CO005, CO007, CO010, CO011]Milestones from founding through the IPO and Q1 2026 operating update.
Dates are sourced from official press releases and public reporting; the figure is an ordered milestone summary rather than a comprehensive chronology.
2014 founding [CO001]
2023 capital structure step-up [CO010]
IPO launch [CO004]
IPO pricing [CO004]
Nasdaq debut [CO004]
1.2 Scale, funding, and operating leverage
The latest public disclosures show a company that has scaled to hundreds of locations, roughly a billion dollars of quarterly revenue, and a large managed fleet, but still depends on recurring fleet investment and external capital. The IPO launched at $24.50 per share and raised roughly $747 million before the company traded on Nasdaq in January 2026. A later first-quarter release showed 407 locations, $989 million of revenue, and raised full-year 2026 guidance, while an earlier financing release showed a $3 billion ABL facility and $640 million of senior notes. That combination suggests meaningful operating leverage, but it also keeps the capital-intensity question front and center.[CO004, CO005, CO007, CO010, CO011]
| person | role | background | fit / coverage | key-person dependency |
|---|---|---|---|---|
| Jabbok Schlacks | Co-founder, CEO, Director | Construction-tech operator and one of the company's original founders | Sets strategy and capital allocation; central to the growth narrative | High |
| Willy Schlacks | Co-founder, President, Director | Product and operating co-founder with deep customer/workflow context | Runs product and operating execution alongside CEO | High |
| Trevor Schauenberg | CFO | Finance leader named in public financing communications | Owns leverage, liquidity, and capital markets execution | Medium |
Leadership roles are drawn from public profiles and company financing communications; background fields stay intentionally brief where public biographical detail is sparse.
[CO001, CO002, CO003, CO010]| stakeholder | role | control / economic importance | diligence ask |
|---|---|---|---|
| Jabbok and Willy Schlacks | Voting-control founders | Control class votes and strategic direction | How durable is dual-class control after IPO? |
| Public shareholders | Minority equity holders | Provide current market valuation and liquidity | How much future dilution or leverage remains? |
| Capital One | Core lender | Provides ABL / liquidity backstop | How covenants and borrowing base evolve as fleet grows |
| Debt investors | Bondholders and noteholders | Finance fleet and growth capex | Refinancing risk and interest burden |
| OWN Program participants | Third-party fleet capital providers | Supply a large share of managed fleet economics | Counterparty concentration and contractual terms |
This is a stakeholder map, not a cap table; it highlights who influences growth, capital intensity, and governance outcomes.
[CO002, CO004, CO007, CO010]1.3 What remains opaque and why it matters
The main underwriting gap is not whether EquipmentShare has scale — it clearly does — but how much of the value accrues to the software layer versus the rental fleet, and how much dilution or leverage is still embedded in the capital structure. Public evidence supports the existence of T3, the OWN program, and a growing branch network, yet the company does not separately disclose external SaaS ARR, segment gross margins by product line, or a fully consistent current headcount figure across sources. Those gaps do not break the story, but they do limit precision around valuation and margin durability. For that reason, this chapter treats the company as public, scalable, and operationally improving, while keeping the hidden economics explicit.[CO008, CO009, CO012]
02Market Analysis
2.1 Market boundary and substitutes
The market is best framed as construction equipment rental plus the connected jobsite stack that sits on top of rental, labor, and service. EquipmentShare is not trying to replace the entire construction budget; it is targeting the spend that is sensitive to uptime, access to equipment, and visibility into assets and crews. Status-quo substitutes remain ownership, local dealerships, brokered rental, and fragmented software tools. That boundary matters because it explains why the company can be both a rental platform and a software vendor, and why the rental relationship is the channel for software adoption. The key implication is that market size must be interpreted through workflow adoption, not just spend categories.[CM001, CM002, CM003, CM004]
| segment/category | included spend | excluded spend | buyer/payer | relevance |
|---|---|---|---|---|
| rental core | equipment rental and service | owned fleet capex | contractor operations | core revenue engine |
| connected jobsite | telematics, access control, labor/time tools | generic office software | ops/IT/field leaders | T3 attach and retention |
| sales / resale | new and used equipment sales | pure commodity retail | dealer and procurement buyers | supports lifecycle monetization |
| status quo ownership | in-house fleets and local management | software not adopted | owners/operators | main substitute |
| fragmented software | point tools and spreadsheets | integrated fleet platform | field ops and finance | competition and migration source |
Boundary table is directional rather than exhaustive; it is intended to separate the rental platform from adjacent software and ownership substitutes.
[CM001, CM002, CM003, CM004]A constrained market view from construction spend to rental to connected-jobsite software.
Layer widths indicate hierarchy, not quantitative proportions.
The layers are conceptual; only the public evidence-based items are quantified.
[CM001, CM005, CM009, CM010]2.2 Sizing lenses and demand drivers
The public evidence supports multiple sizing lenses rather than a single clean TAM. One lens is the U.S. construction project pipeline that management cited in the IPO filing; another is the size of the rental fleet and branch network already in market; a third is the software and telematics attach opportunity on owned or managed assets. Demand is being pulled by infrastructure, industrial, data centers, and advanced manufacturing, while the main constraints are capital intensity, cyclicality, and the fact that many contractors still own a large share of their equipment. Those constraints make adoption slower than pure software, but they also create a higher switching-cost business once embedded. Because the source set is mixed and partly directional, the safest conclusion is that the opportunity is large but not yet precisely measured.[CM005, CM006, CM007, CM008]
| publisher/lens | year | geography | value | CAGR | methodology | confidence | limitation |
|---|---|---|---|---|---|---|---|
| management pipeline | 2026 | U.S. | $7T pipeline cited | n/a | public filing narrative | medium | not a formal TAM |
| public branch footprint | 2026 | U.S. | 407 locations | n/a | operating scale | high | not a market size |
| fleet managed through T3 | 2025/2026 | U.S. | 325,000 pieces | n/a | installed base | high | not all are company-owned |
| rental mix | 2025/2026 | U.S. | about 62% rental revenue | n/a | revenue mix lens | medium | mix is not demand size |
| telematics attach | 2026 | U.S. | unknown standalone ARR | n/a | gap lens | low | software monetization is not separately disclosed |
This table is intentionally evidence-constrained; it preserves sizing paths without inventing a single precise TAM.
[CM005, CM007, CM009, CM010, CM011]| segment | buyer | user | payer | workflow | budget owner | adoption trigger |
|---|---|---|---|---|---|---|
| national contractor | ops and procurement | superintendent / foreman | project or central ops | large jobsites, multiple crews | project ops | need for uptime and fleet control |
| regional contractor | owner / ops lead | field manager | job owner | mixed fleet management | owner ops | need for scale without internal fleet complexity |
| industrial / data center | site leadership | equipment coordinator | project finance | critical-path uptime | capital projects | downtime risk and access control |
| infrastructure / gov | contracting team | equipment manager | public or prime buyer | long-duration heavy fleet | ops and finance | multi-year project visibility |
| small contractor | owner-operator | crew lead | owner | ad hoc rentals | owner | subscription or rental convenience |
Buyer map is representative, not a complete census of every customer segment.
[CM002, CM003, CM005, CM006]2.3 What is still not cleanly measurable
The key diligence gap is that public materials do not isolate the exact share of market opportunity captured by the T3 layer versus the physical rental business. That means the valuation conversation has to stay anchored to evidence: public branch growth, public revenue growth, disclosed customer mix, and disclosed telematics usage. If the business eventually monetizes more of the connected-jobsite layer directly, the market could justify a higher multiple; if not, it should trade more like a scaled rental platform with incremental software upside rather than like a pure SaaS company.[CM009, CM010, CM011, CM012]
03Competitors
3.1 Direct, adjacent, and status-quo alternatives
The direct competitive set is led by very large public rental incumbents, but the real comparison set is broader: used-equipment marketplaces, local dealership networks, fleet-management point tools, and the internal fleet a contractor already owns. EquipmentShare wins when the customer values a single operating layer for equipment, people, and service rather than a low-friction transaction only. That makes the competitive battle more about workflow control, fleet data, and branch density than about a single feature or price quote. In practice, each deal is a system-selection decision, not just a machine rental quote.[CP001, CP002, CP003, CP004]
| competitor | category | scale/funding | target segment | differentiation | limitation |
|---|---|---|---|---|---|
| United Rentals | incumbent rental giant | public multi-billion scale | broad industrial and construction | scale and breadth | technology integration less bespoke |
| Sunbelt Rentals | incumbent rental giant | public multi-billion scale | construction and industrial | dense branch network | less integrated software layer |
| Herc Rentals | incumbent rental giant | public multi-billion scale | industrial and construction | fleet scale and service | less jobsite data visibility |
| Ritchie Bros / RB Global | auction / resale platform | public scale | used-equipment buyers and sellers | marketplace liquidity | not a full-service rental operating system |
| In-house fleet | status quo | not applicable | owner-operators and large contractors | control and sunk assets | capex and management burden |
Scale is intentionally coarse where the source set does not support a clean apples-to-apples metric.
[CP001, CP002, CP003, CP004]EquipmentShare sits between pure rental scale and a connected-jobsite software layer.
| Item | X (1–9) | Y (2–8) | Context |
|---|---|---|---|
| 1. EquipmentShare | 8 | 8 | |
| 2. United Rentals | 9 | 5 | |
| 3. Ritchie Bros / RB Global | 4 | 4 | |
| 4. Local dealer | 3 | 6 | |
| 5. In-house fleet | 2 | 3 | |
| 6. Status quo | 1 | 2 |
Axes are ordinal rather than normalized: x = operational scale, y = jobsite software integration.
[CP001, CP005, CP007, CP010]3.2 Differentiation, pricing, and distribution
EquipmentShare's main differentiation is the combination of rental footprint, service coverage, and T3 data capture. Competitors can imitate individual parts of that stack, but it is harder to match the whole bundle because each layer supports the others. The downside is that pricing is not transparent and many of the same customers can multi-home across vendors or keep an owned fleet for the critical-path assets. That makes the customer relationship durable, but not invulnerable. The customer ends up buying convenience, uptime, and workflow integration together, which is exactly why the comparison set has to stay broad.[CP005, CP006, CP007, CP008]
| buying criteria | EquipmentShare | incumbents | local dealer | owned fleet |
|---|---|---|---|---|
| branch convenience | high | high | medium | low |
| fleet visibility | high via T3 | medium | low | variable |
| pricing transparency | medium | medium | medium | high internal |
| workflow integration | high | medium | low | internal |
| capital intensity | high to company | n/a | n/a | high to customer |
Ordinal scores are evidence-backed but not mathematically precise.
[CP005, CP006, CP007, CP008]| price/unit/contract model | included capabilities | discount or unknowns | implication |
|---|---|---|---|
| rental quote | equipment plus service | opaque, market-based | switching depends on service quality |
| software add-on | T3 and related tools | not separately disclosed | software upside is hard to value |
| dealer sale / resale | asset sale plus parts | bundle pricing varies | competition remains localized |
| owned fleet | capex plus internal ops | fully internal cost basis | status quo remains a strong substitute |
| auction / resale | market transaction | fees vary by platform | not a direct one-stop operating layer |
Pricing is intentionally qualitative because the public source set does not disclose a full rate card.
[CP005, CP006, CP010]3.3 Moat durability and displacement risk
The strongest adverse evidence is that incumbents are well-capitalized, the addressable market includes substitutes that do not require EquipmentShare, and customers can still choose ownership or local dealers. The optimistic view is that data density, branch convenience, and workflow integration create switching costs that are hard for pure software vendors to replicate. On balance, the moat looks real but operational rather than purely technological, which means execution and branch economics matter more than a defensible algorithm. The public takeaway is that the moat is durable only if management continues to out-execute on service and adoption, not because rivals are absent. That puts a premium on branch execution and product adoption depth today.[CP009, CP010, CP011, CP012]
04Financials
4.1 Revenue streams and monetization
The company monetizes the same customer in several ways: rental, sales, parts and service, telematics, and related jobsite tools. That mix is useful because the rental relationship creates a low-friction path to additional products, but it also makes the revenue line less clean than a pure software company. Public disclosures show rental as the majority of revenue and telematics as an important but still relatively small monetization layer. The practical underwriting question is whether incremental attach from T3 can lift margins enough to justify the capital intensity of the fleet. In other words, the story is not just about what the company sells today, but about whether the same customer can be monetized more richly over time without losing the operating discipline that makes the fleet model work.[CI001, CI002, CI003, CI004]
| stream | mechanism | unit | current value/status | quality | diligence ask |
|---|---|---|---|---|---|
| rental | daily/weekly/monthly fleet usage | revenue | majority of revenue | high | utilization by segment |
| equipment sales | new and used sales through the network | revenue | material but lower-margin | medium | mix and resale economics |
| parts and service | repair, maintenance, support | revenue | supporting stream | medium | attach and margin |
| T3 telematics | software / hardware attach | revenue | not separately disclosed | medium | external ARR and pricing |
| OWN program | third-party capital on managed fleet | cash flow | important funding mechanism | medium | counterparty terms |
The table keeps monetization channels separate even when public reporting aggregates them.
[CI001, CI002, CI003, CI009]How customer activity converts into rental, services, and software revenue.
| Node / Connection | Node / from | To | Context |
|---|---|---|---|
| Node 1 | Customer demand | ||
| Node 2 | Rental fleet and branches | ||
| Node 3 | T3 / telematics | ||
| Node 4 | Service and parts | ||
| Node 5 | Revenue and EBITDA | ||
| Node 6 | Public market | valuation reference | |
| Connection 1 | Customer demand | Rental fleet and branches | |
| Connection 2 | Rental fleet and branches | T3 / telematics | |
| Connection 3 | Rental fleet and branches | Service and parts | |
| Connection 4 | T3 / telematics | Revenue and EBITDA | |
| Connection 5 | Service and parts | Revenue and EBITDA |
The flow abstracts away timing and depreciation differences.
[CI001, CI003, CI004, CI007]4.2 Unit economics, liquidity, and leverage
The Q1 2026 release suggests the business is producing operating leverage: revenue rose, mature-location margins were strong, and full-year guidance moved up. At the same time, EquipmentShare still has a large fleet, a meaningful debt stack, and a liquidity profile that depends on continued access to revolving credit and bond markets. That means underwriting cannot stop at top-line growth; it has to weigh depreciation, interest, capital expenditure, and how much of the OWN Program simply shifts financing obligations rather than removing them. The most investor-relevant nuance is that a growing revenue base does not automatically translate into free cash flow if the company keeps reinvesting into branch openings and equipment refresh cycles.[CI005, CI006, CI007, CI008]
| price/unit/contract | list vs realized pricing | discounts/unknowns | source |
|---|---|---|---|
| IPO price | $24.50/share public | underwritten pricing vs aftermarket | official IPO release |
| fleet rental rate | not publicly disclosed | site- and asset-specific | public reporting |
| T3 subscription | not separately disclosed | bundled or add-on depending on account | public reporting |
| OWN payouts | revenue share to third parties | program terms not public | IPO filing reporting |
| service labor / parts | market-dependent | customer-specific | company and trade coverage |
Public pricing is intentionally incomplete; the point is to show where economics are visible and where they are not.
[CI001, CI003, CI008, CI009]| metric | value/null | confidence | why it matters | diligence ask |
|---|---|---|---|---|
| TTM revenue | $4.652B | high | scale and momentum | confirm latest quarter |
| FY2025 revenue | $4.379B | high | baseline growth | compare to 2026 run-rate |
| Q1 2026 revenue | $989M | high | run-rate confirmation | verify seasonality |
| mature-location EBITDA margin | 55% | high | branch economics | segment by age/region |
| net leverage | 2.8x | medium | balance-sheet risk | watch debt and cash |
| liquidity | $1.605B | medium | funding runway | reconcile revolver/cash split |
A compact operating snapshot anchored to the latest public quarter and current market commentary.
[CI005, CI006, CI007, CI008]4.3 What still cannot be underwritten precisely
The most important financial gap is that public disclosures do not separate external software ARR from the rental and services engine. Gross margin by segment is also not transparent enough to build a clean SOTP without assumptions. That makes the company easier to understand as a growth platform than as a narrowly modeled SaaS business. The investment case therefore rests on public revenue growth, location expansion, leverage trends, and the company's ability to keep fleet economics and financing costs under control.[CI009, CI010, CI011, CI012]
05Product & Technology
5.1 What the product is
The product definition is broad because EquipmentShare sells a jobsite operating system, not a single SKU. T3 provides visibility into equipment, people, access control, service status, and utilization, while the physical rental business gives the company a distribution layer and a reason to install hardware. The public materials also show a range of tooling and mobile workflows, including internal apps, time cards, and tool-trailer use cases. In practical terms, the product is best thought of as a combined hardware-software-ops bundle. The product gets stronger when those layers reinforce one another rather than compete for attention.[CE001, CE002, CE003, CE004]
| module/asset/product line | user | status/maturity | differentiation | diligence gap |
|---|---|---|---|---|
| T3 telematics | ops and fleet managers | mature | real-time visibility | standalone ARR |
| rental fleet | contractors and crews | mature | distribution and uptime | utilization by segment |
| mobile tool trailer | field crews | growing | on-site access and tracking | unit economics |
| Uptime Center | service teams | mature | 24/7 monitoring | scalability |
| time cards / internal apps | ops and finance users | internal tooling | workflow speed | how broadly deployed |
Product modules are represented at the level visible in public material and case studies.
[CE001, CE002, CE003, CE005]T3 sits above telematics hardware and below customer workflows, with branch support around it.
- Customer workflows
- jobsite control and reporting
- T3 software
- visibility and coordination layer
- Telematics / hardware
- devices, sensors, and asset signals
- Branch / service network
- physical support and fulfillment
- Uptime Center
- monitoring and exception handling
- Internal apps
- low-code operational tooling
The stack simplifies the platform into the layers most visible in public sources.
[CE001, CE005, CE006, CE008]5.2 Architecture, support, and deployment
The architecture appears to be a telematics and workflow stack sitting on top of a physical branch and service network. Public sources mention an Uptime Center, customer success support, and internal low-code tools that let non-engineers launch operational apps quickly. That suggests a product that is operationally mature even if it is not publicly documented like a SaaS vendor. The downside is that there is little public documentation of APIs, changelogs, or release cadence, so the product has to be judged by customer outcomes and operating behavior rather than by developer-facing proof. In practice, that means the operations team is part of the product surface.[CE005, CE006, CE007, CE008]
| user job | current workflow | company solution | measurable benefit | limitation |
|---|---|---|---|---|
| fleet manager | spreadsheets and fragmented tools | T3 dashboard | single pane of glass | needs hardware installation |
| shop technician | manual service tracking | Uptime Center / service queue | faster maintenance | depends on branch execution |
| field supervisor | phone and text coordination | time cards and access tools | less rework | integration complexity |
| tooling coordinator | lost or damaged tools | mobile tool trailer | lower shrinkage | new product economics |
| ops analyst | custom spreadsheets | internal low-code apps | faster deployment | not a public platform |
These use cases are drawn from public case studies and operating articles rather than a formal product catalog.
[CE002, CE004, CE006]| layer/process/component | role | dependency | risk |
|---|---|---|---|
| hardware telematics | asset data capture | installation and device uptime | device failure or rollout delays |
| cloud workflow layer | data aggregation and visibility | clean data feeds | integration breaks |
| branch/service network | physical fulfillment | fleet and labor | service quality and safety |
| customer success / onboarding | adoption support | training coverage | underutilization |
| internal app stack | rapid ops tooling | non-engineer builders | shadow IT or security risk |
Architecture is inferred from public descriptions of the product and operating model.
[CE005, CE006, CE008, CE011]5.3 Differentiation and trust gaps
The differentiator is the combination of data density, fleet control, and branch execution, not a single patented feature. The biggest trust risks are operational: telematics hardware has to work, service has to be timely, and the system has to stay safe when it is controlling expensive equipment on active jobsites. The public source set supports the existence of safety and governance processes, but it does not give a deep view into security architecture or release management. That means the product is credible, but still somewhat opaque. The most valuable thing the company can do is keep turning that opacity into repeatable customer value.[CE009, CE010, CE011, CE012]
06Customers
6.1 Who the customers are
Public filing commentary shows that the customer base is not a single small-business segment. Instead, the mix skews toward national and regional contractors, industrial buyers, infrastructure projects, and government work, with smaller contractors using the platform more opportunistically. That matters because large, complex jobsites create the strongest need for control, uptime, and the ability to manage fleet, labor, and materials in one place. The rental relationship is the beachhead; software expansion is the land-and-expand logic. That skew also means the company wins more often when the buyer has a project schedule to protect than when the buyer simply wants the lowest cash outlay.[CU001, CU002, CU003, CU004]
| segment | buyer/user/payer | use case | scale | revenue/strategic value | gap |
|---|---|---|---|---|---|
| national contractor | central ops / site super / project finance | multi-site fleet control | largest | high strategic value | exact concentration not public |
| regional contractor | owner / ops lead | mixed fleet management | medium | land-and-expand lane | retention not disclosed |
| industrial | ops / equipment manager | downtime prevention | large | high-margin use case | segment economics opaque |
| infrastructure / government | project and procurement | long-duration jobs | large | sticky work | contract details not public |
| small contractor | owner-operator | ad hoc rentals | small | lower strategic value | usage frequency unknown |
The table reflects public customer archetypes rather than a customer list with named accounts.
[CU001, CU002, CU003, CU004]Land through rental, then expand into software and workflow control.
The journey map is a simplified land-and-expand path.
[CU001, CU005, CU007, CU011]6.2 Adoption path and proof of use
Adoption evidence is strongest when a public case study or operational article shows actual usage rather than just a logo. The Retool case study is useful because it shows internal EquipmentShare teams using low-code tools to build market-data and rate-setting workflows, while the official safety article shows branch-level operational discipline. Together, these sources suggest that the company consumes its own software-style tools internally and then reuses that workflow logic for customer-facing products, which makes adoption look operationally real rather than purely promotional.[CU005, CU006, CU007, CU008]
| metric | value | date | source | confidence | implication | missing denominator |
|---|---|---|---|---|---|---|
| national customer share | >50% | IPO filing period | IRN filing article | medium | enterprise skew | exact revenue contribution |
| regional customer share | 36% | IPO filing period | IRN filing article | medium | mid-market penetration | exact spend |
| local customer share | 10% | IPO filing period | IRN filing article | medium | less dependence on SMBs | segment churn |
| construction project mix | 60% non-res / infra / gov | IPO filing period | IRN filing article | medium | project complexity | project-level revenue |
| T3-managed assets | 325,000 | IPO filing period | IRN filing article | high | product adoption | customer-owned vs company-owned split |
The main point is directional adoption; the denominator is deliberately left blank where public reporting does not define it.
[CU002, CU003, CU004, CU009]| customer | segment | deployment/use case | production vs pilot | outcome | limitation |
|---|---|---|---|---|---|
| Mark's team at EquipmentShare | internal ops | market-data and rate-setting apps via Retool | production | faster internal tooling | not an external customer |
| Louisville branch | field ops | safety and technician development story | production | better safety culture | single branch example |
| mobile tool trailer users | field crews | tool inventory and check-out | production | lower tool loss | anonymous public case |
| national contractors | enterprise | fleet visibility and control | production | publicly described but unnamed | no named account disclosed |
| industrial / data center users | complex jobsites | critical-path asset management | production | strong use case fit | no named account disclosed |
Named proof is limited because public sources mostly describe segments and internal examples rather than customer logos.
[CU005, CU006, CU007, CU008]6.3 Retention, expansion, and concentration gaps
The hard part is that public evidence does not provide a clean NRR, GRR, churn, or customer-count metric. That means retention has to be inferred from branch expansion, internal case studies, and repeated use cases rather than from a standard SaaS dashboard. The favorable read is that the business seems to expand once embedded in a complex jobsite. The adverse read is that concentrated revenue from large national and industrial customers can cut both ways if a downturn or project delay hits. The public record therefore gives a helpful picture of who buys, but only an incomplete picture of how sticky the relationship really is once the initial rental win lands, especially at renewal time.[CU009, CU010, CU011, CU012]
07Risks
7.1 Ranked legal, financial, and operational risks
The highest risks are the ones that can break the thesis fastest: a downturn in non-residential construction, a capital markets squeeze, or a failure to keep the fleet and T3 stack reliable. Governance is also a real risk because the company came public with a founder-controlled structure. Those risks do not make the business weak, but they do mean the investment case depends on disciplined execution and a macro environment that stays constructive enough to support fleet utilization and refinancing. In practice, that means quarterly reporting, branch health, credit access, and customer demand all have to move together. A single weak quarter would not end the story, but a few weak quarters would.[CR001, CR002, CR003, CR004]
| rule/license/case | jurisdiction | status | likelihood | severity | mitigation | residual exposure | diligence path |
|---|---|---|---|---|---|---|---|
| IPO disclosure / public-market obligations | U.S. | ongoing | medium | high | SEC reporting discipline | continuous filing risk | monitor 10-Q/8-K cadence |
| founder-controlled governance | U.S. | ongoing | high | medium | independent oversight | minority investor influence limited | review proxy and board changes |
| employment / safety compliance | multi-state | ongoing | medium | high | safety programs | workplace incidents remain possible | review OSHA / safety disclosures |
No major single legal event is proved in the source set; the table focuses on structural legal exposure.
[CR001, CR004, CR005]High-severity risks cluster in leverage, cyclicality, and operational reliability.
The heatmap is a qualitative severity matrix rather than a numeric risk model.
[CR001, CR002, CR005, CR006]7.2 Operational, safety, and security exposure
Safety is not just a culture point; it is a direct operating risk because the business runs shops, yards, drivers, service teams, and telematics hardware. Public evidence shows the company has launched safety and monitoring programs, but that only reduces, rather than eliminates, the exposure. The same connected-assets model that creates product differentiation also broadens the attack surface and makes downtime or service disruption more visible to customers. Any branch-level miss can show up quickly in customer experience, repair costs, and reputation. That is why operational discipline is part of the product, not just the back office.[CR005, CR006, CR007, CR008]
| failure mode | likelihood | severity | mitigation maturity | residual exposure | unresolved gap |
|---|---|---|---|---|---|
| fleet downtime | medium | high | medium | service disruption | real uptime and repair SLA |
| safety incident | medium | high | medium | injury and reputational risk | incident rates by branch |
| cyber / access control failure | low-medium | high | early | jobsite trust loss | security architecture |
| branch execution slippage | medium | medium | medium | margin compression | new site ramp economics |
| software support gap | low-medium | medium | early | customer churn | support metrics |
| margin pressure | medium | medium | medium | slower expansion | pricing discipline |
| refinancing shock | low-medium | high | medium | liquidity stress | debt maturity profile |
| trust incident | low | high | medium | customer defection | security and safety controls |
The table reflects operational risks that matter because the company controls both software and physical assets.
[CR005, CR006, CR007, CR008]| dependency | counterparty | role | concentration | failure scenario | severity | mitigation | residual exposure |
|---|---|---|---|---|---|---|---|
| capital markets | lenders / bondholders | fleet finance | high | refinancing pressure | high | liquidity and leverage management | rate and covenant sensitivity |
| OWN participants | third-party fleet owners | capital source | high | program pullback | high | contractual structure | counterparty risk |
| construction cycle | customers / projects | demand driver | high | project slowdown | high | diversified end markets | macro cyclicality |
| technology stack | software and hardware vendors | product layer | medium | integration failure | medium | support / monitoring | product reliability |
| talent | technicians and drivers | service delivery | high | labor shortage | medium | training and recruiting | execution risk |
Dependencies are ordered by strategic impact, not by exact contractual concentration.
[CR001, CR002, CR003, CR005]7.3 Thesis-break triggers and what to monitor
The key monitoring signals are leverage, liquidity, customer concentration, branch performance, and whether T3 continues to deepen customer lock-in. If growth slows sharply, if the fleet becomes less productive, or if software never becomes meaningful as a standalone business, the market may eventually re-rate the company as a more ordinary rental operator. The thesis survives if management can keep margins high, the balance sheet stable, and the platform sticky. Missing a few of those signals for long enough would be the clearest warning, especially if customer demand weakens at the same time.[CR009, CR010, CR011, CR012]
08Valuation
8.1 Why the market can still like this story
The bull case is straightforward: the company has public-scale revenue, a large location footprint, improving margins, and a software layer that is embedded in the operating model. The company also raised guidance after Q1 2026, which suggests demand is still healthy. If investors believe the T3 layer can deepen retention and increase monetization, the business deserves a better multiple than a plain rental operator. The thesis is strongest when the market views EquipmentShare as a hybrid platform rather than a fleet-only company. That premium is easier to defend when the public filings and investor-relations updates keep pointing in the same direction, quarter after quarter.[CV001, CV002, CV003, CV004]
| recommendation | confidence | risk rating | valuation stance | decision implication |
|---|---|---|---|---|
| buy | medium | medium | attractive | growth + platform upside still outweighs risk |
| track | medium | medium | fair | if execution slows or valuation resets |
| avoid | low | high | stretched | if leverage or growth deteriorates |
This is the summary judgment table that bridges evidence to an investment stance.
[CV009, CV010, CV011, CV012]Scale and platform evidence lead to a positive stance, but leverage and transparency cap confidence.
| Node / Connection | Node / from | To | Context |
|---|---|---|---|
| Node 1 | Scale / locations | ||
| Node 2 | T3 and workflow lock-in | ||
| Node 3 | Margin expansion | ||
| Node 4 | Leverage and opacity | ||
| Node 5 | Quarterly proof | ||
| Node 6 | Buy / Track | ||
| Connection 1 | Scale / locations | T3 and workflow lock-in | |
| Connection 2 | T3 and workflow lock-in | Margin expansion | |
| Connection 3 | Margin expansion | Buy / Track | |
| Connection 4 | Leverage and opacity | Buy / Track |
The flow compresses the thesis into the four factors most visible in public evidence.
[CV001, CV005, CV007, CV009]8.2 Why the market might discount it
The bear case is equally simple: the business remains capital intensive, public disclosure is still incomplete, and the software layer is not separately valued. That means the market can only underwrite the company by assuming fleet productivity, financing discipline, and software attach all continue to improve. If any one of those slows, the valuation can compress quickly because the market will revert to seeing a cyclical rental business with leverage rather than a high-multiple software platform. Even a modest miss on execution can matter when the story depends on both growth and capital discipline, especially if funding terms stop looking friendly.[CV005, CV006, CV007, CV008]
| argument | what would change the view |
|---|---|
| T3 and branch density justify a higher multiple | if software attach never becomes visible |
| guidance and margin expansion support quality growth | if margin expansion stalls |
| OWN improves capital efficiency | if financing conditions tighten |
| public disclosures still underwrite a platform story | if transparency worsens |
Each anti-thesis item is a concrete break point rather than a generic risk statement.
[CV001, CV005, CV006, CV008]| scenario | assumptions | valuation/return logic | key risks | probability signal |
|---|---|---|---|---|
| bull | software monetization expands and margins continue up | multiple expansion plus earnings growth | execution and macro | possible but evidence-dependent |
| base | rental growth continues and branch margins stay healthy | steady compounding with moderate multiple | capex and leverage | most consistent with current evidence |
| bear | macro slows and software stays bundled | multiple compression on cyclical concerns | deleveraging pressure | high if demand weakens |
Scenario analysis is intentionally qualitative because the public source set does not disclose all valuation inputs.
[CV001, CV005, CV006, CV007]8.3 Recommendation and thesis breaks
The most defensible stance is still positive but not complacent: the evidence supports a Buy/Track-style rating with moderate confidence rather than a high-conviction software multiple. Current valuation data suggest the market is no longer paying the IPO peak, but it is still giving the company credit for growth and technology leverage. The thesis breaks if leverage, margin, or software monetization stall; it strengthens if public evidence starts to show durable software revenue and continued branch-level margin expansion. Fresh quarterly disclosures would be the cleanest way to test that view, and the next report should lean heavily on those numbers.[CV009, CV010, CV011, CV012]
Disclaimer
This report is prepared for informational and diligence purposes only and does not constitute investment advice. It is based on public disclosures, filings, press releases, and third-party reporting available as of the report run date. Market and valuation figures are estimates or market snapshots unless explicitly sourced to company disclosures.
Evidence index
| ID | Statement | Confidence | Sources |
|---|---|---|---|
| CO001 | EquipmentShare was founded in 2014 and is based in Columbia, Missouri. | High | SO001, SO008 |
| CO002 | Jabbok Schlacks and Willy Schlacks remain the public faces of the company as co-founders and operating leaders. | High | SO003, SO005, SO008 |
| CO003 | The company sells an integrated bundle of equipment rental, equipment sales, parts/service, and T3-connected jobsite technology. | High | SO001, SO002, SO008 |
| CO004 | EquipmentShare priced its IPO at $24.50 per share, sold 30.5 million Class A shares, and raised about $747 million in gross proceeds. | High | SO003, SO004 |
| CO005 | The first-quarter 2026 release showed 407 locations and $989 million of revenue for the quarter. | High | SO007, SO002 |
| CO006 | The official website describes T3 as a real-time visibility layer for fleet, assets, and people across construction jobsites. | High | SO001, SO002 |
| CO007 | The IPO-filing period disclosure cited 373 rental locations, 7,768 employees, and 325,000 pieces of equipment managed by T3. | High | SO005, SO002 |
| CO008 | Public sources do not separately disclose external T3 ARR, so the software layer cannot yet be valued from a standalone revenue line. | Low | |
| CO009 | Sacra estimates trailing-twelve-month revenue at $4.652 billion through March 31, 2026 and FY2025 revenue at $4.379 billion. | Medium | SO007 |
| CO010 | EquipmentShare expanded its ABL facility to $3 billion and closed a $640 million senior-notes transaction in 2023. | High | SO006, SO001 |
| CO011 | The company's public disclosures and third-party summaries point to a capital-intensive but profitable rental business with improving operating leverage. | Medium | SO007, SO005 |
| CO012 | A current diligence gap remains around consistent headcount reporting, standalone software monetization, and the exact current market value of the public equity. | Low | |
| CM001 | The market boundary is better framed as equipment rental plus connected-jobsite operations than as standalone software. | Medium | SM001, SM002, SM006 |
| CM002 | Public sources show national, regional, industrial, infrastructure, and government buyers as the main demand centers. | Medium | SM003 |
| CM003 | Status-quo substitutes include owning fleets, using local dealers, and managing jobsites with spreadsheets or point tools. | Medium | SM006, SM002 |
| CM004 | The company uses the rental relationship as the channel for adoption of T3 and other jobsite tools. | Medium | SM001, SM002, SM006 |
| CM005 | Management and third-party coverage point to a very large project pipeline and a demand tailwind from industrial, infrastructure, and data-center work. | Medium | SM003, SM005 |
| CM006 | Capital intensity and cyclicality remain the core constraints on adoption and valuation. | Medium | SM004, SM003 |
| CM007 | The public materials support a multi-layer opportunity in rental, telematics, and workflow software, but not a clean TAM calculation. | Medium | SM004, SM005, SM006 |
| CM008 | EquipmentShare reported 407 locations and raised 2026 guidance, showing the market remains receptive to its footprint expansion. | Medium | SM005 |
| CM009 | The 7 trillion dollar projects-pipeline claim is a directional market story, not an independently audited market size. | Low | |
| CM010 | A standalone software valuation is not possible from public disclosure because external T3 revenue is not separately reported. | Low | |
| CM011 | The rental mix and the installed base suggest a business that monetizes workflow control, not just short-term equipment access. | Medium | SM003, SM002, SM006 |
| CM012 | The strongest adverse read is that the same macro cycles that lift rental demand can also compress utilization and capital returns. | Medium | SM004, SM003 |
| CP001 | United Rentals, Sunbelt Rentals, and Herc Rentals are the clearest large-scale rental incumbents facing EquipmentShare. | Medium | SC001, SC002, SC004 |
| CP002 | Ritchie Bros / RB Global and other used-equipment channels represent meaningful adjacent and substitute routes for buyers. | Medium | SC001, SC004 |
| CP003 | The status quo still includes owned fleets and local dealer relationships, which are credible alternatives for many contractors. | Medium | SC005, SC007 |
| CP004 | EquipmentShare differentiates by pairing branch convenience with a connected-jobsite software layer that incumbents often sell separately. | High | SC007, SC008, SC004 |
| CP005 | Pricing is not fully transparent in public materials, so comparison has to be made on package value rather than a single rate card. | Low | |
| CP006 | The T3 layer creates workflow lock-in by capturing fleet, labor, and utilization data that would be cumbersome to recreate elsewhere. | Medium | SC007, SC008 |
| CP007 | Customers can still multi-home across vendors or keep a large owned fleet for critical-path assets, which limits absolute lock-in. | Medium | SC005, SC004 |
| CP008 | Incumbent rental leaders have the capital to add technology and defend branch density, so EquipmentShare cannot rely on being the only tech-enabled player. | Medium | SC002, SC006 |
| CP009 | A broad competitive moat still depends on execution quality, service coverage, and branch economics rather than on software alone. | Medium | SC004, SC007 |
| CP010 | The public source set does not support a precise price comparison across all major competitors, so unsupported cells must stay qualitative. | Low | |
| CP011 | The strongest adverse evidence is that many contractors can remain productive with owned equipment and local dealer support. | Medium | SC005, SC001 |
| CP012 | The most important strategic question is whether EquipmentShare can turn T3 from an attachment into a durable standalone advantage. | Low | |
| CI001 | EquipmentShare monetizes rental, equipment sales, parts and service, and T3-connected tools across the same customer base. | High | SI001, SI004, SI003, SI002 |
| CI002 | Rental is still the largest revenue stream, while telematics remains smaller but strategically important. | Medium | SI004, SI003 |
| CI003 | The OWN program supports growth by letting third parties finance equipment that EquipmentShare still manages. | High | SI001, SI004, SI005 |
| CI004 | T3 and related tools are monetization layers, but the public source set does not isolate their ARR. | Low | |
| CI005 | Sacra and management commentary point to $4.652 billion of TTM revenue through March 31, 2026 and $989 million of Q1 revenue. | High | SI001, SI003, SI002 |
| CI006 | Mature rental locations reached a 55% adjusted EBITDA margin on a trailing-twelve-month basis. | High | SI001, SI002 |
| CI007 | Net leverage was about 2.8x and liquidity about $1.605 billion in the public Q1 2026 reporting set. | Medium | SI002 |
| CI008 | The raised 2026 guidance implies continued growth but does not remove the capital intensity of the fleet model. | Medium | SI002 |
| CI009 | Public filings and commentary show that the company still has to fund fleet growth, debt service, and seasonal working-capital swings. | Medium | SI004, SI005 |
| CI010 | The most important missing metric is gross margin and software margin by segment. | Low | |
| CI011 | Public evidence supports a business that is profitable enough to raise guidance, but not yet transparent enough for a fully clean SOTP model. | Medium | SI002, SI003 |
| CI012 | The adverse read is that growth still depends on recurring capex and debt markets rather than on software-like marginal economics. | Medium | SI004, SI005 |
| CE001 | T3 is a real-time visibility layer for fleet, assets, and people on construction jobsites. | Medium | SE001, SE002, SE007 |
| CE002 | The product bundle extends beyond telematics into time cards, access management, service, and workflow tools. | Medium | SE004, SE005 |
| CE003 | EquipmentShare uses hardware plus software to capture jobsite data rather than selling a pure software-only experience. | Medium | SE005, SE007 |
| CE004 | Internal ops teams have built market-data, rate-setting, and mobile tool-trailer workflows with low-code tools. | Medium | SE004 |
| CE005 | The company operates an Uptime Center and support model that reinforces adoption and service reliability. | High | SE002, SE006 |
| CE006 | The style guide and technical case studies are the clearest public developer-signal-like artifacts, but the public API surface remains sparse. | Low | |
| CE007 | The mobile tool trailer and Bluetooth tagging use case shows that the product can expand into adjacent workflow problems. | Medium | SE004 |
| CE008 | The public source set supports a product that is operationally mature, not a beta software experiment. | Medium | SE002, SE005, SE006 |
| CE009 | Safety and compliance are part of the product value proposition because the hardware and software operate on active jobsites. | High | SE006, SE002 |
| CE010 | The most important product gap is the lack of public documentation for APIs, release cadence, and security architecture. | Low | |
| CE011 | A large chunk of product value appears to come from operational integration rather than from one discrete app. | Medium | SE007, SE004, SE005 |
| CE012 | The adverse read is that connected assets widen the attack surface and raise the cost of system reliability. | Medium | SE006, SE005 |
| CU001 | The public customer mix skews toward larger contractors and complex jobsites rather than pure small-business use. | Medium | SU001, SU005 |
| CU002 | More than half of customers were described as national companies, with 36% regional and only 10% local. | Medium | SU001 |
| CU003 | Around 60% of revenue came from non-residential, infrastructure, and government projects in the IPO filing period. | Medium | SU001 |
| CU004 | Industrial customers accounted for a meaningful portion of the customer base, reinforcing the importance of uptime and critical-path equipment. | Medium | SU001 |
| CU005 | The Retool case study shows EquipmentShare teams using internal apps for market data, rate setting, and tool-trailer workflows in production. | Medium | SU002, SU009 |
| CU006 | The safety champion article shows branch-level execution and training culture that supports customer service quality. | Medium | SU003, SU010 |
| CU007 | The company appears to land through rental and then expand into workflow tooling and broader operational control. | Medium | SU006, SU002, SU005 |
| CU008 | The mobile tool trailer use case suggests the product expands into adjacent operational pain points once trust is established. | Medium | SU002 |
| CU009 | Public evidence does not provide NRR or GRR, so retention has to be inferred rather than directly measured. | Low | |
| CU010 | The strongest adverse read is customer concentration in national and project-based accounts, which ties demand to macro cycles. | Medium | SU001, SU005 |
| CU011 | Named external customer logos are scarce in the public source set, so most proof is segment-level rather than account-level. | Low | |
| CU012 | The customer story is strongest where public case studies show actual production use rather than marketing claims. | Medium | SU002, SU003 |
| CR001 | Construction cyclicality is the biggest structural risk because it drives utilization and project timing. | Medium | SR003, SR004 |
| CR002 | Debt, fleet financing, and refinancing access remain meaningful risks even after the IPO. | High | SR002, SR003 |
| CR003 | The founder-controlled governance structure limits minority shareholder influence. | Medium | SR004 |
| CR004 | The company has to manage public-company disclosure and compliance risk in addition to operating risk. | Medium | SR004 |
| CR005 | Safety, service quality, and uptime are material operational risks because the company handles physical assets and crews. | High | SR001, SR004 |
| CR006 | Connected assets widen the cyber and access-control attack surface, even if the company has no disclosed breach. | Medium | SR001, SR004 |
| CR007 | Technician and driver hiring remains a practical dependency for branch-level execution. | Medium | SR005, SR006 |
| CR008 | OWN-program participants and lenders are key dependencies because they supply fleet capital and liquidity. | High | SR002, SR004 |
| CR009 | Safety Champion and related programs show the company is actively trying to mitigate branch and site risk. | Medium | SR001 |
| CR010 | The monitored indicators that matter most are leverage, utilization, location ramp, and customer demand mix. | Medium | SR003, SR004, SR010 |
| CR011 | The most visible downside is a margin squeeze if demand slows while fleet and interest costs stay fixed. | Medium | SR003, SR002 |
| CR012 | The least visible but potentially most important risk is that software never becomes a truly standalone value driver. | Low | |
| CV001 | The company still has a public-scale revenue base and a large branch network, which supports a premium versus a small private rental operator. | Medium | SV001, SV005 |
| CV002 | Q1 2026 reporting and the post-IPO Fitch rating both support the case that execution and financing access improved into midyear. | Medium | SV011, SV012 |
| CV003 | The valuation story improves if the market believes T3 and the platform create recurring revenue and retention effects. | Medium | SV002, SV001 |
| CV004 | The current public evidence is enough to support a premium rental multiple, but not enough to justify a pure SaaS multiple. | Medium | SV001, SV002, SV005 |
| CV005 | The bear case is that the company still behaves like a capital-intensive rental business with leverage and cyclicality. | High | SV001, SV006, SV003 |
| CV006 | The software layer is not separately priced in public disclosures, so the market has to infer its value indirectly. | Low | |
| CV007 | The current public valuation appears below the IPO-debut peak, which leaves room for upside if execution remains strong. | Medium | SV004, SV001, SV012 |
| CV008 | The bull case depends on continued margin expansion, software attach, and disciplined capital management. | Medium | SV005, SV002 |
| CV009 | The most defensible recommendation is positive but measured: buy/track rather than a high-conviction growth multiple. | Medium | SV001, SV005, SV006 |
| CV010 | Current public evidence does not allow a clean bull/base/bear valuation with hard probabilities, only a directional scenario grid. | Low | |
| CV011 | The highest-value next disclosure would be a standalone T3 revenue or ARR line plus segment gross margins. | Low | |
| CV012 | If leverage rises or margins stall, the market can quickly re-rate the story as a cyclical rental business rather than a platform. | Medium | SV003, SV005 |
| ID | Publisher | Title | Quote |
|---|---|---|---|
| SO001 | EquipmentShare | EquipmentShare - Construction Equipment and Tool Rental | |
| SO002 | EquipmentShare | About Us - Equipment Rental and T3 Technology | EquipmentShare | |
| SO003 | EquipmentShare | EquipmentShare Announces Launch of Initial Public Offering | The initial public offering price is currently expected to be between $23.50 and $25.50 per share. |
| SO004 | EquipmentShare | EquipmentShare Prices Initial Public Offering | priced its initial public offering of 30,500,000 shares... at a price to the public of $24.50 per share. |
| SO005 | International Rental News | What we learned from EquipmentShare’s IPO filing | At the time of the filing, it had 373 rental locations in the US, 7,768 employees, and 325,000 pieces of equipment managed by its T3 technology platform. |
| SO006 | EquipmentShare | EquipmentShare Closes $3 Billion Senior Secured Asset-Based Revolving Credit Facility With Capital One Bank and Announces the Successful Closing Its Debut Bond Offering | increase its borrowing capacity from $2.1 billion to $3 billion through a senior secured asset-based revolving credit facility with Capital One |
| SO007 | Sacra | EquipmentShare revenue, valuation & funding | Sacra estimates that EquipmentShare generated $4.652B in trailing-12-month revenue through March 31, 2026. |
| SO008 | Yahoo Finance | EquipmentShare.com Inc. (EQPT) Company Profile & Facts - Yahoo Finance | EquipmentShare.com Inc. was founded in 2014 and is based in Columbia, Missouri. |
| SM001 | EquipmentShare | EquipmentShare - Construction Equipment and Tool Rental | |
| SM002 | EquipmentShare | About Us - Equipment Rental and T3 Technology | EquipmentShare | |
| SM003 | International Rental News | What we learned from EquipmentShare’s IPO filing | At the time of the filing, it had 373 rental locations in the US, 7,768 employees, and 325,000 pieces of equipment managed by its T3 technology platform. |
| SM004 | Sacra | EquipmentShare revenue, valuation & funding | Sacra estimates that EquipmentShare generated $4.652B in trailing-12-month revenue through March 31, 2026. |
| SM005 | Market Chameleon | EquipmentShare Lifts 2026 Outlook After Robust Q1: Rental Margins and Technology Power Growth | EquipmentShare raised its full-year 2026 guidance across multiple fronts: total revenue range is now $5,147–$5,575 million. |
| SM006 | Contrary Research | Report: EquipmentShare Business Breakdown & Founding Story | Contrary Research | T3 streams billions of data points daily and integrates hardware and software to give contractors actionable insights. |
| SM007 | EquipmentShare | EquipmentShare Prices Initial Public Offering | priced its initial public offering of 30,500,000 shares... at a price to the public of $24.50 per share. |
| SM008 | EquipmentShare | EquipmentShare Announces Launch of Initial Public Offering | The initial public offering price is currently expected to be between $23.50 and $25.50 per share. |
| SC001 | Tracxn | EquipmentShare - 2026 Company Profile, Team, Funding ... - Tracxn | EquipmentShare has 4,329 employees as of Aug 26. |
| SC002 | Bloomberg | EquipmentShare.com Inc - Company Profile and News | |
| SC003 | EquipmentShare | EquipmentShare Prices Initial Public Offering | priced its initial public offering of 30,500,000 shares... at a price to the public of $24.50 per share. |
| SC004 | Sacra | EquipmentShare revenue, valuation & funding | Sacra estimates that EquipmentShare generated $4.652B in trailing-12-month revenue through March 31, 2026. |
| SC005 | International Rental News | What we learned from EquipmentShare’s IPO filing | At the time of the filing, it had 373 rental locations in the US, 7,768 employees, and 325,000 pieces of equipment managed by its T3 technology platform. |
| SC006 | AlphaSpread | EquipmentShare Raises $747 Million in Nasdaq Debut, Valued Over $7 Billion | Shares of EquipmentShare began trading on the Nasdaq Global Select Market ... giving the company a market value of about $7.16 billion. |
| SC007 | EquipmentShare | EquipmentShare - Construction Equipment and Tool Rental | |
| SC008 | EquipmentShare | About Us - Equipment Rental and T3 Technology | EquipmentShare | |
| SI001 | EquipmentShare | EquipmentShare Reports Strong First Quarter Financial Results and Raises Full-Year 2026 Guidance | Total revenue of $989 million for the first quarter and $4.652 billion on a TTM basis. |
| SI002 | Market Chameleon | EquipmentShare Lifts 2026 Outlook After Robust Q1: Rental Margins and Technology Power Growth | EquipmentShare raised its full-year 2026 guidance across multiple fronts: total revenue range is now $5,147–$5,575 million. |
| SI003 | Market Chameleon | EquipmentShare Lifts 2026 Outlook After Robust Q1: Rental Margins and Technology Power Growth | EquipmentShare raised its full-year 2026 guidance across multiple fronts: total revenue range is now $5,147–$5,575 million. |
| SI004 | Sacra | EquipmentShare revenue, valuation & funding | Sacra estimates that EquipmentShare generated $4.652B in trailing-12-month revenue through March 31, 2026. |
| SI005 | International Rental News | What we learned from EquipmentShare’s IPO filing | At the time of the filing, it had 373 rental locations in the US, 7,768 employees, and 325,000 pieces of equipment managed by its T3 technology platform. |
| SI006 | EquipmentShare | EquipmentShare Closes $3 Billion Senior Secured Asset-Based Revolving Credit Facility With Capital One Bank and Announces the Successful Closing Its Debut Bond Offering | increase its borrowing capacity from $2.1 billion to $3 billion through a senior secured asset-based revolving credit facility with Capital One |
| SI007 | PM Insights | EquipmentShare Files for IPO as Valuation Jumps 131% From Series E | EquipmentShare files for IPO as valuation jumps 131% from Series E. |
| SI008 | AlphaSpread | EquipmentShare Raises $747 Million in Nasdaq Debut, Valued Over $7 Billion | Shares of EquipmentShare began trading on the Nasdaq Global Select Market ... giving the company a market value of about $7.16 billion. |
| SI009 | Forge Global | EquipmentShare IPO Timeline and Financing Details | EquipmentShare has raised a total of $2.9 billion in funding over 13 rounds. |
| SE001 | EquipmentShare | EquipmentShare - Construction Equipment and Tool Rental | |
| SE002 | EquipmentShare | About Us - Equipment Rental and T3 Technology | EquipmentShare | |
| SE003 | EquipmentShare | EquipmentShare Style Guide | EquipmentShare Style Guide |
| SE004 | Retool | How EquipmentShare is revolutionizing the construction industry | Retool Blog | The team’s dependency on spreadsheets also made it difficult for their data management processes to scale quickly enough to meet the business’ growing data demands. |
| SE005 | IronPros | EquipmentShare T3 Takes a Transformational Approach to Construction Equipment and Operations | EquipmentShare’s T3 platform gives construction teams real-time visibility into fleet, assets, and people. |
| SE006 | EquipmentShare | EquipmentShare’s Safety Champion Program Advances Mission of Protecting Employees | EquipmentShare launched its Safety Champion Program in January 2026. |
| SE007 | Contrary Research | Report: EquipmentShare Business Breakdown & Founding Story | Contrary Research | T3 streams billions of data points daily and integrates hardware and software to give contractors actionable insights. |
| SE008 | Lensa | Telematics Installer job in Trotwood at EquipmentShare | Telematics Installer job in Trotwood at EquipmentShare |
| SU001 | International Rental News | What we learned from EquipmentShare’s IPO filing | At the time of the filing, it had 373 rental locations in the US, 7,768 employees, and 325,000 pieces of equipment managed by its T3 technology platform. |
| SU002 | Retool | How EquipmentShare is revolutionizing the construction industry | Retool Blog | The team’s dependency on spreadsheets also made it difficult for their data management processes to scale quickly enough to meet the business’ growing data demands. |
| SU003 | EquipmentShare | EquipmentShare’s Safety Champion Program Advances Mission of Protecting Employees | EquipmentShare launched its Safety Champion Program in January 2026. |
| SU004 | The Silicon Review | In Conversation with EquipmentShare Leadership: ‘Our Sole Mission is to Make Construction More Productive and Efficient’ | We are an incredibly agile and nimble company made up of creative problem solvers. |
| SU005 | Contrary Research | Report: EquipmentShare Business Breakdown & Founding Story | Contrary Research | T3 streams billions of data points daily and integrates hardware and software to give contractors actionable insights. |
| SU006 | EquipmentShare | EquipmentShare - Construction Equipment and Tool Rental | |
| SU007 | EquipmentShare | About Us - Equipment Rental and T3 Technology | EquipmentShare | |
| SU008 | EquipmentShare | EquipmentShare Prices Initial Public Offering | priced its initial public offering of 30,500,000 shares... at a price to the public of $24.50 per share. |
| SU009 | Lensa | Telematics Installer job in Trotwood at EquipmentShare | Telematics Installer job in Trotwood at EquipmentShare |
| SU010 | Dice | IT Systems Administrator - EquipmentShare - Columbia, MO, US | IT Systems Administrator - EquipmentShare - Columbia, MO, US |
| SR001 | EquipmentShare | EquipmentShare’s Safety Champion Program Advances Mission of Protecting Employees | EquipmentShare launched its Safety Champion Program in January 2026. |
| SR002 | EquipmentShare | EquipmentShare Closes $3 Billion Senior Secured Asset-Based Revolving Credit Facility With Capital One Bank and Announces the Successful Closing Its Debut Bond Offering | increase its borrowing capacity from $2.1 billion to $3 billion through a senior secured asset-based revolving credit facility with Capital One |
| SR003 | Sacra | EquipmentShare revenue, valuation & funding | Sacra estimates that EquipmentShare generated $4.652B in trailing-12-month revenue through March 31, 2026. |
| SR004 | International Rental News | What we learned from EquipmentShare’s IPO filing | At the time of the filing, it had 373 rental locations in the US, 7,768 employees, and 325,000 pieces of equipment managed by its T3 technology platform. |
| SR005 | Lensa | Telematics Installer job in Trotwood at EquipmentShare | Telematics Installer job in Trotwood at EquipmentShare |
| SR006 | Dice | IT Systems Administrator - EquipmentShare - Columbia, MO, US | IT Systems Administrator - EquipmentShare - Columbia, MO, US |
| SR007 | startup.jobs | Credit Card Specialist at EquipmentShare | Credit Card Specialist at EquipmentShare |
| SR009 | EquipmentShare | News Releases | EquipmentShare news releases and announcements |
| SR010 | EquipmentShare | EquipmentShare Reports Strong First Quarter Financial Results and Raises Full-Year 2026 Guidance | Total revenue of $989 million for the first quarter and total available liquidity of $1.6 billion. |
| SR008 | Contrary Research | Report: EquipmentShare Business Breakdown & Founding Story | Contrary Research | T3 streams billions of data points daily and integrates hardware and software to give contractors actionable insights. |
| SV001 | Sacra | EquipmentShare revenue, valuation & funding | Sacra estimates that EquipmentShare generated $4.652B in trailing-12-month revenue through March 31, 2026. |
| SV002 | Forge Global | EquipmentShare IPO Timeline and Financing Details | EquipmentShare has raised a total of $2.9 billion in funding over 13 rounds. |
| SV003 | PM Insights | EquipmentShare Files for IPO as Valuation Jumps 131% From Series E | EquipmentShare files for IPO as valuation jumps 131% from Series E. |
| SV004 | AlphaSpread | EquipmentShare Raises $747 Million in Nasdaq Debut, Valued Over $7 Billion | Shares of EquipmentShare began trading on the Nasdaq Global Select Market ... giving the company a market value of about $7.16 billion. |
| SV005 | Market Chameleon | EquipmentShare Lifts 2026 Outlook After Robust Q1: Rental Margins and Technology Power Growth | EquipmentShare raised its full-year 2026 guidance across multiple fronts: total revenue range is now $5,147–$5,575 million. |
| SV006 | EquipmentShare | EquipmentShare Prices Initial Public Offering | priced its initial public offering of 30,500,000 shares... at a price to the public of $24.50 per share. |
| SV007 | Tracxn | EquipmentShare - 2026 Company Profile, Team, Funding ... - Tracxn | EquipmentShare has 4,329 employees as of Aug 26. |
| SV008 | Bloomberg | EquipmentShare.com Inc - Company Profile and News | |
| SV011 | MarketScreener | EquipmentShare Reports Strong First Quarter Financial Results and Raises Full-Year 2026 Guidance | EquipmentShare Reports Strong First Quarter Financial Results and Raises Full-Year 2026 Guidance. |
| SV012 | Nasdaq | EquipmentShare Assigned First-Time 'BB-' Issuer Default Rating by Fitch; Senior Secured Second Lien Notes Rated 'BB'; Outlook Stable | EquipmentShare assigned first-time 'BB-' issuer default rating by Fitch; outlook stable. |