Updates from Peruzzi

Blog posts

How to move from an AI prototype to production: An enterprise AI roadmap
AI 5 min read
LinkedIn
How to move from an AI prototype to production: An enterprise AI roadmap

Building an AI prototype is relatively easy, it can be done even in 10 days. But turning that prototype into a production-ready AI solution that delivers measurable business value? This is where most organisations struggle.

Many enterprise AI projects begin with a successful proof of concept (PoC). The AI model performs well, stakeholders are impressed, and the business sees real potential. Yet months later, the project is still stuck in pilot mode, unable to scale across the organisation. If you’re wondering how to move from an AI prototype to production, the answer isn’t to build more AI. It’s to follow a structured enterprise AI implementation roadmap that reduces risk while delivering measurable business outcomes.

In this article we guide organisations through every stage of AI implementation: from the initial assessment to a fully managed production environment.

Why enterprise AI projects stall after the Proof of Concept

One of the biggest misconceptions in enterprise AI is that a successful AI proof of concept automatically leads to a successful deployment. In our previous article, Why 95% of enterprise AI projects never make it beyond the Proof of Concept, we already established what the main mistakes are made. In this article however, we would like to share a pilot-to-production roadmap.

To begin with, the PoC answers one question: Can this AI solution work?

But, the production asks a completely different question: Can this AI solution operate securely, reliably, and at enterprise scale?

See the difference? Many AI initiatives fail because organisations attempt to jump directly from a prototype to production without validating the business case, preparing their data, or establishing governance. Successful AI deployment requires much more than a working mode: a roadmap.

The enterprise AI roadmap: From assessment to managed service

In this roadmap, we will share the phases, the challenges and goals as an enterprise AI roadmap to help organisations with implementing their AI POCs.

1, Phase 1 - AI assessment

Goal: Validate the business opportunity before investing in development. Every successful AI implementation starts with understanding the business problem, not the technology. An AI assessment identifies where AI can deliver measurable value while evaluating data quality, technical feasibility, governance requirements, and expected return on investment.

Deliverables:

  • Business use case prioritisation
  • AI strategy roadmap
  • Data readiness assessment
  • High-level solution architecture
  • Cost-benefit analysis

2, Phase 2 - AI Proof of Concept (PoC)

Goal: Validate technical feasibility. The purpose of an AI Proof of Concept isn’t to build a finished product, it’s to prove that the proposed solution can solve a defined business challenge. This phase should remain intentionally focused on one workflow, one business process, or one high-value use case.

Deliverables:

  • Working AI prototype
  • Initial integrations
  • Technical validation
  • Early KPI measurements
  • User feedback

3, Phase 3 - Minimum Viable Product (MVP)

Goal: Create the first production-ready AI application. This is where many organisations discover that the hardest work is no longer AI, rather the AI production readiness.

An MVP introduces the capabilities that transform a prototype into a usable business solution:

  • Secure authentication
  • Role-Based Access Control (RBAC)
  • Human-in-the-loop workflows
  • Monitoring and logging
  • Governance
  • User experience
  • Integration with existing business systems

This is the stage, where the AI stops being a demonstration and becomes an enterprise application.

4, Phase 4 - AI Production Deployment

Goal: Deliver a secure, scalable enterprise AI solution. Moving an AI solution into production is an operational readiness exercise.

Before go-live, organisations should validate:

  • AI governance
  • Security
  • Compliance
  • Performance
  • Disaster recovery
  • Cost monitoring
  • User adoption
  • Operational ownership

This is the point where AI deployment becomes business transformation.

5, Phase 5 - Managed AI Services

Goal: Continuously improve AI after deployment. A successful AI implementation doesn’t end when the solution goes live. Business requirements evolve, data changes, models improve, regulations shift. Without ongoing optimisation, today’s successful AI solution becomes tomorrow’s technical debt.

Managed AI Services ensure:

  • Performance monitoring
  • AI regression testing
  • Security updates
  • Cost optimisation
  • Continuous improvement
  • User support
  • Platform maintenance

