Picture a new frontline worker on their first day…
Shift starts at 6am.
The manager is pulled in three directions.
Nobody told them where the break room is, what the safety protocol is, or how to log a time-off request.

So they find a coworker and ask.

That coworker becomes their onboarding system.

Gallup found that only 12% of employees strongly agree their organization does a great job onboarding new people. Twelve percent. That number should bother more leaders than it does.

Here's the test I keep coming back to: at the end of week one, how many questions did your new hire have to track down a person to answer?

If the number is high, you don't have an onboarding problem. You have an information architecture problem.

The manager will answer the questions. That's not the issue. The issue is that the answers only exist in someone's head — not somewhere the employee can find on their own.

What sticks after the first week isn't the orientation slideshow. It's whether the new person can get what they need without creating work for someone else.

Where do I request time off? Who do I call when equipment breaks? What's the policy on X?

Those answers should live somewhere findable, on the device they have, in plain language.

If they don't, you've built a system that runs on human bandwidth. And human bandwidth is the one resource every frontline operation runs out of first.

#onboarding #frontlineworkers #employeeexperience #internalcomms #workplaceculture

Why AI changes the deployment conversation

Traditional SaaS gave buyers a fairly simple deployment question: cloud or on-prem, public cloud or private instance, standard controls or extra controls. AI makes that conversation much more important because workforce AI is only useful when it has broader context. It needs to reason across policies, people data, schedules, tasks, training, support history, approvals, and exceptions. That is exactly what makes it valuable, and exactly what makes governance harder.

This is especially true in frontline-heavy organizations. A store manager asking about a payroll exception, a nurse checking a policy, or a plant supervisor escalating a safety issue is not just using generic collaboration data. They may be touching employee records, compliance rules, union agreements, benefits information, schedules, or performance history. That changes the bar for enterprise buyers.

CISOs and enterprise architects need control over identity, keys, network access, logging, data flows, model routing, residency, retention, and incident response. HR and compliance leaders need audit trails, approvals, responsible ownership, and clear boundaries on what an agent can and cannot do. One rigid deployment model will not work for every company, every country, or every workflow.

At MangoApps, this is why we support multiple deployment models instead of forcing every enterprise into one pattern. Some customers want fully managed SaaS. Others need private cloud, customer-controlled network boundaries, or on-premise deployment for stricter regulatory environments. The principle is simple: same app, same AI, deployed where enterprise IT requires it.

The AI conversation cannot just be about better answers. It has to be about where the data lives, how it is accessed, who controls it, how actions are traced, and how safely the system can operate across the rest of the enterprise stack. In the AI era, deployment flexibility is not an infrastructure detail. It is part of the trust model.

There was a time when the holy grail metric for any app was "stickiness."

How long did you have someone's eyeballs? Social media turned this into a science. Time spent was the whole game.

That logic made sense for apps selling your attention to advertisers.

It makes zero sense for workforce apps.

If your frontline employees are spending a ton of time inside your workforce app, something has gone wrong.

They're not there to scroll. They're nurses, store associates, warehouse crews. Their job happens away from the screen.

Every extra minute staring at a phone looking for a policy update is a minute they're not doing the actual work. ⏱️

The metric that matters for a workforce app is almost the opposite of stickiness. It's speed. Friction removed.

There's an old communications rule: be brief, be brilliant, be gone.

That's exactly what a good frontline app should do. 🎯

At MangoApps, that's the bar we hold ourselves to. Not time spent on the platform, but how fast someone can get what they need and get back to work.

We serve over 2 million users in some of the most fast-paced work environments out there. The win isn't engagement in the social media sense.

The win is getting people back to their actual jobs faster.

Stickiness was a great metric for Instagram.

For the frontline, it's the wrong scoreboard entirely.

#frontlineworkers #employeeexperience #digitalworkplace #workforcetech #internalcomms

AI ARR needs a gross margin test

A lot of AI companies are announcing they grew ARR to 8 or 9 figures in just a few months.

First, congratulations. That is impressive. But we should be careful not to compare apples to oranges.

In traditional SaaS, revenue often came with 80%+ gross margins once the product was built and scaled. In many AI businesses, a meaningful part of every dollar goes back into compute, inference, model costs, and infrastructure.

That does not make these bad businesses. It just means the revenue profile is different.

A grocery store can be a great business. So can a software company. But $100M of grocery revenue and $100M of high-margin SaaS revenue are not the same thing.

The better question is not how fast ARR is growing. It is how much durable gross profit is left after serving the customer. That is where the real comparison should start.

AI will not reduce the need for customer success and implementation. It will make them more important.

Customers increasingly expect software to adapt to their workflows, policies, language, permissions, and operating model. That doesn't happen by bolting on AI features. It takes strong implementation, clean data, thoughtful configuration, workflow design, and ongoing customer success.

Companies that understand this shift and organize around it will lead. Companies that think AI eliminates the need for Customer Success (CS) team and put AI chatbots as the answer will miss the point.

