Services

Pick the problem that sounds like yours. Each one says what I would do about it, and whether you can start today. If yours is not on the list, we can still talk it through.

Odoo

Available now

Odoo made to fit the business it runs, and kept fitting through the next upgrade.

The problem

What I do about it

It does not do what the business actually does.
Odoo configured and extended to match how the business actually runs.
You are moving off an older system and its history has to come with you.
Migration from the system you are leaving, with the history that has to survive it.
Work already done has made the next upgrade hard.
Version upgrades, and customisations written to survive the next one.
The customisations cost more in maintenance than they saved.
Code review of what your team, or another supplier, has already written.
It is slow, or it falls over.
Performance analysis and load testing, for an instance that is slow rather than wrong.
The same thing gets entered twice.
Integrations, for when the answer lives in another system.
Email, single sign-on and the rest of the plumbing nobody wants to own.
The technical configuration nobody wants to own: email, single sign-on, access rights.

Odoo in full: prices, and how an engagement starts

Software away from Odoo, built from nothing or joined where it already runs.

The problem

What I do about it

The software you need does not exist, and nothing off the shelf is close.
New applications, from the first line to the machine they run on.
What you have can no longer be changed without breaking something else.
Work inside a codebase that already exists, including one somebody else left behind.
The person who wrote it has gone, and nobody wants to open it.
Documentation and handover, because your own team carries this afterwards.
Every release is an event, so releases happen rarely.
The delivery pipeline: tests, builds, releases, and a way back when one goes wrong.

Fullstack development in full: prices, and how an engagement starts

AI

Available now

Putting models where they earn their place: in the delivery pipeline, in the work a team repeats every day, in retrieval over your own documents.

The problem

What I do about it

Everyone is asking what you are doing about AI, and nobody has said what it is for.
One use picked because it pays for itself, and the honest answer when a script would do.
There was a pilot, and nobody has opened it since.
Models inside the delivery pipeline: review, triage, and the checks nobody has time to run.
The answer is somewhere in your own documents, and nobody can find it.
Retrieval over your own documents, so an answer cites something you can open.
A team spends its week on work that never varies.
The work a team repeats every day, automated where a model is genuinely better than a script.
Nobody will sign off on where the data goes.
Your data stays where you keep it, and that is written down before anything is built.

AI in full: prices, and how an engagement starts

Audit

In development

Software quality, CI/CD, processes, security and search visibility, reviewed and written up as findings you can act on.

The problem

What I do about it

Security is somebody's job in principle and nobody's in practice.
Security: the assessment, and the fixes ranked by what leaving them costs.
The tests are green, and nobody trusts them.
Code quality and test coverage, read against how often the code actually changes.
A release goes out, and going back is a conversation rather than a button.
Delivery: how a release gets out, and what happens when one has to come back.
The site is live and search engines are not finding it.
Search visibility and accessibility, audited the same way and reported together.

Hosting

Planned later

Deployment, hosting and scaling for applications, in the cloud and on your own machines.

The problem

What I do about it

Something has to run this, and nobody wants to be the one holding the pager.
Deployment and scaling, in the cloud or on machines you own.
Deploying is a person following notes, so it happens on a good day.
Releases that run the same way every time, so deploying stops being an occasion.
When it goes down, finding out why takes longer than fixing it.
Backups, monitoring and the unglamorous parts that only matter at three in the morning.

Learning

Planned later

Online courses on the subjects this work runs on.

The problem

What I do about it

Your team keeps buying the knowledge instead of holding it.
Courses on the subjects the work above runs on, taught from delivery rather than from slides.
The work comes back because nobody was taught to carry it.
Teaching from the delivery itself, so the team taking it over has already done it once.
What training exists is a slide deck nobody has opened twice.
Material your team keeps, so a new joiner starts where the last one finished.

Three ways to work together

Whichever service you start from, the engagement takes one of three shapes. In all three, what I make for you is yours once it is paid for.

Prices exclude VAT.

Retainer day rate, by days a week

3 days a week: €720 a day, €8,640 to €10,800 a month.

Days a week

Advisory and retainer work is billed in arrears on the 1st of each month, for the hours or days worked, from the timesheet. A retainer's reserved days are the least a month is invoiced, and changing or ending one takes a month's notice.

Start with the problem, not with the proposal

A written scope comes back within two working days, with its assumptions and its exclusions stated. It costs nothing, and it is yours whether or not you hire me.

Tell me about your project, or the problem you want solved.

Or write to info@avanserv.com, and I will come back to you with a scope.