Microsoft says its hands-on AI work spans nearly 500 projects and over 200 customers
The company points to repeat engagements and faster customer workflows. Its examples range from measured production results to systems still being built.
Loading page…
The company points to repeat engagements and faster customer workflows. Its examples range from measured production results to systems still being built.
Listen to this story
Microsoft’s Frontier Company positions its 6,000-person unit as an embedded AI engineering operation, reporting that most customers returned after an initial project and generated hundreds of follow-on engagements. Its examples span deployed onboarding and telecom systems as well as workflows still being built and research hypotheses awaiting lab validation, so reported benefits are not directly comparable. The clearest quantified case is Northern Trust’s reduction in onboarding preparation time; its 96.5% figure is a controlled-test F1 score, not a broad production accuracy claim.
Microsoft reported nearly 500 projects with more than 200 customers across 28 countries.
Northern Trust says onboarding data preparation fell from about two and a half weeks to three days, an 83% reduction across production cases.
The 96.5% F1 score came from seven controlled test cases using anonymized workbooks; it is not a general production accuracy rate.
Microsoft said on November 12, 2026, that its Frontier Company had engaged in nearly 500 AI projects with more than 200 customers across 28 countries. Alongside those totals, the company published customer outcomes spanning financial data preparation, telecom networks and materials research—putting specific business workflows behind its pitch for hands-on AI engineering.
The disclosure came from Rodrigo Kede Lima, president of Microsoft Frontier Company, an operating business of 6,000 industry and engineering experts. Its forward-deployed engineers work alongside customer teams to build systems for particular business processes. The examples describe engineers working with bank analysts, network specialists and researchers, rather than simply supplying access to an AI tool.
Microsoft also said most customers whose initial projects were complete had returned for additional engagements, generating hundreds of follow-on projects. Kede Lima framed those repeat engagements as evidence that customers had measured value and found another workflow worth redesigning. That is the company’s interpretation of the repeat business, alongside its disclosure of the project totals.
Northern Trust provides a detailed example. Its onboarding agent converts clients’ historical investment transactions into the bank’s standardized format for its Front Office Solutions platform. The companies’ November 9 announcement said data preparation fell from about two and a half weeks to three days, an 83% reduction. Analysts use Excel and SharePoint to review, refine and approve the work.
The timing measurement covered real client onboarding cases after deployment. It included data transformation, analyst review, exception handling and final validation—not just the agent’s processing time. Northern Trust compared the average time for those agent-assisted production cases against the previous workflow. Human oversight remained part of the process, including checking outputs and resolving exceptions before clients went live.
The quality figure needs a different reading. Although the November 12 post called it 96.5% first-pass accuracy, the detailed announcement identifies a 96.5% F1 score, a measure combining precision and recall. It came from seven controlled test cases using anonymized historical transaction workbooks. Outputs were checked against analyst-prepared references before human corrections; it is not a general production accuracy rate.
Other examples in Microsoft’s disclosure describe different stages of work: a workflow under construction, research leads awaiting laboratory tests and a factory simulation supporting operators. Their reported benefits should be read at those stages, rather than treated as equivalent deployment results.
Microsoft also describes knowledge transfer as part of the engineering work. At Publicis Groupe, its teams are co-building AI processes that use business context and improve through real-world outcomes and human feedback. Kede Lima’s stated longer-term test is whether customers can run, govern and improve their own AI systems after the engagement—not only what Microsoft delivers during it.
Loading discussion...
Join the conversation
Explain which signal would carry more weight in your decision.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.