Teams | Collaboration | Customer Service | Project Management

Freshworks Chief People Officer Johanna Jackman on bringing HR onto Freshservice to streamline operations, improve employee experience, and unlock higher-impact work.

Over the past few decades in the technology industry, some of the biggest constraints to building products have been about having enough engineers, time, or compute. For the first time, that era is ending. Tech teams are experiencing a revolution unlike anything they’ve seen before. The barriers to entry for building have all but disappeared. The constraint no longer comes from producing enough output, but from deciding what to build, and the restraint required to build something good.

ClickUp is one of the most popular project management tools in the world. It’s flexible, packed with features, and built to replace multiple apps like Trello, Asana, Notion, and even Google Docs. But here’s what many teams realise after using it for a few weeks: ClickUp pricing looks affordable at first, but it becomes expensive once you factor in AI add-ons, usage limits, and scaling costs.

Imagine a typical morning for your support lead. A customer, let’s call him John, forgot how to update his billing information. John goes to your website, finds your support email, and sends a message. That email enters your help desk as a ticket. Your agent, Sarah, sees the notification, opens the ticket, identifies the issue, and manually types out the same three-step process she has explained twelve times already today. She hits send, and John finally gets his answer.

A few weeks ago, we soft-launched the Wire Integrations SDK in Staging and called it Phase 1 - the foundation. Today, we're taking the next step. Phase 2 brings the SDK to production in Wire, and with it, Apps become a properly typed, properly visible part of Wire. With this release, Wire becomes a place where automation lives natively: secure by design, end-to-end encrypted, and built on the protocols our customers trust with their most sensitive conversations. Here's what shipping.

A growth marketing team builds an intake rule in Asana that handles their repetitive tasks. The rule handles every incoming request: One branch for high priority requests spins up and assigns subtasks so that the team can get straight to work. Another for medium-priority tasks uses AI to summarize the request and suggest next steps. A third routes low-priority requests to the team's backlog with a due date. The rule is complex, and it works beautifully. Then the sales team wants to use it too.

Working hours are the periods of time during which employees are expected to perform their job. They determine when work happens, how many hours are required, and how teams coordinate availability and coverage across a day or week.

Managing employee leave may seem straightforward at first—but as organizations grow, the process quickly becomes complex and inefficient. A single leave request often passes through multiple touchpoints: employees submit requests, managers review them, HR validates policies, and payroll teams ensure accurate updates. This multi-step employee leave workflow relies heavily on manual coordination, which creates bottlenecks at every stage.

The difference between a high-performing remote team and a struggling one often comes down to one critical factor: the right remote work tools. It's not about using more tools. It's about using the right tools in the right combination, a thoughtfully assembled tech stack that eliminates friction, enhances collaboration, and turns distributed teams into productivity powerhouses. In 2026, organizations with mature remote work operations don't rely on luck or trial and error.

Most organizations are operating at a fraction of their true capacity. Employees spend hours on tasks that should take minutes. Information gets lost in email threads. Team members work in silos, unaware of what others are doing. Deadlines slip. Quality suffers. Costs climb. The frustrating truth is that this inefficiency isn't due to people not working hard. It's because they're working hard without the right tools. They're doing manually what modern productivity software can automate.