Why a vendor-independent AI team got certified on Claude

FLO AX promises its clients vendor independence, and FLO has just become a certified Claude partner. Marián Grofčík, who leads AX, on why he sees no contradiction.

The page that introduces FLO AX makes a promise close to the top: “Vendor-independent by design. No reseller margins, no platform incentives.” This month FLO became a Certified Services Partner in Anthropic’s Claude Partner Network, and I was one of the people pushing hardest for it. If I were reading both from the outside, I would want to know which of the two we mean.

We mean both, and the explanation starts with what I hear from clients, because for most of them the choice of model is the least important decision on the table.

Most companies pick a model before they pick an owner

About half of my calls with clients and prospects open with the same sentence: “We’ve started our AI transformation.” An hour later we usually agree that there is a gap between the progress the company believes it has made and what is happening on the ground. The licences have been bought, three to five enthusiasts are doing impressive things with them, the dashboards look great, and most of the people who received a licence open the tool rarely, if at all.

In the same conversations I hear long debates about which model did better in the latest benchmark, and I have met companies whose first AI step was buying their own hardware to run their own models. For a company at that stage, the model comparison is noise. The first thing I suggest to everyone is to say out loud who in the company owns AI adoption. In smaller firms it tends to land on the owner by default, who builds four useful apps for themselves and assumes the rest of the team is doing the same.

When a client hires us to build, the model becomes our problem

For the people doing the building, the picture flips. Once a client asks us to build something, the choice of model is ours to make, which is where it belongs, and we can only make it well if we know the model in depth.

Our delivery runs on a 90/10 split. A pipeline of specialised agents carries about 90% of the work, from mapping requirements to technical design through the build and continuous testing. The remaining 10% stays with senior people: deciding which problems are worth solving, signing off architecture and security, steering each loop towards value, and making sure people adopt the result. That 10% only works if the person signing off knows how the model behaves inside our pipeline, where it is reliable, where it needs a second look, and what shifts from one release to the next. You can know five models a little or one model very well, and a senior reviewer needs the second.

In Customer Experience, the same principle sits behind our AI-native delivery framework for Salesforce, which runs on Claude and has compressed delivery timelines by up to 40%. When our AX team applied the 90/10 split to our own back office, we shipped a production app in two weeks, where the traditional route would have meant three to six months and a budget of around €100,000. Our back-office manager, who has no development background, tested builds in the morning and saw her changes live within hours.

The split is a target rather than a mantra. On a recent automotive project we landed nearer 80/20. The client’s designers review visual assets against a set of 1,000 to 1,500 rules, and the machine now checks almost all of them. A designer still has to judge roughly one asset in a hundred, and because the assets get reused, we need each of those judgements only once. Deciding where that line sits was the part no agent could do for us.

Certification gets us into the first meeting

“We know the model well” is an easy sentence to write, and clients have read it in plenty of pitches. Ten years in the Salesforce ecosystem have left me with a mild certification habit, because there a partner is judged by how many certified people it can put on a project. So for most of the past year I kept asking colleagues when they planned to take their Claude exam, and in October I finally sat mine, the Claude Certified Architect (Foundations). Today, people across BX, CX, AX and Data hold Claude certifications.

A certificate doesn’t make anyone senior, and I wouldn’t hire on one alone. I know what our people can do because I work alongside them. A client meeting us for the first time has no way of knowing that yet, and a certification is the quickest way to show it. It gets us into the first meeting, where we can demonstrate the rest. The partnership adds what an exam can’t: Anthropic’s partner training and product update calls, so the people reviewing our agents’ work hear about changes to the model from the team that makes them.

Independence describes whose interest we serve

What does vendor-independent mean for us now? Three things, and I’m happy to be held to all of them. We don’t resell model licences or take a margin on what clients pay for them. When another model fits a client’s case better, we say so and build with it, as our Data & AI team already does on projects where it fits. And clients keep what we build, along with the knowledge to run it, so they stay with us by choice.

For many of our Customer Experience clients the question may answer itself. Since Salesforce and Anthropic announced Claudeforce in August, Claude has been running as a reasoning model inside Agentforce, so it arrives in a platform they already use. Convenience is a perfectly good reason to start, as long as someone has already decided who owns the result.

We chose a model for ourselves so that our clients can spend their attention on the decision that matters more: who in their company owns AI, and what it is for.

Written by Marián Grofčík.

Comparing models before anyone owns AI?

That is where many of Marián’s first conversations with clients start. Our AX team will help you name who owns adoption, find the work worth handing to agents, and choose the model for that work on its merits, Claude or otherwise.

Go top

Our growth and expansion are backed by Rockaway, one of the largest investment groups in the CEE region.

© 2026 FLO Group s.r.o., VAT: CZ11983311, Rohanské nábřeží 678/27, 186 00, Prague, Registered in the Commercial Register maintained at the Municipal Court in Prague, File No: C 357494