Skip to content
PTENES
For Companies · AI Partner

AI comes into the company in pieces: someone buys a tool, a vendor turns up, an idea for automating something appears, the team asks for rules. If nobody owns this, every decision lands on the owner or goes undecided. AI Partner exists so it doesn’t work that way.

Diagnosis

When this can no longer be decided on the side

What happens instead
When this can no longer be decided on the side — What happens instead
We did one AI project and now nobody knows what comes nextThere is now a roadmap, revised every month.
The team uses AI tools the company never approved or evaluatedUsage rules written down, and the tools evaluated first.
Proposals arrive with AI in them and there is no way to judge the priceWe test them against a case of yours before any contract.
There are too many automation ideas and no way to rank themRanked by hours and by risk, not by enthusiasm.
Nobody internal has the time — or the mandate — to decide thisSomeone decides — from outside, and with the context.
What we built works, but it stopped where it was leftIt moves again: a monthly review of what is in production.
Path

Three modes

01

Advisory

We decide with you: roadmap, tools, vendors and rules. Your team or a third party does the building.

02

Delivery

We decide and we build. The common one: this month’s decisions become next month’s system.

03

Dedicated

Reserved capacity every month, for companies with more processes queued than the other modes can carry.

Scope

What stops landing entirely on you

The list of candidate processes, ranked by hours and by risk. Revisited every month, not once a year.

Tested against one of your cases before there is a contract. When the answer is that it is not worth the price, that is the answer you get.

A process in small form, so you can watch it work before deciding to build it properly.

What may go into an outside tool and what may not. Written down, so the team can look it up.

On the processes and tools the team already uses — not a generic AI course.

Hours, what changed, what did not, and what we decided not to do.

Artefact

Monthly report

At the end of the month it has to be possible to see what moved, what was decided and what was not worth doing. Otherwise it is just one more retainer.

Monthly report
HoursWhere they wentProcess by process
ImpactWhat changedMeasured against the starting point
DecisionsWhat was settledTools, vendors, rules
Left outWhat did not moveAnd why
Circuits

What gets out of the way in a month

01

Evaluating a tool

The team asks for a tool → Tested against a real case · AI → Cost, risk and alternative → Buy or do not buy

02

A candidate process

Process proposed → Measured: frequency and hours → Prototype in days · AI → Ships or gets dropped

03

Putting it to use

System in production → Training on the actual work → Usage rules written down → Reviewed the following month

It is not a bucket of hours to invent work with. It is someone taking the decisions that come up and making them move.

Questions

Frequently asked questions

How is this different from hiring a project?

A project answers a question you have already asked. The retainer is for the ones that turn up afterwards — the new tool, the next process, the vendor promising AI. If you only have one question, do the project: it costs less, and we will tell you so.

Is there lock-in?

No. It is monthly and it ends at the end of a month. What we built is yours, with the code and the documentation.

What if there is nothing to do in a given month?

It happens, and we say so rather than invent work to justify the invoice. If it happens two months running, we suggest pausing until there is something.

Do you work with our IT team or over their heads?

With them. The people who know the systems are the ones already there, and without them an ERP integration takes three times as long. Where there is no internal team, we handle it and leave it documented.

Has AI already come into the company, but everything still lands on you?

In 30 minutes we work out whether there is enough work and enough decisions for continuous support to make sense — or whether solving one thing and moving on is enough.

Keep going

One connected set of services