UpKeep

Overview

UpKeep turned maintenance work orders from a desk-bound record into a technician's mobile workflow. Ryan Chan had watched plant technicians write field notes on paper and later re-enter them into software. He built the reverse: capture the request, photo, labor, parts, and completion record where the work happened.^[1]

The company remains operating. Its May 2026 transaction brought strategic growth capital from software investor Accel-KKR. The parties did not describe a shutdown or full acquisition and did not publish the stake, valuation, or price. YC nevertheless classifies UpKeep as acquired.^[2][3] Ryan stayed CEO, and the announcement said UpKeep served over 4,000 companies and 400,000 users in 60 countries. This is a successful recapitalization story with an undisclosed ownership structure.

UpKeep's technician-first design created a bottom-up entry into a category usually sold to managers. That advantage produced real scale: $50 million of disclosed venture funding, 10 million work orders by 2020, and a platform that now covers maintenance, safety, training, analytics, sensors, and AI.^[4] The same expansion creates the central tension. A simple mobile wedge won adoption; platform breadth and enterprise controls are now required to defend the account.

Founding Story

Chan was a process-development engineer at a membrane manufacturing plant. One-to-three-percent process improvements could be worth hundreds of thousands of dollars, yet the maintenance system still depended on technicians writing notes by hand and returning to a desktop.^[1] He took evening iOS classes at community college, worked on the app before dawn while employed, and later left engineering for an iOS developer role.

The origin dates vary because Chan built before he formed the company. In his January 2017 launch thread, he said he started UpKeep in 2015 and had worked on it for about two years. YC's current profile lists 2016 as the founded year, which this report uses for company metadata.^[5][3]

The first version came from his mother's garage. A welder found it in the App Store, used it at one facility, and helped it spread to others. That discovery shaped the go-to-market model. Chan could not outspend established maintenance vendors on manager-focused search ads, so he marketed the mobile app to technicians and let usage travel upward.^[5]

The pricing followed the workflow. Requesters could be free; UpKeep charged technicians and administrators, initially from about $25 per paid user per month. The person reporting a broken air conditioner did not need a licensed seat. The technician and manager who resolved it did.^[5]

Timeline

• 2015–2016: Chan builds the first mobile app while working, then formalizes UpKeep; the sources differ on the start date.^[3][5]
• January 2017: UpKeep launches from YC's Winter 2017 batch with 240 paying customers.^[1]
• June 2017: The company raises a $2.7 million seed round and reports 40,000 users, including Stericycle and Unilever.^[6]
• March 2018: A $10 million Series A led by Emergence brings total funding above $12.7 million; UpKeep reports 70,000 users and one million work orders.^[7]
• December 2019: UpKeep launches its own real-time asset sensors, its first product line beyond work and asset management.^[8]
• May 2020: Insight leads a $36 million Series B. UpKeep reports 2,000 customers and 10 million work orders.^[4]
• March 2025: UpKeep introduces early access to UpKeep Intelligence, bringing AI assistance into maintenance data and workflows.^[9]
• February–March 2026: Studio adds an AI app builder and marketplace; UpKeep Learn turns procedures and work history into training and compliance records.^[10][11]
• May 2026: Accel-KKR makes an undisclosed strategic growth investment. Chan remains CEO.^[2]

What They Built

The first product coordinated three actors: a requester who saw a problem, a manager who prioritized it, and a technician who repaired it. A requester could attach a photo. The manager assigned the work. The technician recorded time, parts, and completion on a phone. The shared record shortened the interval between failure and repair and preserved a history for the asset.^[1]