Search Results

The era of buying a PBX, tucking it into a communications room, and ignoring it for a decade died many years ago, in all but highly regulated and security-conscious organizations. For the majority of enterprises, moving from an on-premise PBX to UCaaS (Unified Communications as a Service) was a fundamental shift in how a business operates and reflective of how most of us now “rent” music and movies. The unified communications market moved from owning depreciating gear to subscribing to a service that seems to evolve in real-time. Beyond Technology: The New Buying Reality Decades ago, a PBX refresh was almost entirely a "technological" decision, do I get reliable dial tone and does it have a feature set my users need? Today, there is a buying committee that now needs to consider the PESTLE framework (Political, Economic, Social, Technological, Legal, Environmental) because the stakes have moved beyond the IT decision maker. We aren't just comparing phone feature lists anymore. A buying committee is now weighing: Political / Legal: Can the US government see our data under the CLOUD Act? (France’s recent public sector move to Visio suggests the answer is "yes," unless you host sovereignly). Social: Does the platform support a mobile-first, hybrid workforce — or does it still assume work happens at a desk? Economic: Are we prepared for the FinOps reality where our monthly bill fluctuates based on usage rather than a fixed seat count? Environmental: Is the hardware we’re buying for meeting rooms sustainable, or will it be e-waste in three years when the OS updates? Enterprises need to revisit their buying criteria and ensure their scorecard weighs up "Jurisdictional Data Risk" and "Subscription Flexibility" as heavily as "Uptime." Financial and Operational Shifts: Capex to Perpetual Opex The CFO has traded large, infrequent capital outlays for a perpetual operating expense. While we lose the old depreciation leverage, we gain the ability to scale without getting stuck with "dying” hardware. Procurement is now managing a service relationship. This requires "FinOps" to ensure you aren't paying for 1,000 licenses when only 800 people are logging in. In the UCaaS environment, this now means establishing a recurring governance model for subscription management rather than treating it as a "one and done" project. The Regulatory Minefield: Sovereignty and Compliance Previously, IT dictated telephony system updates. Now, vendors push updates on their schedule, often introducing new features like AI meeting summaries that trigger new legal obligations. We are subject to laws like DORA, which labels UCaaS providers as "critical third parties," and the EU AI Act, which may classify certain transcription tools as "high-risk," creating implications outside of our control. Organizations now need to audit their UCaaS stack for jurisdictional risk. If you have significant European operations, evaluate if your sensitive data needs to reside on sovereign clouds like SecNumCloud-certified platforms. Hardware Obsolescence and the MDEP Effect For those in the Microsoft ecosystem, the Microsoft Device Ecosystem Platform (MDEP) now standardizes the Android OS on desk phones and meeting bars, effectively taking the software "keys" away from hardware partners like Yealink, HP (Poly), or Cisco Webex. Standardization is great for security (managed via Intune ), but it creates a "forced" retirement cycle. Endpoints may hit a wall because they can’t run newer Android versions Microsoft mandate. Simply put If the OS outgrows the chipset, your device becomes obsolete. For Microsoft Teams-powered organizations, map your current hardware inventory against Microsoft’s AOSP certification dates. The inconvenient truth is to stop viewing endpoint devices as 10-year assets and start viewing them as 3-year disposable peripherals. The New Buyer Dynamic: Experience Infrastructure The buying committee now includes the Chief Experience Officer (CXO). The separate budgets for "phones" and "contact center" are merging into "Experience Infrastructure," which connects UCaaS and CCaaS. This integration aims to link front-office agents with back-office support staff and ingest data directly into systems of record. The traditional swim lanes of IT (network, telecoms, etc.) have been replaced by specialists who understand the "messy middle": how to integrate UCaaS and CPaaS into workflow and what is needed to improve team productivity. CXOs and legal teams are now (or should be) part of the steering committee. You need to align on whether your AI-driven customer insights are creating revenue or just creating a massive compliance liability. SO WHAT? Implications for Buyers (Enterprises) Advantages of Moving to UCaaS Real-time Feature Evolution:  Subscription-based services evolve in real-time, providing immediate access to new features and capabilities, unlike a decade-old on-premise system. Financial & Operational Flexibility:  The shift from large, infrequent Capital Expenditure (CapEx) to perpetual Operating Expense (OpEx) allows for easier scaling up or down without being stuck with "dying" hardware. Improved Business Integration:  Merging UCaaS and CCaaS into "Experience Infrastructure" links front-office agents with back-office staff and ingests data directly into systems of record to improve team productivity. Cautions for the New Buying Process Jurisdictional Data Risk:  Must weigh heavily where data resides (e.g., CLOUD Act implications) and may need to seek sovereign cloud solutions for operations in regions like Europe. FinOps & Usage Fluctuations:  Monthly bills fluctuate based on usage, requiring active "FinOps" (Financial Operations) management to prevent paying for unused licenses. New Regulatory Liabilities:  Vendor-pushed updates, especially those including features like AI meeting summaries, can trigger new legal obligations under laws like DORA and the EU AI Act. NOW WHAT! For Enterprise Buyers Advantages Continuous innovation:  Subscription platforms deliver capabilities in real time rather than waiting for hardware refresh cycles. Operational flexibility:  OpEx models allow organisations to scale without inheriting stranded infrastructure. Deeper integration:  Experience Infrastructure links customer-facing teams with operational systems, improving workflow efficiency. Key Watchpoints Jurisdictional data risk:  Understand precisely where data resides and which legal frameworks apply. FinOps discipline:  Monitor usage carefully to avoid funding unused licenses. Regulatory exposure:  Vendor-led feature releases may introduce compliance obligations with little warning. For Vendors Opportunities Predictable recurring revenue  driven by subscription economics. Strategic relevance  as communications platforms become embedded in experience delivery. Accelerated hardware refresh cycles  as platform standards shorten device lifespans. Challenges Heightened regulatory scrutiny  as providers assume critical third-party status. Rising sovereign cloud expectations  for public-sector and multinational buyers. Platform dependence , particularly within ecosystems where OS mandates can force device obsolescence .

