{"course":{"slug":"agents-and-automation","title":"Agents and Automation","url":"https://addaly.com/learn/agents-and-automation","level":"intermediate","track":"build"},"lesson":{"slug":"buy-build-or-wait","title":"Buy it, build it, or wait for it","url":"https://addaly.com/learn/agents-and-automation/buy-build-or-wait","position":8,"of":72,"minutes":8,"answer":"Search the tools you already pay for before designing anything, and remember that an API call is about five per cent of the work of an integration.","keyIdea":"Search the tools you already pay for before designing anything, and remember that an API call is about five per cent of the work of an integration."},"body":{"format":"markdown","text":"## Search first\n\nA team spent three weeks building a receipt-filing agent. Their accounting package had done receipt capture with OCR for two years, on the mobile app, under a menu nobody had opened. This is common enough to be a rule: spend an hour reading the feature list of the tool that already holds the data before you design anything at all.\n\nLook specifically inside the system of record: the CRM, the accounting package, the helpdesk, the spreadsheet suite. Vendors ship AI features into those products faster than they update their marketing pages, and a native feature comes with the auth, the audit log and the support contract already attached.\n\n## Three costs, and the one that gets forgotten\n\nEvery automation has a build cost, a run cost and a maintenance cost. The first is a week you can see. The second is a monthly bill you can price. The third is what kills projects, and it is paid in attention rather than money.\n\nOver a year, expect a model you called by name to be deprecated or repriced, an API you depend on to change a field, a login to expire, a colleague who understood it to leave, and the upstream file format to shift. None of these are unusual events; together they mean the thing needs a competent person several times a year. Budget the person. There is no trustworthy industry figure for what proportion of build cost this is, and anyone quoting one precisely is guessing, but the direction is not in doubt, and a project with no named maintainer has a life expectancy measured in months.\n\n## When buying wins\n\nYou are mostly paying for connectors and for somebody else's on-call rota. A hosted automation tool maintains hundreds of integrations, each with its own auth dance, pagination style and rate limits, and absorbs the breakage when a vendor changes an endpoint. If your flow touches nine services, that maintenance is the product and it is worth real money.\n\nYou are also buying compliance paperwork: the security questionnaire, the data-processing agreement, the certifications your customer's procurement team will ask for.\n\n## When building wins\n\nThree situations. First, when the data cannot leave: a hospital's records, a lab's formulations, anything under a contract that names the countries it may sit in. Second, when the vendor's shape fights the work: the moment you need a loop with a condition inside it, a code review, or a rollback to last Tuesday's version, a visual builder becomes the expensive option. Third, volume.\n\nPer-task pricing is the quiet one. If a tool bills per step and one job is five steps, then two thousand jobs a month is ten thousand billed tasks. Compare that against a small virtual server running n8n or a plain cron job on a machine you already have. Prices move constantly, so check the current ones rather than trusting any number you read in a course, but the shape of the curve does not move: per-task pricing is cheap at pilot volume and turns hard against you somewhere in the low tens of thousands, and pilots grow.\n\n## When waiting wins\n\nIf the platform that already holds your data has the feature in beta, an integration you build now has a short life. Ask about the roadmap, treat the answer as marketing, and wait only when there is a dated commitment or a beta you can actually log into. \"Coming soon\" is not a plan you can schedule around.\n\n## The \"it's just an API call\" fallacy\n\nThe call is about five per cent of it. The rest is authentication and token refresh, rate limits and backoff, pagination, retry on the transient errors and not on the permanent ones, mapping their error codes to yours, handling the schema changing under you, storing the secret somewhere that is not the repository, logging enough to debug it at 3am, and a named person who will do that. Every one of those is an afternoon, and together they are the integration.\n\n## The free paths\n\nSelf-hosting is real and it is not free: it moves the cost from a bill to your evenings, which is a trade, not a saving. With that said: **n8n** self-hosts and is the usual answer for visual flows, though its licence is \"fair-code\" rather than OSI-approved open source, so read it if you plan to resell. **Node-RED** is Apache-2.0 and excellent for event wiring. **Windmill** runs scripts with a UI on top. **Apache Airflow** or **Prefect** for scheduled data pipelines. And beneath all of them, cron plus thirty lines of Python still runs an enormous amount of the world's automation. Zapier and Make have free tiers with task caps that are fine for proving a flow works and too small to run one.\n\n## The decision in one paragraph\n\nWrite down what happens if you do nothing for six months. Sometimes the answer is \"we keep paying two hours a week\", which is a hundred hours a year and worth solving. Sometimes it is \"nothing, this ran twice last quarter\". The second answer is not a defeat. It is the cheapest result this course can give you."},"check":{"question":"A team is deciding between a hosted automation tool and self-hosting the same flow. Which fact is the strongest argument for buying rather than building?","options":[{"text":"The flow touches nine third-party services, each with its own authentication, pagination and rate limits.","correct":true},{"text":"The process runs forty thousand times a month and each run is three simple steps.","correct":false,"tempting":"High volume on a simple flow is exactly where per-task pricing turns against you; this argues for building, not buying."},{"text":"The team already runs servers and has a deployment pipeline in place.","correct":false,"tempting":"Confuses capability with justification: being able to build lowers a cost, it does not create a reason."},{"text":"The data is under a contract that says it may not leave the company network.","correct":false,"tempting":"Points the other way: a constraint on where the work may run is a standard argument for self-hosting."}]},"prev":{"slug":"unit-economics-of-a-run","title":"What one run costs, and what it is worth","url":"https://addaly.com/learn/agents-and-automation/unit-economics-of-a-run"},"next":{"slug":"choosing-code-or-no-code","title":"n8n, Zapier, Make, or a file of Python","url":"https://addaly.com/learn/agents-and-automation/choosing-code-or-no-code"},"authorship":"Founder and series editor: Dr Mustafa Mun. Written by AI models to a written standard. Exam keys checked blind by a second model: 3,665 of 3,666 agreed. Academic review invited.","review":{"status":"Draft, open for academic review"},"cite":"Addaly (2026) 'Buy it, build it, or wait for it', in Agents and Automation. Edited by M. Mun. Addaly. Available at: https://addaly.com/learn/agents-and-automation/buy-build-or-wait (Accessed: 13 October 2026).","licence":{"name":"CC BY-NC-SA 4.0","url":"https://creativecommons.org/licenses/by-nc-sa/4.0/"},"reader":{"schema":1,"title":"Buy it, build it, or wait for it","courseTitle":"Agents and Automation","module":{"index":1,"slug":"deciding-what-to-build","title":"Before you build: script, workflow, or agent"},"answer":null,"keyIdea":"Search the tools you already pay for before designing anything, and remember that an API call is about five per cent of the work of an integration.","hero":{"kind":"plate","image":null,"alt":null,"caption":null},"blocks":[{"t":"h2","id":"search-first","runs":[{"text":"Search first"}]},{"t":"p","runs":[{"text":"A team spent three weeks building a receipt-filing agent. Their accounting package had done receipt capture with OCR for two years, on the mobile app, under a menu nobody had opened. This is common enough to be a rule: spend an hour reading the feature list of the tool that already holds the data before you design anything at all."}]},{"t":"p","runs":[{"text":"Look specifically inside the system of record: the CRM, the accounting package, the helpdesk, the spreadsheet suite. Vendors ship AI features into those products faster than they update their marketing pages, and a native feature comes with the auth, the audit log and the support contract already attached."}]},{"t":"h2","id":"three-costs-and-the-one-that-gets-forgotten","runs":[{"text":"Three costs, and the one that gets forgotten"}]},{"t":"p","runs":[{"text":"Every automation has a build cost, a run cost and a maintenance cost. The first is a week you can see. The second is a monthly bill you can price. The third is what kills projects, and it is paid in attention rather than money."}]},{"t":"p","runs":[{"text":"Over a year, expect a model you called by name to be deprecated or repriced, an API you depend on to change a field, a login to expire, a colleague who understood it to leave, and the upstream file format to shift. None of these are unusual events; together they mean the thing needs a competent person several times a year. Budget the person. There is no trustworthy industry figure for what proportion of build cost this is, and anyone quoting one precisely is guessing, but the direction is not in doubt, and a project with no named maintainer has a life expectancy measured in months."}]},{"t":"h2","id":"when-buying-wins","runs":[{"text":"When buying wins"}]},{"t":"p","runs":[{"text":"You are mostly paying for connectors and for somebody else’s on-call rota. A hosted automation tool maintains hundreds of integrations, each with its own auth dance, pagination style and rate limits, and absorbs the breakage when a vendor changes an endpoint. If your flow touches nine services, that maintenance is the product and it is worth real money."}]},{"t":"p","runs":[{"text":"You are also buying compliance paperwork: the security questionnaire, the data-processing agreement, the certifications your customer’s procurement team will ask for."}]},{"t":"h2","id":"when-building-wins","runs":[{"text":"When building wins"}]},{"t":"p","runs":[{"text":"Three situations. First, when the data cannot leave: a hospital’s records, a lab’s formulations, anything under a contract that names the countries it may sit in. Second, when the vendor’s shape fights the work: the moment you need a loop with a condition inside it, a code review, or a rollback to last Tuesday’s version, a visual builder becomes the expensive option. Third, volume."}]},{"t":"p","runs":[{"text":"Per-task pricing is the quiet one. If a tool bills per step and one job is five steps, then two thousand jobs a month is ten thousand billed tasks. Compare that against a small virtual server running n8n or a plain cron job on a machine you already have. Prices move constantly, so check the current ones rather than trusting any number you read in a course, but the shape of the curve does not move: per-task pricing is cheap at pilot volume and turns hard against you somewhere in the low tens of thousands, and pilots grow."}]},{"t":"h2","id":"when-waiting-wins","runs":[{"text":"When waiting wins"}]},{"t":"p","runs":[{"text":"If the platform that already holds your data has the feature in beta, an integration you build now has a short life. Ask about the roadmap, treat the answer as marketing, and wait only when there is a dated commitment or a beta you can actually log into. “Coming soon” is not a plan you can schedule around."}]},{"t":"h2","id":"the-it-s-just-an-api-call-fallacy","runs":[{"text":"The “it’s just an API call” fallacy"}]},{"t":"p","runs":[{"text":"The call is about five per cent of it. The rest is authentication and token refresh, rate limits and backoff, pagination, retry on the transient errors and not on the permanent ones, mapping their error codes to yours, handling the schema changing under you, storing the secret somewhere that is not the repository, logging enough to debug it at 3am, and a named person who will do that. Every one of those is an afternoon, and together they are the integration."}]},{"t":"h2","id":"the-free-paths","runs":[{"text":"The free paths"}]},{"t":"p","runs":[{"text":"Self-hosting is real and it is not free: it moves the cost from a bill to your evenings, which is a trade, not a saving. With that said: "},{"text":"n8n","b":true},{"text":" self-hosts and is the usual answer for visual flows, though its licence is “fair-code” rather than OSI-approved open source, so read it if you plan to resell. "},{"text":"Node-RED","b":true},{"text":" is Apache-2.0 and excellent for event wiring. "},{"text":"Windmill","b":true},{"text":" runs scripts with a UI on top. "},{"text":"Apache Airflow","b":true},{"text":" or "},{"text":"Prefect","b":true},{"text":" for scheduled data pipelines. And beneath all of them, cron plus thirty lines of Python still runs an enormous amount of the world’s automation. Zapier and Make have free tiers with task caps that are fine for proving a flow works and too small to run one."}]},{"t":"h2","id":"the-decision-in-one-paragraph","runs":[{"text":"The decision in one paragraph"}]},{"t":"p","runs":[{"text":"Write down what happens if you do nothing for six months. Sometimes the answer is “we keep paying two hours a week”, which is a hundred hours a year and worth solving. Sometimes it is “nothing, this ran twice last quarter”. The second answer is not a defeat. It is the cheapest result this course can give you."}]}],"check":{"question":[{"text":"A team is deciding between a hosted automation tool and self-hosting the same flow. Which fact is the strongest argument for buying rather than building?"}],"options":[{"text":[{"text":"The flow touches nine third-party services, each with its own authentication, pagination and rate limits."}],"correct":true,"tempting":null},{"text":[{"text":"The process runs forty thousand times a month and each run is three simple steps."}],"correct":false,"tempting":[{"text":"High volume on a simple flow is exactly where per-task pricing turns against you; this argues for building, not buying."}]},{"text":[{"text":"The team already runs servers and has a deployment pipeline in place."}],"correct":false,"tempting":[{"text":"Confuses capability with justification: being able to build lowers a cost, it does not create a reason."}]},{"text":[{"text":"The data is under a contract that says it may not leave the company network."}],"correct":false,"tempting":[{"text":"Points the other way: a constraint on where the work may run is a standard argument for self-hosting."}]}],"order":[1,2,0,3],"why":null},"prev":{"slug":"unit-economics-of-a-run","title":"What one run costs, and what it is worth","minutes":9},"next":{"slug":"choosing-code-or-no-code","title":"n8n, Zapier, Make, or a file of Python","minutes":8}}}