Skip to content
427

How it works

Buying an automation product is a defined project with a clear scope, an agreed price, and a system that you own at the end.

From first contact to delivery

A fixed sequence from first message to a running system.

  1. 1

    Contact

    Tell us which product you are interested in and what you want to automate.

  2. 2

    Requirements

    We go through your current workflow, documents, systems and edge cases.

  3. 3

    Scope & quote

    You receive a written scope and a final project price before any work starts.

  4. 4

    Customization

    The product is adapted to your fields, rules, outputs and integrations.

  5. 5

    Implementation

    The system is installed into accounts and infrastructure that you own.

  6. 6

    Testing

    We test with your real documents and data until the agreed scope is accepted.

  7. 7

    Delivery

    The system is handed over. You remove our access and keep full control.

Your system. Your data. Your infrastructure.

Ownership & handover

Our standard delivery model is customer-owned, customer-paid and customer-controlled. Where a product needs infrastructure, it is set up in your accounts — not ours.

  1. 1You choose an automation product.
  2. 2We discuss your existing workflow and requirements.
  3. 3A final scope and project price are agreed.
  4. 4You create the required accounts and infrastructure under your organization.
  5. 5You temporarily invite us with appropriate access.
  6. 6The product is customized and installed into your environment.
  7. 7Testing and acceptance are completed.
  8. 8After delivery and payment, you remove our access.
  9. 9The automation continues operating without depending on our accounts or infrastructure.

What you typically own

The exact setup depends on the product and your requirements. A typical installation can include:

  • Code repository

    A private repository in your GitHub organization containing the system's code.

  • Database

    A Supabase project for structured records, files and review history.

  • Hosting

    A Vercel team or project that runs the web application.

  • AI API account

    An Anthropic API account used for document and text understanding, billed directly to you.

  • Email and office integrations

    Connections to your Microsoft 365 or Google Workspace environment where needed.

  • Other services

    Any other service the agreed scope requires, always under your ownership.

What you pay for

Project price
A one-time price for customization, installation, testing and delivery, agreed in the quote.
Running costs
Usage of the services in your accounts (hosting, database, AI API) is billed to you directly by those providers.

Tell us what you want to automate

Send a short description of your workflow by email or WhatsApp. We will reply with next steps and questions for scoping.