At MangoApps, we've always treated Customer Success as one of our most important functions. Engineering builds the product; Customer Success makes sure it works in the real world, across real organizations, with real complexity. The average MangoApps deployment touches about a dozen systems and 3 policy frameworks before go-live — none of which AI can figure out on its own. Our 75+ NPS score, year after year, reflects that belief.

As AI makes software more personalized for every organization, the winners will be the companies that do the hard work after the sale: connect the right systems, understand the customer's workflows, configure the product correctly, govern the data, and keep improving it as the organization evolves.

That's where SaaS leadership will be decided.

No, companies won’t stop buying software

Companies are not going to stop buying software and start building everything themselves. That idea is not grounded in history. We can all cook at home, but restaurants are massive businesses. We can all make coffee, but people still line up at Starbucks.

The reason is simple: people and companies do not only pay for capability. They pay for convenience, reliability, speed, polish, support, trust, and the ability to focus on their own business. AI coding makes building software easier, but easier does not mean easy, and it definitely does not mean everyone should build everything.

I have been agentic coding for over 18 months. I enjoy engineering. AI coding is a great accelerator and confidence booster. But building a meaningful product at scale still requires architecture, permissions, integrations, UX, security, workflow design, support, and a lot of judgment. AI does not remove those challenges. It shifts where the hard work lives.

So no, I do not think companies will stop buying software. I think we will see more software everywhere. Some will be internal tools, and those tools will get better. But most durable software will still come from teams whose entire job is to build, support, and evolve it. AI will change who can build software. It will not change what it takes to build great software.

The Frontline Tax: What You're Paying to Ignore 80% of Your Workforce

Eighty percent of the global workforce is deskless. They run your stores, floors, wards and routes. And lot of them are still running on bulletin boards, group texts, and a manager who heard it from another manager.

This isn't a culture problem. It's an operating cost. Call it the Frontline Tax.

Gallup pegs disengagement at $8.8 trillion globally, that's 9% of GDP. McKinsey finds frontline turnover costs 1.5x to 2x annual salary per departing worker. Workplace research consistently shows frontline employees receive critical operational information days, sometimes weeks after their HQ counterparts. In a margin-thin operation, that lag is the difference between a profitable shift and a write-off.

The Frontline Tax shows up in four line items every COO already owns:

1. Shrinkage and safety incidents that trace back to a policy nobody read.
2. Turnover at 50–75% in retail, hospitality, and logistics, driven less by pay than by workers feeling invisible.
3. Compliance gaps because attestation lives in a binder.
4. Productivity drag from supervisors spending a third of their week chasing information that should have been pushed to a phone.

The fix isn't another app. Frontline workers already drown in apps. The fix is a single destination for comms, training, tasks, recognition, schedules, knowledge that opens on the device they actually carry, in the language they actually speak, with the manager loop closed.

That's the operating thesis behind every serious frontline platform decision happening right now.

The question for operators isn't whether to invest. It's whether you keep paying the Frontline Tax quietly, line by line, or move it onto the balance sheet and fix it.

Most companies are still paying. The ones that stopped are pulling away.

There is a lot of discussion right now about the coming “SaaS collapse.”

AI is one of the most important technology shifts we will see in our lifetime. It will reshape software, disrupt categories, and challenge how products are built and priced. That part is real. But what is coming next is not a collapse. It is a reset in how software serves the business.

For decades, companies have been forced to adapt themselves to software. They bought rigid systems, bent workflows to fit predefined models, trained employees around generic experiences, and layered tool after tool to fill the gaps. The result has been complexity and a constant mismatch between how a business operates and how its systems actually work.

AI changes that dynamic in a fundamental way. It makes it possible to deliver software that is contextual, role-specific, and aligned to how each organization actually works, without the cost and time of traditional customization. When that barrier goes away, expectations change. Businesses will no longer accept one size fits all systems.

If there is one thing I have learned from building companies for over 20 years, it is this. You want complete alignment with your customers. When customers are thinking about building custom or in-house solutions, you do not fight that instinct. You enable it. That is what AI now makes possible, and it is a core part of how we think about MangoApps AI.

At MangoApps, we are building for this shift. A unified, brandable workforce platform that adapts to every role, every team, and every workflow. Frontline employees, desk workers, managers, field teams, HR, IT, and communications each get an experience that actually fits how they work.

The future of SaaS is not just more intelligent software. It is software that finally fits the business.

One of the biggest misconceptions I see right now is that AI agents are ready to take over most work. They’re not. Especially in frontline organizations where accuracy directly impacts customers, operations, and safety. Even in one of the most advanced use cases like agentic coding, accuracy is still in the 80 to 90 percent range. For most enterprise scenarios, that simply isn’t good enough. Imagine a store associate, nurse, or technician getting it wrong 20 percent of the time.

We’ve seen this movie before. Voice didn’t really take off until accuracy crossed that ~95 percent threshold. AI will get there. The level of investment going into this space makes that inevitable. But as you get closer to 90 percent, every 1 percent improvement becomes significantly harder.

