Overview
Smartcuts was a Chrome extension founded in 2019 by Brian Noguchi that recorded clicks and keystrokes and replayed them as no-code automations on similar web pages — "like Excel macros for any website." The company went through Y Combinator's Winter 2021 batch, raised a $125K seed round, and attracted backing from SignalFire, HOF Capital, and founders of Firebase, FitBit, HubSpot, Lyft, and Segment. It was headquartered in New York City with a distributed team across Shanghai and the UK.[1][2][4]
Smartcuts failed to achieve escape velocity because it built a browser-extension macro recorder in 2021 — a category that was simultaneously too technically fragile (DOM-dependent, with no reliable element location) and too easily commoditized by both incumbent RPA tools and the platform-level automation features that Chrome and web apps were already absorbing. The company never left private beta, never achieved meaningful distribution, and by 2026 was a zombie startup: still hiring for "Employee #4" roles with roughly 1.3K monthly website visits.[12][14]
The company is technically still active as of 2026, but every signal points to stagnation rather than growth. There has been no public launch, no Chrome Web Store user counts, no press coverage, and no official shutdown announcement — the most likely failure mode is not a dramatic collapse but a slow fade.
Image 1 / 2
Founding Story
Brian Noguchi is a serial founder with a pedigree that made Smartcuts a credible seed bet. Before Smartcuts, he co-founded Lever (YC S12), the applicant tracking system that went on to raise over $123M and was acquired by Employ in 2022. He served as Entrepreneur in Residence at SignalFire from 2015-2016, founded Lab79 in 2016, and studied Mathematical and Computational Sciences at Stanford (2003-2007), where he was President of BASES, the Business Association of Stanford Entrepreneurial Students.[9][10] His earlier career included a stint as CEO & Co-founder of Trendessence, Inc. (2007-2009) and a summer as a Business Analyst at McKinsey & Company (2006).[20]
The co-founder, Scott Wang, served as Lead Product Engineer, but there is no public information on how the two met or why they chose this specific problem.[11] The team was tiny — three people at YC, growing to roughly six by 2025.[6][13]
The founding insight appears to have been that browser automation was stuck in two camps: developer tools like Selenium that required code, and enterprise RPA platforms that were expensive and heavy. Noguchi's vision was a middle path — a consumer-grade tool that anyone could use. The product vision was ambitious: a "universe of discoverable and easy-to-use automations, created and maintained by a community of passionate users," a crowdsourced engine that maps workflows within and between web apps.[15]
Hiring copy from the company described the mission in sweeping terms: "a new category of productivity software that brings automation to the masses and changes how people interact with the Internet."[21] That framing — a new category, not a better tool — would prove to be part of the problem. The company was selling a vision of what browser automation could become, not a product that solved a specific pain for a specific user.
Timeline
- 2019: Smartcuts founded by Brian Noguchi.[1]
- 2021: Smartcuts participated in Y Combinator's Winter 2021 batch, with Brad Flora as the primary YC partner, and raised a $125K seed round from YC.[2][3]
- 2022-01-13: Smartcuts listed among YC companies that started as Chrome extensions, alongside Text Blaze, RescueTime, Requestly, Motion, and Compose.ai.[18]
- 2025-04: GetLatka estimated Smartcuts' revenue at roughly $1M ARR with 6 employees (low-confidence third-party estimate).[13]
- 2026: Smartcuts still hiring for Software Engineer & Employee #4 and Lead Designer & Employee #4.[12]
- 2026-07: Smartcuts' estimated monthly website traffic was approximately 1.3K visits.[14]
What They Built
Smartcuts was a Chrome extension that recorded a user's clicks and keystrokes and replayed them as no-code automations on similar web pages. The YC description framed it as "like Excel macros for any website."[2] The core loop was simple: a user performs a repetitive task once, records it, and then replays it on other pages that share the same structure.
The technical stack was modern but niche: ReasonML/ReScript, Next.js, Vercel, GraphQL, and the serverless database Fauna.[8] The choice of ReasonML/ReScript — a typed functional language that compiles to JavaScript — signaled a team that prioritized type safety and correctness, but it also meant a smaller talent pool and slower iteration for a category where speed-to-market mattered.
The engineering challenges were substantial. The company's own hiring materials listed three core problems: designing a product that doesn't expose engineering concepts to users, building an algorithm to reliably locate elements on a page without requiring CSS selectors, and leveraging AI to automatically detect and extract structured records from web pages.[16]
The element-location problem was the crux. CSS selectors are brittle — a single class name change breaks a macro. Smartcuts needed a way to identify elements that survived page updates, which required either visual recognition, semantic understanding of the page structure, or some combination. This is a genuinely hard computer science problem, and there is no public evidence of how well the solution worked in practice.
The product vision extended beyond a simple recorder. Smartcuts wanted to become a "universe of discoverable and easy-to-use automations, created and maintained by a community of passionate users" — a crowdsourced marketplace where users could share and discover workflows.[15] This marketplace vision required network effects: a critical mass of automation creators, a critical mass of consumers, and a discovery mechanism that matched them. None of that materialized.
The company was in private beta with paying customers, from individual consumers to "well-known, publicly traded technology companies," but no names or numbers were ever disclosed.[7] The product never had a public launch, never appeared on Product Hunt, and never generated press coverage.
Market Position
Target Customers
Smartcuts' target customer was ambiguous. The product was positioned for "the masses" — anyone who does repetitive work in a browser. But the company also claimed paying customers among "well-known, publicly traded technology companies," suggesting enterprise interest.[7] This straddling — consumer tool and enterprise product simultaneously — is a classic seed-stage trap. The use cases, sales motions, and pricing for a consumer Chrome extension versus an enterprise RPA tool are entirely different.
Market Size
The browser automation market was real but fragmented. The broader RPA market was projected to grow significantly through the 2020s, but the consumer/prosumer browser automation niche was much smaller. The category included Axiom.ai, Automa, UI.Vision RPA, and iMacros — all of which had existing user bases and free tiers.[17] Smartcuts was also listed among YC companies that started as Chrome extensions, a category that included Text Blaze, RescueTime, Requestly, Motion, and Compose.ai — but none of those were direct competitors, which illustrates how broad and ill-defined the category was.[18]
Competition
The competitive landscape was structurally hostile to a new entrant. The incumbents — Axiom.ai, Automa, UI.Vision, iMacros — had years of head start, established user bases, and free tiers that made switching costs effectively zero. They competed on the same core mechanic (record and replay) but with more mature element-location algorithms and broader site compatibility.
The deeper structural problem was that browser automation was being absorbed from two directions simultaneously. At the platform level, Chrome was adding native automation features, and web apps were becoming more standardized, reducing the need for custom macros. At the enterprise level, RPA incumbents like UiPath and Automation Anywhere were adding browser automation to their platforms, with the distribution and sales teams to reach enterprise buyers.
Smartcuts' positioning — "Excel macros for any website" — was clever but misleading. Excel macros work because the document is stable; the cell structure of a spreadsheet doesn't change between uses. Web pages are not stable documents. They are rendered from HTML that changes with every deployment, every A/B test, every personalization engine. A macro that works on a page today breaks tomorrow when a developer renames a CSS class or a product manager moves a button. This is not a solvable engineering problem; it is a fundamental property of the medium.
The crowdsourced marketplace vision was the only potential moat, but it required network effects that never materialized. No community, no discoverability, no critical mass of automations. The marketplace was a vision, not a product.
Business Model
Smartcuts never publicly disclosed its revenue model. The company was in private beta with paying customers, which implies a subscription model, but pricing tiers, if any, were never made public.[7]
GetLatka estimated ~$1M ARR with 6 employees as of April 2025, but this is a low-confidence third-party estimate with no disclosed methodology.[13] If the estimate is even directionally correct, it implies roughly $167K ARR per employee — a reasonable figure for a seed-stage SaaS company, but one that would not support the "new category of productivity software" ambition.
The absence of revenue data is itself a signal. A company with genuine traction and a credible revenue model typically shares those numbers in hiring materials and investor updates. Smartcuts' hiring copy emphasized the vision — "a new category of productivity software" — rather than metrics like customer count, retention, or revenue growth.[21] For a company five-plus years post-founding, that is a telling omission.
The company raised $125K from YC in 2021, plus backing from SignalFire, HOF Capital, and notable angel investors.[3][4] With a team of 3-6 people in New York City, annual burn was likely in the $500K-$1M range — meaning the company would have needed multiple follow-on rounds to survive to 2026. The fact that it is still operating suggests either additional funding that was never disclosed or a founder-funded operation running on minimal burn.
Traction
Traction data is thin and mostly negative. The company was in private beta with paying customers, including "well-known, publicly traded technology companies," but no names or numbers were ever disclosed.[7] GetLatka's ~$1M ARR estimate is low-confidence and unverifiable.[13]
The most telling metric is website traffic: approximately 1.3K monthly visits as of July 2026.[14] For a company that had been operating for seven years, had gone through YC, and was still hiring, this is a catastrophic number. It suggests almost no organic demand, no marketing reach, and no word-of-mouth growth. A single well-executed Product Hunt launch would typically generate more traffic than this.
The company never appeared on the Chrome Web Store with meaningful user counts, never generated press coverage, and never had a public launch. The hiring posts for "Employee #4" roles in 2026 — five years after YC — indicate a company that was alive but not scaling.[12]
Post-Mortem
The core problem: "Automation for the masses" is a category, not a product
Smartcuts' fundamental error was building a general-purpose tool for an ill-defined user. "Automation for any website" sounds compelling in a pitch deck, but it is not a product. It is a category. The company's own hiring copy — "a new category of productivity software that brings automation to the masses" — reveals the ambition but also the absence of a specific wedge.[21]
Contrast this with the companies that succeeded in adjacent spaces. Zapier succeeded by focusing on a specific integration pattern (app-to-app workflows) and building a massive library of connectors. UiPath succeeded by targeting a specific buyer (enterprise operations teams) with a specific pain (legacy system automation). Axiom.ai succeeded by focusing on a specific use case (web scraping and data extraction) with a clear ROI.
Smartcuts tried to be everything to everyone. The result was a product that was too generic to sell, too technically fragile to trust, and too undifferentiated to win.
The technical fragility: web pages are not stable documents
The "Excel macros for any website" analogy was the product's fatal flaw. Excel macros work because the spreadsheet is a stable document — the cell structure doesn't change between uses. Web pages are rendered from HTML that changes with every deployment, every A/B test, every personalization engine.
Smartcuts' engineering team knew this. Their stated challenge was "building an algorithm to reliably locate elements on a page without requiring CSS selectors."[16] This is a genuinely hard problem — it requires either visual recognition, semantic understanding of page structure, or a combination of both. There is no public evidence of how well the solution worked, but the company's failure to launch publicly suggests it never reached a level of reliability that the team was comfortable shipping.
The deeper issue is that this problem is not solvable to a degree that makes the product trustworthy. Even a 95% success rate means one in twenty automations fails — and for a user automating repetitive work, a failure that requires manual intervention is often worse than doing the task manually. The cost of a broken automation is not just the time lost; it is the trust lost. Users who experience a broken macro once are unlikely to try again.
The commoditization trap: no moat against incumbents or platforms
Smartcuts faced competition from two directions simultaneously. At the low end, free and freemium tools like Automa and UI.Vision offered the same record-and-replay mechanic with years of maturity. At the high end, enterprise RPA platforms were adding browser automation to their feature sets, with the distribution and sales teams to reach enterprise buyers.[17]
The crowdsourced marketplace vision was the only potential moat — a network effect where more users create more automations, which attract more users. But network effects require a critical mass of supply and demand, and Smartcuts never showed evidence of either. No community, no discoverability, no critical mass of automations. The marketplace was a vision, not a product.
The structural problem is that browser automation is a feature, not a business. Chrome itself was adding automation features. Web apps were becoming more standardized. The need for custom browser macros was shrinking, not growing. Smartcuts was building a product for a problem that the platform was already solving.
The zombie state: alive but not scaling
The most striking aspect of Smartcuts' story is that it never died — it just stopped growing. As of 2026, the company was still hiring for "Employee #4" roles, seven years after founding and five years after YC.[12] Website traffic was ~1.3K monthly visits.[14]
This is the classic zombie startup state: a company that has enough runway or revenue to survive but not enough traction to grow. The founders are likely drawing modest salaries, the product serves a small base of paying customers, and the company continues to exist because shutting it down would be an admission of failure.
The counter-narrative is worth considering: perhaps Smartcuts is a lifestyle business that generates enough revenue to sustain its founders without needing to scale. GetLatka's ~$1M ARR estimate, if accurate, would support a small team comfortably.[13] But this framing is generous. A company that raised from YC, SignalFire, and notable angels, and that describes itself as building "a new category of productivity software," was not founded to be a lifestyle business. The investors who backed it expected a return, and a $1M ARR company with no growth trajectory does not return a venture fund.
The structural lesson: distribution is the moat
Smartcuts' story is a case study in the difference between building a product and building a business. The product was technically ambitious — a no-code automation tool that could handle any website without CSS selectors. But the company never solved the distribution problem. No public launch, no Chrome Web Store presence, no press coverage, no community.
A Chrome extension is a distribution channel, not a business. Without a clear go-to-market motion, even a well-funded seed startup cannot escape the Chrome Web Store's long tail. The companies that succeeded in this space — Text Blaze, RescueTime, Motion — all found a specific wedge and a specific user to serve. Smartcuts tried to serve everyone and served no one.
Key Lessons
-
A browser extension is a distribution channel, not a business. Smartcuts built a technically ambitious product but never solved the go-to-market problem. The company had no public launch, no Chrome Web Store presence, and ~1.3K monthly website visits after seven years. A product without distribution is a demo, not a company.
-
"Automation for the masses" is a category, not a product. Smartcuts' positioning was too broad to sell. The company described itself as building "a new category of productivity software," but categories are not built by declaration — they are built by serving a specific user with a specific pain. Zapier succeeded by focusing on app-to-app workflows; UiPath succeeded by targeting enterprise operations teams. Smartcuts tried to serve everyone and served no one.
-
The "Excel macros for the web" analogy is compelling but misleading. Excel macros work because the spreadsheet is a stable document. Web pages are rendered from HTML that changes with every deployment. Smartcuts' core technical challenge — reliably locating elements without CSS selectors — was not a solvable engineering problem but a fundamental property of the medium. A 95% success rate is not enough for a tool whose value depends on trust.
-
Crowdsourced marketplaces require a critical mass of supply and demand. Smartcuts' vision of a "universe of discoverable and easy-to-use automations" required network effects that never materialized. No community, no discoverability, no critical mass of automations. The marketplace was a vision, not a product — and a vision without a wedge is not a business.
-
The zombie state is a failure mode. Smartcuts never died; it just stopped growing. Seven years after founding, the company was still hiring for "Employee #4" roles with negligible traffic. For a venture-backed company, stagnation is a form of failure — one that is harder to diagnose and harder to fix than a dramatic shutdown.
Sources
- Y Combinator — Smartcuts
- Y Combinator — Smartcuts (product description)
- Extruct.ai — Smartcuts profile
- Work at a Startup — Smartcuts
- Extruct.ai — Smartcuts investors
- Y Combinator — Smartcuts team
- Work at a Startup — Smartcuts (traction)
- Work at a Startup — Smartcuts (tech stack)
- FundraisingFox — Brian Noguchi
- FundraisingFox — Brian Noguchi (Stanford)
- Jobs With Startups — Smartcuts
- Y Combinator — Smartcuts jobs
- GetLatka — Smartcuts revenue estimate
- Jobs With Startups — Smartcuts traffic
- Work at a Startup — Smartcuts (product vision)
- Work at a Startup — Smartcuts (engineering challenges)
- Extruct.ai — Smartcuts competitors
- Requestly Medium — YC companies that started as Chrome extensions
- Crunchbase — Smartcuts
- FundraisingFox — Brian Noguchi (early career)
- Y Combinator — Smartcuts Lead Designer job posting