Hopefully, my last few posts haven't deterred you from implementing AI in your company. They're meant to educate you, so you can go in with eyes wide open and make informed decisions. If you're still ready to implement, you might be wondering where to start. Do you need to hire a team of PhDs and published AI experts? Are you sunk if that's not in the budget right now? The short answer is no, but keep reading to learn more.

AI Without the PhD: Implementing AI for Companies

A lot of AI advice is written for tech companies with unlimited budgets and teams full of researchers. They talk about building data science departments, hiring PhDs, and creating centers of excellence. That's great if you're Google or a well-funded startup.

But you're probably not. You're a normal company with a normal budget trying to figure out if AI can actually help your business. You don't have a research lab and you don't need one.

Well, I have some good news for you. Normal companies can build real AI capabilities without hiring a single PhD. In fact, some of the most successful AI implementations came from scrappy teams at regular companies who focused on well defined, practical problems instead of impressive credentials.

This is about being strategic with limited resources. About making AI work in the real world with real constraints. The goal isn't to build something that impresses at a conference. It's to build something that delivers value to your business.

The PhD Trap (And Why You Don't Need It)

There's this assumption that if you're serious about AI, you need to hire data scientists with advanced degrees. Companies post job descriptions requiring PhDs in machine learning, years of research experience, and publications in top journals.

This creates a mismatch between what you're hiring for and what you actually need. PhDs are trained to do novel research and push the boundaries of what's possible. Most business AI problems don't require novel research. They require applying existing techniques to practical problems.

PhDs are also expensive and hard to find. You're competing with tech giants who can pay more and offer more interesting problems. And even if you hire one, there's a good chance they'll be frustrated working on business problems instead of research challenges.

What most business AI problems actually require is understanding the problem domain, knowing which existing tools and techniques apply, and having the practical skills to implement and maintain solutions. You don't need someone inventing new algorithms. You need someone who can pick the right tool and make it work.

The companies succeeding with AI aren't necessarily the ones with the most PhDs. They're the ones who matched their talent to their actual problems and focused on shipping useful solutions.

You do need deep expertise for certain problems. If you're doing cutting-edge computer vision research or building novel language models, sure, hire PhDs. But if you're trying to predict customer churn, automate document processing, or optimize your supply chain, you probably don't.

Start with the problem, not the pedigree. Figure out what you're actually trying to solve, then hire for those capabilities.

What You Actually Need First

Clean, Accessible Data (Not Data Scientists)

Yes, I've written about this many times before. Before you hire anyone with "data scientist" in their title, get your data house in order. You can't do AI without decent data infrastructure, and most companies' data is a mess.

Hire data engineers before data scientists. Data engineers build the pipelines, clean up the mess, make data accessible, and create the foundation that makes AI possible. They're less glamorous but more important at this stage.

Getting your data infrastructure right is the foundation everything else builds on. Without it, even the best data scientist will spend all their time fighting with data quality issues instead of solving business problems.

Yes, it may be less flashy than hiring AI experts, but you need to put your ego aside for now. A good data engineer will simply enable more AI capability than a great data scientist working with terrible data.

Business Problem Clarity

You need to know exactly what you're trying to solve. Not "we want to use AI" or "we want to cut cost" but "we have this specific, well-defined problem and AI might be a tool to help solve it."

AI absolutely is a tool, not a strategy. The strategy is solving business problems. AI is one potential way to do that. Start with the problem and do the analysis to determine to whether AI is the right solution.

Ask "where does AI make sense for our business?" not "how do we use AI everywhere?" Most of your business probably doesn't need AI. It's your job to find the specific areas where it creates real value.

People Who Understand Both Business and Technology

The most valuable role in practical AI isn't the pure technical expert. It's the translator who understands both the business and the technology well enough to connect them.

Seasoned business analysts who learn AI tools often beat data scientists who don't understand your business. They know the problems, they know the constraints, they know what would actually work in a production environment. Adding AI skills to that foundation is powerful.

You need a bridge between the technical and business sides. Someone who can translate business problems into technical requirements and technical capabilities into business value. This role is often more important than pure technical expertise.

The Right First Hires (They're Not Who You Think)

If you're building AI capability from scratch, here's what to hire for, in order.

Data engineer before data scientist. They'll build the foundation that makes everything else possible. Without clean, accessible data, you're dead in the water.

Business analyst with some technical proficiency and AI curiosity. Someone who knows your business deeply and is excited to learn AI tools. They'll identify the right problems and understand whether solutions actually work.

Product manager who can work with AI. Someone who can define requirements, manage stakeholders, and shepherd AI projects from concept to production. They don't need to be technical experts, but they need to understand AI capabilities and limitations.

The AI-capable generalist beats the specialist for most normal companies. Someone who's pretty good at data work, understands business problems, can code a bit, and communicates well is more valuable than someone who's brilliant at one specific discipline or niche.

Consider contractors for specialized expertise you need occasionally rather than hiring full-time. You don't need a full-time computer vision expert if you have one computer vision project.

Use consultants strategically for expertise, not execution. Bring them in to set direction, teach your team, and solve specific hard problems. Don't outsource the work you should be building capability for.

Your existing team can probably do more than you think. Before hiring, see if you can upskill current employees who already understand your business. A good employee who learns AI is often better than an AI expert who has to learn your business.

The most effective setup for normal companies is often a small, scrappy team that actually ships things rather than a large specialized department that does mostly planning.

Off-the-Shelf Tools Are Your Friend

Custom AI is expensive and usually unnecessary. Unless you have truly unique problems, someone has probably already built a solution.

The 80/20 rule applies heavily here. Off-the-shelf solutions can handle 80% of use cases. Custom development should be reserved for the 20% where you actually need to build something specific to your business.

There are tools available now for customer service automation, document processing, data analysis, forecasting, recommendations, and dozens of other common business problems. Start there before building anything custom.

Use APIs and managed services when possible. Let someone else handle the infrastructure, maintenance, and updates. You focus on applying the capability to your business problem.

Good enough beats perfect for most business problems. An off-the-shelf solution that's 80% accurate and ships next month is usually better than a custom solution that's 95% accurate and takes a year to build.

The build versus buy decision for resource-constrained companies should lean heavily toward buy. Build only when you've exhausted off-the-shelf options or when the custom solution creates real competitive advantage.

Start with existing tools and graduate to custom development only when you've proven the value and hit the limits of what's available. Don't start with custom.

Start Small and Specific

Pick one clear, contained problem to solve. Not "AI transformation" but "automate processing of customer service emails about returns."

Trying to boil the ocean fails. You spread resources too thin, nothing ships, momentum dies. Small, focused projects with clear scope and requirement actually get finished.

Quick wins build momentum and organizational support. A small success proves the concept, builds capability, and makes it easier to get resources for the next project.

Good starting points for normal companies would be things like:

• Automating one repetitive manual process


• Improving one forecasting task


• Enhancing one customer-facing experience

Focus on success with that specific repetitive process you picked. Once you've implemented that successfully, you can expand. But start narrow.

Small projects also let you learn before the stakes are high. You'll make mistakes, so better to make them on a small project than a company-wide initiative.

You're building organizational muscle incrementally. Each project teaches you more about what works in your environment. Starting small isn't thinking small, it's being smart about how you build capability.

The "Good Enough" Philosophy

Perfect is too often the enemy of done. In normal companies with limited resources, Turning something useful to production beats perfecting something that never launches.

Eighty percent accuracy with something that gets used and delivers value beats 95% accuracy for something that's still in development. The business value comes from using the solution, not from talking about how good the solution will be when it launches.

Put another way, sometimes business value justifies imperfection. If automating a completely manual task saves 20 hours a week even with 80% accuracy, that's valuable. Don't let pursuit of perfection kill practical value.

Manage expectations about AI limitations upfront. Make sure stakeholders understand that AI won't be perfect and that's okay. Set realistic expectations about what "good" looks like.

These scrappy implementations that solve real problems will usually beat ultra polished pilots as well. So, prioritize functionality over sleekness. You can always improve the aesthetics of something that's running later. But, you can't improve something that never launches.

We can't talk about value without hitting on ROI. The ROI of good enough is often better than the cost of perfect as well. Every month you spend perfecting is a month you're not generating savings or increased revenue. Sometimes good enough today must win over perfect eventually, simply because that math works for good enough and not for perfect.

Remember, you can always iterate and improve in production. Deliver something that works reasonably well, then make it better based on real usage and real feedback. Don't wait for perfect to start getting value.

Leveraging Partners Strategically

You don't have to do everything yourself. Strategic use of partners can accelerate capability building.

Outsource specialized tasks you'll only do occasionally. If you need to set up infrastructure once, hiring a consultant makes more sense than building permanent capability.

Use implementation partners who transfer knowledge, not just ones who do the work and leave. The goal is building your internal capability, not creating permanent dependency on a consulting firm.

Managed services make sense for companies not ready to own the full stack. Let someone else handle the infrastructure and maintenance while you focus on using the capability and realizing the value.

Be strategic about what you keep in-house versus what you outsource. Keep the business logic and domain expertise internal. Basically, anything directly supporting your core competency. Outsource the commodity technical work.

I've hit on it before, but I'll say it again. You need to avoid vendor lock-in. Only Use partners to build capability, not to create long-term dependencies on their services. Make sure you're learning and building internal knowledge, not just paying for services.

Finally, the right partners can accelerate your learning. That can translate to accelerated value realization.

Common Mistakes Normal Companies Make

Don't try to copy what tech giants do. They have different resources, different problems, and different constraints. What works for them won't work for you.

Don't hire for credentials instead of capability. The person with the impressive resume might not be the person who can actually solve your problems.

Don't build custom solutions when off-the-shelf would work. This wastes time and money solving problems someone else already solved.

Don't start too big and get overwhelmed. Ambitious transformation initiatives usually fail. Small, focused projects usually succeed.

Don't neglect data infrastructure. Trying to implement AI with bad data infrastructure is like building on sand. The foundation is too unstable.

Don't expect immediate transformation. Building capability takes time. Set realistic expectations about the pace of change.

Don't underestimate change management. Technology is often the easy part. Getting people to adopt new ways of working is the hard part.

You Can Do This

You don't need a research lab to use AI effectively. Normal companies with normal budgets can build real AI capabilities that deliver real business value.

Start practical, start small, and build from there. Focus on solving specific problems rather than pursuing AI for its own sake. Use existing tools before building custom solutions. Hire for practical capability rather than impressive credentials.

Remember, the winners in AI aren't always the companies with the most PhDs or the biggest budgets. They'll be the ones who identified clear problems, picked appropriate solutions, and actually shipped something useful.

Your advantage as a normal company is that you can focus on practical value instead of impressive technology. You don't need to publish papers or win awards. You just need to solve business problems effectively and deliver increased value.

Start small. Be practical. Deliver something. Learn from it. Do it again. That's how normal companies build real AI capabilities.

Interested in working with us? Check out FailingCompany.com to learn more. Go sign up for an account or log in to your existing account.

#FailingCompany.com #SaveMyFailingCompany #ArtificialIntelligence #AIForNormalCompanies #SaveMyBusiness #GetBusinessHelp