Skip to content

DappaSol / Services / Business Automation

By , Founder · Updated November 2026

The handover charter: who owns what.

Before you pay anyone to automate part of your business, get seven answers in writing. These are mine. The clauses further down are written so you can copy them into any vendor's agreement, including a competitor's.

In short

  • Everything runs in your accounts, in your name, from day one, and is handed over in full once the build is paid.
  • You can change, pause or remove anything after handover without asking.
  • You get the list, the logins, a readable log, a one-page handbook per automation and an alarm for when a job has not run.
  • If you stop paying for ongoing support, everything built and paid for keeps running.
  • The 30-day warranty starts the day the written job passes.

1. Whose accounts does it run in?

Yours. Accounts and data are in your name from day one, and everything I build is handed over in full once the build is paid. I work as an invited user inside the tools you already pay for, and you can take that access away whenever you like. Removing it before the written job passes, or during the warranty, pauses the 21-day guarantee and the warranty.

Logins and keys are created in your accounts, in your name, and they stay there.

Ask any vendor: "If we fall out tomorrow, what do I have to ask you for?" The right answer is nothing. For us that is true from the day the build is paid. Before that, the accounts and logins are still yours.

2. Who can change it?

You, or anyone you name. One person on your side holds admin rights to every tool involved. After handover you can change, pause or remove anything without asking me.

Each automation also has one named person on your side. They get its alert, they can pause it, and their name is on its handbook page. An automation that belongs to nobody is the one that sits broken.

One honest limit: if you change the tools after handover, I cannot promise the results still hold. That is written into what I do not promise, below.

3. What do you get at handover?

The listEvery automation, one line each.
The loginsEvery login, in your name.
The logEach automation writes a log you can read. It is the same log the guarantee is checked against.
The handbookOne page per automation, in plain English: what starts it, what it does, where it runs, how to pause it, and what to check first if it stops.
The alarmA check on whether each job ran when it should have. If it has not, the named person gets an alert. The alert tells a person. It does not fix anything by itself, so the handbook says how to pause the job and what to check first.

The alarm is on that list because of my own mistake. One of the automations this studio runs on stopped on 4 September 2026 and nobody noticed until 10 October. It failed without telling anyone. Every build I ship now gets the check. The whole story is here.

4. What happens if you stop paying us?

Everything built and paid for keeps running.

Autopilot is the studio keeping your automations running and expanding them, from $500 per 4-week cycle. It is optional and never required to keep what I built working. The subscriptions to your own tools are in your name and paid by you, at whatever those tools charge. I do not mark them up.

5. What does the warranty cover?

The 30-day warranty starts the day the written job passes. In those 30 days, faults in what I built get fixed at no charge. Changes you make to the tools, and changes a third-party tool makes to itself, are outside it. After the 30 days a fix is a fixed price, agreed before the work.

The written job is one sentence with a number in it, agreed before the first payment. For example: "Every website enquiry gets a reply within 2 minutes and lands in the CRM." (A CRM is the system that holds your customer list.) "Doing the job" means it meets that sentence on real work for 7 days in a row, counted from the automation's own log. The 7-day run is inside the 21 days.

Live and doing the job in 21 days, or I keep building free for up to 30 more days. If it still has not passed, either side can walk and nothing more is due.

The conditions sit on the automation page: access to your tools by day 2, answers within 2 working days, and a written job that does not change.

6. What I will not automate

  • Answers to your customers made up by a model with nobody checking, unless you approved that exact job in writing. Your reputation is the business. An acknowledgement a person wrote once can send itself. A real answer gets a person. Ours finds the conversations and queues them, and a person writes every reply.
  • Money that moves unseen. No payment and no invoice goes out without a person seeing it first. Our own invoices are the honest example: previewed on a phone on the 28th, with three days to stop them before they send on the 1st.
  • A job nobody does the same way twice. If two people on your team do it differently, it needs agreeing before it needs automating.
  • AI where a plain rule will do. Plain rules are cheaper and do not make things up.
  • Anything that can fail without telling you. If I cannot put an alarm on it, I do not build it.

