Nottelabs

What do they actually do

Nottelabs (Notte) is a developer platform that runs autonomous browser agents to automate tasks on any website. Developers use a cloud console plus Python/JS SDKs to create agents, provide sessions and secrets, pick a reasoning model, and run tasks; the core runtime is available in an open-source repo (site/docs, getting started, GitHub).

In practice, these agents log in, navigate, click, scrape, and return structured outputs while relying on model-based reasoning to be more resilient than brittle DOM-only scripts. Notte provides the cloud infrastructure to execute, scale, and monitor these agents so teams don’t have to run browser fleets themselves (use-case writeup, site).

For enterprise needs, Notte includes a vault for secure secret storage and a Payments feature that issues virtual cards so agents can complete purchases without exposing real corporate cards (docs, Payments).

Who are their target customer(s)

• E‑commerce operations teams: Need to monitor prices and sometimes place orders at scale, but scraping and click scripts break when sites change. They also need a safe way to let automations pay without exposing real cards (use‑case, Payments).
• SaaS product and engineering teams: Automating cross‑product web workflows (onboarding, syncs, integrations) consumes time due to brittle scripts that fail on UI changes; they want automations that keep working with less maintenance (docs, use‑case).
• Competitive‑intelligence and data collection teams: Collecting structured data across many sites is hard to scale reliably; scrapers often break on layout changes and outputs vary run‑to‑run (use‑case).
• QA and reliability teams: End‑to‑end web flow validation with DOM‑selector tests leads to high maintenance and false positives/negatives; they want higher‑level, behavior‑aware checks (use‑case).
• Enterprise security, finance, and ops teams: Need to allow automated agents to access accounts or transact without exposing credentials or funds; require secure secret storage and controlled virtual cards to operate safely in production (docs, Payments).

How would they acquire their first 10, 50, and 100 customers

• First 10: Run high‑touch pilots with developers already engaging on Notte’s GitHub and the Playwright‑replacement blog, offering free credits and an engineer‑assisted proof‑of‑concept with a clear reliability SLA; leverage YC alumni intros and existing signups for fast procurement (GitHub, blog, YC).
• First 50: Publish ready‑to‑run playbooks for ecommerce orders, CI/QA checks, and competitive scraping; seed examples in docs/GitHub and targeted developer channels. Offer standardized 30–90 day pilots (including vault and virtual‑card setup) that convert to paid seats if runs are stable (docs, Payments).
• First 100: Use early customers as public case studies and references; add light outbound (SDRs) to ecommerce ops and SaaS teams with metric‑tied pilots. Form two channel partnerships (automation agency, fintech/payment partner) and ship procurement/security collateral on vaults and virtual cards to speed enterprise approvals (Payments, docs).

What is the rough total addressable market

Top-down context:

Notte competes across three mature budgets: web automation/testing (teams building on Playwright/Selenium), hosted scraping/automation platforms (e.g., Apify, Zyte), and enterprise RPA suites (e.g., UiPath) — each already adopted by thousands of organizations (Playwright, Apify, Zyte, UiPath).

Bottom-up calculation:

If 6,000 mid‑market and enterprise teams adopt a managed browser‑agent platform for critical web workflows at an average $20k annual contract, the initial serviceable TAM is roughly $120M annually. Expansion into additional teams and workloads per company would increase this over time.

Assumptions:

• Focus on North America/EU mid‑market and enterprise teams already running or planning browser automation (ecommerce ops, SaaS product/QA, data collection).
• Average deal size reflects platform + usage for a few production agents with enterprise features (vaults, payments).
• Count excludes long‑tail hobbyists and includes only teams with ongoing, production web workflows.

Who are some of their notable competitors

• Playwright (Microsoft): Open‑source browser automation library many teams use to write and run scripts in their own CI/infra; the low‑level alternative when you want full control and don’t need a managed agent platform.
• Apify: Cloud platform for running hosted browser jobs (“actors”) for scraping and automation, with scaling and storage built in; competes on ready‑made hosted execution.
• UiPath: Enterprise RPA suite for web/desktop automation with orchestration and governance; chosen when centralized control and audits across many business processes are required.
• Zyte (formerly Scrapinghub): Web Scraping API with headless rendering, anti‑ban, and AI extraction; a fit when the need is reliable, large‑scale data collection rather than model‑driven agent behavior.
• Browserless: Hosted browsers‑as‑a‑service for Puppeteer/Playwright with session persistence and anti‑bot tooling; used when teams just need managed headless browsers, not LLM agents or payments.