Production AI isn’t a project, it’s an operating capability.

Why does this AI roadmap reduce risks?

A structured AI implementation roadmap gives every stakeholder confidence. The CFO should see that every investment phase has measurable outcomes and clear budget control. The Risk & Compliance team has to be sure that governance and security are introduced before enterprise rollout. The CIO & CTO should see that the architecture, scalability, and integrations are validated before production. The Business Sponsors must be sure that the value is demonstrated incrementally rather than waiting for a “big bang” deployment.

This phased approach significantly reduces the risk associated with enterprise AI deployment.

Our approach to AI implementation

We specialise in helping organisations move from AI prototype to production. In order to do so, rather than treating AI as a standalone development project, we deliver a structured enterprise AI implementation framework built around measurable business value.

This roadmap helps organisations reduce delivery risk, accelerate time to value, and build secure, scalable AI solutions on Microsoft Azure.

Ready to move from AI prototype to production?

If your organisation has a promising AI prototype but isn’t sure how to achieve AI production readiness, the next step isn’t more experimentation, it’s a structured roadmap. Discover how we help organisations accelerate AI implementation, reduce deployment risk, and build production-ready enterprise AI solutions that deliver measurable business outcomes.

10/08/2026
Microsoft Fabric data agents: Why a great demo isn't enough for production
AI 5 min read
LinkedIn
Microsoft Fabric data agents: Why a great demo isn't enough for production

When organisations first implement a Microsoft Fabric Data Agent, the results are often impressive. Executives can ask business questions in natural language, receive instant insights, and experience conversational analytics for the first time. It’s an exciting milestone, but it isn’t the finish line.

Many organisations mistake a successful demonstration for AI production readiness. In reality, the hardest part begins after the demo. Enterprise AI isn’t judged by how well it performs in a workshop, rather by whether business leaders can trust the answers when they’re making financial, operational, or strategic decisions. That’s why production-ready Microsoft Fabric Data Agents require much more than an impressive proof of value.

The new risk of conversational analytics

Traditional reporting platforms provide governed dashboards built on carefully defined business logic. A Microsoft Fabric Data Agent changes that experience completely. Instead of opening reports, users ask questions in natural language. The AI identifies the relevant semantic model, generates queries, applies filters, and produces an answer in seconds. This creates a completely new operational risk.

An answer can be:

  • Fluent
  • Confident
  • Plausible

…and still be wrong.

Perhaps the wrong semantic model was selected, or the AI interpreted “revenue” differently from Finance. Maybe a complex filter combination excluded important records, or a recent semantic model update unintentionally changed answers that previously worked perfectly. These are never obvious failures, as they’re the silent ones. And that’s exactly what makes enterprise AI governance so important.

Why five successful questions don’t prove anything

One of the biggest mistakes organisations make during a Microsoft Fabric Proof of Value is relying on manual demonstrations. A handful of stakeholders ask familiar questions: the answers look correct, the project gets approved, but unfortunately, that isn’t an acceptance test.

Enterprise AI platforms should never be approved because five questions worked during a meeting. They should be approved because they continue delivering accurate answers after:

  • semantic models change
  • new data sources are introduced
  • business definitions evolve
  • AI instructions are updated
  • permissions are modified
  • new users begin asking unexpected questions

A successful demo proves your Microsoft Fabric Data Agent can answer questions, but it doesn’t prove it can answer the next thousand correctly.

Production AI starts with measurable trust

We believe trusted AI starts with trusted data, as we already showed results of implementing Microsoft Fabric for financial data modernisation in our previous article. But trusted data alone isn’t enough, as you also need trusted answers. That’s why every Microsoft Fabric Data Agent should have a measurable benchmark before it reaches production.

Rather than relying on subjective demonstrations, organisations should build a ground-truth evaluation dataset together with business owners. We recommend starting with one business domain and defining 30–50 representative business questions.

