[SHARE YOUR FEEDBACK] - Value return of Make

Hi :wave:,

in the last several months we started to notice that helping our users to understand value return of Make might be something to look into. It seems that there is room for an improvement within our product and we are now trying to get a bit more feedback directly from our users. We would like to learn more about how can Make be better at helping you, our users, to understand what value you are getting back from Make.

How do you perceive the value return of Make? Do you measure it? Why is this information important to you? :thinking:

If you want to chat and share your answers to the (not only) questions above, please let us know by repying to this post.

Alternatively, feel free to share you feedback directly here. :point_down: We’ll take care of it.

Thanks!
Michal,
Product Manager

5 Likes

I am working through the Academy and see a lot of value in the long term. I have a good idea of what scenarios i want to put in place to really help me with my product management. As much as all the workflow platforms say there is no coding required it is still a big learning curve for someone like me not technical.

I am struggling with one flow and have used the AI, but many areas don’t work properly so have been unable to move to finalise my first scenario. I have created a post but so far no response.

1 Like

I find myself more and more paying close attention to the operations used in each scenario to determine if the “juice is worth the squeeze” for using make.com or finding an alternate solution. Example - I wanted to send a lot of emails to customers lately and found that the scenario I created was taking as many operations (which equals dollars) than just paying for an email service to send them. I know there are work-arounds with grouping emails and reducing modules, but that’s my feedback. I wish I didn’t have to “worry about” operations at some level. Other than that - I absolutely love make.com and it’s been a game changer for all that I’m involved in.

1 Like

hi,

The added value of Make is (for me who uses it daily):

  • Its ease of use
  • The integrations of many solutions on the market

However, the cost of operations when processing large volumes of operations can appear to customers as a brake.

For my part, I start by showing the customer what their current management processes cost them (often relying on humans, which is not a bad thing in itself), once this awareness is made, it is important to remain factual without judgment, between the cost of developing a scenario and what it costs (I host the scenarios in a Teams subscription) over a year.
In 100% of cases, there is a saving, that being said, when the volume of data is large, the number of operations consumed is also important, and in some customer cases, the ROI of Make is not advantageous compared to an n8n (I use it on dedicated hosting). And in this case I sometimes “mix” the two solutions.

However, Make remains my preferred solution for quick integrations.

Last point, it is not always easy to distinguish the modules maintained by Make from the others. For a client I had to trace the API calls via the HTTP request module, because the Prestashop modules contained bugs.

1 Like

It would be nice to be able to see how much a run of one scenario costs. Then, if you optimise it, you can see how much you’ve saved.

I recently ran out of ops because one of my scenarios got accidentally scheduled to run every 15 min. It would have been nice to put a rule in to say scenarios should not be using up more than x ops or dollars a day.

About value: that’s a bit harder to measure - we know we’re saving people’s time by automating some of their work, but that’s not really calculated in our case. I know that if one of my colleagues spends 30min a day recreating a specific spreadsheet, if I spend 2 days automating it in a scenario, I will have saved that person’s time within 16 work days, so it makes sense to automate that process.

3 Likes

I’m currently spending quite a few operations to get my scenario and operations data out of Make and into Notion, where I can analyze it much better.

Make is very fun to use — as long as you don’t have to think about operations. These days, I have to be quite careful when deciding to start a new scenario, and I’ve often wondered where all my operations go. Of course, I know there’s an operations counter in the scenario view, but with 40+ folders, 200+ scenarios, and a monthly reset on that counter, it just doesn’t cut it for me.

What I’m currently doing:

I have a database in Notion with all my scenarios, which are linked to the business processes they’re part of. Once a week, I sync all the operations data into my Notion workspace. This allows me to:

• Track costs over a longer period,

• Calculate the “cost per year” for every scenario,

• Roll up those costs to the process database.

Seeing that I spend only about €50 a year on automating otherwise labor-intensive tasks is super helpful. On the flip side, identifying scenarios where I’m splurging on automating low-value tasks is equally insightful.


Statuses and costs of my “Bookkeeping” scenarios right inside the dashboards where they are relevant is super valuable for us


Having a much longer history of my operations usage helps me understand the value and cost of any given scenario.

The Irony:

This process is great and all, but ironically, the scenarios I use to get this data into Notion consume 20–25% of my total operations! I won’t be able to keep doing this for long.

It would be much more helpful to have deeper insights into this data directly in Make. Right now, it’s not even possible to sort scenarios by their operations or data usage!

1 Like