Make.com blueprints. Digital downloads, instant delivery.hello@kettleford.com
KettlefordAutomation blueprints
Make.com blueprints, built and written up

Automation infrastructure for everything that follows the sale.

Ready-made Make.com scenarios for orders, reviews, leads and invoicing. Import one, connect your own accounts, and the invoice, the confirmation email, the spreadsheet row and the follow-up happen without you. Every product ships with its setup written down, module by module.

A stapled setup guide lying open on a dark desk, its pages showing a flow diagram of connected boxes, with a spreadsheet grid on a loose sheet beside it and a dark red ribbon bookmark.
Payment
One payment at a hosted checkout. Nothing renews and nothing is taken later.
Delivery
A download link on your receipt, straight away.
Refunds
14 days, no reason needed, on every product.
Seller
Yazie Henok Alemseged, a sole proprietor in Washington. One person, named on every page.

What is in every download

Files, not lessons
.json

Blueprint files you import straight into Make.com, so nobody rebuilds modules by hand from a screenshot.

PDF

The setup, written out step by step, with a note on every module and why it is set the way it is.

.csv

The spreadsheet a scenario reads and writes, columns already in order, for every product that uses one.

Errors

The ways each scenario breaks and what it does when it does, listed case by case rather than left for you to find.

Three ways to buy

eleven products, one payment each

Compare everythingPrices are in euros. VAT may be added at checkout depending on where you are.

Three workflow areas, one spreadsheet

Each has a single blueprint to start with
01

Order Ops

Order confirmed / Invoice raised / Customer email / Sheet log / Team notified

Order confirmed, then invoice, customer email, a row in the sheet, and a note to the team. The paperwork nobody wants to do twice.

Start with Order Confirmation Blueprint, €14.97 EUR
02

Review and Feedback

Trigger / Personalised link / Send / Follow up once / Response logged

A trigger fires, the buyer gets a review link with their own details already filled in, and the reply lands somewhere you can actually read it.

Start with Review Request Blueprint, €14.97 EUR
03

Lead Follow-Up

Captured / Enriched / Written to CRM / Sequence runs / Owner notified

Capture, enrich, write to the CRM or the sheet, then follow up on a schedule until somebody replies or the sequence ends.

Start with Lead Capture Blueprint, €14.97 EUR

What the scenarios actually do

Eight of the twenty-seven
  1. An order is confirmed

    Checked against every order seen before, invoiced through Stripe, confirmed to the customer by email, logged in the sheet, and the team told only when it matters.

    In Order Confirmation Blueprint
  2. A delivery is marked done

    A review request waits in the spreadsheet and goes out days later with the customer's details already filled in. One follow-up, only to people who have not replied.

    In The Nine
  3. A form is submitted

    The lead is cleaned, checked for duplicates, written to the sheet and assigned in turn. A first follow-up goes out and stops the moment they answer.

    In The Library
  4. A refund is issued

    Recorded, flagged to the team, and the review request queued for that order is cancelled before it embarrasses anyone.

    In The Library
  5. Friday afternoon

    One digest of the week's orders, review replies and stale leads, instead of an alert for every event.

    In The Library
  6. The first of the month

    Recurring invoices raised once and chased when unpaid, and renewal reminders sent on purpose rather than by accident.

    In The Complete Library
  7. An expense lands

    Logged with its category normalised, so the sheet you open at year end is one you can actually use.

    In The Complete Library
  8. Nothing happens

    Two scenarios watch the others: one finds orders logged but never invoiced, one finds rows a scenario claimed and never finished. Both stay quiet until something is wrong.

    In The Library

How it works

  1. Buy the product. Checkout is hosted and processed by Stripe. One payment, and the receipt arrives with a download link on it.
  2. Download the files. Blueprints, the guide and the licence in one folder. You do not install anything and you do not create an account.
  3. Import into Make.com. New scenario, then Import Blueprint, then pick the file. The guide walks through it if you have not done it before.
  4. Connect your own accounts. The scenarios ship without connections attached, on purpose. You point each module at your own accounts, which is the part the guide spends most of its pages on.

Why these, and not a free template

Everything here can be checked before you pay
01

A note on every module

The guide explains what each module is for and why it is configured the way it is, so you can change it without guessing.

02

Failures named in advance

Each guide carries a table of the failures that actually happen, what causes each one, and what to change.

03

What you need, before you pay

Every product page lists the apps a scenario touches and says where a paid Make.com tier is needed, under a heading called What you need before you buy.

04

Nothing bought twice