The benchmark should include:

  • Frequently asked operational questions
  • Complex filtering scenarios
  • Period comparisons
  • Ambiguous terminology
  • Missing-data situations
  • Questions the AI should refuse to answer
  • High-risk finance and compliance scenarios

Each question should include:

  • the expected answer
  • the governed semantic model
  • the responsible business owner
  • required user permissions
  • validation date

This benchmark becomes your production release criteria, not just another spreadsheet.

AI evaluation should measure more than accuracy

AI evaluation isn’t simply about calculating an accuracy percentage, because production-ready conversational analytics should also test:

  • Permission boundaries

Can different user roles only access the information they’re authorised to see?

  • Semantic consistency

Does the Microsoft Fabric Data Agent consistently interpret business terminology?

  • Ambiguous questions

Can the AI recognise uncertainty instead of inventing an answer?

  • Refusal behaviour

Does the system appropriately decline unsupported or restricted requests?

  • Performance

Can users receive responses quickly under realistic workloads?

  • Operational cost

Can conversational analytics scale without unpredictable Azure consumption costs?

These are all part of AI production readiness. If you’d like to know whether your idea or AI pilot is ready for scaling, fill out our AI Readiness Form!

Regression testing is the missing production control

Your Microsoft Fabric Data Agent will continue evolving: semantic models change, instructions improve, new data sources are added and later business definitions evolve. Every one of these changes has the potential to alter how the AI answers questions. That’s why AI regression testing should become part of every production deployment.

Before promoting any change, organisations should:

  • Execute automated evaluation against benchmark questions
  • Review incorrect and unclear responses
  • Validate business-critical answers with data owners
  • Test multiple permission scenarios
  • Promote changes through controlled Development, Test, and Production environments

Software teams already understand regression testing, so why would enterprise AI be treated differently?

From Proof of Value to production

The difference between a pilot and production is the operational discipline. Successful organisations don’t approve Microsoft Fabric Data Agents because stakeholders enjoyed the demonstration, but because answer quality can be measured repeatedly.

That requires:

  • governed semantic models
  • controlled deployments
  • measurable evaluation
  • business-approved benchmarks
  • continuous monitoring

Only then does conversational analytics become a trusted part of enterprise decision-making.

Our approach to integrate Microsoft Fabric

At Peruzzi, we help organisations move beyond successful AI demonstrations. Our Microsoft Fabric Proof of Value combines Data Engineering, AI Engineering, and enterprise AI governance to ensure conversational analytics is ready for real business use, not just a compelling presentation.

We help organisations:

  • prepare governed semantic models
  • define measurable business questions
  • build ground-truth evaluation datasets
  • validate AI accuracy
  • implement regression testing
  • establish production-ready release processes

Because enterprise AI isn’t successful when the demo works: it’s successful when your business can trust every answer.

Key takeaways

If you’re evaluating Microsoft Fabric Data Agents, don’t ask whether everyone liked the demo. Instead, ask whether your organisation can repeatedly prove the answers are correct. That’s the difference between an interesting AI pilot and a production-ready enterprise AI solution.

05/08/2026
Why 95% of enterprise AI projects never make it beyond the Proof of Concept
AI 5 min read
LinkedIn
Why 95% of enterprise AI projects never make it beyond the Proof of Concept

According to an MIT study, 95% of generative AI pilots at companies are failing. This is an outrageous number for failed AI deployment, but we see this trend amongst our clients’ projects. The situation might sound very familiar: the proof of concept is successful, the stakeholders are impressed, the technology demonstrates real potential. Yet months later, the solution is still stuck in pilot mode, unable to meet the security, governance, scalability, and operational requirements of a production environment. Now you might wonder: how is this even possible?

After helping organisations deliver AI implementations on Microsoft Azure, we’ve found that the same obstacles appear time and time again. In this guide, we share a practical audit framework designed for CTOs, Heads of Engineering, and AI Production Owners to identify where projects typically stall, and how to move them into production with confidence.

Why do AI deployment projects stuck?

