01What counts as one custom automation
A custom automation is a specific workflow built around a real gap in how the business runs day to day, not a feature toggled on from a settings page. That could be a rule that flags a returning customer differently when they message in, a connector that pushes a new order straight into an existing spreadsheet or accounting tool instead of someone copying it over by hand, or logic that routes an urgent request to a phone call instead of an email queue. Two a month is a working cadence, not a hard ceiling that resets to zero unused capacity: what matters is that each one solves an actual manual step somebody was doing before, rather than adding a feature nobody asked for.
- A custom automation solves a specific manual step, not a generic feature toggle
- Examples: routing returning customers differently, connecting orders to an existing spreadsheet, urgent leads to a call
- Two a month is a working cadence built around real gaps, not a fixed feature menu
02What a larger custom build looks like, for scale
The AUTOMATE allowance is scoped for the size of automation most small businesses actually need month to month, not a full platform rebuild. To see what custom automation looks like at a bigger scale, ATP Spedition is the clearer picture: PROOF48 built one transport management system covering three different logistics businesses, courier, moving and freight, each with its own quoting, VAT calculation and invoicing rules, running from one shared codebase across web and driver apps. That is a project, not a monthly allowance, but it shows the same underlying discipline: automation built around how the specific business actually operates, never a generic workflow forced onto it from outside.
- AUTOMATE's monthly allowance is sized for ongoing small-business needs, not a full rebuild
- ATP Spedition shows custom automation at project scale: one system, three logistics lines, shared rules
- The same discipline applies at any scale: build around the business, not a generic template
One system built around three different businesses
ATP Spedition runs courier, moving and freight out of one system we built specifically for how those three lines actually operate, each with its own quoting and invoicing rules rather than a shared generic workflow forced across all three. It is a full custom project, not a monthly automation allowance, but it is the clearest example of what building around a real business, instead of a template, actually looks like.
See the build: ATP SpeditionQuestions, answered
What happens if we do not use both automations in a month?
The allowance is a monthly cadence for ongoing work, described plainly as two a month on the AUTOMATE plan; check the plan details for how unused capacity is handled month to month.
Can a custom automation be bigger than what fits in a month?
Yes. Something at the scale of ATP Spedition's transport management system is a full custom project, scoped and priced on its own, separate from the monthly AUTOMATE allowance.
Where PROOF48 fits
Two custom automations a month means two workflows built specifically around how the business runs, not two generic templates. AUTOMATE, at 2,997 EUR a month, bundles that allowance with a chatbot, booking automation and a CRM; the same underlying discipline, at project scale, is what shipped ATP Spedition's transport management system.
Cosmin Tiu · Founder, PROOF48
Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.