A company gets three quotes for an AI implementation, all with similar pricing and the same “AI is our specialty” slide. The difference between them only shows up a month after launch, when one implementation handles real data and the other two go back for fixes. Below, we look at what to check instead of the slide deck, so that difference shows up earlier.

A demo is not daily use

Any team can stitch together a demo in a few days where the model answers questions from a curated set of examples. The real test starts the next day, when the system meets real, messy data: low-quality scans, invoice formats nobody anticipated, customers writing in ways no prepared scenario covered.

We wrote more about this in our piece on what actually separates a demo from AI in daily use — the gap between a demo and a working system is fundamental, and most offers on the market don’t address it at all.

So the first question worth asking when choosing a partner isn’t “can you build a demo” — it’s “what happens a month after launch, when data shows up that nobody planned for.”

Questions worth asking a potential partner

Instead of asking generically “do you know AI,” a few specific questions quickly reveal whether a partner is thinking about daily operation or just about the pitch.

  • Do you have your own product where AI runs in daily use, not just client projects? A company that maintains its own AI-based product knows firsthand the cost of errors and support over time.
  • What happens when the model gets it wrong? A good partner has a ready answer: what mechanisms catch bad outputs, and where automation ends and a human takes over.
  • Where exactly does the AI’s suggestion end and the system’s decision begin? If a partner can’t clearly point to that boundary, they probably haven’t designed one.
  • How is the data that reaches the model secured? It’s worth asking directly where data is physically processed and what happens to it after a query is done.
  • Who maintains the system after launch, and what does that maintenance actually look like? A partner with no maintenance plan is, in practice, planning a one-off project, not a long-term partnership.

Red flags

A few signals that should raise a warning flag in conversations with a potential partner:

  • “AI will do it all by itself” — with no mention of oversight, escalation to a human, or control mechanisms.
  • No concrete answer about error handling — vague reassurance instead of a description of the actual mechanism.
  • Pricing that only covers “building” — with no mention of maintenance, monitoring, or updating the model over time.
  • No firsthand experience keeping AI running after go-live — a partner who has never maintained a product built on language models is learning at your project’s expense.
  • All talk about technology, none about process — no mention of process audits, pilots, or success criteria.

Why this matters to us

We hold ourselves to the same criteria we describe above — we implement AI not only for clients but in our own products, in daily use. In Qkwit, AI reads accounting documents, while the actual tax and social security calculations are handled by a deterministic engine, not the model.

In Brokik, our rental management platform running in 25 countries, AI helps adapt an existing document to a change described in plain text, and the account holder approves every entry. These aren’t case studies written for a pitch — they’re systems we maintain and are accountable for ourselves, every day.

What to expect from a good partner

A well-run AI implementation tends to follow a similar shape regardless of industry: it starts with an audit of a specific process, moves through a pilot on real, if limited, data, and only after the system proves stable does it move to a full rollout, with a clear maintenance plan attached. A partner who proposes jumping straight to full automation, skipping the pilot stage, usually hasn’t planned for what happens when something goes wrong.

In short

Choosing an AI implementation partner comes down to one question: does this team know firsthand what maintaining a model looks like month after month, or can they only build a good demo. You can read more about how we approach implementations on our AI page.

Frequently asked questions

Can a smaller team implement AI well, or do we need a large firm?

Company size isn’t the main criterion here. What matters more is whether the team has real experience maintaining AI systems after go-live — regardless of whether that’s a large organization or a small, specialized team.

How long should the process audit stage take before implementation?

It depends on how complex the process is, but a good audit always ends with a concrete conclusion: what can be automated safely, and what needs human oversight.

Should we expect a partner to guarantee the model will never make a mistake?

No — that kind of guarantee is a warning sign, not a selling point. A responsible partner will tell you plainly that models make mistakes, and show you how the system is designed to handle that.

Does a partner need its own AI-based product to implement AI well for us?

It’s not a strict requirement, but it’s a strong positive signal — it shows the partner understands the costs and pitfalls of maintaining such systems from firsthand experience.

Where should we start the conversation with a potential partner?

With a specific process you want to improve, not with the general phrase “AI implementation.” The more concrete the starting point, the easier it is to tell whether a partner actually understands the problem.