When AI implementation initiatives fail to progress beyond the proof-of-concept stage, the root cause is rarely the model itself. Instead, organisations typically encounter one or more of these challenges:

  • Poor data quality and inconsistent data governance
  • Missing identity and access management (RBAC)
  • Security and compliance concerns
  • Architecture that cannot scale beyond a prototype
  • Lack of monitoring, logging, and observability
  • No clear ownership or operational processes
  • Difficulty integrating AI into existing business workflows
  • Limited internal capacity to productionise the solution

The good news? These are engineering and delivery challenges, not signs that your AI strategy has failed.

Production readiness audit checklist – AI Readiness Assessment

We have created a 5-minutes-long AI Readiness Assessment which helps you to categorise where your enterprise AI deployment stands. It also gives you real advices on how to more forward with your AI implementation. Click here to fill it out!

Data foundation – the key in your AI readiness

Before deploying your enterprise AI, ask yourself:

  • Is the underlying data accurate, complete, and governed?
  • Are data sources reliable?
  • Can the AI access trusted information consistently?
  • Is sensitive information properly classified? Without trusted data, even the most advanced AI model will produce unreliable business outcomes.

Security & identity as a part of your AI readiness

Enterprise AI must fit into your existing security architecture. Not only because of GDPR, but because not following security requirements will result in breaking regulations and laws, and losing your business due to negative reputation. It’s plain simple: it would cost you your company.

Ask yourself these questions:

  • Does the solution integrate with Microsoft Entra ID?
  • Are role-based permissions (RBAC) implemented?
  • Are secrets stored securely using Azure Key Vault?
  • Is every user action auditable?

Architecture & scalability in your enterprise AI deployment

A successful prototype isn’t automatically production-ready. Scaling a product will take time, as you need to consider the followings:

  • Can the solution scale to thousands of users?
  • Can components be updated independently?
  • Is the infrastructure resilient?
  • Have performance bottlenecks been identified?

Monitoring & operations – to avoid hidden costs in your AI implementation

Once AI goes live, visibility becomes critical. Hidden costs or certain bugs can really hinder your AI deployment plans.

Ask:

  • Can you monitor costs?
  • Can you trace every AI interaction?
  • Are failures automatically detected?
  • Is there an operational support model?

Governance & human oversight

We recently published a case study, Case study: From AI prototype to AI production in two weeks about why keeping humans-in-the-loop is essential. Without them, AI might falsify or hallucinate decisions, therefore we need to always integrate the human decision-making into the process. Enterprise AI shouldn’t about replacing people, it’s about enabling better decisions by people.

Ask:

  • Is every AI-generated recommendation reviewable?
  • Is there human approval where required?
  • Are decisions explainable?
  • Can outputs be audited?

The most common misconception in AI Proof of Concept deployment

Many organisations assume their AI project failed because the technology wasn’t mature enough. In reality, the AI often performs exactly as expected.

What’s missing is everything around it:

  • governance
  • workflows
  • integrations
  • security
  • operational readiness

The difference between a demo and a production system is rarely the model: it’s the architecture surrounding it.

How Peruzzi helps your AI deployment

At Peruzzi, we specialise in AI deployment with taking the AI Proof of Concept beyond. Our Production Readiness Assessment helps organisations identify technical and operational risks before they become expensive delays.

Instead of another lengthy consultancy engagement regarding your AI implementation, you’ll receive:

  • A structured assessment of your current AI landscape
  • A prioritised remediation roadmap
  • Clear production readiness recommendations regarding your AI deployment
  • Estimated implementation effort
  • A phased plan for moving from prototype to production

Whether your AI initiative is still in development or already stuck in pilot mode, we help you turn promising prototypes into secure, scalable enterprise solutions.

Key takeaways

If your AI project has stalled, you’re not alone - AI implementation is harder than it seems. Most enterprise AI initiatives face the same challenges: not because the technology is flawed, but because production readiness requires a different mindset than experimentation. The good news is that these issues can be identified early and addressed systematically. With the right architecture, governance, and delivery approach, AI can move from an impressive demo to measurable business value.

