When you're evaluating a consultant or agency to help with AI implementation, one question matters more than you might think: how do they make money? If they make money by selling you software licenses, their incentive is to get you to buy software. If they make money by charging a fee for advice, their incentive is to give you good advice. These incentives are not aligned, and they matter far more than you'd expect.

TimeCraft Advisory doesn't sell AI tools. We don't resell software licenses. We don't have revenue-sharing agreements with vendors. We don't earn commissions when you buy from a particular platform. We make money by charging fees for our assessment work, our recommendations, and our implementation support. This means our incentive is exactly what you want it to be: to help you make the right decision for your organisation, which might be to use AI or might be to not use AI, or might be to use a very specific tool that solves your problem efficiently with minimal complexity.

The Commission Problem in Software Consulting

Vendor-affiliated consultants face a fundamental conflict of interest. If they recommend a solution from a vendor they have a partnership with, they earn a commission or get credit toward their own licensing fees. If they recommend an independent tool that's genuinely better for your situation, they earn nothing. Or worse, they actively lose a deal because they're pushing the vendor they're affiliated with and you choose a competitor instead.

This problem shows up in predictable ways. Vendor-affiliated consultants tend to recommend their affiliated vendor's tools even when better alternatives exist. They emphasise the vendor's strengths and downplay or ignore its weaknesses. They make aggressive projections about how much value the tool will deliver. They minimise the effort required to implement it successfully. They're often genuinely unaware that they're doing this because they've rationalised the conflicts away. They work for the vendor. The vendor's tool is legitimately good. Of course it's the right recommendation for this client. What could possibly be unfair about that?

The problem becomes visible when an organisation brings in an independent party to review the decision afterwards. The independent reviewer says: "This tool is fine, but there's a much lighter-weight alternative that would have worked better for your situation and cost a quarter as much." Or: "This tool is capable but much more complex than you actually need. You could have solved this problem in half the time and at a third of the cost with a simpler option." Or: "Your vendor-affiliated consultant deliberately glossed over the implementation complexity and the integration headaches because they were motivated by the commission."

The worst cases are where the recommended tool genuinely doesn't fit. A vendor-affiliated consultant recommends an enterprise-grade solution requiring six months of implementation and significant customisation when the client actually needed a simple, straightforward tool that could be operational in weeks. The commission is large, so the incentive to recommend the heavy solution is strong. The client ends up overpaying, over-engineering, and spending far more time and money than necessary on implementation.

Why Independence Matters for Recommendations

When we assess your organisation and make recommendations, we have no financial incentive to recommend a particular vendor. We're genuinely going to recommend whatever solves your problem in the most practical, cost-effective way. If your problem can be solved with existing spreadsheet skills, we'll tell you that. If your problem requires a simple off-the-shelf tool, we'll recommend the simplest option that works. If your problem genuinely requires a more sophisticated platform, we'll explain why and recommend the best option regardless of whether we know the vendor or not.

This independence extends to the honest assessment that many organisations don't need AI at all, or don't need it yet. They have more fundamental issues to solve first. A company with poor data quality doesn't need a sophisticated data analytics tool. It needs to fix its data. A company that doesn't have basic process documentation doesn't need AI to automate processes. It needs to standardise the processes first. An organisation that's constantly changing its systems doesn't need AI that requires careful configuration and training. It needs to stabilise the environment first.

We've told clients "you're not ready for the solution you're asking about" more than once. We've recommended that they solve simpler problems first, build their team's capability, improve their data, and come back to AI in six months when they've cleared the foundation. This costs us nothing, because we're not earning commissions. It benefits our client enormously because they avoid wasting money and time on a solution that won't succeed in their current context. They come back six months later, ready to actually implement successfully, and the experience builds trust.

The Business Model Shapes Everything

Our business model as an independent consultant shapes how we work in visible ways. First, we do thorough assessment work before making recommendations. We could quickly recommend solutions and move to implementation. That's faster and cheaper for us. But thorough assessment takes time, and we invest that time because that's how we make decisions defensible. We interview your team, map your processes, understand your technical environment, and identify your constraints before we say what should happen.

Second, we're candid about limitations. If a tool has a weakness, we tell you about it. We don't try to convince you the weakness doesn't matter or that you can work around it. We tell you it exists and you decide whether you can tolerate it. If the tool is 90% right but fails on 10% of cases and you need 100%, we say so. You might still choose the tool if that 10% is acceptable, but at least you know.

Third, we're willing to recommend that you don't buy something. This isn't just theoretical. We regularly recommend against implementing the solution the client is considering. Sometimes it's because a simpler solution exists. Sometimes it's because they're not ready. Sometimes it's because the cost versus benefit doesn't justify it. We could recommend it anyway and earn the implementation fees, but that would be selling them something they don't need.

Fourth, we own the implementation risk. If we recommend a solution and it doesn't work as advertised, our reputation is damaged and future clients trust us less. A vendor-affiliated consultant has some insulation because the vendor shares responsibility. We have no such insulation. Our recommendations are directly tied to our reputation.

How to Evaluate Consultant Independence

If you're working with a consultant on technology decisions, here's how to evaluate whether they have conflicts of interest. Ask directly: "Are you compensated differently based on which tool I choose?" Ask: "Do you have revenue-sharing agreements or commissions with any of the vendors you recommend?" Ask: "If I choose a different vendor than the one you initially recommended, does your implementation work continue the same way?" Ask: "Have you ever recommended against a vendor or advised a client not to buy something?"

The answers will tell you a lot. A consultant with no conflicts of interest can answer clearly and directly. A consultant with conflicts will hedge, qualify, or try to convince you the conflicts don't matter. They might say: "Our partnership with this vendor means we can get you a better deal and better support." That's possibly true, but it's also a reason for them to recommend that vendor regardless of whether it's actually the best option for you.

You can also evaluate how the consultant charges. Fee-based consulting means the consultant's revenue is independent of what you buy. Vendor-affiliated consulting means the consultant's revenue depends on licensing fees or implementation services tied to particular vendors. The incentives are different and they matter.

What Independence Looks Like in Practice

When we assess an organisation, we map your processes, understand your constraints, identify your goals, and then recommend solutions. Some organisations need best-of-breed platforms assembled together. Some need a single integrated platform. Some need custom development. Some need simple manual processes before they need tools. Some need to clean their data before they can use it effectively. Some are not ready for automation because they haven't standardised their processes.

We also help you understand implementation complexity. A tool that's 80% right for your situation is a big win. A tool that's 100% right but requires six months of implementation and significant custom configuration might not be worth it. A tool that's 70% right but needs workarounds and custom code is often a bad choice even if it theoretically covers what you need. We help you think through these trade-offs honestly.

Finally, we're transparent about the fact that this approach costs you money. Thorough assessment, honest recommendations, willingness to say "don't buy," and implementation that prioritises success over quick revenue means we charge more for our time than consultants who just sell you whatever tool they're affiliated with. You're paying for independence and good judgment. That's fair. What's not fair is commission-based recommendations disguised as independent advice.