Complex workflows without Zapier: from enquiry to payment
How to chain contact, quote, signature, invoice and payment in a small business: eight steps, three ways to build it and how each tool counts usage.
Héctor RedondoCEO and founder of BAI Business

Contents
- The whole flow, step by step
- Three ways to build it
- With a connection tool
- With a tool you host yourself
- Inside an integrated platform
- How much the same flow uses
- Which to choose according to your situation
- Measure what you pay today
- Frequently asked questions
- How many steps does the flow have from the first contact to payment?
- How does each tool count what a flow uses?
- What happens if a step of the flow fails halfway through the process?
- When is an integrated platform enough?
- You may also be interested in
- Sources
The flow from the first conversation to payment has eight steps and seven handovers of data. You can build it with a connection tool, with one you host yourself or inside an integrated platform; what changes is how many programs are involved and how usage is counted.
Reviewed on 2026-10-10. BAI Business sells a platform that includes these functions and publishes this article; that is why we also say when you don't need it.
The whole flow, step by step
Before choosing a tool, it helps to write down what has to happen. For a service small business, the process has eight steps:
- The contact arrives. By form, message or call, with name, contact details and what they are looking for.
- The customer and the opportunity are created. With their owner and an initial status.
- It is qualified. By rules or because a person reviews it.
- The quote is generated. From the data in the record, without typing it again.
- It is sent and signed. With an alert if the customer doesn't reply within the time you decide.
- The invoice is generated. From the data in the signed document.
- Payment is collected. With a payment link and a reminder if the invoice falls due.
- The sale is closed. The opportunity moves to won and the work with the customer begins.
Each handover from one step to the next is a piece of data that has to arrive correctly. If each step lives in a different program, each handover is a connection to maintain and a place where it can fail.
Three ways to build it
With a connection tool
Zapier or Make link the programs you already use: when something happens in one, the tool does something in another. It fits if you are starting out, if the flow is short and if you don't want to administer anything. What to watch is that from five or six steps with conditions on, the flow costs more to maintain, and that when it fails you have to find out in which of the programs it happened.
With a tool you host yourself
n8n lets you run the flows on your own server; according to its page it has a self-hosted Community edition on GitHub. It fits if someone with a technical profile can look after the server and if you want the flow's data not to pass through third parties. What to watch is that hosting it means installing it, updating it and making backups, and that the programs it connects are still the same.
Inside an integrated platform
If the customer, the documents, the invoices and the payments live on the same platform, the flow doesn't cross programs. According to its solution sheets, BAI Business keeps each document in BAI's archive linked to its customer and sends it to be signed by one or several people through their link, generates each invoice from the customer's record, with Verifactu if it is active, and, if an invoice falls due unpaid, the customer receives a reminder with the invoice and the link to pay. The ready-made automations chain the steps: you choose what starts them and what happens next. What to watch is that, if you need a specific outside program, that stretch still needs a connection tool.
How much the same flow uses
An illustrative calculation of ours: a flow of six actions that runs 200 times a month. In Zapier, a task is used when a Zap completes an action successfully, so it would be about 1,200 tasks a month, and its free plan includes 100. In Make, each action of a module counts as one credit, that is, about 1,200 credits, and its free plan includes 1,000. In n8n the price depends on the complete executions of the flow, regardless of the steps, so it would be 200 executions (accessed on 2026-10-10 on the pages of Zapier, Make and n8n).
The unit each tool measures changes what you pay according to how many steps your flow has. The prices of each are in Zapier alternatives for small businesses.
Which to choose according to your situation
- Connection tool: if you are starting out, the flow is short and you don't want to administer anything.
- Tool you host yourself: if there is already a technical profile in the team and the usage charged per task or credit is expensive for you.
- Integrated platform: if almost the whole flow fits in its modules and you want the handovers between steps to stop being a problem.
Measure what you pay today
Many small businesses don't know how much they pay in overlapping subscriptions. One way to find out:
- Export the bank statement for the last three months.
- Filter the recurring software charges.
- For each one, ask what would happen if you cancelled it tomorrow.
The ones you don't know what they are for are candidates for cancelling; the ones that do the same as another, for consolidating; the ones nobody has opened in a month, for cancelling right away.
Frequently asked questions
How many steps does the flow have from the first contact to payment?
Eight: the contact arrives, the customer and the opportunity are created, it is qualified, the quote is generated, it is sent and signed, the invoice is generated, payment is collected and the sale is closed with the follow-up of the new customer. Each handover of data between programs is a point where it can fail.
How does each tool count what a flow uses?
According to their pages, Zapier uses one task when a Zap completes an action, Make one credit for each action of a module, and n8n charges per complete execution of the flow regardless of the steps (accessed on 2026-10-10).
What happens if a step of the flow fails halfway through the process?
It depends on the tool, so check in its documentation what it retries and what it alerts you about. What matters is having alerts switched on: a flow that fails without telling you is the worst case, because you find out when a customer complains.
When is an integrated platform enough?
When almost the whole flow fits in its modules: customers, documents and signature, invoices and payments. If you depend on a specific outside program, a connection tool is still needed for that stretch.
You may also be interested in
- Automating your business without Zapier: when to use a connection tool and when to automate inside the platform.
- Zapier alternatives for small businesses: prices and plans of the connection tools.
Sources
- Zapier pricing and plans, accessed on 10 October 2026.
- Make pricing and plans, accessed on 10 October 2026.
- n8n pricing and plans, accessed on 10 October 2026.
Keep reading
Automation
Automating without Zapier: when to build it in your platform
When Zapier is still the answer and when to automate inside the platform where you already have customers, appointments and payments. With signs to decide by.
Automation
Automating invoicing and collections in your business
What can be automated when invoicing and collecting, what to leave by hand, what payment terms and interest the law sets and how to set up payment reminders.
Automation
What it means to automate a business and where to start
What it means to automate a business, how an automation works, what to automate first, what to leave by hand and how to start in a week.