04/08/2026
Case study: From AI prototype to AI production in two weeks
AI 3 min read
LinkedIn
Case study: From AI prototype to AI production in two weeks

Most enterprise AI project don’t fail because of the AI, they fail because they never make it to production. We all been there. The proof of concept works, the demo impresses stakeholders, the model generates the right answers, it’s time to deploy… This is when new challenges appear, such as governance, workflow orchestration, integrations, security, compliance, user adoption, and operational readiness. We can pinpoint it that this is exactly where many AI initiatives stall.

This case study shows how we helped a UK legal-tech startup bridge that gap to go-to-market with a legal workflow automation AI in Azure. Rather than building another AI prototype, we transformed an existing proof of concept into an investor-ready, production-ready solution in just two weeks - reducing manual effort by up to 80% while accelerating the client’s path to market.

The client had already built a legal workflow automation AI PoC in Azure, which worked, the AI performed well. But when investors and enterprise customers asked to see a complete Data Subject Access Request (DSAR) workflow, there wasn’t one. Instead, requests were handled across emails, manual reviews and disconnected systems.

There was no single process to:

  • receive new requests
  • classify them
  • collect the required information
  • generate response packages
  • monitor statutory deadlines

The legal AI PoC existed, but the business workflow didn’t. That meant the product wasn’t ready for enterprise AI customers, even though the underlying AI already was.

Why did this matter?

For an early-stage legal-tech company, this wasn’t just an engineering problem, it was a commercial one. Without an end-to-end workflow they couldn’t confidently demonstrate the product to investors or enterprise buyers. Every delayed release meant slower go-to-market, delayed customer acquisition and increasing pressure on the leadership.

Rather than rebuilding the client’s platform, Peruzzi Solutions focused on what mattered most: creating the missing business workflow that transformed an AI capability into a product customers could actually use. We designed and delivered a complete DSAR process that automated request intake, AI-assisted classification, workflow management and response generation, while keeping legal professionals in control through a human-in-the-loop approach.

Keeping people at the end of the workflow was critical: we all know that AI can hallucinate, as we already discussed this in a** previous article,** therefore building in human monitoring and review helps with the decision-making. The result was a solution that could be demonstrated with confidence and scaled for real customer deployments.

Business impact of the production AI

Within just two weeks, the client had an investor-ready DSAR workflow, an AI legal inbox triage with human review, that dramatically reduced manual effort while accelerating product readiness.

  • 70–80% reduction in manual effort

Routine administrative work across the DSAR process became largely automated, allowing legal teams to focus on review rather than repetitive administration. For employees, the time spent was reduced from 20-40 hours to 2-4 hours, which is a huge improvement in their workflow.

  • Faster path to market

Instead of spending months extending an internal prototype, the client was able to demonstrate a complete end-to-end workflow to customers and investors.

  • A legal AI that fits regulated industries

The workflow was designed with human oversight built in, ensuring AI supported legal professionals without replacing decision-making.

  • Built for future growth: DSAR automation in Azure AI

The solution provided the foundation for a scalable compliance platform rather than another isolated proof of concept.

Key takeaway

Many organisations believe their AI project is “almost finished” because the model works, while in reality, the hardest part is rarely the AI. It’s everything around it: from production workflows, through governance, integration security to human oversight. That’s the difference between a promising demo and a product customers are willing to trust.

03/08/2026
Case Study: Microsoft Fabric Proof of Value for Financial Data Modernisation
AI 3 min read
LinkedIn
Case Study: Microsoft Fabric Proof of Value for Financial Data Modernisation

Finance reporting, resource planning, and operational tracking are complex processes that involve not only numerous data sources but also a significant amount of manual effort. Connecting systems, reading Excel spreadsheets, and understanding formulas - and sometimes even macros - can be challenging.

Our client required a modern, scalable data foundation in Microsoft Fabric to improve financial reporting, reduce manual data preparation, and establish a robust foundation for future analytics. We successfully delivered this solution, enabling a more efficient and scalable reporting environment.

The problem