Cisco reports second quarter 2026 results Cisco is repositioning collaboration as a hardware-dependent extension of the network to mask slowing software adoption. SO WHAT? Cisco is shifting its financial weight. Networking grew 21% while collaboration managed only 6% in Q2 2026. High-end room kits and premium screens appear to have driven these gains, not Webex seats. The vendor is moving away from competing with Microsoft Teams on software features. Instead, it is folding collaboration into broader CAPEX-heavy infrastructure deals. For buyers, this turns a communication tool into a long-term architectural commitment. You aren't just buying an app; you are (and arguably, always have been), bolting onto the Cisco backbone. Analyst Take The strategic consequence of Cisco’s Splunk integration is increased operational friction. Cisco aims to use Splunk’s data to personalize Webex, yet this adds layers of telemetry to tools users often avoid. The Pitch:  Cisco claims its "Agentic AI" and sovereign infrastructure focus creates a secure, intelligent workspace that justifies a premium. The Reality:  Deeply embedding collaboration into the network layer might create significant technical debt. Organizations could find themselves locked into proprietary hardware cycles to maintain basic software functionality. Cisco is trading market aggression for a "safe choice" posture. It cannot outpace Zoom on integrated software or Microsoft on bundle value. By leaning into "sovereign" messaging, it targets risk-averse government and hyperscale accounts. This shift suggests Cisco may be deprioritizing the mid-market. Webex is increasingly a "bundled default" rather than a user preference. According to Gartner, Microsoft Teams dominates with over 320 million monthly active users, making specialized software-only plays difficult for Cisco. [Source: Gartner Magic Quadrant for UCaaS, 2025]. The vendor risks becoming the "IBM of Collaboration"—reliable, but heavy and slow. If I Was Advising the Vendor Prune the Software Stack:  Shift focus away from low-tier Webex seats that compete with "free" Microsoft bundles and double down on high-margin, executive-grade hardware. Monetize Resilience:  Stop selling features and start selling "unbreakable" uptime. Use competitors' outages to position Cisco as the only viable option for mission-critical communication. Simplify the "Splunk Tax":  Ensure the integration of Splunk data doesn't lead to "configuration hell" for IT staff. NOW WHAT! For Buyers Audit Usage Before Renewal:  Track active Webex engagement versus total license count to eliminate "zombie" seats in your next contract. Test Hardware Neutrality:  Evaluate open-standard meeting room gear that supports multiple platforms (Teams, Zoom, Webex) to avoid proprietary hardware traps. Unbundle the Security Spend:  Require Cisco to break out the specific cost of collaboration within larger security or networking enterprise agreements. The market is moving toward a reality where you either buy a platform (Microsoft) or an infrastructure (Cisco).

