Where these 33 reports land
Build it2
Scope it19
Keep it12
Category report
Automation
33 products ranked by how much of their useful core an AI coding agent can reproduce: 2 strong builds, 19 scoped builds, and 12 weak replacements.
How the score breaks down here
- Interface
- 51
- Core workflow
- 45
- Data access
- 42
- Operations
- 22
- Trust & safety
- 44
44/100 average buildability
Why people keep paying here
- integrations31 of 33 reports
Connectors, OAuth flows, and vendor API changes require constant upkeep.
- scale infra27 of 33 reports
Reliability at the vendor's scale is an operations problem, not a prompt.
- execution polish7 of 33 reports
The last 20 percent is sync, migration fidelity, speed, and edge cases.
The typical achievable core in this category: automate a small number of known workflows with logs, retries, and manual recovery.
Build it
IFTTT
For a few personal applets, a script or simple webhook worker is enough; the full consumer integration catalog and smart-home breadth are what you lose.
Build it
n8n Cloud
Because n8n itself is open source, the core cloud subscription can be replaced by self-hosting if you can own hosting, updates, and backups.
Scope it
Zapier
A few personal automations are easy; Zapier's moat is the 9,000+ app integration catalog, auth handling, retries, task history, UI, and reliability.
Scope it
Make
A handful of workflows can be coded quickly, but Make's paid value is the visual builder, app modules, scheduling, observability, and maintenance.
Scope it
Import.io
The visible enterprise web data loop is buildable, but a credible replacement needs more than the first screen. Import.io earns its keep through connectors, auth, reliability, so expect a substantial build and a narrower personal scope.
Scope it
ParseHub
The visible visual web scraping loop is buildable, but a credible replacement needs more than the first screen. ParseHub earns its keep through connectors, auth, reliability, so expect a substantial build and a narrower personal scope.
Scope it
Sumora
The visible surface, a prompt box that produces a researched, personalized outreach message, is a one-sitting build. What takes real work is everything that keeps an agent from quietly going insane on step seven: persistent memory about your business and each contact, retries, browser sessions that survive logins and captchas, cost ceilings, and a human approval gate before anything is actually sent. For one person automating their own pipeline, you can get to genuinely useful in a focused implementation because you are allowed to be the approval step and the error handler. The gap widens fast the moment you want it unattended, multi-user, or connected to a real CRM and mailbox over OAuth. The failure mode also matters: a broken personal script wastes your evening, a broken agent emails the wrong prospect from your domain.
Scope it
Relay.app
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Relay.app, build a small human-in-the-loop workflow across two approved services. The hard boundary is polished approvals, ai steps, integrations, shared workflows, and managed execution, plus connector breadth and execution reliability.
Scope it
Activepieces Cloud
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Activepieces Cloud, use a managed open-source workflow runner instead of operating queues and upgrades. The hard boundary is managed hosting, connector updates, execution capacity, support, and reliability, plus connector breadth and execution reliability.
Scope it
Apify
The visible web scraping platform loop is buildable, but a credible replacement needs more than the first screen. Apify earns its keep through connectors, auth, reliability, so expect a substantial build and a narrower personal scope.
Scope it
Browse AI
The visible web data extraction loop is buildable, but a credible replacement needs more than the first screen. Browse AI earns its keep through connectors, auth, reliability, so expect a substantial build and a narrower personal scope.
Scope it
Hexomatic
The visible web scraping + automation loop is buildable, but a credible replacement needs more than the first screen. Hexomatic earns its keep through connectors, auth, reliability, so expect a substantial build and a narrower personal scope.
Scope it
Lindy
The visible AI assistants + automation loop is buildable, but a credible replacement needs more than the first screen. Lindy earns its keep through connectors, auth, reliability, so expect a substantial build and a narrower personal scope.
Scope it
Octoparse
The visible visual web scraping loop is buildable, but a credible replacement needs more than the first screen. Octoparse earns its keep through connectors, auth, reliability, so expect a substantial build and a narrower personal scope.
Scope it
Parabola
The visible visual data automation loop is buildable, but a credible replacement needs more than the first screen. Parabola earns its keep through connectors, auth, reliability, so expect a substantial build and a narrower personal scope.
Scope it
Relevance AI
The visible AI workforce platform loop is buildable, but a credible replacement needs more than the first screen. Relevance AI earns its keep through connectors, auth, reliability, so expect a substantial build and a narrower personal scope.
Scope it
Robomotion
The visible robotic process automation loop is buildable, but a credible replacement needs more than the first screen. Robomotion earns its keep through connectors, auth, reliability, so expect a substantial build and a narrower personal scope.
Scope it
Orshot
The render itself is not the moat. Headless Chromium plus a Handlebars template gets you a PNG or a PDF from JSON with a focused implementation, and for one team rendering its own OG images that really is the whole job. What does not fall out of a focused implementation is everything around the render: a visual editor non engineers can use, one design that re solves cleanly into a story, a square, and an OG card, workflows that fire on a schedule or a webhook against Sheets and Airtable, publishing into 15 plus social platforms, and a render farm that stays warm and predictable under burst. Build it if you own the templates and the volume is small. Keep paying if the people making the creatives do not write HTML.
Scope it
Saply
A capable coding agent can build the personal core: extract a clean, text-based CV, structure or tailor it with an LLM, and render a branded DOCX. It will work on tidy CVs and silently drop data on the rest. Saply's value is extraction accuracy across thousands of real-world CV layouts, tuned so no field goes missing on a client-facing document, plus the integrations that keep recruiters inside Word, their email, and their ATS.
Scope it
Aldena
One room's worth of this is a focused implementation now that the agent loop ships as an SDK: five role-scoped agents in a Docker sandbox, a manager that hands work down, a prompt before anything destructive, a pull request at the end. What does not fall out of that weekend is the rest of it. A server per project that somebody else patches and meters, ten OAuth integrations that stay authorized, memory that survives the run, and a screen where the person paying for the work can watch it and approve it. Build the room. The building around the room is the subscription.
Scope it
LeaseLineage
A solo broker can build the CRM, CSV prospecting, draft sequences, and pipeline in a contained effort, but reliable contact data, Gmail and Outlook sync, deliverability, compliance operations, and brokerage collaboration are ongoing products.
Keep it
Workato
Do not mistake the interface for the product. Workato's durable value is connectors, auth, reliability, which a solo one-shot build cannot reproduce responsibly. The prompt therefore builds only the closest honest personal consolation tool.
Keep it
Bardeen
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Bardeen, automate a narrow browser workflow on user-approved pages with visible steps. The hard boundary is browser automation library, integrations, cloud execution, templates, and model orchestration, plus connector breadth and execution reliability.
Keep it
Gumloop
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Gumloop, build one AI-assisted workflow from user-approved files and APIs. The hard boundary is hosted agent runtime, model routing, connectors, browser operations, and collaboration, plus connector breadth and execution reliability.
Keep it
Pipedream
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Pipedream, run a small event-triggered code workflow with approved credentials and durable logs. The hard boundary is managed runtime, event sources, oauth, secrets, connectors, scale, and support, plus connector breadth and execution reliability.
Keep it
SalesTouch
The local CRM and AI drafting layer are straightforward, but SalesTouch's core value is reliable access to LinkedIn's private network: authenticated sessions, live data extraction, residential IP routing, human-paced queues, limits, cooldowns, reconnection, and ongoing adaptation to platform changes. A one-shot clone either stops at manual copy and paste or becomes brittle automation that can put the LinkedIn account at risk.
Keep it
Albato
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Albato, connect two services and expose every transformation and retry. The hard boundary is connector library, app integrator, oauth, hosted execution, and support, plus connector breadth and execution reliability.
Keep it
FlowHunt
You can build one agent; you cannot build FlowHunt. A single-purpose AI agent, take a knowledge base or a data source, route a prompt through a model, take an action, return the result, is a one-sitting build. But the paid product's value sits outside that solo rebuild: a hosted runner that stays up, 100+ maintained connectors with all the OAuth and schema-drift upkeep behind them, one-provider model routing with credit accounting, a no-code visual builder aimed at people who will not write code, and team workspaces. That is integration breadth plus managed infrastructure, which is a structural moat, not polish. The prompt below is the honest consolation build: the one workflow you actually run, self-hosted, and you own its upkeep from then on.
Keep it
Integrately
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Integrately, connect two services through a fixed trigger and action with retries. The hard boundary is integration catalog, prebuilt recipes, oauth, schema upkeep, and hosted execution, plus connector breadth and execution reliability.
Keep it
Pabbly Connect
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Pabbly Connect, connect two documented APIs with a small durable workflow runner. The hard boundary is connector breadth, task economics, templates, support, and hosted reliability, plus connector breadth and execution reliability.
Keep it
Tray.io
Do not mistake the interface for the product. Tray.io's durable value is connectors, auth, reliability, which a solo one-shot build cannot reproduce responsibly. The prompt therefore builds only the closest honest personal consolation tool.
Keep it
ServiceNow
You can build a ticket tracker with a focused implementation. You cannot build ServiceNow, because ServiceNow is not a ticket tracker: it is a CMDB, an approval engine, a change management workflow that auditors accept, and a discovery agent crawling every asset on a corporate network. Nobody buys it because the forms are nice, they buy it because Sarbanes-Oxley auditors and ISO reviewers already know what a ServiceNow change record looks like. The personal version of this makes no sense either, since a single human does not need a change advisory board. If you genuinely want the shape of it for yourself, build a small request queue with states and an audit log and stop there.
Keep it
Diffbot
Do not mistake the interface for the product. Diffbot's durable value is connectors, auth, reliability, which a solo one-shot build cannot reproduce responsibly. The prompt therefore builds only the closest honest personal consolation tool.