The organisation relied on multiple fragmented systems for finance, fundraising, resource planning and operational tracking.​ Reporting was supported by Azure SQL, Azure Data Factory and Power BI, but data remained spread across separate sources and preparation processes.​ This made it difficult to create a consistent, trusted view of performance across the organisation.​

The organisation wanted to evaluate Microsoft Fabric as a strategic platform for future data and analytics initiatives. Microsoft Fabric is Microsoft’s all-in-one data and analytics platform that brings together data engineering, data integration, data warehousing, business intelligence, data science, and AI into a single SaaS solution.

The solution

The challenge of the project was to demonstrate how Fabric could simplify data management, improve reporting capabilities, and provide a scalable foundation for future integrations, while minimising disruption to existing operations. To achieve it, we delivered a Microsoft Fabric solution using a modern, layered data architecture.​

This solution connected multiple source systems, including the accounting system, Salesforce and other operational platforms, into a unified data foundation.​ Power BI reporting was delivered directly from Fabric, giving users access to trusted data through a single reporting layer.​ It automated data ingestion, transformation, and reporting while establishing a roadmap for future integrations and enterprise-wide Fabric adoption.

The impact

Unified platform: Created a single reporting platform across finance, fundraising and operational data.​

Efficiency: Automated key data ingestion and transformation processes.​

Trusted reporting: Improved consistency and reliability of business reporting.​​

Scalability: Established a reusable foundation for future data sources and analytics use cases.​

Governance: Implemented data governance with Microsoft Purview.

Key Takeaway

A successful data platform is about creating a trusted, scalable foundation that supports reporting today and AI initiatives tomorrow.

24/06/2026
Case study: Building a data platform processing 1B+ events daily
Data Engineering 2 min read
LinkedIn
Case study: Building a data platform processing 1B+ events daily

The electricity market processes an unimaginable number of events: we turn on the lights, dry our hair, or work on our laptop while charging our phone—these are all separate events which need to be handled by the electricity industry. Our client requested one thing: build a platform which can handle it all. Not a small request!

The problem

The electricity market operates on half-hourly settlement periods, requiring precise calculation and reconciliation of energy consumption across multiple market participants.

This creates significant technical challenges:

  • Massive data volumes exceeding 1 billion events daily
  • Strict accuracy requirements for financial settlement
  • Real-time processing needs across the entire market
  • Complex coordination between multiple systems and stakeholders

The existing landscape required a platform that could handle scale, speed, and reliability simultaneously.

The solution

We designed and built a cloud-native, microservices-based platform on Microsoft Azure to process and aggregate energy market data at national scale.

The architecture included:

  • Azure Databricks → high-throughput data processing
  • Azure Data Factory → orchestration of data pipelines
  • Azure Event Hubs & Service Bus → real-time data ingestion and messaging
  • Azure Kubernetes Service (AKS) → scalable microservices infrastructure
  • Cosmos DB & Azure SQL → storage and transactional processing

How does it work?

The platform enables:

  1. Continuous ingestion of high-volume energy data
  2. Real-time aggregation and transformation
  3. Settlement-period calculations across the market

As the platform evolved, machine learning capabilities were introduced to support predictive analytics, advanced forecasting, and automated model pipelines.

The impact

The platform delivers:

  • Scalability, which handles 1B+ events daily with room for growth.
  • High reliability designed for continuous, uninterrupted operation.
  • Accuracy, supporting critical financial settlement processes.

Key takeaways

At this scale, the challenge isn’t just processing data, it’s designing systems that remain reliable under constant load, flexible and maintainable over time. Cloud-native architecture makes this possible, but only when designed correctly from the start.

08/06/2026
Case study: AI-powered document validation at scale: Reducing admin work by 75%
AI 3 min read
LinkedIn
Case study: AI-powered document validation at scale: Reducing admin work by 75%

More and more organisations realise that gathering and validating documents is a real hassle. Scanned PDFs, handwritten reports or spreadsheets in several places is making it almost impossible to keep track or update them. Our client in the construction industry faced the same issue: so we implemented an AI-powered document validation tool.

