The details are complete
The folder and agreed tasks are created in the right place.
The project and how we work together
Describe the recurring task in your own words. Together, we’ll work out whether it can be automated and what the project needs.
How we get started
Tell me in your own words what is done manually and which apps are involved.
You receive a written proposal explaining what I will build and how we will check that it works.
I build the automation in your company’s own environment. We check the agreed scenarios before it goes live.
You receive the automation, instructions and guidance on what to do if something goes wrong.
How do we check that it works?
For the project setup example, we would use a form, Google Drive and Notion. Before building, we would agree on what should happen in each scenario.
The folder and agreed tasks are created in the right place.
The work stops as agreed and the missing detail is identified.
We check that the same project is not created twice.
The person in charge is notified. The instructions explain how to continue.
These are proposed checks. This example has not been built or run here.
Before you decide
You do not need to know how to build the automation. You need your company’s own n8n Cloud account and a person who receives the instructions, checks results and follows up on any failure notifications. Before we agree, I explain which accounts and access permissions are needed.
A good starting point is a recurring task with steps that can be clearly described. Examples include moving form details to a list or preparing a project. Suitability depends on the current task and the apps you use.
Building an automation for one agreed task, the agreed setup in your n8n Cloud account, testing, instructions and one limited round of fixes. Up to three apps are included. The final scope, price and correction period are confirmed in writing.
Subscriptions and usage fees for n8n and any other required services are separate. For example, an AI service may charge for usage. We review the required services before the project starts.
Before building, we agree on how failures will be reported and who receives the notification. We check the agreed failure scenarios and I write instructions for continuing. The delivery includes one agreed round of fixes. Later changes require a separate agreement.
This service is a defined build and setup project. Ongoing maintenance, server administration and on-call support are outside its scope. After delivery, your company is responsible for use, its own accounts and following up on failure notifications.
The first project is limited to a task that can also be handled manually if it stops. This service does not cover maintaining self-hosted n8n, processing sensitive personal data or running critical business operations around the clock. Actions affecting payments, publishing or clients are assessed separately, with human approval agreed where needed.
I do not promise a specific saving in advance. We record the current work involved and later compare it with the work, corrections and running costs after setup.
Who you’ll work with
At AIGhostTools, I build automations for recurring business tasks. I want you to understand what is being built and how to use it.
We start in writing. You describe the task and I work out the implementation. I also use AI tools while building, and I am responsible for reviewing the work and carrying out the agreed tests.
Tell me what you need
Tell me which task repeats, how often it happens and which apps you use. No technical terms needed.
I’ll use your description to assess whether the task fits this service. You receive a proposal before we agree to start.
hello@aighosttools.comYou can also email me directly.