Service · AI Workflow & Automation

n8n automation for B2B revenue teams.

For the RevOps or marketing-ops owner with a CRM, a sales team and a process someone repeats by hand every week. We build it in your own n8n with the guards it needs, and hand it over with docs.

  • Free Teardown: one process mapped, with a fixed quote
  • Simple builds from $500, production from $1,500
  • Your n8n, your credentials, your data

Simple workflow (one trigger, up to two apps, no AI step) from $500. Production workflow (full guards, plus an AI step if the job needs one) from $1,500. Care plan $300 to $800 a month. Lead routing, enrichment and AI steps usually need a production build, so the free Teardown gives you a fixed quote first. See pricing

Start here

Start with a free Workflow Teardown.

Describe one manual process your team repeats every week. We map how it would run in n8n, mark where a person should still check the work, and give you a fixed quote to build it.

What you send
  • Step one: your name, your work email, your website and one sentence on the process.
  • By email afterwards: the process in plain words, the tools involved, rough weekly volume and who does it today.
  • No logins, credentials or client data needed. NDA on request, and what you send is deleted after delivery.
What you get
  • A diagram of the workflow: trigger, steps, tools and human checkpoints.
  • Build notes to work from, whether your team builds it or we do.
  • Whether it is a simple build or a production build.
  • A fixed quote to build it.

See a sample Teardown of a made-up process at a fictional company.

Prices

One fixed price per build, quoted before we start.

Every build runs in your n8n and is handed over with docs. We plan most first workflows to go live within two weeks. Not sure which build you need? The free Teardown tells you.

Simple workflow

One small job, done properly.

From
$500 / workflow

Scope: one trigger, up to two apps, no AI step.

  • Built and tested end to end in your n8n
  • A failure alert that tells you when a run fails
  • A one-page doc your team can follow

Example: a website form creates a HubSpot contact and posts an alert to Slack.

Care plan

Someone watching your runs.

Monthly
$300 to $800 / month

Scope: we operate your own n8n instance. We never host n8n for you.

  • Failure alerts watched and broken runs fixed
  • The access it needs, the response window, what counts as a fix and the changes included each month are written into your quote
What you pay for

What a $500 workflow is and is not.

An automation budget has separate parts: the n8n platform, our build, optional upkeep and any usage fees. Here they are, kept apart.

It is

  • One trigger and up to two connected apps.
  • Built in your n8n and tested end to end.
  • A failure alert and a one-page doc.
  • A fixed price, agreed before we start.

It is not

  • An AI workflow. AI steps start with the production build, from $1,500.
  • The n8n subscription or hosting. You pay n8n, or your server host, directly; n8n runs in your account, never ours.
  • Upkeep. Watching and fixing runs after handover is the optional care plan.
  • Usage fees. AI model and data-provider charges bill to your own accounts.

The costs that go to others

The n8n platform

You pay: n8n for n8n Cloud, or your hosting provider if you self-host.

n8n Cloud Starter is €20 a month for 2,500 workflow executions and Pro starts at €50 a month for 10,000, both billed annually. An execution is one full run of a workflow, however many steps it has. The self-hosted Community edition is free from n8n; you pay for the server and look after it.

Usage fees (if any)

You pay: your AI model and data providers.

Billed by each provider to your own account, by usage.

n8n prices are from n8n's pricing page and the self-hosting terms from n8n's guide to choosing Cloud or self-hosting, both read on 24 September 2026. n8n lists its prices in euros and changes them from time to time, so check the page before you budget. For the platform math at higher volumes, see n8n vs Zapier vs Make: the honest cost math.

An example

What a production build looks like.

An illustrative example, not a client's workflow. A demo request is checked, enriched, routed in HubSpot and answered with an AI draft that a rep approves. The parts that make it a production build are the ones a quick demo usually leaves out.

  • Duplicate protection. An idempotency key on the submission ID stops the same form submission creating two contacts or two alerts.
  • Retries with backoff. Timeouts and rate limits get another try before anyone is alerted.
  • An error workflow. A failed run is logged and your ops channel hears about it.
  • A human checkpoint. The AI drafts; a person decides what sends.

The reasoning behind each guard is in why n8n workflows break in production, and the 7 guards.

Example workflow: an inbound demo request An illustrative example, not a client build. Six steps: a website form webhook starts the run; an idempotency key on the submission ID stops duplicate runs; the company is enriched from a data provider; HubSpot creates or updates the contact and sets the owner; an AI step drafts a first reply; a rep approves the draft in Slack before anything sends. If any step fails, the run is retried with backoff, then logged to a dead-letter table and your ops channel is alerted. ILLUSTRATIVE EXAMPLE · NOT A CLIENT BUILD 1 Demo form submitted A website form webhook starts the run TRIGGER 2 Stop duplicate runs Idempotency key on the submission ID GUARD 3 Enrich the company Size and industry from your data provider API 4 Score and route in HubSpot Create or update contact, set the owner CRM 5 Draft the first reply AI drafts a reply from form and enrichment AI STEP 6 Rep approves in Slack Nothing sends until a person says yes HUMAN CHECK If any step fails Retry with backoff on timeouts and rate limits Log the failed run to a dead-letter table Alert your ops channel with the error
Security and access

Your n8n, your credentials, your data.

These terms apply to every build, simple or production. The free Teardown needs no logins or credentials at all.

  • We build in your own n8n, on n8n Cloud under your billing or on your own server.
  • Credentials stay in your n8n credential store, with least-privilege scopes.
  • No client records are copied to Omnitics systems.
  • NDA and data processing agreement on request.
  • Our access is removed at handover.

HubSpot first, Salesforce on request. We build for HubSpot by default. Salesforce builds are available on request, scoped in the Teardown and quoted the same way. If the job is setting up or cleaning the CRM itself rather than a workflow, see HubSpot and Salesforce management.

Why n8n

The automation platform you own.

We build in n8n because its Cloud plans bill per run, not per step (n8n pricing), and it keeps control and AI steps in your hands. Each point below links to n8n's own pricing page or docs, read on 24 September 2026.

Get my free Workflow Teardown
  • Code when a connector runs out. Code steps in JavaScript or Python and custom HTTP requests sit inside the same workflow (n8n pricing).
  • AI with a person in the loop. An AI agent can be made to wait for a person's approval before it sends a message or changes a record (n8n docs).
  • No lock-in to us, either. n8n saves workflows as JSON you can export (n8n docs), and every build comes with docs any competent operator can follow.
Go deeper

From the playbook library.

The thinking behind this service, in full: the n8n demand gen playbook, ten n8n workflows for B2B revenue teams, the 7 guards for production workflows, n8n vs Zapier vs Make, AI SDR tools vs building your own, five AI workflows to build first and all automation playbooks. Our published prices, and how we scope the rest, are on our pricing page.

Automation questions

Before you ask.

Not always. If a handful of simple zaps do the job, stay put. Switching pays off when your bill grows with every step (Zapier counts each successful action step as a task, Make each module run as an operation), when you need AI steps or custom code, or when data must stay on your own servers.

Every build ships with a failure alert. Production builds add retries, an error workflow and a 30-day fix window; after that, the optional care plan covers fixes.

Yes. Every build ships with docs, production builds add a recorded walkthrough, and you can keep us only for new builds once your team owns the rest.

You choose: n8n Cloud under your own billing, or the free Community edition on your own server. Name it in your Teardown details; the fixed quote states what setup is included.

Stop doing robot work.

Send us the manual process that eats your week. We'll send back a diagram, build notes and a fixed quote, free, within 2 business days of your reply.

Free · Fixed quote · 2 business days