The problem

A workforce solutions provider in the UK construction industry was managing compliance and documentation for thousands of workers.

This resulted in:

  • 100,000+ documents 1,000 different document types
  • Files arriving in inconsistent formats, layouts, and quality

Many documents were low-quality scans, poorly structured and demanded hours of manual labor to process. As expected, this resulted in a growing operational burden of manual data extraction, time-consuming validation and high risks of human error. There was one solution: the organisation needed a scalable way to process, validate, and monitor documents efficiently without increasing headcount.

The solution

We designed and implemented an AI-powered document validation pipeline on Microsoft Azure.

The solution combined:

  • Azure Document Intelligence: OCR and structured data extraction from diverse document formats
  • Azure OpenAI: Normalisation and interpretation of unstructured data
  • Azure Functions: Scalable processing pipeline for batch validation and reprocessing

How does it work?

  1. Documents are ingested into the system in various formats (PDFs, scans, images)
  2. OCR extracts raw text and structural elements
  3. AI models identify and normalise key fields
  4. Validation logic checks for: Missing data, Incorrect values, Expired documentation
  5. The system flags issues and triggers alerts for review

The architecture was designed to handle the high document volumes and ongoing revalidation.

The impact

The results were immediate and measurable:

  • 75%+ reduction in administrative workload
  • Automated processing of 100,000+ documents
  • Proactive alerts for expired or invalid records
  • Improved compliance and auditability
  • Scalable foundation for future growth

Key takeaways

Most operational bottlenecks are not caused by lack of data. They are caused by data that is unstructured and inconsistent, hence difficult to process. By combining AI with a well-designed pipeline, organisations can turn messy data into reliable, actionable information.

28/05/2026
2026 Work Trend Index by Microsoft – How do we use AI at work?
AI 3 min read
LinkedIn
2026 Work Trend Index by Microsoft – How do we use AI at work?

AI is such a pillar in our lives that we don’t even think about when to use it, because the answer is: always. Microsoft, a frontier in AI engineering and the developer of Microsoft 365 Copilot, a chatbot that can code and solve problems, ran its annual survey. The 2026 Work Trend Index survey is based on data from 20,000 people across 10 countries, along with trillions of anonymised Microsoft 365 productivity signals.

With the idea in mind that AI and agents can expand human potential at work while decreasing cognitive effort, the survey tried to answer one question: how do we use AI exactly?

How do we use AI at work?

According to the survey, employees use AI to lift the ceiling of what they can do, meanwhile leaders decide what humans and AI do, hence shifting the workplace entirely. It’s not only about marketers asking “propose 10 new slogans for me”: 49% of workers use AI to analyse, process and understand new information, make decisions and solve problems.

Only 19% answered that they use it mainly to communicate with supervisors or peers or interpret info for others. 17% already produce outputs, such as documents, while 15% use it to gather information. What used to be Google is a chatbot now. Furthermore, 66% of users said that thanks to AI they spend more time on high-value work.

What does this mean in a work setting? It might mean that the “dead internet” theory came alive: more people copy-paste the received email from their colleagues into Copilot and ask it to respond. Then that colleague does the same thing. It also means that 58% say they’re producing work they couldn’t have a year ago.

Juniors are not necessarily juniors anymore, as they have a 24/7 available professional system to help them out. The learning curve is shorter as they can access every piece of information and are capable of doing work they shouldn’t yet be capable of.

What are the four modes of working with AI?

We can establish four modes of working with AI according to the results.

Delegation:

  • Turning raw data and notes into structured data
  • Pulling, formatting and reporting

Collaboration:

  • Refining a proposal or document through multiple rounds of feedback and prompts
  • Writing a communication where the tone or framing needs to be adjusted through multiple rounds of feedback

Asking:

  • Looking up facts, dates or definitions
  • Reformatting a table or figure
  • Rewriting sentences, checking grammar