The EU AI Act (Regulation 2024/1689), effective from early 2026, introduces one of the most consequential regulatory frameworks the technology sector has faced. For unified communications (UC) and customer experience (CX) buyers operating in – or touching – the European market, platform selection now carries long-term operational liability. The staged rollout is already underway. Prohibited AI practices were banned in February 2025, transparency requirements for General-Purpose AI followed in August, and by 2 August 2026 , the full regime governing High-Risk systems will take effect. This is no longer a future compliance exercise. It is a present procurement risk. The Territorial Reality: A Global Standard A common misconception among US-based vendors is that the Act applies only within European borders. Article 2 makes clear its reach is far broader. If your organisation uses a UC platform that generates outputs consumed within the EU, both you – and your vendor – fall under its jurisdiction. Implication:  Procurement teams must vet global providers with the same scrutiny applied to local European vendors. There is no practical “opt-out” if your employees, customers, or data intersect with the EU. The Emotion AI Fault Line: Prohibited vs High-Risk One of the most significant implications for buyers centres on emotion-based AI. The Prohibited Zone (Article 5) AI systems designed to infer emotions in the workplace – such as detecting stress or anger from vocal patterns to influence employment decisions – are broadly banned. The High-Risk Zone (Annex III) Sentiment analysis, which evaluates text for positive or negative tone, remains permissible but is frequently classified as high risk when used for employee monitoring. The Buyer’s Challenge:  Demand technical evidence that “supervisor coaching” tools rely on objective linguistic analysis rather than biometric inference. Several organisations faced regulatory scrutiny in late 2025 after voice-trigger mechanisms were judged to cross into prohibited territory. The distinction is subtle – but financially material. Article 25: The Hidden Liability Transfer Article 25, governing responsibilities along the AI value chain, is particularly consequential for buyers. If a deploying organisation makes a “substantial modification” to an AI system – or repurposes it beyond its original intent – it may legally assume the role of Provider . Implication:  Integrating a seemingly low-risk meeting summarisation tool into automated HR workflows could shift full liability to your organisation, including exposure to fines exceeding €35 million. In the AI era, risk is increasingly defined by use case , not vendor classification. The Cost of Ignoring the Shift Failure to prepare for the Act introduces risk across multiple dimensions: Financial Exposure Fines for prohibited practices can reach €35 million or 7% of global turnover. Even administrative missteps may trigger penalties up to €7.5 million. The Emerging “AI Freeze” Organisations are already abandoning pilots lacking governance or AI-ready data. Late 2025 saw a wave of cancellations where compliance costs overwhelmed projected ROI. Operational Disruption A regulatory order to withdraw a non-compliant tool could halt critical workflows overnight. If customer operations rely on that system, service continuity itself becomes vulnerable. Compliance is no longer a legal sidebar – it is operational resilience. UC Vendor AI Audit Checklist (Internal Tools) Procurement teams should incorporate the following into evaluation workflows: Technical Documentation (Article 13):  Can the vendor clearly explain the system’s logic, limitations, and training context? Real-Time Transparency (Article 50):  Is AI usage visibly disclosed to users to satisfy the right to be informed? Inference Residency:  Does live processing remain within EU data boundaries? Human Oversight (Article 14):  Can outputs be audited, traced, and overridden? Liability Definitions (Article 25):  Does the contract precisely define “substantial modification”? Ambiguity here is rarely harmless. CX Vendor AI Audit Checklist (Customer-Facing Tools) For conversational and routing AI, ensure vendors address: Immediate interaction disclosure Machine-readable labelling of synthetic content Availability of Fundamental Rights Impact Assessments (FRIA) Bias mitigation protocols within training datasets Clear human escalation pathways Transparency is becoming a competitive differentiator — not merely a regulatory obligation. SO WHAT? The EU AI Act reframes AI adoption from a technology decision into a governance decision. Platform selection now shapes legal exposure, operational continuity, and reputational risk. The organisations that adapt earliest will treat AI not simply as capability – but as regulated infrastructure. NOW WHAT! For Enterprise Leaders Establish a formal AI inventory and risk register. Issue structured audit requests to all vendors. Pause high-risk pilots lacking FRIA readiness. Enforce transparency disclosures across interfaces. Confirm inference and data residency align with EU sovereignty expectations. Preparation is no longer optional – it is strategic risk management. Final Thought The AI race has entered a new phase. Innovation alone is no longer the differentiator – accountability is. In Europe especially, the winners may not be those who deploy AI fastest, but those who operationalise it responsibly. Because in regulated markets, trust scales faster than experimentation. (Disclaimer: This article is provided for informational purposes only and does not constitute legal advice. Organisations should consult qualified counsel to ensure compliance with the EU AI Act.)