It works in coding today because developers are used to it. Debugging is part of the workflow. That tolerance doesn’t exist in most frontline environments where errors have real consequences.

So the practical approach is simple. Focus on use cases where 80 percent accuracy is acceptable and keep a human in the loop to catch the rest. That’s exactly where we’re focused at MangoApps, enabling frontline AI use cases that are grounded in reality. From helping a technician troubleshoot an issue in real time to guiding a store associate during a customer interaction, all with the right guardrails in place.

When AI can do 80 percent of the work in 5 to 10 percent of the time, that’s a massive gain. If you’re not leaning into that, you’re leaving real productivity on the table.

At MangoApps, we believe the next generation of frontline software should feel less like software and more like a natural extension of how people already work. Frontline teams should not have to pause what they are doing, find a device, navigate a system, and fill out forms just to get an answer, report an issue, or ask for help. In many of these moments, the most natural interface is voice, and increasingly, live video.

We have been investing in voice-first experiences for over a year. The opportunity is clear, but the economics are still catching up. Today, a minute of live voice interaction can cost anywhere from $0.15 to $0.25, which translates to $9 to $15 per hour. So the real question is not whether voice can be added, but where it actually makes sense.

That is the focus for us at MangoApps. We are looking closely at which frontline workflows are valuable, urgent, and human enough to justify a voice-first or video-first experience. For the frontline, voice is not a novelty. It has the potential to become the interface that finally aligns with how work actually gets done.

We talk to internal communications leaders constantly.

And one thing comes up in almost every conversation: they're under-resourced, fighting for budget, and more often than not, someone has already decided that SharePoint or Workday is "good enough" for employee communication.

On paper it looks like savings.

In practice it's a bet — that the information people need will somehow find its way to them anyway.

History is pretty clear on what happens when that bet goes wrong.

Nokia's engineers knew Symbian couldn't compete with the iPhone. They said so to each other. They just didn't say it to the people making the decisions. The culture didn't allow it.

A $250 billion company became a cautionary tale — not because it lacked smart people, but because it lacked a way to get what those people knew into the rooms where it mattered.

Kodak invented the digital camera in 1975. Leadership buried it because it threatened film sales.

Same story at Blockbuster. Same story at BlackBerry.

In every case: not a knowledge problem. A transmission problem.

That's what under-investing in communication actually costs. Not a less polished newsletter. A company that can't turn what it knows into what it does.

I wrote about this at length because comms leaders deserve better ammunition when they're making the budget case. The historical record is there, it's stark, and it's more persuasive than another deck about engagement best practices.

Read more here: https://www.mangoapps.com/articles/why-communication-fails-before-companies-do

#internalcommunications #employeeexperience #digitalworkplace #leadership #workplacestrategy

AI that Frontline Internal Communications Teams Should Look For

Corporate or internal communications in frontline organizations is one of the functions with a lot to gain from AI. Communications teams are typically small, constantly expected to do more with less, and responsible for reaching every employee across the organization - including frontline workers, field service teams, and corporate staff.

Here are 6 ways to get more value from the natively built-in AI tools every day:

1. Writing and content creation capabilities: Built-in AI writing tools across posts, campaigns, surveys, and tasks help reduce the time between having something to say and publishing compelling content. With AI-powered image generation that automatically fits perfectly within communication blocks of any size, the time required to create supporting visual assets is significantly reduced. These tools also improve the quality, consistency, and professionalism of content created by anyone with content authoring permissions.

2. AI recommendations, summarization, and featured image capabilities: Built-in AI recommendation tools help authors automatically enable the right options for each post based on its content. For example, marking it for employee advocacy or tagging it as “must read.” AI-generated summaries can be automatically used for push notifications, messages, and SMS, ensuring clear communication across channels. AI also generates company-branded featured images for posts, helping drive higher readership while significantly reducing the time needed to prepare and publish complete communications.

3. Read-aloud, video subtitles, and multilingual capabilities: Built-in AI tools allow employees to listen to posts, access video subtitles in their native language, and view sites and pages automatically translated into their preferred language. This improves accessibility and global reach without creating additional work for the communications team.

4. AI-assisted approval and AI moderation capabilities: Built-in AI-assisted approval helps ensure content aligns with company policies and communication guidelines before it is published. AI moderation tools with emotion and harm analysis, along with customizable tolerance levels from low to very high, provide automated review and moderation across communication workflows. This significantly reduces the manual effort communications teams spend today on approvals, compliance, and content moderation.

5. Governance and content management Prevents outdated, duplicate, and contradictory content that can erode employee trust. Reduces manual content audits by automatically identifying content that needs attention. Gives communications teams clear data and evidence to support regular content governance and improve overall content quality.

6. AI-powered search and AI assistants: Reduces IT and HR support tickets by giving employees direct, instant answers to their questions. Makes institutional knowledge easy to find in just a few clicks, improving productivity and self-service. Removes employee frustration caused by not being able to quickly access the information they need.