Exploration:

  • Probing what agents can do autonomously
  • Trying different prompt strategies
  • Testing whether Copilot can handle new workflows

These modes shows how we think about AI: a companion that supports our work and allows us to focus our cognitive energy on more important tasks.

But if this is all done by AI, what do humans do?

Agents are now used in every industry, but the pattern of adoption varies widely. Software and technology are frontiers, but banking, manufacturing, healthcare, media and even nonprofit firms have adopted some form of agent.

New studies emerge frequently showing that leaning on these tools might negatively affect creativity, problem-solving skills, attention span, memory and critical thinking specifically. We are prone to believe that everything an AI chatbot says must be true. We are convinced that because it gathers information from all around the globe, more information means more accuracy, hence it doesn’t make mistakes.

The most important question is: are companies ready to support employees in using AI and agents in the best way possible, without allowing them to lose their creativity and problem-solving skills? Or: can we learn how to use AI fairly but not over rely on it?

The opportunity is there for every leader and organisation: building a place where agents increase what people can do, where human judgment stays at the center of the work that matters, and where we all have the agency to decide what comes next.

Sources: https://www.microsoft.com/en-us/worklab/work-trend-index/agents-human-agency-and-the-opportunity-for-every-organization#wti2026-modular-nav-shell

https://www.bbc.com/future/article/20260505-how-to-use-ai-without-turning-your-brain-to-mush

https://news.harvard.edu/gazette/story/2025/11/is-ai-dulling-our-minds/

18/05/2026
Case study: Microsoft Power Platform in healthcare
AI 2 min read
LinkedIn
Case study: Microsoft Power Platform in healthcare

As healthcare organisations grow, operational complexity often increases faster than their internal systems can handle. This was the case for a senior care facility in that needed a more scalable and efficient way to manage daily tasks for its social workers. Microsoft Power Platform is an effective tool, but has its limits.

This is where we stepped in: we partnered with the client to redesign and optimise their existing Power Platform-based system.

The problem

The client operates a long-term elderly care facility, providing essential daily support to senior citizens. Their job is key in society so they needed a platform which is based on Microsoft Power Platform and easy enough to maintain, but capable of managing task assignments and client-specific to-do lists for social workers.

  • Task management processes became difficult to oversee and maintain
  • The system relied on hardcoded elements, limiting flexibility
  • Reporting capabilities were limited and fragmented
  • Scaling the solution to support future growth became a challenge

In addition, the client had a strategic goal: to transform their internal system into a product that could be offered to other care facilities. This required a more structured, modular, and easily deployable solution.

The solution

We approached the project with a focus on simplification, scalability, and long-term usability.

First, we conducted a thorough review of the existing system to identify bottlenecks, redundancies, and areas for improvement. Based on these insights, we redesigned the architecture to support a more modular and maintainable structure.

The optimised solution included:

  • Power Platform enhancements to streamline task and checklist management
  • Azure SQL integration for structured, reliable data storage and improved reporting
  • Azure Logic Apps to automate recurring and manual processes
  • Template-based architecture to allow easy deployment across different environments
  • Removal of hardcoded dependencies, making the system more flexible and easier to maintain

By reorganising the system into a scalable framework, we ensured that it could be customised and extended without increasing complexity.

The impact

The improvements delivered measurable results across operations, adoption, and cost efficiency:

  • 40% reduction in task assignment time: Social workers can now manage their daily responsibilities more efficiently, reducing administrative overhead.
  • 25% reduction in administrative costs: Automation and improved tracking reduced the need for manual oversight and coordination.

Beyond these metrics, the most important outcome was qualitative: Social workers gained more time to focus on patient care instead of administrative tasks - and this is priceless.

Key Takeaways

This project highlights a common pattern in digital transformation initiatives:

  • Systems built for immediate needs often struggle to scale over time
  • Complexity increases when flexibility and structure are not designed upfront
  • Automation alone is not enough - architecture and usability are equally critical

By focusing on simplification, modularity, and real user needs, organisations can unlock significantly more value from their existing technology stack.

21/04/2026