Global cloud communications platform Infobip has unveiled AgentOS, a managed solution designed to orchestrate autonomous, AI-driven customer interactions. The platform marks a shift from manual workflows to "goal-driven" automation, allowing AI agents to manage complex customer journeys across various digital channels. SO WHAT? As the industry moves from basic application-to-person (A2P) messaging toward "agentic" commerce, major players like SAP and Salesforce are racing to unify customer data. Infobip’s launch addresses a critical market gap: while AI adoption is high, only 5% of enterprise AI projects reach production due to fragmented data silos and unstructured internal information. Capabilities & Limitations Capabilities: Unified Orchestration: Combines a Conversational Customer Data Platform (CDP) with real-time journey mapping. Omnichannel Integration: Natively supports two-way contextual engagement on WhatsApp, RCS, and SMS. Autonomous Resolution: Employs goal-oriented AI to handle tasks from product discovery to frictionless checkout. Limitations: Data Readiness: Effectiveness depends heavily on a business’s ability to eliminate internal data silos and provide structured data. Human Oversight: Requires a "human-in-the-loop" approach for complex cases that exceed the AI’s autonomous parameters. Implementation Barriers: High organizational readiness is required to transition from traditional campaigns to autonomous interactions. Signals to Watch The 2030 Horizon : Infobip predicts a shift to "agent-to-agent" commerce, where personal AI assistants autonomously negotiate with brand AIs to complete purchases. Interoperability : As businesses adopt multiple AI tools, the focus will shift to how AgentOS integrates with open standards being developed by groups like the Agentic AI Foundation. Sources : https://www.businesswire.com/news/home/20260226218185/en/Infobip-is-Set-to-Launch-AgentOS-to-Orchestrate-Autonomous-AI-Driven-Customer-Journeys-at-Scale

I didn’t plan to start a business. There was no big "aha!" moment or dramatic exit. It was just a slow, growing frustration that I couldn’t ignore anymore. I didn’t plan to start a business. There was no big "aha!" moment or dramatic exit. It was just a slow, growing frustration that I couldn’t ignore anymore. For years, I worked in traditional market research. It’s a world based on expensive subscriptions and gated reports. But here is the problem: when every company buys the same research, they all start saying the same things. Everyone uses the same buzzwords and the same strategies. It makes every brand look and sound, well, the same! The turning point was realizing that my definition of independence didn't always align with the commercial pressures of sales. I saw how easily research could become steered or “encouraged” to support a specific business outcome. To me, being independent only works if you are willing to walk away when the truth gets “blurry.” I knew I had the skills and the experience to do this on my own. My business, So What, Now What? , was a move toward providing that clarity. The First Steps Starting was uncomfortable. Even with years of experience, uncertainty does not disappear. I had some savings and a strong support system. That gave me space to focus on the fundamentals: choosing tools, building the website, handling the administration. Actually, setting up the "boring" administrative stuff felt good and made the business feel real. I always had departments and colleagues that took care of that in the past. But the most important decision was not operational. It was philosophical. What would this business stand for? Deciding What Not to Do Most people think the hardest part of a new business is deciding what to offer. Actually, the hardest part is deciding what you won’t do. I decided right away that I would never sugar-coat my feedback. If a client’s messaging is confusing or their strategy is weak, I’m going to tell them. I see too many companies making things way more complicated than they need to be. My job is to fix that, even if the truth is blunt. Breaking the Rules For years, I believed you needed a five-year plan and significant capital to go out alone. That is the corporate mindset. Reading The Autonomous Freelancer by Dominic Kent changed that perspective. The lesson was simple: You don’t need anyone’s permission to start. You don’t need a five-year plan. You just need to be committed and willing to start before you feel 100% ready. Why Small is Better I expected other freelancers to be my competition. Instead, I found a community. We shared leads, compared notes, and helped each other grow. This was the opposite of the "gatekeeping" I saw at big firms. This community helped me realize something important: most tech companies don't actually understand how people buy solutions.. How People Actually Buy There is a myth that buyers follow a straight line from seeing an ad to buying a product. They don't. Most of the decision-making happens in the "Dark Funnel", places like private chats, online forums, and industry events. Places that companies can't track. Decisions are also made by committees, not just one person. Everyone in that group has different goals. Helping companies navigate that mess is a huge part of what I do now. I had to stop writing like an academic and start writing for busy people who need answers fast. Where Good Ideas Come From Now that I work for myself, I find ideas in weird places. Some come from client calls, but some even come from my running club or a casual lunch! Recently, a friend mentioned sharing one of my articles with their IT team. Another designed my website. My Goal I left the big research world because I wanted to get rid of the noise and the "corporate theatre." I want to help companies speak with authority instead of using confusing jargon. One thing will keep me going: be clear. Be clear about your work. Be clear about your values. Be clear about your time. Clarity forces better questions. And better questions lead to better decisions.