Where your approval sits

Before the build, the written scope lists every step that waits for a person's yes. Two are on every list. No payment and no invoice goes out without a person seeing it first. Nothing a model writes goes to your customers without a person checking it, unless you approved that exact job in writing.

7. What I do not promise

  • Revenue or headcount cuts. An automation gives hours back. The person who does the job today is in the scoping conversation, and what changes for them is your decision.
  • Results from tools you change after handover.
  • That it never breaks. Mine have. That is why the alarm is in the handover.

Copy these clauses

These are the terms above, written so they can go into any vendor's agreement, ours or someone else's. They are plain-English working terms, not legal advice. Have whoever reads your contracts read these too.

1. ACCOUNTS. Every automation runs in accounts registered to the client, in the client's name, from day one. What the vendor builds is handed over in full once the build is paid. Logins and keys are created in the client's accounts and stay there. The vendor works as an invited user. The client can remove the vendor's access at any time. Removing it before the written job passes, or during the warranty, pauses any delivery deadline the vendor has given and the warranty in clause 6.

2. CHANGES. A named person on the client's side holds admin rights to every tool involved. Each automation has one named person on the client's side who receives its alerts and may pause it. After handover the client may change, pause or remove any automation without the vendor's permission.

3. HANDOVER. At handover the client receives: (a) a list of every automation, one line each; (b) every login, in the client's name; (c) a log for each automation that the client can read; (d) a one-page handbook per automation in plain English, covering what starts it, what it does, where it runs, how to pause it and what to check first if it stops.

4. SILENCE. Each automation has a check that alerts a named person when a job has not run.

5. STOPPING. If the client stops paying for ongoing support, everything built and paid for keeps running. Ongoing support is optional and is never required to keep what was built working. Subscriptions to third-party tools are held and paid by the client.

6. WARRANTY. For 30 days from the day the written job passes, the vendor fixes faults in what the vendor built at no charge. Changes the client makes to the tools after handover are outside the warranty. Changes a third-party tool makes to itself are also outside it.

7. THE WRITTEN JOB. Before the first payment, each automation has one sentence with a number in it that says what it must do. The written job "passes" when the automation meets that sentence on real work for 7 days in a row, counted from its own log.

8. PEOPLE. No automated message goes to the client's customers without a person on the client's side having written or approved it, unless the client approved that exact job in writing. No money moves and no invoice sends without a person seeing it first. The steps that wait for a person's approval are listed in writing before the build.

See it on your own week

Send me three jobs you repeat every week. Within one working day you get one page back: the one I would automate first, what would replace it, and one I would leave alone. No call, no charge, five a week.

To see what the paid map looks like, read the sample Game Plan.

FAQ

Can I use these clauses with another vendor?

Yes. That is what they are written for. If a vendor will not sign the accounts clause or the stopping clause, you have learned something useful before paying.

Is this a contract?

No. It is the set of plain-English terms that go into the one-page agreement we sign before any money moves. It is not legal advice.

What happens if something breaks after the 30 days?

You have the handbook, the log and the logins, so you or anyone you choose can fix it. You can also ask us for a fixed price for the fix, or put the automations on Autopilot, from $500 per 4-week cycle. Autopilot is optional.

Who pays for the tools the automation runs in?

You do, directly, in your own name. We do not resell or mark up third-party tools.

Do you use AI in every build?

No. Where a plain rule does the job we use a plain rule. AI earns its place only where something has to be read or written, and nothing a model writes goes to your customers without a person checking it, unless you approved that exact job in writing.

What happens to the person who does the job now?

The person who does the job today is in the scoping conversation. What changes for them is your decision, and we do not promise headcount cuts. An automation gives hours back. What those hours go to is yours to decide.