Kicking off a Process Automation project

There's no single installation with automation: each project follows a structured process that makes sure we build the right thing, at a cost agreed from the start. This page describes each phase and what we need from you.

Project phases

1. 1

   Discovery call

   A call of around half an hour to understand your business, the tools you use and the tasks you want to automate. No commitment.

2. 2

   Process mapping

   We describe the current process step by step: who does what, with which tools, how often and what exceptions exist. This can be a second call or a screen share while you do the task.

3. 3

   Fixed-price proposal

   We send a proposal covering scope, integrations, timeline, fixed price and maintenance cost where applicable. We only go ahead with your approval.

4. 4

   Access

   We ask for only the access strictly needed to the tools involved, shared securely as described below.

5. 5

   Build

   We build the automation and keep you updated on progress. If something outside the scope comes up, we talk before carrying on.

6. 6

   Testing

   We test with test data and, where possible, in parallel with the manual process until we're sure the results are right.

7. 7

   Handover

   We switch the automation on, give you a plain description of what it does and explain what to do if something goes wrong.

What to prepare

• The list of tools involved (for example invoicing software, email, spreadsheets, CRM).
• Real examples of the process: a typical email, an invoice, a spreadsheet.
• The exceptions you know about: customers with special terms, partial payments, refunds.
• A contact person who knows the process well.

Sharing access securely

We follow the principle of least privilege: we ask only for the permissions the automation needs to work. Wherever the tool allows, we use API keys or dedicated users rather than your personal account.

Timelines

Simple automations involving two or three tools are usually ready within a few weeks. Projects with more integrations or custom code take longer. The exact timeline is always in the proposal. After handover, see the configuration page.