About Kettleford
A small operation selling automation files it builds and tests itself. There is one person behind it and no pretence otherwise.
Who this is
Kettleford is run by one person in the United States, trading as a sole proprietor. It is a trading name rather than a company: there is no corporation behind it, and the individual named on the business information page is the seller, the contracting party and the person who answers the support email. The name itself is invented and does not stand for anything, which is why this page exists: a coined word tells you nothing, so the explaining has to be done in plain sentences.
The day job is building automations. Order flows, follow-up sequences, the connective work that sits between a form and a CRM and an invoice and a spreadsheet. The same problems keep appearing, which is where the choice of what to build came from. The blueprints themselves are built fresh for this catalogue rather than lifted out of anyone else's account, for the reason in the next section.
How a pack gets built
Every blueprint is built from scratch for this catalogue, in a clean Make.com account, against real accounts on the apps it touches. None of it is exported from work done for someone else, which matters for an obvious reason: a scenario built for one business carries that business's field names, its assumptions and sometimes its data. Then each one is run end to end until it works, and then run again with things deliberately broken to see what it does.
That second part is the reason these cost more than a folder of exported JSON. It is easy to build a scenario that works when the webhook fires once, the API answers, and every field is present. It is more work to decide what should happen when the same order arrives twice, when the invoice tool times out halfway, or when someone renames a column in the sheet. Each pack documents those cases by name, and the scenarios handle them.
When a product ships, its guide carries a table of the failures that actually happened during that testing, what caused each one, and what to change. Not as a claim about results, just the record of the thing having been run rather than exported and hoped over.
Built to order, when the catalogue does not fit
The same work is available directly. When a workflow is not one of the products, it can be built: scoped and quoted in writing first, built in your own Make.com account with connections you authorise yourself, and written up the same way the products are. The custom automation page explains how that works, what it costs and what gets turned down.
What is deliberately not here
There are no testimonials on this site, no customer logos, no case studies and no numbers about how much time anyone saved. Kettleford is new. Inventing social proof would be quicker than earning it, and a great many sites in this corner of the internet have taken that route. When there are real testimonials, they will appear with the names of people who agreed to give them.
There are also no income claims. These scenarios do paperwork. What that is worth in your business depends on your business, and anybody who tells you a number for it is guessing.
Not connected to Make.com
Kettleford is not affiliated with, endorsed by, or sponsored by Make.com or Celonis. Make and Make.com are trademarks of their respective owners, used here only to identify the platform these products are built for.
Getting in touch
Email hello@kettleford.com. Questions before buying are welcome and often better asked than guessed at. More on the contact page.