Top Generative AI Trends Shaping the Future of Business in 2026
![]() |
| Top Generative AI Trends Shaping the Future of Business in 2026 |
Introduction
AI can help an employee finish a report in minutes instead of an hour. That’s useful. But does saving time actually make a business perform better? Honestly, I don’t think it does, at least not automatically.
Here’s the thing: when thousands of employees use the same tool, you’d expect costs to drop and service to improve. It isn’t that simple. McKinsey’s August 2026 global survey found that 80% of respondents said AI had improved their personal productivity (that’s a big number), yet only 37% said it had contributed to their organization’s earnings before interest and taxes (EBIT). That’s a wide gap, and it hasn’t moved much since last year.
Now, where does the time go? Imagine a support team of 20 agents using AI to draft 200 replies a day. Each answer appears in seconds. Then comes the catch: someone has to read it, fix the tone, and double-check the refund policy it quoted. If that review takes five minutes per reply, the “time saved” is gone, and you’ve added a new task to everyone’s day. Sound familiar?
That’s my problem with judging AI by its features. I’d rather ask two simpler questions: does the tool solve a real problem, and can you measure the difference? So in this article, I’ll walk you through the generative AI trends shaping business in 2026, show how companies are using them, and flag the risks you’ll want to manage. I’ll also cover how to pick the right applications, protect your data, and decide whether the results justify the cost. Let’s start with what’s actually changing.
Watch the Video: Generative AI Trends in 2026
Watch this video for a quick overview of the key generativeAI trends shaping the future of business in 2026.
1. The Generative AI Landscape in 2026
Generative AI has moved well beyond chatbot experiments. Businesses now use it for software development, customer service, marketing, research, and internal operations. But here’s the part that surprises people: powerful tools haven’t automatically meant higher profits. So what’s going on?
McKinsey’s 2026 global survey gives part of the answer. Adoption is deepening, with 44% of respondents saying their organizations were scaling AI across the enterprise, up from 38% in 2025. The hard part is what comes next: turning individual productivity gains into company-wide results. Only 37% of respondents said AI had contributed to their organization’s earnings before interest and taxes (EBIT). I’d call that the real story of 2026.
1.1. The Current State of Generative AI in Business
In 2026, generative AI is becoming part of everyday workflows. It isn’t a separate tool you open now and then anymore. Companies use it to draft documents, summarize long reports, generate code, analyze customer feedback, prepare marketing materials, and pull answers from internal knowledge bases.
The technology is also moving past simple prompts. AI agents can carry out several steps toward a goal, use connected tools, and work inside existing business systems. They might process requests, investigate a technical issue, or coordinate a routine workflow. Reliable? That depends on the task, the information available, and the safeguards around the agent. I wouldn’t hand one the keys without all three.
Larger companies are moving faster. Among respondents from organizations with annual revenue above $1 billion, 40% reported scaling AI agents in at least one function, compared with 27% the previous year. For smaller organizations, the figure stayed at 22%.
Technology isn’t the whole picture, though. Integration costs, training, security, output quality, and accountability all shape the outcome. An assistant can write a decent first draft in seconds (that part’s easy). But someone still has to verify the facts, fix the errors, and check that the result meets company standards.
So the challenge isn’t finding an AI tool anymore. It’s deciding where the technology improves a process, and how we’ll know it’s worth the money.
1.2. What Has Changed in Generative AI Since 2024?
Honestly, the biggest change is the move from experiments to real implementation. Today’s systems can handle different kinds of information, connect to software tools, and replace tasks that once needed several applications or manual steps.
Stanford HAI’s 2026 AI Index shows how fast this is happening. Global corporate AI investment more than doubled in 2025, and private investment in generative AI grew by more than 200%. Generative AI also reached 53% population adoption within three years, faster than the personal computer or the internet. Impressive? Sure. But notice what these numbers don’t tell us: investment and consumer adoption aren’t the same as business profitability.
The second shift is agents and workflow integration. Instead of just writing text or answering questions, AI systems now perform sequences of actions and help developers write code. In McKinsey’s survey, nearly one-third of respondents said their organizations had decided against buying at least one software product or feature, because AI coding agents could build it internally. That’s a big deal. It suggests generative AI may change not only how employees work, but also how companies choose and build software.
More capability doesn’t mean less need for human judgment. AI answers can still be wrong, and agents that can access data or take actions add risk. In my view, review, testing, and tight permissions matter more as autonomy grows, not less.
Put simply, AI is easier to build with, and easier to plug into existing systems, than it was two years ago. Whether it works reliably? We’re still proving that, task by task.
1.3. Business Adoption Rates and Market Penetration
Adoption statistics are tricky. Some surveys ask whether an organization uses AI at all; others ask about a particular function, or whether deployment has reached enterprise scale. They measure different stages, so don’t treat them as interchangeable.
Stanford HAI’s 2026 AI Index, citing survey data, reports that 88% of organizations used AI in at least one business function in 2025, and 70% used generative AI in at least one function. That shows how far AI has spread. It doesn’t say much about how deeply, or how often, people use it.
McKinsey’s measure is stricter: 44% of respondents said their organizations were scaling AI across the enterprise, up from 38% in 2025. Think about what that means. A company can use AI in one department without wiring it into wider operations, setting consistent governance, or showing a financial return. That’s not scaling; that’s a pilot with a good press release.
Company size matters too, as the agent figures above show. Larger organizations often have more budget for infrastructure, specialists, and enterprise-wide rollouts. Smaller businesses can use accessible cloud tools, but they’re up against tighter limits on budget, expertise, data quality, and integration with existing software.
So how should you measure your own adoption? Don’t rely on one number. Track how many functions use AI, what share of employees use approved tools, how many workflows you’ve redesigned, and what’s changed in cost, quality, speed, customer satisfaction, or revenue.
Adoption tells you who’s using AI. Only measurement tells you whether it’s working.
1.4. AI Regulation and Compliance in 2026
Once generative AI is embedded in operations, governance isn’t optional; it’s part of the implementation. You need to know what your systems can do, what information they process, how outputs are used, and who’s responsible when something goes wrong.
The EU’s AI Act is the clearest example of a risk-based framework, and its rules arrive in stages. Prohibited practices and AI literacy duties have applied since February 2025, and obligations for general-purpose AI models since August 2025. Then came a twist. The Digital Omnibus on AI, in force since July 2026, pushed the high-risk requirements for stand-alone systems (think hiring or credit-scoring tools) to 2 December 2027, and for AI embedded in regulated products to 2 August 2028. Transparency obligations and enforcement powers over general-purpose models, however, still applied from 2 August 2026. Which rules affect you depends on your role and the systems you use, so check the European Commission’s official timeline.
If you operate across borders, expect several overlapping regimes: data protection, confidentiality, intellectual property, consumer protection, and sector rules. The EU framework is a useful reference point, but other jurisdictions have their own requirements. Your obligations depend on the intended use, and on whether you’re a provider, deployer, or customer.
Good governance starts before you deploy at scale. Set clear policies on which tools employees can use, what they can enter, how AI-generated content gets checked, and when a human must approve the result. Review vendor terms, data retention, and access permissions. And have a plan for reporting incidents; you’ll need it sooner or later.
Compliance isn’t a one-time task. Systems, processes, and rules keep changing, so regular reviews help you catch new risks and update policies. Companies that pair clear accountability with practical safeguards can adopt generative AI without exposing customers, employees, or operations to avoidable risk.
2. The Top Generative AI Trends in 2026
Let’s be honest: generative AI has moved well beyond answering questions. Businesses are integrating it into daily workflows, customer service, internal knowledge bases, and even major decisions. Yet not every promising tool delivers real value. Instead of asking, “What’s new?” I think businesses should start with a more useful question: what problem are we trying to solve, and is AI actually the right solution?
Six trends stand out in 2026: AI assistants for workplace productivity, autonomous agents, personalized customer experiences, AI-powered business intelligence, generative AI for marketing, and smaller specialized models. Each offers opportunities, but none is a perfect fit for every business. Let's look at what these tools can do, where they fall short, and how companies can decide whether they're worth using.
2.1. AI Assistants for Workplace Productivity
AI assistants are a natural starting point for many businesses. Their appeal is easy to understand: employees can use them to draft emails, summarize meetings, prepare reports, explain unfamiliar concepts, analyze documents, and create first drafts of presentations. One email may take only a few minutes to write, but dozens of small tasks like these can consume a surprising amount of time over a working week.
Do these tools actually save time? Research suggests they can. In a 2023 experiment published in Science, researchers Shakked Noy and Whitney Zhang gave professionals writing tasks, including press releases and short reports. Participants who used ChatGPT completed their tasks about 40% faster, and independent graders rated their work approximately 18% higher in quality. The experiment focused on relatively short, self-contained tasks, so the results won't necessarily translate directly to every workplace. Still, the findings provide a useful starting point.
I wanted to test this for myself rather than rely only on published research. So I gave ChatGPT a task I actually needed: writing a professional email explaining that a report would be delayed by two days. It produced a usable draft in about three seconds. Writing a similar email from scratch took me roughly three minutes. I didn't need to edit the AI version before using it, which made the difference especially clear. Of course, this was a simple writing task, not a controlled experiment, and the result won't apply to every situation. Still, it showed me something practical: when the request is clear and the task is routine, AI can remove a small but real amount of work from the day.
There's more to productivity than writing emails, though. A manager might use an assistant to summarize a lengthy report before a meeting, while a sales representative could turn rough meeting notes into a follow-up message. The employee still needs to check the details and make the message personal, but the first draft is already there. Integration makes this process easier, too. When AI features are built into familiar office software and business systems, employees don't have to keep switching between different applications. Access to approved company documents can also make answers more relevant than those from a general chatbot.
The downside is easy to overlook when a demonstration goes well. An assistant can misunderstand instructions, invent details, or produce a polished answer that contains errors. I wouldn't send an important report to a client or make a decision based on an AI response without checking it first. That matters even more when confidential information is involved.
If you're considering an assistant for your team, don't start by buying the tool with the most impressive demonstration. Start with one repetitive task. Record how long it takes, test the AI-assisted version, and count the corrections needed before the result is ready to use. Then ask the people doing the work whether the new process makes their day easier. A tool that saves two minutes on paper but creates extra checking work may not be worth it.
My rule of thumb is simple: choose the task first, then the tool. Once employees understand what an assistant can and cannot do, it becomes a practical helper rather than another piece of software they have to manage.
2.2. Autonomous AI Agents in Business Operations
AI agents take things a step further than assistants. Instead of simply responding to a prompt, they work toward a goal by completing multiple steps and using connected tools along the way. Imagine an IT support team handling dozens of routine requests each day. An agent could classify a ticket, search the knowledge base, suggest a solution, and draft a response. In a carefully controlled environment, it might also update the ticket or carry out an approved action. More complicated cases would still go to a human specialist.
The same idea applies to customer support, software development, sales operations, and internal administration. An agent might prepare a sales briefing using approved records, flag missing information in a request, or help developers test and debug code. However, not all agents have the same level of autonomy. Some recommend the next step and wait for approval; others can take action within predefined limits.
That distinction matters. An agent that drafts a customer response presents a different risk from one that can issue refunds, change account permissions, or edit important records. If an agent makes a mistake and no one catches it, the error can spread across connected systems. The more authority a system has, the more carefully it needs to be monitored.
There's also a gap between the promise of AI agents and what businesses can reliably achieve today. In June 2025, Gartner predicted that more than 40% of agentic AI projects would be canceled by the end of 2027, citing rising costs, unclear business value, or inadequate risk controls. It also warned about vendors rebranding ordinary chatbots and automation tools as AI agents, a practice it called “agent washing.”
I see this as a reason to be selective, not a reason to dismiss the technology. An agent doesn't need to run an entire department to be useful. Handling a well-defined, multi-step process with less manual coordination can already make a difference.
For a first project, I'd choose a workflow with predictable steps and a result that can be measured. A support-ticket process, for example, could be evaluated by checking completion time, classification accuracy, and the number of cases requiring human intervention. Access should follow the principle of least privilege: the agent gets only the tools and data it needs. Activity logs, testing, escalation rules, and human approval for consequential actions should be part of the setup from the beginning.
The lesson is straightforward: give agents room to help, but don't give them unlimited authority. Start small, examine the results, and expand their responsibilities only when the evidence supports it.
2.3. Personalized Customer Experiences
Customers increasingly expect businesses to understand what they need. They want relevant recommendations, useful answers, and service that feels consistent across different channels. Generative AI can support this by combining customer context with language generation and, in some cases, recommendation systems or predictive analytics.
Consider a few everyday examples. A retail assistant could help shoppers compare products based on their stated preferences. A travel company might create an itinerary that fits a customer's budget and interests. A service provider could tailor its replies to earlier conversations, provided the relevant data is available and its use is permitted.
Personalization isn't limited to customer-facing chatbots. It can also help employees who handle customer conversations. In a study published in the Quarterly Journal of Economics in 2025, researchers Erik Brynjolfsson, Danielle Li, and Lindsey Raymond examined 5,172 customer support agents using an AI assistant that suggested responses during conversations. Productivity, measured by issues resolved per hour, increased by 15% on average. Newer and lower-skilled workers benefited the most, while the most experienced workers saw small gains in speed alongside small declines in quality. Customers were also more polite and less likely to ask for a manager.
These findings are encouraging, but they need to be read in context. The study covered one company and one type of support work, so its results shouldn't be treated as a guarantee for every business. The practical takeaway is that AI can support customer service, particularly for less-experienced employees, but the benefits depend on the task and the people using the system.
There's a more personal side to this issue, too. Have you ever seen an advertisement that seemed to know a little too much about you? Even when a recommendation is technically relevant, it can feel uncomfortable if you don't understand how a company obtained your information. Poor recommendations, incorrect assumptions, and overly intrusive messages can quickly damage trust.
That's why I would treat privacy as part of the customer experience, not just a technical requirement. Businesses need to follow applicable data-protection rules, restrict access to customer information, and explain how personal data is used. They should also test their systems for unfair treatment and avoid making sensitive inferences without an appropriate legal basis.
To find out whether personalization is genuinely helping, measure customer satisfaction, resolution times, repeat purchases, conversion rates, and complaints. Compare those results with a baseline from before the system was introduced. If engagement increases but complaints rise as well, the picture is more complicated than a single positive metric might suggest.
The goal isn't to personalize every interaction. It's to make the right interactions more useful. Good automation should leave customers feeling understood, not watched, and people should still have an easy way to speak with a real person when they need one.
2.4. AI-Powered Business Intelligence and Decision-Making
Business intelligence has traditionally involved collecting data, preparing reports, and navigating dashboards. Generative AI is changing how people interact with that information. Instead of searching through several reports, a user can ask a question in plain language, receive a summary, and explore possible explanations for a change in performance.
The risk becomes clearer when we consider an actual business decision. Suppose a retail manager asks why sales fell in one region last month. An AI system might point to lower customer demand, but that explanation is only a starting point. The manager should check sales figures against earlier months, compare the region with other locations, and look for changes in prices, stock availability, or customer traffic. If the evidence doesn't support the explanation, it shouldn't be accepted simply because the answer sounds convincing. I'd want to see the figures and understand how the system reached its conclusion before acting on it.
For me, that's a basic rule: if a system provides an answer but gives me no practical way to verify it, I'm not ready to rely on it for an important decision.
Businesses should therefore connect AI analytics to reliable, well-defined data sources and test how their systems handle calculations, ambiguous questions, and missing information. Important decisions need traceable figures and verified analysis, not generated explanations alone.
It's also worth separating two questions: what happened, and what should we do about it? AI can help identify patterns and compare scenarios, but deciding whether to change prices, invest in a new project, restructure a team, or alter a customer policy requires context and accountability. Those decisions shouldn't rest on an AI-generated summary alone.
A useful evaluation should look beyond how quickly a system produces an answer. Measure report-preparation time, answer accuracy, correction rates, and whether employees make better-informed decisions. If the tool produces reports faster but introduces errors that go unnoticed, the apparent productivity gain may be misleading.
AI should make trustworthy information easier to access. It shouldn't remove the need to question the evidence or think carefully about what the results mean.
2.5. Generative AI in Marketing and Content Creation
Marketing is one of the most visible areas of generative AI adoption because so much content work involves repeatable tasks. Teams use AI to brainstorm campaign ideas, draft product descriptions, prepare social media posts, adapt messages for different audiences, and create initial versions of advertising copy.
For a small business with a limited budget, this can make a real difference to the amount of work it can manage. A retailer might generate several draft descriptions for a product range, while a marketing team could adapt one campaign message for email, a website, and social media. Designers can also explore visual concepts before investing time in producing final assets.
Still, I wouldn't confuse producing more content with doing better marketing. The main advantage of AI is usually speed and flexibility, not fully automated creativity. Businesses still need to understand their audiences, set a clear strategy, verify claims, and maintain a consistent brand voice.
An AI-generated draft can be a useful starting point, but generic language can make a business sound like every competitor using the same tools. We've all come across marketing copy that says a lot without giving us a good reason to care. It's easy to publish, but it's just as easy to forget. A specific example, an original observation, or a genuine customer insight can make a message much more distinctive.
There are practical risks as well. Generated content may contain invented facts, misleading claims, or biased language. It can also raise copyright and licensing questions. Images and videos bring additional concerns when they depict real people, imitate recognizable styles, or mislead audiences about what actually happened.
A responsible workflow should include human review, fact-checking, brand guidelines, and clear rules for sensitive or regulated claims. Businesses should check the commercial-use terms of the tools they use and the content those tools produce. When disclosure is legally required or important for maintaining audience trust, they should provide it.
The best way to judge an AI marketing tool is to measure results rather than output volume. Engagement, qualified leads, conversions, production costs, and the amount of editing each draft requires can reveal whether the tool is actually helping. Publishing twenty posts instead of ten means little if neither audience engagement nor business results improve.
In my view, AI works best as a support tool for marketers who already understand their audience. It can speed up production and help explore ideas, but original insight, reliable information, and a genuine understanding of customers remain the more lasting advantages.
2.6. Smaller Specialized Models for Business Tasks
Not every business task requires the largest AI model available. Smaller models, including those adapted or fine-tuned for specific purposes, can be a practical choice when a business needs one focused capability rather than a general-purpose assistant.
A company might use a smaller model to classify support tickets, extract information from invoices, summarize internal documents, or identify patterns in technical records. Because the task is narrowly defined, it's possible to evaluate the model against clear performance criteria. Depending on the setup, a smaller model may also cost less to run, respond faster, or give a business more control over where its data is processed.
These advantages aren't automatic. A smaller model may struggle with unusual cases, complex reasoning, or unfamiliar information. Fine-tuning and deployment can require technical expertise, suitable training or evaluation data, ongoing maintenance, and regular checks for performance drift. A model that performs well on one dataset may struggle when the inputs or business process change.
That's why I'd compare models using real tasks from the business rather than relying only on benchmark scores or vendor demonstrations. Test accuracy, response time, operating costs, security requirements, integration effort, and how the system handles mistakes. For invoice processing, for example, it's worth checking not only how many fields the model extracts correctly but also how it handles missing information or an unusual invoice format.
Sometimes, a hosted general-purpose model is the simplest option. In other cases, a smaller model or a combination of different models may be more suitable. There's also a middle ground: retrieval-augmented generation (RAG), which allows a general-purpose model to retrieve information from approved documents before answering. This can help ground responses in company information without requiring the business to train a model from scratch.
The right choice depends on the task, the quality of the available data, the cost of mistakes, and the resources available to maintain the system. Smaller specialized models make sense when the task is clearly defined and the business can demonstrate reliable performance at an acceptable cost.
So, where does this leave businesses in 2026? After looking at these six trends, I wouldn't recommend that a business adopt AI simply because competitors are doing it. I'd begin with one task that takes too much time or creates a recurring problem, then test whether an AI tool actually improves it. My own email experiment showed how much time a simple task can save, but it also reminded me that one successful example doesn't prove that every task will benefit. Businesses need to measure the results, check the quality, and listen to the people using the tools. If the benefits aren't clear, there's no need to force adoption. In 2026, the real advantage isn't using the most AI. It's knowing where AI helps, where it falls short, and when human judgment matters most.
3. Generative AI Applications Across Industries
Generative AI is already part of everyday business. Companies use it to draft documents, answer customer questions, analyse information and help employees get work done. But the benefits aren’t the same everywhere. A tool that saves time in one setting can create new risks in another, particularly when people’s money, health or education is involved.
I’ve seen this in my own work, on a much smaller scale. When I prepared a 40-page colouring book for sale on Selar, I used ChatGPT to help with parts of the book, including the product description. It gave me something to work with, but it also got things wrong. At one point it repeated one page and reused the same drawings, even though I’d asked for different ones. I had to catch that myself, and I had to rework the description so it matched the actual book and the way I wanted to present it. Then came Flutter. My application’s code had an error I couldn’t get past, and ChatGPT corrected it. Correcting the error cost me about 30 minutes, and the fix worked, but only after I’d applied the change and tested it myself.
Neither story proves that AI will transform an entire business. What they show is simpler: AI can get you moving, but you still have to judge the result. And that matters even more when a mistake costs more than a wasted afternoon. So where does it cost the most? Let’s start there.
3.1. Healthcare and Life Sciences
Think about how much of a doctor’s day goes to paperwork—consultations to document, notes to write up, patient information to organise, all on top of the clinical work. Generative AI could lift some of that and give doctors more time with patients. Honestly, it’s the most appealing promise in this chapter.
A pilot study by Ma et al. (2025) examined an ambient AI scribe at an academic medical centre. It involved 45 physicians across eight outpatient specialties over three months. The tool was used in 55.25% of visits. Median note-taking time fell by 0.57 minutes, while daily documentation time decreased by about seven minutes.
Are those numbers impressive? I’d say encouraging, but modest. It was a pilot study, not a randomised trial, so it doesn’t show that every healthcare organisation would get the same result. A few minutes a day can mean a lot to a busy clinician, but it doesn’t tell us whether every generated note is accurate.
That’s the part providers can’t overlook. A system can write fluent medical language and still get an important detail wrong, much like my repeated page looked fine until I checked it. Privacy, accuracy and accountability all call for safeguards and human review before anyone relies on AI-generated notes. And if a doctor’s notes need that much care, what about a bank’s?
3.2. Finance and Banking
Banking raises the stakes in a different way. Banks handle sensitive information and work under strict regulation, so a tool that’s merely convenient won’t cut it. Generative AI can help with customer enquiries, internal reports and document review, and it may save employees from combing through long documents by hand.
Moharrak and Mogaji (2025) examine how generative AI is being integrated into banking, including the opportunities and challenges of using it in a regulated industry. Their qualitative research explores organisational readiness, privacy, reliability and compliance. It tells us about the issues banks face; it doesn’t measure productivity gains in a controlled way, and I wouldn’t read it as if it did.
So what should a bank look for? Not speed alone. A confident but wrong answer about a financial product could mislead a customer or create a compliance problem, and sensitive information has to be handled with care.
I think AI works best here when employees have clearly defined tasks and established review procedures. The final responsibility stays with people, especially when an answer could affect a customer’s money or the bank’s legal obligations. Retail faces a lighter version of the same problem.
3.3. Retail and E-commerce
Retail never stands still. There are product descriptions to write, customer questions to answer, recommendations to make and catalogues to update. Generative AI can draft descriptions, suggest replies to common enquiries and adapt marketing content for different audiences. For small sellers who do most of this themselves, even a modest saving is welcome. That’s how it felt with my Selar listing: the draft saved me effort, but I still checked every claim, and every page, against the actual book.
Ni et al. (2026) studied generative AI assistants in Alibaba’s customer-service operations. They reported differences in handling speed and customer ratings, but the effects weren’t uniformly positive, and some high-performing agents struggled with multitasking. What stands out to me is the broader point: an AI assistant can change how employees organise their work, not just how fast they finish it.
Retailers need to look beyond the number of replies generated or the time saved. Product claims must be accurate, customer data must be protected, and automated replies need to fit the situation. A fast answer isn’t much use if it sends a shopper in the wrong direction. Speed versus understanding is also the heart of the next story.
3.4. Education and Learning
Education is where I find the question of “help” most interesting. Generative AI can explain difficult concepts, produce practice questions, help teachers prepare materials and give students another way into a problem. That’s especially useful when a learner needs one more explanation, or a teacher is short on time.
But helping a student finish an exercise isn’t the same as helping them understand it. Someone who’s handed the answer may complete the task without learning how to solve a similar problem alone. We’ve all copied an answer we didn’t really understand. That gap shows up the moment the AI isn’t there.
Bastani et al. (2025) investigated this in a randomised study of around 1,000 high-school mathematics students in Türkiye. Students using GPT-4 did better during practice, and a specially designed tutor with safeguards produced even larger practice gains. In a later assessment without AI, however, the group that had used the general GPT-4 tool scored 17% lower than the group that had practised without it. The safeguarded tutor avoided much of this negative effect.
That doesn’t mean AI is always harmful in education. It suggests that design and use matter. An assistant that gives hints and pushes students to work through a problem may support learning better than one that hands over the answer.
Teachers still have to decide when AI is appropriate, how students should use it and how to check real understanding. The goal isn’t finishing assignments faster. It’s learning something you can use on your own. Professionals face a similar test, only with higher stakes.
3.5. Professional and Business Services
Law firms, consultancies and other professional service providers work with long documents, detailed evidence and complex arguments, which is exactly the kind of material AI summarisers are built for. Generative AI can summarise it, organise it and prepare a first draft. That may save time, but the quality of the result depends on the source material and the checks that follow.
Burgess et al. (2024) tested generative AI for identifying arguments in decisions of the Australian High Court. Across five decisions, they found substantial differences between the models they tested, with some performing far better than others under the study’s assessment.
Those results belong to the particular models, tasks and evaluation in that study. They aren’t a ranking of current systems or a guarantee of performance on other legal work, and models change so fast that any ranking would date quickly. The more useful lesson, in my view, is that results can differ sharply even when every tool writes convincing prose.
In legal and consulting work, an incorrect summary or an unsupported claim can have serious consequences. I wouldn’t trust a summary I hadn’t checked myself, and professionals shouldn’t either. They need to verify sources, protect confidential information and take responsibility for the advice they give. AI can help with preparation, but it can’t replace professional judgement. And when the error sits in a procedure rather than a paragraph, things get physical.
3.6. Manufacturing and Supply Chains
On a factory floor, a wrong answer isn’t just a bad sentence. Manufacturing runs on procedures, technical instructions, equipment information and coordination between workers. Generative AI may help employees find the right instruction, make sense of technical documentation or answer questions that would otherwise mean searching several sources.
Colabianchi, Costantino and Sabetta (2024) examined a digital assistant for assembly manufacturing built on a large language model. Their laboratory experiment explored whether it could support workers and improve aspects of task performance. Because it took place in a laboratory, it doesn’t show that the same benefits will appear on a live production line.
The quality of the information behind the system matters a great deal here. An outdated procedure or a wrong technical instruction could do far more harm than a badly worded marketing message, and I doubt any worker would argue otherwise. Workers need answers they can trust, not just answers that arrive quickly.
Manufacturers should connect AI tools to reliable documentation and make clear when a response needs confirmation from a qualified colleague. They should also ask a simple question: does the tool make the task easier, or does it add another step to an already complicated process? Software teams ask the same thing every day.
3.7. Software Development and Technology
Software development is where my own experience comes closest to the research. Coding assistants suggest code, explain unfamiliar functions, help locate errors and give a starting point for repetitive tasks. They can cut some routine work, although the quality of the suggestions varies.
My Flutter experience showed both the benefit and the limit. The correction worked, and that was a relief. But one successful fix doesn’t mean every suggestion will be right—a change can solve the immediate problem and still cause another one somewhere else in the app.
A field study by Cui et al. (2025) examined three experiments involving 4,867 software developers at Microsoft, Accenture and a Fortune 100 company. The researchers reported that coding assistants increased the number of tasks completed by about 26% on average, although the effects varied. That’s evidence of potential productivity gains in the settings studied, not a promise of identical results for every developer or project.
Developers still need to test code, review security implications and understand how a suggested change affects the wider system. AI-generated code may contain bugs or rely on assumptions that don’t fit the project. Used carefully, a coding assistant helps developers move forward. Used without review, it can leave them with problems that take longer to fix. Which brings us back to where I started.
What These Applications Tell Us
Look back across the seven industries and the same lesson keeps coming back: generative AI is most useful when it has a clear purpose and someone can check the result. It can assist with clinical notes, banking tasks, retail content, learning materials, legal documents, manufacturing instructions and software development. But the risks aren’t the same in each, and the evidence doesn’t support one universal claim about productivity.
Some studies report better task performance or time saved. Others point to uneven results, possible harm or limits on how widely their findings apply. The setting matters, the way people use the tool matters, and so does the cost of getting something wrong.
My own examples were small, but they make the same point: AI gave me a starting point, not a finished result I could accept without checking. One repeated page in a 40-page colouring book is a minor problem. For a business the stakes are bigger, and so is the question. Where can AI genuinely help? What needs human review? And how will they know the change has improved the work?
Adopting a tool just because it’s new doesn’t answer any of that. Businesses need to start with a real problem, measure what changes and keep people responsible for decisions that need judgement. To me, that’s a far more practical way to assess generative AI than assuming every new application will deliver the same benefits.
4. Real-World Business Case Studies
It’s easy to be impressed by an AI demonstration. A tool can produce an answer in seconds, write a product description, or help an employee find information that would otherwise take much longer to locate. But here’s what I’ve come to believe: the real test begins after the demonstration. Can the business rely on the results? Does the tool actually save time? And what happens when it makes a mistake?
To answer these questions, I looked at how both large companies and small businesses have used generative AI. Their experiences show that it can be useful, but its success depends on how people use it, how they check its output, and whether it solves a real problem.
4.1. How Large Enterprises Implement Generative AI
Large companies have resources that many small businesses simply don’t. They can invest in advanced technology, hire specialists, and organise their data. Even so, rolling out generative AI across an organisation isn’t always straightforward. Privacy, security, accuracy, and employee trust all matter, especially when the system handles sensitive information.
Morgan Stanley: Making internal knowledge easier to access
Morgan Stanley is the example from the financial sector that I find most interesting. The company worked with OpenAI to develop an AI assistant that helps financial advisers find information in the firm’s internal knowledge base. Instead of searching through large collections of documents manually, advisers can ask questions and get answers based on relevant internal material.
OpenAI’s published case study reports that more than 98% of Morgan Stanley’s adviser teams actively use the assistant, and that access to documents rose from 20% to 80%.[1] The same case study credits a formal evaluation framework: the firm tested each AI use case on realistic tasks, with expert feedback, before deploying it.
Those figures come from a case study published by the technology supplier, so I’d read them in that context. Still, what stands out to me is the approach. Morgan Stanley didn’t simply hand employees a chatbot and leave them to work everything out. It focused on making internal information accessible, tested the system before rollout, and worked on how it retrieves and presents answers.
This distinction matters more than it might seem. A generative AI model can sound convincing even when it doesn’t have the right information. Connecting it to relevant internal documents helps, but the quality of those documents and the reliability of the retrieval process still matter. In finance, where advice affects clients’ money, checking the answers isn’t optional.
Klarna: Faster customer service, with questions about quality
Klarna is another example of enterprise adoption. In February 2024, the financial technology company announced that its AI assistant had handled 2.3 million customer conversations during its first month, around two-thirds of its customer-service chats. It also reported that the average resolution time had fallen from 11 minutes to under two minutes, and that the assistant was doing the work of roughly 700 full-time agents.[2] Keep in mind that these are company-reported figures.
They grabbed attention, and it’s easy to see why. They suggested that AI could take on a large share of routine enquiries, and fast. Questions about payments, refunds, and returns are often repetitive, so they’re natural candidates for automation.
Here’s the thing, though: speed is only one part of good customer service. A customer with an unusual problem might need more than a quick automated reply. If the system can’t understand the situation, or keeps repeating the same unhelpful answer, the customer ends up more frustrated than before. Most of us have been there.
Klarna’s own story shows the risk clearly. In 2025, its chief executive told Bloomberg that cost had been too dominant a factor in how the company organised customer service, and that the result was lower quality. The company began recruiting human agents again, while continuing to use AI elsewhere in the business.[5]
So I wouldn’t judge customer-service AI only by the number of conversations it handles. I’d also look at customer satisfaction, resolution quality, and how easily a person can take over when the system reaches its limits.
What can other businesses learn from these examples?
Morgan Stanley and Klarna operate in different markets, but their experiences point to a similar lesson: AI works best when it has a defined role and someone keeps an eye on its performance. It’s not enough for a tool to produce impressive answers in a demonstration. It has to work reliably in the situations employees and customers meet every day.
That takes planning, testing, suitable data, and human oversight. None of it’s glamorous, but in my view it’s what decides whether an AI project becomes genuinely useful.
Large enterprises are only half the story, though. What happens when there’s no budget for specialists or custom systems?
4.2. How Small Businesses Use AI to Compete
Small businesses can use generative AI without building their own models or employing a team of AI specialists. They can draft marketing content, improve product descriptions, explore business ideas, create illustrations, and handle some routine administrative tasks. For someone working with a limited budget, access to these capabilities can make a real difference.
My own experience, however, has taught me that getting a first result isn’t the same as getting a result that’s ready for publication.
My experience creating illustrations for Amazon KDP
I’m preparing children’s colouring books that I plan to publish through Amazon KDP, and I’ve seen both the benefits and the limitations of AI-generated illustrations.
Sometimes I describe a scene carefully, but the image still misses something important. A character looks different from the previous page, an object I asked for is missing, or the composition doesn’t leave enough open space for children to colour. When that happens, I go back and rewrite the prompt, sometimes several times, until the result works.
This matters even more with a complete colouring book. One attractive illustration isn’t enough; the pages need to work together. The characters should stay consistent, the scenes should match the instructions, and the drawings should be suitable for young children. If I accept every image as soon as it appears, mistakes can easily make their way into the finished book.
The cover needs attention too. During the publishing process, Amazon KDP flagged one of my covers because the text was difficult to read against the background or was obstructed by design elements. I had to think about contrast and placement rather than assuming that a visually attractive design would automatically meet the platform’s requirements.
Experiences like these have changed the way I use AI. I still find it useful for developing ideas and producing initial designs, but I don’t treat the first result as the final one. I review the output, correct problems, and check that it meets the requirements of the book.
Why does this matter for a small business? Because time is limited. AI can speed up one part of the work, yet repeated corrections can take longer than you’d expect. The real question isn’t whether the tool generates something quickly; it’s whether the complete process becomes more efficient.
Making AI useful in a small business
If you run a small business, my advice is to start with tasks where the benefit is obvious. A shop owner might use AI to prepare a first draft of a product description, for example, but should still check that it accurately reflects the product. A freelancer might use it to organise ideas before writing a proposal. A small publisher might use it to explore illustration concepts while reviewing every image before including it in a book.
There’s no need to automate everything at once. In many cases, using AI for one repetitive task and learning from the results is a more sensible approach than changing an entire workflow overnight.
Think about the time you spend correcting errors, too. A tool that saves ten minutes on a first draft isn’t much use if it costs you half an hour of revisions. On the other hand, if it consistently cuts the total time needed to finish a task while keeping the quality up, it’s probably worth keeping.
Small businesses have one advantage that’s easy to overlook — they often know their products and customers very well. AI can help them work faster, but that knowledge helps them spot when an answer, design, or recommendation doesn’t make sense.
Whether you’re a global bank or a one-person publisher, though, the same problem keeps appearing: promising pilots that never turn into dependable tools.
4.3. Why Some Generative AI Projects Fail After the Pilot Stage
A successful pilot project can create high expectations. The system works on a small set of examples, the demonstration looks promising, and everyone starts talking about expanding it. Then the project meets everyday business conditions, where the data’s messier, the requests are less predictable, and mistakes can have real consequences.
In July 2024, Gartner predicted that at least 30% of generative AI projects would be abandoned after the proof-of-concept stage by the end of 2025. It listed poor data quality, inadequate risk controls, rising costs, and unclear business value as the main reasons.[3] A later Gartner article, published in January 2026, reported that at least 50% of such projects had in fact been abandoned after proof of concept by the end of 2025, citing the same four causes.[4]
These figures don’t mean that every business will have the same experience. They do, however, show the gap between experimenting with AI and making it work reliably at scale. Let’s look at the reasons one at a time.
1. The business problem was never clear
Some organisations begin experimenting with AI because they don’t want to fall behind competitors. But adopting a technology without knowing exactly what it should improve makes success hard to measure. I’d put this reason first, because everything else depends on it.
A business should be able to explain what it wants to achieve. Does it want to reduce the time employees spend searching for information? Handle routine customer enquiries faster? Help staff prepare documents? Without a specific objective, even an impressive system may deliver little practical value.
2. The data isn’t good enough
AI tools need the right information to produce useful results. If company documents are outdated, incomplete, inconsistent, or hard to access, the system may return answers that are inaccurate or irrelevant.
That’s one reason why connecting a model to an internal knowledge base doesn’t automatically solve every problem. Businesses still need to organise their information, check its quality, control access, and keep it up to date.
3. The real cost is higher than expected
A pilot can seem affordable because it involves only a few users and a limited amount of data. Once the system expands, the business may face extra expenses for model usage, integration, security, monitoring, and staff training.
There’s also the cost of human review. If employees spend a great deal of time correcting AI-generated output, some of the expected savings disappear. Before expanding a project, a business should compare the total operating cost with the benefits it can actually measure.
4. The system makes too many mistakes
A tool can perform well on simple requests but struggle with unusual cases or complicated instructions. It can also produce confident answers that are simply wrong. The problem gets worse when users start relying on its answers without checking them.
Businesses need to test AI with realistic examples, including difficult cases and requests the system shouldn’t answer confidently. They should also decide when a human needs to review the output or take over the task. Testing should continue after launch, because performance can change as the data, workflows, and user needs evolve.
5. Employees aren’t properly involved
A technically capable tool can still fail if employees don’t understand how to use it or don’t trust its results. It can also create extra work when it doesn’t fit existing processes.
Employees need practical training, clear instructions, and a way to report problems. Managers should explain which tasks the tool can support, which decisions stay with people, and who’s responsible for checking its output.
Learning before scaling
Before expanding an AI project, businesses should ask themselves a few direct questions:
Does the system solve a clearly defined problem?
Does it improve the complete workflow, rather than just one step?
Are the results accurate enough for the intended use?
Do the measurable benefits justify the total cost?
Do employees know how to use the tool and when to question its output?
If the answers are unclear, I’d spend on more testing rather than a larger budget. Sometimes the right decision is to improve the data, change the workflow, choose a different tool, or stop a project that isn’t delivering enough value.
In my view, the aim shouldn’t be to introduce AI into as many activities as possible. It should be to find the tasks where it makes a meaningful difference and use it in a way the business can sustain.
5. The Business Value of Generative AI
Generative AI isn’t just a technology experiment any more. Businesses want to know what it actually delivers: less time on routine tasks, lower costs, new revenue, faster product development. So what’s the verdict? I think the honest answer so far is mixed. Some organisations are already seeing measurable benefits. Others haven’t yet managed to turn early experiments into something they can really use.
Here’s what the numbers say. Deloitte’s The State of AI in the Enterprise report, published in 2026, surveyed 3,235 business and IT leaders across 24 countries in August and September 2025. Among them, 66% reported productivity and efficiency gains, close to four in ten reported cost reductions, and just 20% reported higher revenue. That gap is hard to miss — 74% hoped AI would help grow revenue, but only 20% said it already had (Deloitte, 2026).
So why is efficiency so much easier to find than new revenue? And what separates the companies that get real value from those that simply adopt the technology? That’s what I want to work through here, using solid evidence, a few simple tools you can apply yourself, and my own experience where it helps.
5.1. Productivity Gains and Operating Cost Reduction
Let’s start with the most immediate benefit: time. Employees can use generative AI to draft emails, summarise long documents, prepare reports, organise information, and write first versions of marketing content. A useful first draft can shorten the work, and that’s the part I think people underestimate.
Controlled experiments back this up. In a study published in Science in 2023, Shakked Noy and Whitney Zhang gave 453 professionals writing tasks typical of their jobs. Those who used ChatGPT finished about 40% faster, and the quality of their output rose by about 18% on average (Noy & Zhang, 2023). A separate study followed 5,179 customer-support agents who were given an AI assistant. Productivity, measured as issues resolved per hour, rose by about 14% on average. The gain was far larger, around 34%, for the least experienced workers, while experienced workers saw little change (Brynjolfsson et al., 2025). Both studies looked at specific tasks, so I wouldn’t assume the same numbers apply to every job. Still, they show the gains are real when the task suits the tool.
But what does “saving time” really mean? I find it useful to count it like this: net time saved equals the time a task took before, minus the time it takes now, including prompting, reviewing, and fixing the output. Here’s an illustrative example with made-up numbers. Suppose writing a product description by hand takes 30 minutes. With AI, you spend 5 minutes prompting and 10 minutes reviewing and correcting, so the task takes 15 minutes. You save 15 minutes per description, and across 40 descriptions that’s 10 hours. Now suppose the drafts are weak and each one needs 30 minutes of fixing. The same task now takes 35 minutes, which is longer than doing it yourself. Same tool, opposite result. The whole difference sits in the review and correction time, so that’s the number I’d measure first. To turn hours into money, subtract the subscription, set-up, and training costs, and multiply by what an hour of your time is worth.
I’ve seen this pattern in my own colouring-book project. AI speeds up the first draft of an illustration, but I still check every page. My cover is a good example. I asked an AI assistant to adjust it to Amazon KDP’s requirements, and KDP still flagged it. There were two problems. The text blended into the background or was blocked by other elements, and it sat too close to the edge, inside the 0.375-inch (9.5 mm) safe zone. I’ve now sent the cover three times, and it’s still under review. I saved time on the design, then lost much of it waiting and resubmitting. In the formula above, that waiting is part of the cost too.
How widespread is all this in practice? The St. Louis Fed offers a reality check. In its May 2026 survey of 117 firms in the Eighth Federal Reserve District, most reported only experimental or limited use of AI, and about half (49%) didn’t expect any noticeable effect on staffing over the next year (Gutkowski et al., 2026). The sample is small and regional, so I wouldn’t treat it as representative of every business in the United States. Still, it’s a useful reminder that adoption on paper and adoption in practice aren’t the same thing.
Deloitte’s data hints at why the savings can be hard to pin down. Only 30% of organisations said they were redesigning key processes around AI, and 37% were using it only at a surface level, with little or no change to how the work gets done (Deloitte, 2026). If the process doesn’t change, there’s little for the tool to save. Saving time on a task also doesn’t automatically mean a company has cut its costs. Employees might use the time to handle more work, improve quality, or spend longer with customers. Actual savings depend on how the business reorganises its work.
And let’s be clear: not everything should be automated. Some work depends on judgement, trust, or a detailed understanding of a customer’s situation. There, AI works better as an assistant than as a replacement.
That’s the efficiency side. Revenue is another story, and a harder one.
5.2. Revenue Growth and New Business Opportunities
Efficiency is the easy half, as we’ve just seen. But cutting costs is only part of the business case. Can generative AI also help a company attract customers, improve its products, or open up new sources of income?
Marketing is the obvious place to start. Teams can develop alternative product descriptions, adapt campaigns for different audiences, and come up with social media ideas faster. AI can also help businesses explore customer questions and spot patterns in feedback. These uses may support better decisions, but the results still depend on the quality of the offer, the accuracy of the content, and how well the company understands its market.
For small businesses and independent creators, I find the opportunity especially interesting, and I’m one of those creators myself. Tasks that once needed several separate tools, or plenty of time, can sometimes be done with a simpler workflow. A creator can use AI to brainstorm product ideas, prepare an initial description, and organise promotional content. Then comes the part AI can’t do for you: checking the information, making the content distinctive, and deciding whether the product is worth selling.
But faster content doesn’t guarantee higher sales. You can publish more posts and more product pages without attracting a single extra customer. Revenue depends on demand, pricing, distribution, customer trust, and the quality of the product itself, and no tool can change that. Deloitte’s findings make the same point: 74% hoped AI would increase revenue, but only 20% said it had (Deloitte, 2026).
So my takeaway is simple: measure outcomes, not output. Counting AI-generated posts tells you very little. Here’s a method I’d use. Pick one revenue measure before you start, such as conversion rate, repeat purchases, average order value, or the cost of winning a customer. Record it for a few weeks as a baseline. Then introduce AI in one place only, for example the descriptions of half your products, and compare the two groups over the same period. If the AI-assisted group doesn’t move, the tool isn’t contributing to growth, however much content it produces.
And growth doesn’t only come from selling more. It also depends on how quickly a company can build and test new ideas, which brings us to innovation.
5.3. Faster Innovation and Shorter Development Cycles
Revenue isn’t the only place where AI might pay off. It can also change how businesses develop and test ideas. Teams can use it to explore product features, create early prototypes, draft technical documentation, and compare approaches before they commit serious resources.
In software development, AI assistants can explain unfamiliar code, suggest solutions, generate test cases, or flag possible errors. That can speed up parts of the process — especially when the developer already understands the problem and can judge the suggestions. The same idea works outside software. A product team might outline several possible customer experiences, and a marketing team could test different campaign concepts before a full launch. Part of the value is simply that exploring alternatives gets easier.
What does the research say? The OECD has reviewed the experimental studies on generative AI and its effects on productivity, innovation, and entrepreneurship. Its main message: AI’s effectiveness depends on the user’s experience and the task, and people working together with AI get the most out of it (Calvino et al., 2025).
Speed, though, shouldn’t be the only yardstick. A prototype can look convincing and still fail when real customers try it. Generated code can contain errors. An idea that seems strong can rest on wrong assumptions. My cover taught me the same lesson on a small scale. KDP found two problems, contrast and margins. Three submissions in, I know an AI can follow the rules you give it, but it can’t confirm that a platform will accept the result. That’s why human expertise, testing, and feedback still matter. If you want to measure innovation, track the time it takes to reach a tested prototype, the number of revisions along the way, and the defects customers find after launch. Those figures tell you far more than the number of ideas generated.
For me, the practical advantage isn’t that AI removes the need to think a problem through. It’s that exploring possible answers becomes cheaper. You can then spend more time judging the strongest options and less time producing the first draft of every idea.
But there’s a catch. If everyone has access to the same tools, they can all explore ideas just as quickly. So what’s left to compete on?
5.4. Why Proprietary Data Creates a Competitive Advantage
That question leads straight to data. As generative AI tools spread, access to the technology itself becomes less distinctive. Many competitors can use similar models to write content, summarise documents, or support customer service. What sets one company apart, I’d say, is how well it connects AI to its own knowledge and workflows.
I’m not the only one who thinks so. Harvard Business Review authors Scott Cook, Andrei Hagiu and Julian Wright argue that relying only on AI tools everyone can access brings a temporary advantage, while firms with unique customer data and feedback loops are better placed to build a lasting one (Cook et al., 2024).
What counts as proprietary data? Product information, customer feedback, internal procedures, service histories, and specialised industry knowledge are all examples. When it’s accurate, relevant, and properly protected, it can make an AI system’s responses more useful for a particular business. Take a company that uses AI to answer questions about its products. A general-purpose model gives broad information. A system connected to the company’s verified specifications and support documentation gives answers much closer to what the company actually offers.
How do you tell whether your data is a real advantage? I’d ask three questions. Is it unique, meaning a competitor couldn’t easily get the same information? Is it clean, meaning accurate, current, and consistent? And is it in a loop, meaning the way customers use your product or service feeds back and improves the next answer? If you can’t say yes to all three, the data is probably an asset in name only. Outdated records, inconsistent product details, and poorly organised documents lead to weak results, however large the archive is.
None of this means feeding every internal document or customer record into an AI tool. Privacy, confidentiality, access controls, and legal obligations all matter, and sensitive information has to be handled according to the company’s policies and the applicable requirements. I’d set clear rules about which data AI systems can access before anything else.
In the long run, I think the advantage comes from combining capable AI models with reliable internal knowledge, experienced employees, and well-designed processes. The technology may be available to everyone. The quality of a company’s data, and the way its people use it, is far harder to copy.
So generative AI can create business value, but adopting a tool is only the starting point. The stronger results are likely to come when companies define a clear problem, measure the net outcome, protect their information, and keep people involved where judgement is essential.
6. Challenges and Risks of Generative AI
The danger with generative AI is not that it fails all the time. It is that it works well enough, often enough, that people stop checking.
That is the argument of this chapter. An AI tool makes the first draft almost free. It does not make checking the draft any cheaper, and the checking is often where the money goes: someone reads the figures, confirms the source, decides what may leave the building and signs off on the result. Call it the verification bill. It is easy to overlook because the savings show up at once, while the bill may arrive later, as a correction, a data leak or a legal dispute.
Four problems make that bill difficult to avoid. A wrong answer can be fluent enough to pass unnoticed (6.1). Once sensitive information has been entered into an unsuitable service, checking the output cannot undo the disclosure (6.2). The people best equipped to spot mistakes may also be the people who need AI assistance least, while less experienced workers have more to lose from errors they cannot recognize (6.3). And responsibility does not disappear when a tool produces the work (6.4). The final section brings these problems together in a practical test that managers can apply to individual tasks (6.5).
This chapter does not attempt to cover every risk. Bias in outputs, dependence on a single vendor and sector-specific regulation, including the EU AI Act, deserve attention too. Their importance varies with the business, the information it handles and the country in which it operates.
6.1 Fast answers, slow checking
Picture an analyst who asks an AI tool to summarize a supplier contract. The summary reads well. It is organized, confident and about the right length. It also says the payment term is 30 days when the contract says 45. Nothing in the tone gives that away.
The problem is not simply that the tool has made a mistake. It is that the mistake arrives in a form people are accustomed to trusting. Clear writing and a tidy structure usually help a reader follow an argument. With generative AI, those qualities tell us little about whether the underlying claims are correct. Someone unfamiliar with the contract may not notice the error, particularly when it sits beside several accurate details.
Published evaluations show just how widely performance can vary. Stanford’s Institute for Human-Centered Artificial Intelligence reported in its 2026 AI Index Report that hallucination rates across 26 leading models ranged from 22% to 94% on a particular accuracy benchmark. The report also discusses a study, published in Nature Machine Intelligence in 2025, in which GPT-4o’s accuracy fell from 98.2% to 64.4% when a false statement was presented as the user’s own belief (Stanford HAI, 2026).
Neither result should be treated as the error rate a business will experience in its own work. The first comes from a specific benchmark, not a representative sample of everyday business tasks. The second examines how models respond to false beliefs; it does not establish how often GPT-4o will make mistakes when summarizing contracts or preparing reports. The findings are useful for a different reason: they show that performance depends on the task and on how information is presented. A question that contains a mistaken assumption can make it harder for a model to distinguish what the user believes from what is actually true.
For a business, this raises a practical question: how well does the tool perform on the work employees will actually give it? Before relying on an AI system for a recurring task, a company can test it on a sample of past cases whose correct answers are already known. Review the results, record the mistakes and pay particular attention to errors that would be difficult to notice. This will not guarantee future accuracy, but it offers more relevant evidence than a general benchmark alone.
The cost of checking also varies. A figure can be confirmed quickly if the original source is available. A summary of a long contract may require someone to read the relevant clauses and compare them with the AI’s interpretation. In that case, the summary may shorten the reading, but it cannot remove the need to understand the document. The more important the omitted details are, the less useful a summary becomes if nobody checks what it left out.
Asking the AI to verify its own answer does not solve the problem. It may identify an error, but it may also repeat the original claim with the same confidence. The check needs to involve evidence independent of the answer being checked.
That is why review should reflect the consequences of a mistake. A line of product copy may need only a quick read. A regulatory summary, a financial calculation or a legal reference should be checked against the relevant source. No business can eliminate every error, but it can decide in advance which errors are tolerable and which require stronger controls. Waiting until a mistake reaches a customer is an expensive way to establish that distinction.
6.2 What goes in matters as much as what comes out
An inaccurate answer can sometimes be caught before anyone acts on it. Information entered into an unsuitable service presents a different problem: once the material has been disclosed, checking the generated response cannot reverse that decision. The control needs to come earlier, when an employee decides what to enter and which tool to use.
People paste information into AI tools because it saves time. A customer email, a section of an internal report or a draft business plan can seem like harmless context for a prompt. Yet the same information might be subject to confidentiality obligations or internal access restrictions. Convenience can make the decision feel smaller than it really is.
The World Economic Forum’s Global Cybersecurity Outlook 2026, produced in collaboration with Accenture, found that 87% of respondents identified AI-related vulnerabilities as the fastest-growing cyber risk during 2025. The share reporting that they assessed the security of AI tools rose from 37% in 2025 to 64% in 2026 (World Economic Forum, 2026). These figures reflect survey responses, not the proportion of companies that suffered an attack. They nevertheless show that AI security has become a distinct concern for organizations, while formal assessment is still not universal.
Smaller firms may find this particularly difficult. They often have fewer resources for security reviews, and employees can begin using free or personal AI accounts before management has decided which services are suitable for company work. Telling staff to “be careful” offers little guidance if they do not know which information is restricted or what protections a service provides.
The OECD’s survey of more than 5,000 SMEs in Austria, Canada, Germany, Ireland, Japan, Korea and the United Kingdom, conducted in 2024 and published in 2025, provides some context. Among businesses that had not adopted generative AI, 57% said it was not suitable for their work, 54% cited copyright, legal or regulatory concerns, and 52% were concerned about what happens to information entered into AI models (OECD, 2025). These are separate reasons for non-adoption. The figures do not mean that every business had experienced a data incident; they show that uncertainty about the handling of information is one barrier to adoption.
One useful response is to make the safe option the easy option. If employees are expected to use AI, give them access to approved services and explain what those services may be used for. A rule that prohibits sensitive data but provides no workable alternative may push people towards personal accounts rather than prevent the behaviour.
A practical policy should answer four questions:
- Which AI services are approved for company work?
- What must never be entered, including passwords, restricted customer information, confidential contracts or unreleased financial data?
- Who can approve a new tool or a new use involving company information?
- Who reviews the output before it is used to make a decision or sent outside the organization?
The answers should be easy to find and understand. They also need to be revisited when a service changes or employees begin using it for different tasks. A tool suitable for drafting public marketing copy may not be suitable for processing customer records. Approval for one use should not automatically become approval for every use.
6.3 Jobs: the question is who does the checking
If AI can draft a report, answer a customer or prepare a presentation, it is tempting to conclude that fewer employees will be needed. Sometimes a company may indeed reduce the hours required for a task. But a job consists of many activities, and automating one of them does not necessarily eliminate the rest.
Consider an employee who uses AI to prepare a first draft. The employee may still need to understand the client’s request, check the facts, correct the tone and take responsibility for the final version. The actual time saved depends on how much of that work the tool can handle reliably. A draft that needs only minor editing can be useful; one that requires extensive checking may offer little advantage.
There is a further complication: checking often requires much of the knowledge needed to produce the work in the first place. An experienced accountant may spot an implausible figure immediately, while a new employee may not know where to look. AI can therefore save considerable time for an expert who already understands the task, while creating a greater risk for someone who lacks the experience to identify errors.
This is an inference about how expertise and verification interact, not a finding measured by the OECD survey. It matters because a company that measures only how quickly employees produce drafts may overlook who is capable of checking them. The apparent saving may depend on senior staff taking on additional review work, which creates its own cost.
There is also a risk of complacency. If a tool is correct in many routine cases, checking every output can begin to feel like unnecessary work. Employees may gradually skip checks, particularly when deadlines are tight. The answer is not simply to tell people to pay more attention. The workflow needs to make responsibility clear, with appropriate review points, sampling or a second reviewer where the consequences justify it.
The OECD’s Generative AI and the SME Workforce: New Survey Evidence helps put employment claims into perspective. Its representative survey of more than 5,000 SMEs found that 31% were using generative AI, and 83% reported that it had had no effect on their overall staffing needs. Meanwhile, 20% said that generative AI had increased their need for highly skilled workers relative to lower-skilled workers, compared with 9% who reported a decrease in that relative need (OECD, 2025).
These findings are a snapshot of businesses’ experiences in 2024, not a forecast for the next five or ten years. They suggest that, at that point, adoption was more often associated with changes in how work was performed than with changes in overall staffing needs.
For managers, the more useful question is what the organization does with the time AI saves. Employees might serve more customers, devote more attention to complicated cases or develop a new service. A company might also decide that it needs fewer hours for a particular activity. These are different choices, and the technology does not determine which one management makes.
Training deserves similar attention. The OECD survey does not establish whether AI use weakens or improves the development of junior employees, so the following is a reasoned concern rather than a reported finding. New workers often learn by producing imperfect first drafts, receiving feedback and trying again. If AI takes over that first attempt every time, some of those learning opportunities may disappear unless the company deliberately preserves them. On the other hand, AI can help a junior employee understand an unfamiliar topic or explore why a draft needs revision. Whether it supports learning or displaces it depends on how the work is organized.
Training should therefore cover more than writing prompts. Employees need to know how to question a generated answer, check important claims, protect confidential information and recognize when a task requires human judgment. They also need time to carry out those checks. Verification is skilled work, and a productivity calculation that treats it as free will give a misleading picture of the benefits.
6.4 When it goes wrong, a person answers for it
The verification bill cannot simply be passed to the tool. A model can generate text or images, but it cannot take professional responsibility for a filing, a business decision or a public claim. A person or organization chooses to use the output, and the relevant responsibilities remain in place.
Copyright is one example. Having AI produce something does not settle who owns it or whether it can lawfully be used. A company might generate an image for an advertisement or include AI-written material in a product it intends to sell. Before publication, it still needs to consider the rights involved, the service’s terms and the law that applies.
The U.S. Copyright Office addressed part of this issue in its January 2025 report, Copyright and Artificial Intelligence, Part 2: Copyrightability. Under U.S. copyright law, human authorship remains essential, and providing prompts alone will generally not establish sufficient human control over the expressive elements of an AI-generated work (U.S. Copyright Office, 2025). This is a conclusion about U.S. law; businesses operating in other jurisdictions need to consider the rules that apply there.
Authorship is only one part of the legal question. The use of copyrighted material to train models, the use of protected works in particular outputs and the rights attached to generated material raise distinct issues. An image or passage is not automatically free of legal risk simply because an AI system produced it.
The case of Mata v. Avianca illustrates the consequences of failing to verify generated information. In 2023, lawyers submitted a court filing containing fictitious judicial decisions after relying on ChatGPT. The court record documented exchanges in which the system represented fabricated authorities as real, although the chronology of those exchanges was disputed. On June 22, 2023, the U.S. District Court for the Southern District of New York imposed a $5,000 penalty jointly and severally on the respondents (Mata v. Avianca, Inc., No. 22-cv-1461, S.D.N.Y. 2023).
The important point is not simply that the system produced false information. The lawyers submitted the authorities without adequately verifying them. They were responsible for the material filed with the court, and the system’s confident assurances did not remove that responsibility.
The same principle applies in less dramatic settings. If an AI-generated report informs a business decision, someone needs to check the claims that matter and be able to identify who approved the report. A brief record of the tool used, the human contribution, the sources consulted, the checks performed and the person who signed off can help make that process visible. Such a record is not a legal shield, but it is more useful than a workflow in which nobody can explain how the final answer was accepted.
6.5 Putting a price on checking
The sensible position lies between using AI everywhere and avoiding it altogether. The decision should be made task by task, with one central question: does the saving remain once checking and the possible consequences of error are included?
A rough way to think about it is:
Net value = time saved − verification and correction costs − expected cost of errors.
This is a practical decision aid, not a validated formula. It does, however, force a business to count costs that a simple speed comparison leaves out.
Imagine a task that takes 30 minutes to complete manually. An AI tool produces a draft in five minutes, but checking and correcting it takes another 20. The saving is five minutes, not 25. If the process also creates a small chance of an expensive mistake, even that five-minute saving may not justify using the tool. The calculation changes if the task is repeated thousands of times, but repetition helps only if the output remains reliable enough and the review process can keep up.
Two questions are central: how serious would an error be, and how difficult would it be to detect? Together, they give managers an initial way to classify tasks.
| Cost of a wrong answer | Checking is quick | Checking is slow |
|---|---|---|
| High | Use only with a reliable check on every output. | Avoid the use or redesign the task so the answer can be verified. |
| Low | Suitable for routine use with proportionate review. | Consider limited use and sample outputs, provided the consequences truly are minor. |
The most difficult case is the high-consequence task that is also hard to verify, shown at the top right of the table. There, the speed of generation offers little reassurance. If nobody can establish whether the answer is right, the business should not rely on it for a consequential decision without changing the process.
The two questions are a starting point, not the whole assessment. Four considerations help determine what safeguards a task needs:
| Consideration | Question to ask | Easier to manage | Harder to manage |
|---|---|---|---|
| Consequences | What happens if the answer is wrong? | Product copy reviewed before publication | A regulatory summary used in a compliance decision |
| Verifiability | Can someone compare the answer with reliable evidence? | Figures checked against accounting records | A claim with no clear source or independent confirmation |
| Data exposure | Does the task require confidential or personal information? | Public marketing material | Customer records or unreleased business plans |
| Human responsibility | Who reviews and approves the result? | A named editor signs off before release | No one is assigned to check the output |
The first two considerations help estimate the cost of an error and the effort required to detect it. The other two help establish whether the task can be carried out safely and whether anyone is accountable for the result. They are a decision aid, not a validated scoring system.
The subscription fee is only the most visible part of the cost. Training, maintenance, review time and the work required to correct mistakes all belong in the calculation. A tool may look inexpensive until the company counts the hours spent checking its output.
A short trial can reveal more than a polished demonstration. Compare the time needed to complete a task with the existing process. Record how often the output needs substantial correction, and identify mistakes that could have caused real harm. Ask the employees doing the work whether the tool has made the task easier in practice, rather than assuming that a faster first draft means a faster completed job.
The result may be mixed. A company might keep AI for routine drafting, require a second review for material sent to clients and avoid using it for decisions that cannot be verified reliably. That is not a failed experiment. It is a more precise understanding of where the technology helps and where its costs outweigh its benefits.
The decision should be reviewed as conditions change. A tool may be updated, the volume of work may increase or employees may begin using it in ways the original trial did not cover. A process that worked on a small sample may not work at scale. Periodic checks help establish whether the savings remain real and whether the safeguards still work.
Generative AI can make the first stage of a task much faster. Whether it makes the work itself better depends on what happens next: whether the answer can be checked, whether information is handled safely and whether a person remains responsible for the result. Some tasks will benefit with little additional effort. Others will require stronger controls, and some will not be worth automating. The business decision is not how much AI to adopt, but where it improves the work after the full cost of checking has been counted.
7. How Businesses Can Turn Generative AI into Lasting Value
Buying access to a generative AI tool is easy. Working out where it belongs in a business is harder.
A company can give everyone a capable model within a day. That alone won’t make it more productive, more competitive or better at serving customers. The real test starts when the novelty fades and the tool has to fit into an existing process, with its people, its software, its deadlines and its commercial constraints.
Take a company that uses AI to prepare customer proposals. Employees can turn out first drafts in minutes, but a proposal still needs the right prices, accurate product details and a real understanding of what the customer wants. If people spend the time they saved fixing invented details or hunting for figures the tool couldn’t reach, the gain is gone. The work got quicker at one stage and heavier at another. Now suppose the company changes the process so the tool drafts from approved prices and product data. Employees can then spend their time on the commercial judgment that makes a proposal worth sending.
The difference is in how the work is designed, not just which model is used. It’s the other half of the verification bill from Chapter 6. Businesses get lasting value when they make checking cheaper: by feeding the tool reliable information, deciding in advance which claims a person must confirm, and measuring the finished task instead of the speed of the first draft.
McKinsey’s 2025 global survey on AI looked at 25 organizational attributes and how they related to reported bottom-line impact from generative AI. Workflow redesign had the strongest association. Yet only 21% of respondents whose organizations used generative AI said they had fundamentally redesigned at least some workflows (McKinsey, 2025). The survey shows an association, not proof that redesign alone produces financial gains, and it rests on what respondents reported. It still raises a fair question: is the business changing how work gets done, or just asking people to do the same work with a new tool?
A sound strategy answers six questions, in order. Which business problem deserves attention? What kind of solution fits it? Is the value real? How should the work and the people change? What rules keep the risks manageable? And how can the plan adapt as the technology moves?
7.1 Start with the business problem, not the technology
The most impressive demo isn’t necessarily the best opportunity. A model that writes a dazzling marketing campaign gets attention. A quieter application that removes a recurring bottleneck may be worth far more over a year.
Start by looking at where work slows down, where people keep doing the same preparation, and where information has to be reorganized before anyone can act on it. These are places to investigate, not automatic candidates for automation. First you have to understand why the work takes so long.
Suppose the proposal team’s managers think their problem is slow writing. Watching the process shows something else. Much of the time goes into checking which price list is current, confirming product specifications with colleagues and waiting for legal to review unusual terms. Faster drafting would barely touch any of that. The real bottleneck is access to reliable commercial information, and AI can only help if that information is organized and within reach.
That changes the project. Rather than asking AI to write whole proposals, the company could use it to assemble drafts from approved prices and product descriptions, and leave pricing exceptions, negotiations and legal terms to people. It’s less ambitious than full automation. It’s also clearer in purpose and easier to manage.
A promising candidate for AI help usually has four things going for it. The task comes up often enough for small gains to add up. It eats real time or money. You can judge the output against a clear standard. And doing it well matters to the business. None of these guarantees success. A frequent task can still be a poor candidate if errors are hard to spot, and a rare one can deserve attention if each case is expensive.
Ask the people who do the work. A manager may call the monthly report a writing job, while the staff who prepare it know that most of the effort goes into reconciling spreadsheets that don’t agree. In that case, cleaning up the data could be worth more than buying a better writing assistant.
Before picking a tool, the business should be able to state the problem in a sentence, name the current bottleneck and say what a better result would look like. “Use AI to improve reporting” can’t be tested. “Reduce the time needed to prepare the monthly report without increasing factual errors” can.
There’s an opportunity cost, too. Time spent experimenting with one application is time not spent fixing something else. One well-chosen, modest use case is often a better investment than several projects launched just to show the company is keeping up.
7.2 Choose a solution that fits the work
Once the problem is clear, judge the technology against it. No single model suits every company, and the most capable general-purpose system isn’t automatically the best fit.
A marketing team producing public content may care most about writing quality, language support and ease of editing. A company working with internal documents will care more about access controls, document retrieval and how the provider handles data. A business building AI into its own software may need an application programming interface (API), predictable response times, structured outputs and costs that stay manageable as usage grows.
The options aren’t all the same kind of thing. A public chatbot is a way of talking to a model. An enterprise service may add administrative controls for organizations. Retrieval-augmented generation (RAG) supplies a model with relevant material from selected documents. An API lets a business build AI into an existing application or workflow. They can also be combined.
For the proposal team, a RAG system could help the model pull up the current price list and the right product specifications instead of relying on what it learned in training. But retrieving a document doesn’t mean the model reads it correctly. The document itself may be out of date, incomplete or at odds with another source. Retrieval improves access to evidence. You still have to check the answer.
The same goes for choosing a model. A more powerful one won’t fix poor records, unclear procedures or a badly designed workflow. If the tool needs reliable inventory data, that data has to exist. If a person must approve a consequential decision, the process has to keep that approval. Technology can’t stand in for business rules that haven’t been written.
Cost comparisons need the same discipline. The subscription or API price is only one part. Integration, training, administration, review and correction all add to the total. A cheaper model may do fine for low-risk drafting, while a pricier one may earn its keep by consistently cutting manual work. Let measured performance settle it, not the price list.
Before committing, compare the serious candidates on representative tasks. Use examples from real work, strip out sensitive details where needed, and decide beforehand what a satisfactory answer must contain. Then look past polish. Does the output keep the meaning of the source? Does it leave out details staff need? Can it cope with unusual cases? Is it consistent from one run to the next? How much editing does it need before someone can use it?
That last question can decide everything. Two tools may produce equally polished drafts while one needs far more correction, and a comparison based on looks alone might pick the tool that creates more work.
The goal isn’t to find the best model in the abstract. It’s a solution that works well enough on the task at hand, fits the company’s constraints and beats the current process.
7.3 Test the value before scaling
A pilot should answer a business question, not just show that a tool works.
Before the proposal team starts, the company needs a baseline: how long proposals take, how often figures or terms need correcting, how long customers wait for an offer and how often legal has to step in. Without those numbers, a pilot gives you impressions, not a comparison you can trust.
Use proposals that reflect what the team actually handles. Testing only simple quotes will mislead if the tool is eventually meant to help with complex bids. Where you can, compare similar cases under the old and new processes, hold both to the same quality standard and record how long people spend reviewing what the tool produced.
Section 6.5 gave a rough way to think about value: time saved, minus the cost of verifying and correcting, minus the expected cost of errors. The pilot supplies the evidence for each piece. Without measurements, the calculation is just arithmetic on assumptions.
Research shows both why this matters and why context counts. In a study published in The Quarterly Journal of Economics in 2025, Brynjolfsson, Li and Raymond looked at a generative AI conversational assistant used by 5,172 customer-support agents. Access to the assistant raised productivity, measured as issues resolved per hour, by 15% on average. The effects varied a lot. Less experienced and lower-skilled agents improved both the speed and quality of their work, while the most experienced and highest-skilled agents saw small gains in speed and small declines in quality (Brynjolfsson, Li and Raymond, 2025).
That’s useful evidence because it tracks changes in a real workplace instead of relying on what employees say about their own productivity. It doesn’t show that every support team will gain 15%. The study covered one tool in one organization doing one kind of work. The broader lesson is that the effects of AI vary by person and by task, so a business should test its own assumptions instead of treating someone else’s result as a forecast.
A good pilot measures the finished job, not just the stage the tool speeds up:
- Time: How long does the whole task take, including review and correction?
- Quality: Does the final result meet the standard of the current process?
- Errors: What mistakes occur, and what would they cost?
- Operating cost: What do software, integration, training and oversight add?
- Business outcome: Does the change improve the customer experience, cut delays, add capacity or serve another stated goal?
Let the purpose of the project decide what you measure. If the aim is better customer service, faster drafting means little when answers get less accurate. If the aim is quicker reporting, count the time to a report that’s ready to use, not the time to a first summary.
Return on investment (ROI) can help structure the financial case, as long as the calculation is transparent:
ROI = ((Total financial benefits − Total costs) ÷ Total costs) × 100
Define the measurement period and include the implementation and running costs. Also keep cash savings separate from extra capacity. If AI frees up 100 employee hours but salaries stay the same, the company hasn’t necessarily saved that amount in cash. Those hours can still be worth something if people use them to handle more customers, clear a backlog or take on work that would otherwise wait. Just describe the benefit accurately instead of presenting extra capacity as an automatic cut in spending.
When the pilot ends, make the decision explicit: expand, revise, restrict or stop. A modest benefit may justify keeping a tool for a cheap task. A tool that saves a lot of time but introduces errors that are hard to detect may not deserve wider use. What counts is the value of the whole workflow.
Scale on evidence, not enthusiasm. A good result with one small team doesn’t prove the process will work in every department, language or customer group. Keep watching performance after you expand, and revisit the decision if costs, error patterns or uses change.
7.4 Redesign the work and prepare the people doing it
Bringing in AI usually changes how work is divided up before it changes how many jobs there are. A task that used to mean gathering information, writing a draft and revising it may become AI-assisted preparation followed by a tighter human review. Someone has to decide how those stages fit together.
This is where implementations succeed or stall. If people are told to use AI but their workloads, deadlines and approval steps stay the same, they may have little time to learn the tool or check its output properly. If the company expects more output just because drafting got faster, the saved time can vanish without any gain in quality or service.
Redesign starts by deciding which parts of a task the system handles, which need human judgment, and where information or approval has to pass between them. For the proposal team, the tool might organize background material and prepare a draft from approved data. An employee would then verify the figures, assess what the customer needs and approve the offer. The point isn’t to keep every step of the old process. It’s to keep the steps that protect quality and create value, and drop the effort that does neither.
People need training that matches their new responsibilities. Knowing how to write a prompt helps, but it isn’t enough. They have to understand the underlying task, recognize unsupported claims, check the details that matter and know when not to use an answer. Use examples from their own work, so the gap between a plausible answer and a reliable one becomes concrete.
The Brynjolfsson, Li and Raymond study is relevant here. Its findings suggest that AI assistance can help less experienced employees benefit from the practices of more productive colleagues. The authors also report evidence of learning over time (Brynjolfsson, Li and Raymond, 2025). That bears on the concern raised in Section 6.3: employees who lack experience may find it harder to recognize mistakes, even when AI helps them finish tasks faster.
The two points don’t contradict each other, but the distinction matters. In the support setting the researchers studied, the assistant made suggestions inside a process where outcomes could be observed and performance measured. That gave people a way to judge the help they were getting. This is an interpretation, not a finding of the study. Where a task has no clear quality signal and a novice has to judge the generated answer alone, the risk remains. AI can support learning, but it can’t guarantee it.
For a company, the practical question is whether the workflow gives people a reliable way to learn from the tool and to evaluate it. If AI prepares every first draft, new employees may lose the chance to practice the underlying skill unless the company deliberately keeps it. The tool is more likely to help them learn when they compare its suggestions with reliable examples, explain why they accept or reject them and get feedback from experienced colleagues.
Managers should also look at how the workload shifts for reviewers. AI may cut preparation time while raising the demand for checking, handling exceptions and final approval. Those duties need to show up in staffing and performance expectations. Otherwise people are expected to produce more while quietly taking on extra responsibility without the time to manage it.
Nobody needs to become an AI specialist. What people need is enough technical familiarity to use the tools in their roles, enough knowledge of their own work to judge the results, and the sense to recognize when the system has hit its limits.
7.5 Build governance that supports useful adoption
A business can start with one approved tool and one team. As use spreads, departments may buy their own subscriptions, connect models to different information sources or build overlapping workflows. Without coordination, management can lose track of what’s in use, what information is being processed and who’s responsible.
Governance is how you manage that growth. It should set practical boundaries without turning every small experiment into a long approval process.
The U.S. National Institute of Standards and Technology published its Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile in July 2024. It offers voluntary guidance for identifying and managing generative AI risks across the technology’s lifecycle (Autio et al., 2024). It isn’t a legal requirement, but it gives organizations a structured reference they can adapt to their size, activities and tolerance for risk.
For a business, the starting point can be simple. Keep a list of approved tools and significant uses. Spell out what information may go into each service. Give every important application a business owner. Decide who can approve a new use and what review is needed before anyone relies on its outputs.
Controls should fit the task. A tool used to brainstorm public marketing ideas doesn’t need the same process as one that analyzes confidential records or feeds into decisions about customers or employees. Treating every use as equally risky wastes effort. Treating every use as equally harmless leaves gaps that matter.
Make it easy to report problems. People should know what to do if a system gives a misleading answer, exposes information unexpectedly or behaves differently after an update. A clear process says who investigates, when use should be suspended and what evidence is needed before it resumes.
Legal compliance needs its own attention. Obligations can come from privacy, consumer protection, employment, copyright, cybersecurity or AI-specific law, depending on the jurisdiction and the use. A general AI policy doesn’t automatically satisfy them. Businesses need to work out which rules apply to their activities and get specialist advice where necessary.
Good governance makes responsible use easier. People are more likely to follow a policy when approved tools are easy to get, the instructions are clear and requests for new uses are handled in proportion to the risk. If the official route is impractical, people keep using tools on their own, out of management’s view, which is exactly the problem the policy was meant to prevent.
And governance never really finishes. Providers update their systems, employees find new uses and business processes change. A use that was fine for one purpose can become inappropriate when the data, the scale or the consequences change. Reviewing the rules from time to time keeps them in line with the work being done.
7.6 Make the strategy adaptable
A successful pilot shows that one application may be useful. It doesn’t settle how the company should use AI over the long run. A lasting strategy has to deal with the shared foundations that let good applications grow without piling up complexity and dependence.
One risk is fragmentation. Teams buy tools that do similar jobs, keep separate versions of the same internal information, or rely on one employee to run a workflow nobody else understands. Each project can look successful on its own while the whole system gets more expensive and harder to maintain.
A more durable approach separates shared needs from team-specific choices. Security requirements, access management, vendor assessment and core data standards often work better with central coordination. The workflow itself should fit the team doing the work. Where to draw the line depends on the organization’s size, technical capacity and risk profile.
Data quality is often part of this foundation. A model can’t reliably answer questions about company policy if the source documents contradict one another or employees can’t tell which version is authoritative. Before investing in a complex AI system, a business may need to improve its document management, remove outdated material, clarify who can see what and settle on a reliable source for key information. That work is less visible than launching a new application, but it can decide whether the application stays useful.
Vendor dependence deserves a look too. A workflow built around one provider’s distinctive features can be expensive to move if that provider changes its terms, prices or capabilities. Where practical, document your processes, keep control of your underlying data and think about how important applications could be moved. Portability isn’t free, and it isn’t worth maximizing in every project. What matters is understanding the trade-off before the business gets locked into a costly arrangement.
Investment should follow demonstrated need. Not every business needs a custom model, a large AI team or an elaborate automated system. Existing tools can handle many tasks. More complex infrastructure starts to make sense when a recurring problem, a measurable opportunity and the organization’s technical capacity justify the extra cost.
A long-term plan should set a few concrete objectives and review them regularly: shorter reporting times, more consistent customer responses, more time for specialists to handle complex cases. Each objective needs a baseline, an owner and a way to measure the result. The business should also watch for side effects, such as more correction work, lower quality or a new dependence on one provider.
The strategy has to be able to change when the evidence does. A use case may turn out less valuable than expected. A better model may make an application practical that wasn’t before. New requirements or new kinds of data may call for extra safeguards. A business that reviews its decisions can respond without treating every product announcement as a reason to start over.
This matters most for small and medium-sized businesses, where tight budgets make careful choices essential. They can begin with existing tools, a clearly defined task and a realistic pilot, then expand only where the results justify more investment. Copying a technology giant’s AI infrastructure isn’t the goal. Solving the business’s own problems in a way it can manage is.
Go back to the proposal team. A year on, success isn’t measured by how many AI tools the company has bought. It’s whether proposals go out faster with fewer corrections, whether employees can trace where the figures came from, and whether the team would notice and fix the problem if the price list went out of date.
If those things are true, the company has done more than adopt generative AI. It has built a better way of working around it. Access to a capable model is widely available. The discipline to turn that capability into reliable business value is harder to copy.
8. What Comes Next: The Future of Generative AI Beyond 2026
Fluent text and convincing images don’t surprise anyone anymore. What’s more interesting is what happens when these systems stop answering questions and start doing the work: moving through the steps of a business process, reacting to new information, taking actions that used to need a person.
That won’t happen at the same speed everywhere. Some companies are already trying out AI agents in several functions. Others are still struggling to make basic AI tools reliable and affordable. McKinsey’s 2026 global survey shows the split. Although 80% of respondents said AI had improved their personal productivity, only 37% reported at least some impact on their organization’s earnings before interest and taxes (EBIT), about the same as the year before (McKinsey, 2026).
That gap explains a lot. Technology is only one ingredient. Data quality, how a company is organized, what its people know, what the systems cost to run, and how much risk comes with letting software act alone all decide whether a good capability turns into lasting value. Three developments show where this could go beyond 2026: AI that acts, AI that handles many kinds of information at once, and AI that changes how businesses make and deliver what they sell.
8.1 From Answering to Acting: Autonomous AI Systems
Most of us use generative AI the same way. We ask, the model answers, and we decide what to do with the answer. We’re the link between every step. We check the output, carry it forward, and finish the job.
Agents change that. Give an agent an objective and it can split the task into steps, look up information, use approved tools, take actions, and check its own results before moving on. Some coordinate several tasks at once or work with other software. Instead of helping with one thing, an agent can take part in a whole workflow.
Take a company writing a proposal for a prospective client. An agent could pull details from approved company records, match the client’s requirements against the services on offer, flag what’s missing, write a first draft, and pass it to an employee for review. That employee still has to decide whether the proposal is accurate, makes commercial sense, and promises only what the company can deliver.
Now let the agent send the proposal itself. Say it copies a price from an outdated record. If a person reviews the draft first, the mistake gets caught before anyone outside sees it. If the agent sends it straight to the client, the wrong price is out, and the client might hold the company to it. The mistake is the same size either way. The difference is whether anyone had a chance to catch it.
That’s the principle: the amount of checking should match how much freedom the system has. A wrong price in a draft is easy to fix. The same slip in a live workflow can reach customers, records, payments, or contracts. More autonomy can cut down on routine supervision, but it also makes it more important to decide exactly what the system is allowed to do.
A Ladder of Autonomy
It helps to think of autonomy as a ladder with four rungs:
- Suggest. The system recommends an action, but a person carries it out.
- Act with approval. The system prepares an action, and a person approves it before it happens.
- Act, then report. The system acts within defined limits, and a person reviews the results afterwards.
- Act independently. The system works within an authorized scope and is monitored through periodic audits and exception reports.
These rungs aren’t a standard. They’re just a handy way to talk about how much authority a task deserves. The right rung depends on what a mistake would cost, how easily the action can be undone, and whether the result can be checked reliably.
Drafting an internal summary, tagging a support ticket, or reformatting a document can sit higher up, since errors are cheap to fix. Sending confidential information, committing large sums, creating legal obligations, or making decisions that seriously affect someone’s livelihood needs stronger safeguards and, often, an explicit human sign-off.
None of this means a high-stakes task has to stay manual forever. Autonomy should be earned. A business needs to know what the system does reliably, where it tends to fail, and how fast a failure can be spotted and contained.
Adoption numbers tell us companies are heading toward agents, not that agents are ready to run complex workflows unsupervised. In McKinsey’s 2026 survey, 40% of respondents at organizations with annual revenues above $1 billion said they were scaling AI agents in at least one function, up from 27% a year earlier. Among smaller organizations the figure stayed at 22% (McKinsey, 2026). Big companies are pulling ahead. But adoption isn’t reliability, and these numbers say nothing about whether the hard parts of deployment have been solved.
For the years after 2026, the sensible path is to start small. Give an agent a narrow set of actions, measure how it does under real working conditions, look into every failure, and widen its authority only when the evidence supports it. How far agents go will depend on the models, yes, but just as much on the limits, monitoring, and recovery plans built around them.
8.2 From Typing to Showing: Real-Time AI Across Text, Images, Audio, and Video
Business has never run on text alone. People work with meetings, phone calls, photos, product demos, recordings, diagrams, spreadsheets, and live operational data. AI that can read and produce several of these together is most useful where a written prompt can’t capture the whole situation.
A customer-service team could pair a customer’s spoken description with a photo of the damaged product. A technician might use a system that compares what the camera sees with the maintenance records. A marketing team could build one campaign across text, images, and video and tailor it to different audiences. In each case the gain comes from joining up information that would otherwise sit in separate tools or take manual effort to connect.
The next step isn’t more file formats. It’s speed of interaction. Today you upload a recording and wait for a transcript. Soon you might talk to a system, show it an object through a camera, hear a reply, and correct it in the same conversation. If it proves reliable, that could support interactive training, remote assistance, live product demos, and quicker access to operational knowledge.
It’s also hard to build. The system has to coordinate different models and kinds of data while balancing response time, computing cost, and quality. Qiu and colleagues’ 2026 StreamWise research looks at exactly this: serving multimodal generation at scale. In the cheapest setup they tested, a ten-minute podcast video generated on A100 GPUs took about 1.4 hours, roughly 8.4 times the video’s running time, for less than $25. Real-time streaming at high quality was possible too, at less than $45 per video (Qiu et al., 2026). What the study shows is the trade-off between speed, cost, and quality. It doesn’t show that every real-time business application is practical or affordable yet.
Reliability is another problem. A system that misreads a photo might recommend the wrong repair. A voice assistant can trip over an accent, a technical term, or a noisy room. A video generator can produce something convincing that’s wrong in the details. And when several kinds of information are combined, a mistake in one can bend the final answer without the user noticing.
So test it where it will actually be used. A great demo in a quiet room doesn’t help someone in a noisy warehouse, a crowded service area, or a place with weak connectivity. Language coverage, accessibility, privacy, running costs, and what a misunderstanding would cost all belong in the evaluation.
If these problems get solved, using AI could feel different. You wouldn’t open a separate app and turn every problem into text. You’d work with something that understands what you’re looking at, listening to, or explaining. That matters most for work with physical objects, inspections, demonstrations, or decisions that can’t wait.
But it depends on the task. A multimodal system may add little where a plain text box already works. Businesses should ask whether the extra capability solves a real problem before paying for the extra cost and complexity.
8.3 From Feature to Foundation: AI-Native Business Models and New Human–AI Collaboration
The biggest change may turn out to be organizational, not technical. Many businesses will bolt AI features onto existing products and processes and enjoy useful efficiencies. Others may use it to ask more basic questions: what do we offer, how do we deliver it, and which parts of the work really need people?
An AI-native business builds AI into the design of a product, service, or operation from the start, not as an optional extra added after the main decisions are made. A small firm might offer personalization that once took a much bigger team. A software company might build a service that adapts to each customer’s workflow instead of a fixed set of features. A professional-services firm might pair automated preparation and analysis with human judgment, specialist knowledge, and direct client relationships.
That could change how competition works. If AI cuts the cost of drafting, prototyping, analysing information, or building basic software, some barriers to entering a market come down, and smaller businesses may get capabilities that used to be affordable mainly for large ones.
But competitors get the same tools. When several businesses can churn out similar content, prototypes, or routine analyses, producing more of it stops being an advantage. What counts is what a company does with these capabilities and whether customers get something meaningfully better.
The OECD’s review of experimental research on generative AI points to potential benefits for productivity, innovation, research and development, and entrepreneurship. It also highlights evidence that outcomes vary with the task and the user’s experience, while noting that evidence on long-term business effects remains incomplete (Calvino, Reijerink, and Samek, 2025). Lower costs open doors. They don’t guarantee a sustainable business, because customers still need a reason to pick one provider over another.
What lasts is harder to copy: trusted customer relationships, proprietary data used responsibly, deep knowledge of an industry, good distribution, distinctive services, and an experience customers can rely on with AI built in. A company that publishes more content or builds more prototypes gains little if its output looks like everyone else’s.
The way people and AI share work will have to change too. AI is good at generating alternatives, handling large volumes of information, spotting patterns, and preparing routine material. People remain essential for setting goals, reading sensitive situations, weighing competing priorities, challenging assumptions, and taking responsibility for decisions that matter. The line between the two will move as systems improve, and it should move based on what’s been observed, not on assumptions about what humans or AI can do.
Nor will every employee automatically get less repetitive work and more time for higher-value tasks. That depends on how a business redesigns its processes, assigns responsibility, and trains its people. In some places AI will take over tedious work. In others it may add new review duties, speed up the pace, or push responsibility onto people without enough support.
Managers will need to look at how AI changes a whole process, not just count the tasks a tool finishes. They should also ask who gains and who pays. Workers may face new performance expectations, customers may get faster service but less personal attention, and owners may take on new costs for software, computing, training, and oversight.
Nothing guarantees that AI-native models will arrive quickly or work in every industry. Regulation, customer trust, integration costs, access to suitable data, and the cost of failure may all slow things down. Some businesses will find that an established process with AI support works better than a redesign. Others will find the technology makes a different product or service possible.
So the question isn’t whether every business must become AI-native. It’s whether a business knows which parts of its value AI could improve, which depend on human relationships and expertise, and which should stay as they are. Real transformation starts there.
Looking Beyond 2026
Autonomous systems may take on longer stretches of work. Multimodal systems may make assistance faster and more aware of context. AI-native businesses may reshape how some products and services are designed and delivered. None of that guarantees reliable performance, lower total costs, or a lasting edge.
The businesses best placed to benefit will explore new capabilities without mistaking possibility for proof. They’ll experiment where the value is real, set safeguards where mistakes could do harm, and change course when the evidence says they were wrong.
That brings us back to the central argument of this book: progress isn’t measured by what a model can produce on its own, but by what an organization can achieve with it, usefully and responsibly.
Before giving an AI system more authority, a business should ask three questions:
- What is the worst thing the system could do with this permission, and could the action be reversed?
- How would we recognize an error, and who would be likely to notice it first?
- What evidence would justify expanding the system’s authority, and what evidence would require us to restrict it?
As AI becomes more autonomous, more immediate, and more deeply embedded in business processes, turning its capabilities into lasting value will remain a human, organizational, and strategic challenge. These three questions are where that work begins.
9. Frequently Asked Questions (FAQ)
What Is Generative AI, and How Does It Work?
Generative AI is software that makes new things: text, images, audio, video, code. It learns patterns from huge amounts of existing material, then produces something that matches the pattern of whatever you ask for.
“Matches” is the important word. These systems are built to produce output that looks right, and sometimes it isn’t. A model can write a confident paragraph with a wrong number in the middle, or draw a lovely picture with one detail quietly off. What you get depends on the model, on how much context you give it, and on the task. It also depends on you, because someone has to check the result. Treat whatever comes back as a quick first draft from an assistant who works fast and rarely admits when it’s guessing.
How Can Generative AI Improve Business Productivity?
Mostly by taking the first pass off your plate: drafting a document, summarizing a long report, throwing out ideas, analysing a spreadsheet, handling the repetitive parts of a workflow. The time saved can be real, and sometimes large.
But it isn’t free. Someone has to check the output. Someone has to train the team and connect the tool to everything else. And someone pays to run it. McKinsey’s 2026 survey shows how easily gains disappear on the way to the bottom line: 80% of respondents said AI had improved their own productivity, yet only 37% reported at least some impact on their organization’s earnings before interest and taxes, or EBIT (McKinsey, 2026). People feel faster. That doesn’t mean the company earns more.
So test it on your own work. Pick one task, time it with the tool and without it, and count the minutes you spend checking. Decide from those numbers, not from the demo.
Can Small Businesses Benefit from Generative AI?
Yes, and you don’t need to build anything. Ready-made tools already cover customer support, marketing copy, research, admin work, and early product ideas.
Start small. Choose one problem that keeps coming back, like answering the same customer questions or writing product descriptions from scratch every time. A good first task is one you do at least weekly, that eats real time, and that you can check in a couple of minutes. Run it for a few weeks and compare it with how you did it before.
Before you commit, ask four things. What data am I handing over? What will it cost each month? Is the output good enough, often enough? And does it fit how my team actually works, or will it sit unused?
Will Generative AI Replace Human Jobs?
In many roles, what changes first is the tasks, not the whole job. A job is a bundle of tasks. AI will take some of them, leave others alone, and make a few matter more: judgment, talking to people, keeping an eye on the work, knowing the subject deeply. How it plays out depends on the occupation, the organization, and how carefully the work is redesigned.
If you manage people, try this. Write down the tasks in a role and sort them into three piles: things AI can prepare while a person decides, things it can handle with a review, and things that must stay in human hands. Then ask what that does to the people doing the work: their skills, their responsibilities, how their days feel. If a tool leaves them with more checking to do and less support, calling it efficient doesn’t make it better.
What Are the Main Risks of Using Generative AI in Business?
Most of the risks are easy to name. Answers can be wrong or invented. Confidential information can leak. Intellectual property can get complicated. Bias can creep in. Security can have gaps. And people can lean on automated decisions more than they should.
The fixes are mostly ordinary good practice. Have a person review anything where a mistake would matter. Decide which tools can receive which data, and who gets access. Before you publish or sell generated content, check the ownership terms, usage rights, and legal requirements that apply. Test results across the different groups of people the system affects. Limit what a tool can reach and what it can do. And name one person who is accountable for important decisions, so “the AI did it” is never the answer.
The risk grows when a system can act, not just write. A tool that drafts an email is one thing; a tool that sends it is another. That’s the logic behind the ladder of autonomy in Section 8: the more freedom a system has, the more checking it needs. Whatever you put in place, test it regularly and have a plan for noticing and fixing failures.
How Can a Business Measure the ROI of Generative AI?
Compare what the initiative earns with what it costs over a set period. Costs include software, computing, integration, training, human review, maintenance, and risk management. The usual formula is:
ROI = ((Total financial benefits − Total costs) ÷ Total costs) × 100
For illustration, say a tool brings in $26,000 of measurable benefit over a year and costs $20,000 once every expense is counted. Then:
ROI = (26,000 − 20,000) ÷ 20,000 × 100 = 30%
The benefit side is where people fool themselves. Hours saved aren’t money until the time goes to something that is. Subtract the hours spent checking and correcting. Add the costs that are easy to forget, like training and changes to your processes.
Alongside the number, watch processing time, error rates, customer satisfaction, and service quality. A positive ROI means something only if the results behind it are reliable and last.
Conclusion: Turning Generative AI into Lasting Business Value
A business can adopt the latest AI tools, give its employees access to powerful models, and produce more in less time, and still be no better off than it was before. The work may look different. The results may arrive faster. But if nobody can explain what has improved, what it has cost, or what has become harder to get right, the business has more technology without necessarily having more value.
This is the distinction that matters. Generative AI can make it easier to produce a draft, explore an idea, analyse information, or move a task through several stages. Those capabilities are real. But between a capability and a business result lie decisions that no model can make on an organization’s behalf: which problems deserve attention, what quality means in a particular context, which risks are acceptable, and when a seemingly useful shortcut creates more work somewhere else.
That’s why the most revealing moment in an AI project often comes after the first impressive result. A draft still needs a reader. An analysis still needs someone who understands the question. An automated action still needs boundaries, and a failure still needs someone who knows what to do next. None of that goes away with a better model. It’s part of the real cost of using the technology, and part of the work of using it well.
As AI systems become more capable, the decisions around them will become more consequential. Agents may handle longer sequences of work; multimodal systems may help people interpret information in new ways; and some businesses may be built around AI rather than adapting it to existing operations. Such changes could create genuine opportunities. They could also make mistakes travel faster, obscure responsibility, or encourage companies to automate processes they haven’t fully understood.
No single response will suit every business. One organization may gain a lasting advantage by redesigning a service around AI. Another may benefit most from giving employees a reliable assistant. A third may find that the cost, uncertainty, or consequences of failure make automation the wrong choice for a particular task. These aren’t stages on a universal path to becoming an AI-powered company. They’re decisions that depend on the work, the people involved, and the value the business is trying to create.
The temptation will be to judge progress by what the technology can do. That is the easiest thing to demonstrate: a fluent answer, a striking image, a task completed in seconds. The harder question is what remains after the demonstration ends. Did the customer receive a better service? Did the decision improve? Was time genuinely freed for more valuable work? Could the result be trusted, and could the organization explain what happened when it was wrong?
Those questions don’t undercut the promise of generative AI. They’re the standard it has to meet.
Ultimately, the goal isn’t to put AI into as many tasks as possible. It’s to make better decisions about which tasks deserve it, where human judgment remains essential, and what evidence should be required before a system is trusted with more. The organizations that understand this will be better placed to benefit from the technology without mistaking activity for progress.
The future of generative AI in business will be decided by what people can responsibly build, improve, and sustain with it, more than by what the technology can produce alone.
References
- Autio, C., Schwartz, R., Dunietz, J., Jain, S., Stanley, M., Tabassi, E., Hall, P., & Roberts, K. (2024). Artificial intelligence risk management framework: Generative artificial intelligence profile (NIST AI 600-1). National Institute of Standards and Technology. https://doi.org/10.6028/NIST.AI.600-1
- Bastani, H., Bastani, O., Sungu, A., Ge, H., Kabakcı, Ö., & Mariman, R. (2025). Generative AI without guardrails can harm learning: Evidence from high school mathematics. Proceedings of the National Academy of Sciences, 122(26), Article e2422633122. https://doi.org/10.1073/pnas.2422633122
- Bloomberg News. (2025, May 8). Klarna turns from AI to real person customer service. Bloomberg.
- Brynjolfsson, E., Li, D., & Raymond, L. (2025). Generative AI at work. The Quarterly Journal of Economics, 140(2), 889–942. https://doi.org/10.1093/qje/qjae044
- Burgess, P., Williams, I., Qu, L., & Wang, W. (2024). Using generative AI to identify arguments in judges’ reasons: Accuracy and benefits for students. Law, Technology and Humans, 6(3), 5–22. https://doi.org/10.5204/lthj.3637
- Calvino, F., Reijerink, J., & Samek, L. (2025). The effects of generative AI on productivity, innovation and entrepreneurship (OECD Artificial Intelligence Papers No. 39). OECD Publishing. https://doi.org/10.1787/b21df222-en
- Chandrasekaran, A. (2026, January 26). Why half of GenAI projects fail: Avoid these 5 common mistakes. Gartner. https://www.gartner.com/en/articles/genai-project-failure
- Colabianchi, S., Costantino, F., & Sabetta, N. (2024). Assessment of a large language model based digital intelligent assistant in assembly manufacturing. Computers in Industry, 162.
- Cook, S., Hagiu, A., & Wright, J. (2024, January–February). Turn generative AI from an existential threat into a competitive advantage. Harvard Business Review. https://hbr.org/2024/01/turn-generative-ai-from-an-existential-threat-into-a-competitive-advantage
- Cui, Z. K., Demirer, M., Jaffe, S., Musolff, L., Peng, S., & Salz, T. (2025). The effects of generative AI on high-skilled work: Evidence from three field experiments with software developers. Management Science. https://doi.org/10.1287/mnsc.2025.00535
- Deloitte. (2026). The state of AI in the enterprise. Deloitte AI Institute. https://www.deloitte.com/us/en/what-we-do/capabilities/applied-artificial-intelligence/content/state-of-ai-in-the-enterprise.html
- European Parliament & Council of the European Union. (2024). Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence (Artificial Intelligence Act). Official Journal of the European Union. https://eur-lex.europa.eu/eli/reg/2024/1689/oj
- European Parliament & Council of the European Union. (2026). Regulation (EU) 2026/1744 of the European Parliament and of the Council of 8 July 2026 amending Regulations (EU) 2024/1689, (EU) 2018/1139 and (EU) 2023/1230 as regards the simplification of the implementation of harmonised rules on artificial intelligence (Digital Omnibus on AI). Official Journal of the European Union, 24 July 2026.
- Gartner. (2024, July 29). Gartner predicts 30% of generative AI projects will be abandoned after proof of concept by end of 2025. https://www.gartner.com/en/newsroom/press-releases/2024-07-29-gartner-predicts-30-percent-of-generative-ai-projects-will-be-abandoned-after-proof-of-concept-by-end-of-2025
- Gartner. (2025, June 25). Gartner predicts over 40% of agentic AI projects will be canceled by end of 2027. https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-predicts-over-40-percent-of-agentic-ai-projects-will-be-canceled-by-end-of-2027
- Gutkowski, V., Gascon, C. S., & Silvanus, R. (2026, July 16). New survey findings on AI adoption and its effects on employment and productivity. Federal Reserve Bank of St. Louis. https://www.stlouisfed.org/on-the-economy/2026/jul/new-survey-findings-ai-adoption-eighth-district
- Klarna. (2024, February 27). Klarna AI assistant handles two-thirds of customer service chats in its first month [Press release]. https://www.klarna.com/international/press/klarna-ai-assistant-handles-two-thirds-of-customer-service-chats-in-its-first-month/
- Ma, S. P., Liang, A. S., Shah, S. J., Smith, M., Jeong, Y., Devon-Sand, A., Crowell, T., Delahaie, C., Hsia, C., Lin, S., Shanafelt, T., Pfeffer, M. A., Sharp, C., & Garcia, P. (2025). Ambient artificial intelligence scribes: Utilization and impact on documentation time. Journal of the American Medical Informatics Association, 32(2), 381–385. https://doi.org/10.1093/jamia/ocae304
- Mata v. Avianca, Inc., No. 22-cv-1461 (S.D.N.Y. June 22, 2023).
- McKinsey & Company. (2025). The state of AI in 2025: Agents, innovation, and transformation. https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai
- McKinsey & Company. (2026, August 25). The state of AI in 2026: On the road to ROI. https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai
- Moharrak, M., & Mogaji, E. (2025). Generative AI in banking: Empirical insights on integration, challenges and opportunities in a regulated industry. International Journal of Bank Marketing, 43(4), 871–896. https://doi.org/10.1108/IJBM-08-2024-0490
- Ni, X., Wang, Y., Feng, T., Lu, L. X., Wang, Y., & Zhou, C. (2026). Generative AI in action: Field experimental evidence from Alibaba’s customer service operations [Preprint]. arXiv. https://arxiv.org/abs/2603.29888
- Noy, S., & Zhang, W. (2023). Experimental evidence on the productivity effects of generative artificial intelligence. Science, 381(6654), 187–192. https://doi.org/10.1126/science.adh2586
- OECD. (2025). Generative AI and the SME workforce: New survey evidence. OECD Publishing. https://www.oecd.org/en/publications/generative-ai-and-the-sme-workforce_2d08b99d-en.html
- OpenAI. (n.d.). Morgan Stanley uses AI evals to shape the future of financial services. https://openai.com/index/morgan-stanley/
- Qiu, H., Chaudhry, G. I., Zhang, C., Goiri, Í., Choukse, E., Fonseca, R., & Bianchini, R. (2026). StreamWise: Serving multi-modal generation in real-time at scale [Preprint]. arXiv. https://arxiv.org/abs/2603.05800
- Stanford Institute for Human-Centered Artificial Intelligence. (2026). The AI Index 2026 annual report. Stanford University. https://hai.stanford.edu/ai-index
- U.S. Copyright Office. (2025). Copyright and artificial intelligence, Part 2: Copyrightability. https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf
- World Economic Forum. (2026). Global cybersecurity outlook 2026. https://www.weforum.org/publications/global-cybersecurity-outlook-2026/

No comments:
Post a Comment