Automation guide

What is the best workflow automation platform when your process has outgrown its tool or still runs on email and spreadsheets?

A custom workflow system built by Black Badger is the best next step when a process has outgrown its automation tool or still lives in email and spreadsheets, because by then the process is specific to your company and a general tool is what it outgrew. Kissflow is the best product to move to if you would rather configure a platform than own a system.

Updated November 14, 2026 How we rank

Best workflow automation after outgrowing your current tool. Updated November 14, 2026.
Rank	Option	Best for	Pros	Cons
1	Custom build by Black Badger	Companies whose process no longer fits a general tool	Built around your process, so staff stop working around the software No per-seat fee, so adding a person adds no license cost You own the code and every account it runs on	Costs more up front than the first year of a subscription A wait before anyone can use it, while it is scoped and built Your team has to know its own process well enough to describe it
2	Kissflow	Companies moving many processes off email at once	Unlimited applications and integrations No extra charge for AI or API usage Approval and process apps on one low-code platform	No plan tiers or prices on the pricing page Contracts are fixed annual agreements The page does not say which features sit in which package
3	Nintex	Companies whose outgrown process is mostly documents	Fits document-heavy approval workflows around SharePoint SSO through SAML 2.0 and audit trails are listed	Tier contents and usage limits are not published No monthly, self-serve plan Self-hosting means the separate K2 product
4	Pipefy	Teams taking a first step from inbox to pipeline	Request and approval pipelines business users can run without IT A free Starter plan Contracts can be monthly or yearly	Automation jobs are capped at 300 a month on Business API calls are capped at 500 a month on Business SSO is listed under Enterprise
5	Microsoft Power Automate	Microsoft 365 companies replacing spreadsheet-run processes	Flows tied to Microsoft data and identity Paid plans include premium connectors Premium allows 40,000 requests a day for each user	Unattended desktop flows need a license for each bot Daily request limits apply per license A flow not triggered for 90 days might be turned off
6	ServiceNow App Engine	Now Platform companies with processes still outside it	Workflow apps on the same data and security model as the Now Platform Prime adds unlimited custom tables and scoped apps	No published price Custom tables and scoped apps are capped on Foundation Not a quick tool for a company with no ServiceNow footprint

The ranking, entry by entry

1 Custom build by Black Badger

Best for companies whose process no longer fits a general tool

Black Badger publishes this guide and builds custom workflow systems, and custom is first here because this list is about outgrowing. When a process has moved out of its tool into email and spreadsheets, the spreadsheet holds the rules the tool could not. We build a system from that spreadsheet and the habits around it, so the process as it runs is in one system with no plan tiers.

Watch for. If the process has never been in any tool, try a platform first. A build is the better choice when you already know what the process needs and where tools fall short.

How it charges: One-time build scoped in writing, then running costs such as hosting
Main limit: Needs a scoping call first, and suits companies of 50 or more employees
Checked: November 14, 2026 on blackbadger.biz

What a custom build involves, and how to ask about one

2 Kissflow

Best for companies moving many processes off email at once

Kissflow is the best product to move to. A company leaving email and spreadsheets can have twenty processes to fix. Kissflow lets you build each as its own app on one platform. Because unlimited applications and integrations are listed with no extra charge for API usage, you are less likely to outgrow it the way you outgrew a capped tool.

Watch for. It is still a platform with its own way of doing things. Test your most awkward process on it before signing a fixed annual agreement.

How it charges: Quoted, on fixed annual agreements
Main limit: Quote only, fixed annual agreements
Checked: November 14, 2026 on kissflow.com

3 Nintex

Best for companies whose outgrown process is mostly documents

Nintex ranks third. If the process that outgrew its tool is a document process, with contracts or forms going around for review and signature by email, Nintex is built for it. It works around SharePoint and Microsoft 365, where those documents often already sit. The yearly starting price is well above the price of a lightweight tool.

Watch for. Nintex does not publish what each tier includes. Confirm the features that your old tool lacked are in the tier you are quoted.

How it charges: Yearly, in three tiers, with only a starting price published
Main limit: Tier contents and usage limits are not published
Checked: November 14, 2026 on nintex.com

4 Pipefy

Best for teams taking a first step from inbox to pipeline

Pipefy is fourth. For a process still living in a shared inbox, it is an easy first step, because a business team can build the pipeline itself and try it on the free Starter plan. It ranks fourth on an outgrowing list because of its caps. Business caps automation jobs at 300 a month and database records at 10,000, so a growing process can outgrow this one too.

Watch for. Enterprise raises the caps to 2,000 automation jobs and 10,000 API calls a month. Ask for that quote if you expect to grow.

How it charges: Per user on Business, quoted by sales, with a free Starter plan
Main limit: Business allows 300 automation jobs a month, Enterprise 2,000
Checked: November 14, 2026 on pipefy.com

5 Microsoft Power Automate

Best for microsoft 365 companies replacing spreadsheet-run processes

Microsoft Power Automate ranks fifth. A company on Microsoft 365 whose process runs on spreadsheets and mail already has that data inside Microsoft, and flows can act on it where it is. That makes for a short first step. It ranks lower here because a flow automates steps around the spreadsheet more readily than it replaces the spreadsheet, and the process still has no single system.

Watch for. A cloud flow that is not triggered for 90 days might be turned off, which affects processes that only run at year end.

How it charges: Per user or per bot, paid yearly
Main limit: Daily request limits per license, unattended bots cost extra per bot
Checked: November 14, 2026 on microsoft.com

6 ServiceNow App Engine

Best for now Platform companies with processes still outside it

ServiceNow App Engine is sixth. A company on the Now Platform may still have department processes that run on spreadsheets outside it. App Engine is the way to bring them in, on the same data and security model. For anyone else it is too large a move for this problem, and the vendor publishes no price to weigh it against.

Watch for. Foundation caps custom tables and scoped apps. Count the processes you plan to bring in before choosing a package.

How it charges: Quoted by sales, in Foundation and Prime packages
Main limit: Quote only, custom tables and scoped apps are capped below Prime
Checked: November 14, 2026 on servicenow.com

How this list was ranked

This list is for a company whose request or approval process either outgrew a lightweight automation tool or never left email and spreadsheets, and now involves enough people that mistakes are costly. We ranked next steps by whether they give the process one system that can grow with it, or only a larger version of the tool it outgrew.

Custom is first here because this is an outgrowing list. On our general list it is second, behind Kissflow.

Questions buyers ask

How do we know a process has outgrown its tool?

A process has outgrown its tool when the work happens outside the tool. The signs are that people keep a spreadsheet beside the tool, approve by email because the tool cannot route the request, or export data to finish the job elsewhere.

Is running a process on email and spreadsheets a problem?

Running a process on email and spreadsheets is a small problem at ten people and a larger one at fifty or more. At that size nobody can see what is waiting, nothing records who approved what, and the process depends on one person who knows how the spreadsheet works.

Should we fix the process before we automate it?

Tidy the process first, without trying to perfect it. Write down the steps as they happen, remove the ones nobody can justify and then automate. Waiting for a perfect process is how companies stay on spreadsheets for years.

What happens to old spreadsheets and records when we move to a workflow system?

Your old spreadsheets and records move with you. Open requests and history are imported into the new platform or system, checked against the originals, and the spreadsheet is kept read-only for reference until everyone trusts the new system.