How to build and sell an AI automation agency

Straight answers to the questions AI agency builders actually ask. Two lines: Build it (the technical how-to) and Sell it (winning and pricing the work).

Line

Topic

Showing 1-19 of 19

Sort

Build it

How to build a knowledge base an AI can actually answer from

A knowledge base that reads fine to a human can still make an AI hallucinate, because the two are searching it in completely different ways.

AI & RAGAirtable, n8n, Supabase

Build it

Airtable, Google Sheets or a real database: what to store data in

The choice between a spreadsheet, Airtable, and a real database isn't about size. It's about how much the data needs to protect itself.

Data & StorageAirtable, Google Sheets, Postgres

Build it

Make vs n8n: which automation platform should you start with?

A non-developer building their first client automations needs speed, not architectural purity, and that changes which platform wins.

Tools & PlatformsMake, n8n, Docker

Sell it

Project, retainer or hourly: how to price AI automation work

Picking project, retainer, or hourly is not a formatting choice, it decides who carries the risk of every unknown in the build.

Pricing

Build it

Building a voice AI agent: the speech-to-text, LLM and text-to-speech pipeline

Speech-to-text, the model, and text-to-speech look like three separate tools to wire together, but the real difficulty is the seams between them.

Voice AIElevenLabs, VAPI, Twilio

Build it

OAuth2 vs service accounts: authenticating to an API cleanly

Every integration eventually asks the same question: log in as the client, or mint a key and move on. Here is how to actually decide.

Auth & Credentialsn8n, Google Drive, Google Calendar

Build it

Email trigger vs database trigger: which should fire your workflow?

Both triggers look simple to wire up, but one of them quietly breaks the moment a client's inbox behaves like an inbox instead of a data feed.

Workflow Designn8n, Airtable, Make

Build it

How to break a big automation into reliable, retryable steps

Big automations fail as one unit unless you split them into small, retryable pieces with real checkpoints between each one.

Workflow Designn8n, Airtable

Build it

Scraping sites that fight back: Cloudflare, dynamic loading and empty HTML

Cloudflare walls, JavaScript-rendered pages, and pagination that breaks past page one all kill naive scrapers, and each one has a different fix.

APIs & ScrapingApify, Firecrawl, n8n

Sell it

Start with one high-impact automation to build trust

Before you build anything ambitious for a client, pick the one automation that pays back fast and let it earn you permission for the rest.

DeliveryAirtable, Make, n8n

Sell it

Warm outreach before cold: getting the order right

Warm outreach converts faster than cold outreach, so it has to run first, not in parallel and not as an afterthought.

OutreachLinkedIn, Instantly AI

Sell it

Position yourself as 'AI and automation', not just 'AI'

Calling yourself an AI agency invites price comparisons against ChatGPT. Calling yourself an AI and automation agency invites a conversation about the client's actual workflow.

Positioning

Build it

How to stop one bad record killing your whole workflow

One bad record does not have to take down a whole run. Here is the order most builders learn to fix it in, usually after the third crash.

Workflow Designn8n

Sell it

Framing automation ROI: the cost-of-an-employee math

Clients don't buy automation, they buy the avoided cost of a hire, so anchor every proposal to what a person doing that job would cost.

SalesAirtable, Notion, Trello

Build it

Should you use one AI prompt or a chain of them in your automation?

Every automation forces a choice between one large prompt doing everything and a chain of smaller ones passing work along, and the wrong pick shows up as silent failures weeks later.

AI Promptingn8n, Google Sheets

Sell it