Custom builds
Have an automation built for you
When the workflow you need is not one of the products, describe it here. You get a straight answer within one US business day, Monday to Friday: either a product already covers it, or a written quote to build it.
- Describe it. The form below turns your answers into a brief and opens it in your own email app. Send it when you are happy with it. Rough is fine; the point is to get the trigger, the apps and the outcome down.
- We ask questions. Usually three or four: what starts it, what should happen when a step fails, how many a month. If a product already covers it, we say so and the conversation ends there with nothing owed.
- You get a written quote. Scope, price in euros, what is included, what is not, how long it is expected to take, and how it is paid. Nothing starts and nothing is charged until you accept it in writing.
- It gets built and written up. In your own Make.com account, using connections you authorise yourself, or delivered as a blueprint with a setup guide written the same way the products are. The quote says which, and either way you keep everything: the scenarios, the files and the documentation.
What it costs
Quoted per job. There is no rate card, because the range is wide: a single scenario joining two apps is a different job from a five-system process with approval steps. The quote is the price, and it does not move once accepted unless you change the scope.
Custom work is paid by invoice, which states the scope, the amount, the currency and any tax that applies. It is not sold through this website or through the same checkout as the products, and no payment is ever taken here.
Good fits
- A workflow with an approval step, a pricing rule, or a decision that depends on more than one thing.
- An in-house system with its own API that no ready-made module talks to.
- Several systems that have to agree with each other, where one falling behind is the actual problem.
- A product you already run that needs extending. The blueprint becomes the specification, which is a good way to write one.
Things we turn down
- Anything built to send email to people who did not ask for it.
- Scraping a site whose terms forbid it.
- Anything that needs your passwords. A Make.com connection you authorise yourself is the only access we use.
- A quote against a number, hours saved or revenue gained, before the process has been seen. Anyone who gives you one is guessing.