Package and subscription terms

1. What is sold, in one line each

• Kit ($49, one-time): the first blueprint’s n8n workflow file, a setup guide for your tools, the message scripts and the prompts, on a page that stays yours for twelve months. You import and run it.
• Install ($249, one-time): the first blueprint put into your own accounts by us, without a call, within two working days of your granting access; templates rewritten in your voice from messages you send us; a recorded walkthrough; 30 days of fixes.
• Package ($490, one-time): all three blueprints for your role, adapted to how you work and installed in your accounts, live in about a week, with a recorded walkthrough, a one-page runbook and 30 days of fixes.
• Managed automation ($197–297 a month): one standard blueprint set up in your tools and run for you — hosting or deployment to your own account, monitoring, fixes when a connected API or model changes, small improvements inside the blueprint’s scope, and a monthly report. Cancel monthly.
• Custom build (from $2,000, quoted): a workflow built to your own rules under a written scope that defines “done”, delivered into your accounts to keep, with documentation and 30 to 60 days of fixes. The scope document is the contract for a custom build; these terms fill in what it does not say.

Each package page says which three blueprints it contains and where the standard version stops. Anything not on the page is not included; if it matters to you, ask before paying and we will answer in writing.

2. Prices, payment and what is billed by others

Prices are in US dollars and are the ones shown on the page at the time you pay. Kits, installs and packages are paid once, by card, through Stripe. Managed automations are billed monthly in advance from the day you subscribe; you can cancel at any time from the Stripe receipt or by replying to any of our emails, and the cancellation takes effect at the end of the paid month.

Model usage (for example Claude API tokens), SMS, enrichment credits and any paid n8n, Make or Zapier plan are billed by those providers to your own accounts. We do not resell them, mark them up, or hold them. Before you pay we tell you the typical monthly amount for your case; it is usually tens of dollars.

3. When things arrive

• Kit: the link to your kit page is in the confirmation email, sent when your payment is confirmed, usually within a minute.
• Install: the access checklist is in the confirmation email, sent when your payment is confirmed; the blueprint is live in your accounts within two working days of your granting the access on it. There is no call; questions go by email. A live walkthrough is optional and only if you ask.
• Package: the access checklist for all three blueprints is in the confirmation email; the package is live within about a week of your granting access, with a recorded walkthrough and a one-page runbook. No call.
• Managed automation: an access checklist on payment; setup within five working days of receiving access; first runs in approval mode until you tell us to let it run.

Timelines depend on you granting access. If access takes longer, the timeline moves by the same amount and nothing else changes.

4. What “30 days of fixes” means

For installs, packages and custom builds, the 30 days start on the day the automation goes live in your accounts. During that period we fix, at no charge, anything we installed that stops doing what the blueprint page or the scope document says it does — including breakage caused by a connected tool or model changing its API — and we correct mistakes in how we set your rules, templates or credentials.

Fixes do not include new features, new tools or channels, changes to your own rules after go-live, work caused by you changing or removing credentials, or problems in your own accounts and data. Those are quoted separately or covered by optional maintenance ($99–250 a month). Managed automations include fixes for as long as you subscribe.

To report a problem, reply to your confirmation email with the record it got wrong. We acknowledge within one working day.

5. The credit rule

For 30 days after you buy a kit, its full price is credited against an install; for 30 days after an install, its full price is credited against the package for the same role; for 30 days after a package, its full price is credited against a custom build. The credit arrives as a single-use code in your confirmation email and is applied at checkout. Credits are not transferable, not redeemable for cash and not combinable with other discounts.

6. Refunds

• Kit: full refund within 14 days if you cannot get the template running and we cannot get it running for you by email. Once we have helped you get it running, or after 14 days, the kit is yours and non-refundable.
• Install and package: full refund if, once you have granted access, we cannot connect the blueprint to your tools for a reason on our side (the blueprint does not do what the page says, or we cannot make it work with a tool the page lists). Once the automation is live in your accounts, the fee is earned and the 30 days of fixes apply instead. If you cancel before granting access, we refund in full less any card fees Stripe does not return.
• Managed automation: the first month includes setup and is not refundable once setup has started. After that, cancel any time; you are not charged again and you keep the workflow files.
• Custom build: as set out in the scope document. Unless it says otherwise, work done to date is charged pro rata if you stop the project.

To ask for a refund, reply to your confirmation email. Refunds go back to the card you paid with, within ten working days.

7. Your accounts, your data, your files

Everything runs in your own accounts: your CRM, your email, your ledger, your n8n. You grant us the narrowest access that lets us set the automation up, and you can revoke it at any time; we delete any credential we hold when the work is handed over or the subscription ends. We do not copy, keep or train on your data. Model calls go to an API under terms that do not use your data for training, and where a zero-retention arrangement is available we use it.

You own the workflow files we install and everything they produce. When a managed subscription ends we give you the files. Kits and the material on your kit page are licensed to you for your own use; they are not for resale or redistribution.

8. What you are responsible for

• Giving us access that is yours to give, and telling us about anything the automation must not touch.
• The content of messages sent in your name. The automations start in approval mode so that you see them first; what you approve is yours.
• Consent and compliance for your own messaging — for example texting consent, fair-housing rules, employment and data-protection rules in your jurisdiction. The blueprints carry guardrails for these; they do not replace your own judgement or your professional obligations.
• Keeping the tools the automation depends on in service and paid for.

9. What we do not promise

We promise that what we install does what its page says. We do not promise business outcomes — more leads, faster hires, fewer errors — and figures on the site labelled “worked example” are illustrative, not a client’s results. Automations make mistakes, which is why every one we install has an approval step and a place where uncertain items go to a person. Third-party tools change; that is what the fixes and maintenance are for.

10. Liability

To the extent the law allows, our total liability for anything arising from a kit, install, package, subscription or custom build is limited to the amount you paid us for it in the three months before the claim, and we are not liable for indirect or consequential loss. Nothing here limits liability that cannot be limited by law.

11. Changes and contact

We may update these terms; the date at the top is the current version, and the version in force when you paid applies to that purchase. Questions before or after buying: [email protected]. The general Terms of Service and Privacy Policy apply to the site itself.