Each tier holds the one below it. The single blueprints are the same files, byte for byte, as their scenarios in the library.

05

The sheet arrives built

Where a scenario reads a spreadsheet, the template ships with the columns in the right order, so the schema is not something you decode from prose.

06

Twice is the enemy

Any scenario that could invoice or email the same person twice checks a data store first, and the guide has you watch it refuse before anything goes live.

A large sheet of paper on a dark desk with a rough pencil sketch of a workflow, two small square notes resting on it, a wooden ruler along the top edge and a dark red paper tab on one corner.
Custom builds

Need something the catalogue does not cover?

Not every workflow is a common shape. If yours has an approval step, a pricing rule, or a system with its own API, describe it and you get a straight answer: either a product already covers it, or a written quote to build it.

Custom work is scoped and quoted before anything starts, built in your own Make.com account with connections you authorise yourself, and documented the same way the products are, so you can run it without us afterwards.

Plain dealing

What Kettleford is not

  • Not a course. There are no lessons to work through. You are buying working files and the instructions for them.
  • Not a promise of results. These scenarios do paperwork. What that is worth depends on your business, and anyone giving you a number for it is guessing.
  • Not affiliated with Make.com. We build for their platform and are not connected to them in any way.
  • Not decorated with testimonials. There are none yet. When there are, they will carry the names of people who agreed.

Refunds

Fourteen days, no reason required, back to the card you paid with. If a blueprint will not import or a documented step does not work, tell us first and we fix it. If we cannot, you get the refund whether or not the fourteen days have passed.

The full policy is on its own page and reproduced in full on every product page above the buy button.

Who you are buying from

Kettleford is a trading name. The seller is Yazie Henok Alemseged, a sole proprietor in Washington, United States. Name, telephone and both mailboxes are on the business information page, and the same person answers all of them.

Payment is taken at a hosted checkout and processed by Stripe. No card details are entered on this website.

Questions people ask before buying

The ones that arrive by email most often. If yours is not here, hello@kettleford.com gets a reply within one US business day, Monday to Friday.

Do I need to know Make.com already?

A little. You should have opened it once and know what a scenario and a module are. The import itself is four clicks and the guide walks through them. Connecting your own accounts is where the guide spends most of its pages, one module at a time.

Will it work with my shop, form or CRM?

Usually, if it can send a webhook or Make has a module for it. The scenarios are built around ordinary parts: a webhook in, Google Sheets, a mailbox, Stripe, Slack. Each product page lists exactly which apps a scenario touches. If yours is not there, ask before buying. It is a faster answer than a refund.

Do I pay once, or every month?

Once. This is not a subscription, nothing renews, and no further amount is ever taken from your card by us. The Vault includes twelve months of updates, and when that window ends nothing is charged and nothing is taken away.

Will it run on Make.com's free plan?

A useful subset will. Webhook-triggered scenarios only spend operations when something arrives; the scheduled ones wake up whether or not there is work to do. The library's guide has a costs page with a worked example, and there is an article here on counting operations before you switch anything on.

What happens if a blueprint will not import?

Tell us first. A common cause is a module version Make has changed since the blueprint was built, and the guide covers the fix: delete that one module, add it again from the app list, and re-map its fields. If we cannot get it working, you get a refund whether or not the 14 days have passed.

Can I use these for my clients?

The standard licence covers one business, yours, across as many Make.com accounts as it owns. Deploying in a client's own account needs one of the two client tiers: five clients, or the Agency Licence for up to 25. Both hold the same files as The Vault; what you are buying is the right to deploy them.

What if my workflow is not in the catalogue?

Describe it on the custom automation page. You get a reply within one business day: either a product already covers it, or questions followed by a written quote. Nothing is charged until you accept a quote, and nothing is ever charged on this website.

Who actually runs this?

One person: Yazie Henok Alemseged, trading as Kettleford from Washington. There is no company behind the name, no support team, and no pretending otherwise. The business information page has every detail a buyer could want, including the telephone number.

Notes on building scenarios that do not fall over

All writing
A printed flow diagram on paper, one box circled in dark red pencil, with an arrow drawn to a separate box added below it in the margin.

What breaks in a Make.com scenario, and what to do about it

A scenario that has run cleanly for months will eventually meet a duplicate webhook, a timed-out app, or a column someone moved. This is what handling that looks like, section by section, and where it belongs.

Start with one scenario

The cheapest way to find out whether this way of working suits you is a single blueprint at €14.97 EUR. Everything above it contains it, so nothing is bought twice.