Genesys to Offer Experience Orchestration Services on AWS European Sovereign Cloud Genesys is introducing a sovereign deployment model within AWS European Sovereign Cloud, designed to meet rising regulatory expectations across the EU. The trade-off for buyers may be simple: greater legal assurance in exchange for reduced technical agility. SO WHAT? Regulators are reshaping cloud architecture. Vendors are being pushed toward expensive, fragmented infrastructure models that transform a global cloud into a collection of regional islands. European business leaders are already feeling this tension. Recent data shows that 88% of European executives view balancing innovation with digital sovereignty as a strategic priority. The implication is clear: organisations are being forced to choose between rapid AI evolution and strict jurisdictional control. Sovereignty is no longer a compliance sidebar. It is a board-level design constraint. Analyst Take This move introduces what can reasonably be described as a “Sovereignty Tax” on customer experience. The positioning suggests sovereignty without compromise. History suggests otherwise. Logically and physically separate cloud regions rarely maintain perfect feature parity. Sovereign environments often lag in AI model updates that depend on cross-border data scale. The promise is high-end AI with strict EU data residency. The reality may involve: delayed feature rollouts integration friction with global CRM and ERP systems increased operational overhead from managing separate encryption keys and EU-only support models Data contained within a sovereign boundary can become harder to leverage for global intelligence initiatives. What is framed as compliance reassurance may evolve into architectural constraint. The Strategic Tension Pitch: Sovereignty without compromise.Reality: Compliance comfort at the cost of speed, scale, and simplicity. Maintaining physically and logically isolated infrastructure adds cost. Those costs will either be absorbed by vendors or passed on to buyers. In most cases, they become embedded in premium tiers. The shift from “Cloud First” to “Control First” changes the economics of CX platforms. If I Was Advising the Vendor Lock in the public sector and tier-one banks. Focus on institutions where compliance budgets are fixed and risk tolerance is low. Monetise sovereignty deliberately. Bundle compliance reporting and governance tooling into a premium Sovereignty-as-a-Service tier. Prove parity. Commit to a measurable feature-parity SLA to reassure buyers they will not become second-class users inside sovereign regions. NOW WHAT – For Buyers Audit the support chain. Confirm that EU-based personnel requirements extend to 24/7 operational support. Test AI latency locally. Measure real-world performance of agentic workflows inside the sovereign environment. Review export constraints. Ensure that metadata, recordings, or training signals can move without breaching compliance obligations. Sovereignty may reduce legal exposure. It may also increase architectural rigidity. The core question is no longer whether you can host data locally. It is whether the performance and intelligence trade-offs justify the premium. Final Question If sovereignty becomes mandatory, will your AI be intelligent enough to justify the cost of its residency?