Skip to content
PTENES
Methodology

We don’t start by asking which AI you want to use. We start by seeing where your team copies, waits, confirms and repeats. Then we decide what to connect, what to build and what is better left alone.

Philosophy

The problem isn’t the ERP. It’s the path to it.

An order arrives by email. Someone opens the PDF, looks up the reference, copies it into Excel, retypes it into the ERP and confirms with the customer. None of this is hard. The problem is that it happens over and over and always depends on someone.

In our own products the pattern was the same, in a different field: the practice happened — a training, a class, a consultation — but the record scattered into loose notes. The technical answer is identical in both cases: structure what comes in, validate it, push it into the right system, and leave the hard decision to a person.

We only automate what pays off — and we show you the numbers before we start.

Framework

Three questions before building

01

Where do you lose time?

We follow one real process from start to finish and see where there is copying, waiting, repetition and dependence on one person.

02

What is worth changing?

Not everything deserves automation. We start with what repeats, costs time and has clear enough rules.

03

What do we get out of the way?

We connect systems, automate steps or build the missing tool. The team is left with less work by hand.

See · Choose · Take out of the way

The six steps

From the work as it is today to work that moves

No giant projects. We start with a circuit your team recognises and make that circuit work better.

We follow the work as it happens today.

We decide where it is worth starting.

We automate, connect or build what is missing.

The new circuit goes into the systems the team already uses.

We check whether the work actually got simpler.

If there is more work to take out of the way, we move to the next one.

Questions

Frequently asked questions

01How long does an automation project take?

It depends on the process, but the first useful result usually lands in weeks, not months. We start with the most expensive, most repetitive process, put it in production, measure it, and only then move to the next one.

02Do we have to change systems?

No. The method is to integrate into what already exists — email, ERP, spreadsheets, internal tools. Replacing systems is expensive, slow, and rarely the thing that solves the problem.

03Does the AI decide on its own?

Not where that is risky. The AI prepares — extracts, classifies, proposes, drafts — and a person approves anything with consequences: a payment, a shipment, a reply to a customer. That is deliberate design.

04What if automating isn’t worth it?

We say so. Some processes cost more to automate than to keep doing by hand, or the volume doesn’t justify it. Saying where the answer is no is part of the check-up.

The same method in our own products

We applied this method to ourselves first. Each product covers one field — padel, team sports, education, therapy — with the same engineering underneath.