How to Scale a Digital Business with Make.com

Scaling a digital business with make.com is easier when you follow a practical, experiment-driven approach like the one used by FINN’s CTO, Max-Josef Meier. This how-to guide turns his experience into clear steps you can follow in your own company.

The source story from FINN shows how courage, no-code tools, and disciplined iteration can take a complex mobility product from idea to large-scale success. Below you will learn how to plan, build, and improve your own automations using the same mindset.

Understand the FINN and Make.com Story

FINN is a car subscription company that decided to digitize the entire car leasing experience. Instead of building everything with traditional development only, they relied heavily on no-code and automation tools such as make.com to move quickly.

The CTO focused on:

• Building a fully digital car subscription journey
• Automating repetitive processes early
• Letting teams ship value fast without waiting for long dev cycles

This background matters because it proves that a large-scale, regulated product can still grow quickly when you mix strong engineering with flexible no-code tools.

Plan Your Automation Strategy with Make.com

Before you build scenarios in make.com, you need a clear strategy that connects business goals to concrete workflows.

1. Define your core objective

From the FINN example, every automation ties back to the same question: does this help more customers subscribe to cars online, faster and more reliably?

Apply the same thinking by defining one main objective, such as:

• Reduce manual operations time
• Shorten onboarding time for new customers
• Increase conversion rate in a digital journey

2. Map your current manual processes

Walk through your existing process step by step:

1. List each manual action (emails, spreadsheets, updates, approvals).
2. Identify systems used (CRM, databases, support tools).
3. Mark pain points such as delays, errors, or duplicated work.

This map becomes your blueprint for which pieces should be automated first in make.com.

3. Prioritize high-impact workflows

FINN’s team kept a sharp focus on what drives the most value. Do the same by ranking each process on:

• Business impact (revenue, cost savings, risk reduction)
• Frequency (how often it runs per day or week)
• Complexity (how many steps and tools are involved)

Start with workflows that have high impact and medium complexity. They will give you meaningful wins without slowing you down.

Build Your First Make.com Scenario

Once your priorities are clear, you can begin building automation flows in make.com based on FINN’s style of rapid experimentation.

Step 1: Choose a simple, real business case

Pick a process that happens often, such as:

• New customer sign-up notifications
• Assigning leads to the right sales team
• Updating contract status across tools

FINN continually focused on real customer journeys. Your first scenario should do the same so you can see concrete outcomes quickly.

Step 2: Connect your core tools inside Make.com

In your make.com dashboard:

1. Create a new scenario.
2. Add the first app or trigger module (for example, your web form tool or CRM).
3. Connect other systems you use daily: support platforms, billing, internal databases, or email tools.

By connecting them visually, you create an overview similar to what FINN used to understand and optimize their digital subscription journey.

Step 3: Define triggers and actions

For each workflow:

• Trigger: The event that starts the scenario (e.g., new order, new lead, updated contract).
• Actions: The steps make.com should execute automatically (e.g., send confirmation, create tasks, sync records, update a dashboard).

Design your first scenario so that a single trigger leads to a complete, consistent response without manual work.

Step 4: Test safely and iterate

The FINN team treated every digital improvement like an experiment. Do the same in make.com by:

1. Running the scenario on test data first.
2. Checking each module output for errors and data quality.
3. Gradually switching from test mode to live mode once you are confident.

Small, fast iterations helped FINN grow without losing control of quality. This principle is crucial when you scale automation.

Scale Operations with Make.com Inspired by FINN

As your first automations prove useful, you can scale them, just like FINN scaled its subscription business.

Standardize your best scenarios

Identify which make.com scenarios work reliably and standardize them as part of your operating model:

• Create clear naming conventions for scenarios.
• Document triggers, inputs, and outputs.
• Set ownership for maintaining each scenario.

This discipline keeps your automations manageable as they grow in number and complexity.

Support cross-functional teams

FINN’s story shows the power of collaboration between engineering, product, and operations. To mirror that:

• Invite non-technical stakeholders to help design workflows.
• Use visual scenario diagrams in make.com to discuss improvements.
• Encourage teams to request new automations for their daily problems.

No-code tools become most valuable when more people can participate in building and refining processes.

Monitor results and refine

Scaling is not only about adding more scenarios. It is about improving the ones that exist. Take time to:

• Track error rates and scenario run times.
• Review business metrics related to each automation (for example, reduced processing time).
• Refactor scenarios when they become too complex.

This approach helped FINN keep a high-quality digital experience even while operations expanded rapidly.

Leadership Lessons from FINN for Using Make.com

Max-Josef Meier’s experience at FINN provides leadership insights that matter for anyone investing in make.com and no-code automation.

Balance engineering and no-code

The CTO combined strong software engineering with strategic use of no-code tools. The lesson:

• Use traditional development for core systems where performance and control are critical.
• Use make.com for flexible workflows, integrations, and fast experimentation.

This balance prevents bottlenecks while protecting your technical foundation.

Encourage courage and experimentation

FINN’s journey shows that courage to try new approaches is essential. In practice, this means:

• Allowing teams to build and test small automations without heavy bureaucracy.
• Accepting that some experiments will not work and need to be replaced.
• Rewarding learning and speed, not only perfection.

With this culture, your organization can move as quickly as FINN did while still maintaining control.

Further Resources on Make.com and No-Code Scaling

You can read the full FINN story and learn more about the CTO’s approach to no-code and automation on the original article here: FINN CTO Courage and No-Code.

For broader digital growth strategies that combine automation, AI, and marketing, you can also explore specialized consulting resources such as Consultevo, which focuses on scalable digital systems.

Putting Make.com Lessons from FINN into Action

To apply the lessons from FINN and make.com in your organization:

1. Clarify one main business objective for automation.
2. Map your current manual workflows and pain points.
3. Prioritize one or two high-impact processes.
4. Build simple, end-to-end scenarios in make.com.
5. Test, iterate, and standardize successful flows.
6. Encourage cross-functional teams and experimentation.

By following these steps, you can turn no-code automation into a core capability for your business, just as FINN did, and use make.com as a central engine for reliable, scalable digital operations.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help