651-315-1009

Most video-conferencing products were designed around a familiar assumption: the meeting itself is the work. Participants enter a full-screen grid, look at faces, take turns speaking, and leave when the conversation ends. Around challenged that model. Its video calls were designed for teams that needed to create, review, and make decisions together while keeping documents, design tools, and other working applications in view.

That distinction explains much of the enthusiasm Around attracted from designers, startups, and distributed teams. The product did not merely compete on call quality. It reconsidered how much visual space a meeting should occupy, how remote participants should be represented, and how several people in one room could join without producing an echo. The company summarized its philosophy with an intentionally direct line:

“Meetings don’t have to crush your soul.”

Around was ultimately acquired by Miro, the visual collaboration platform. The acquisition was a logical strategic fit: both products approached remote work as a shared creative activity rather than a sequence of conventional conference calls.

A Video Layer Built Around Actual Work

The conventional meeting interface allocates most of the screen to rectangular video feeds. In an eight-person call, that can mean eight large tiles competing with the presentation, prototype, spreadsheet, or whiteboard that participants are supposed to discuss. The design creates an odd imbalance: faces occupy the largest area even when the team’s attention should be on an artifact.

Around became known for a more compact visual model. Instead of turning every participant’s room into a prominent rectangle, it could keep people present in smaller, focused video bubbles. The practical benefit was not simply aesthetic. Reducing the visual footprint of the call left more space for the application where the work was happening.

Consider a common laptop resolution of 1,440 by 900 pixels. A traditional meeting window occupying 70% of the display can consume more than 900,000 pixels of usable attention space once interface controls are included. A lightweight communication layer leaves substantially more room for a design canvas, code editor, or planning board. The exact savings vary by layout, but the principle is measurable: less interface devoted to passive video means more interface available for active collaboration.

This made Around particularly relevant to product teams. Designers could inspect a mockup without constantly switching windows. Engineers could keep code or technical diagrams visible. Managers could discuss priorities while looking at the same planning material. Video remained important, but it served the work rather than displacing it.

Hybrid Audio Was More Than a Convenience

One of Around’s most distinctive ideas addressed a difficult hybrid-work scenario: two or more people are sitting in the same physical room while additional colleagues join remotely. With ordinary conferencing software, local participants often gather around one laptop or use a dedicated room system. If everyone opens the call on an individual device with microphones enabled, the result can be feedback, duplicated voices, and delayed echoes.

Around promoted a different arrangement: everyone could join from their own device, keep microphones active, and still participate without the familiar echo problem. Its audio technology was presented as a way to recognize and manage devices located near one another. That mattered because individual devices preserve individual identity. Remote colleagues do not see a distant conference room containing several barely distinguishable people; they see each participant as a separate member of the conversation.

The difference becomes clearer in a six-person example. Suppose three employees share a room and three work remotely. A single conference-room camera effectively creates four visible units: one group and three individuals. Giving each person a device creates six visible units, a 50% increase in separately represented participants. That does not guarantee perfect inclusion, but it reduces a structural disadvantage. Each person has a comparable visual presence and a more direct route into the discussion.

User feedback highlighted this outcome in practical terms. One reported scenario involved two people on-site and one person online, with all three experiencing similar conversational influence and no echo. That observation points to the product’s broader value: audio engineering was being used to improve social balance, not merely to make sound cleaner.

Presence Without the Full-Screen Performance

Video fatigue is not caused by video alone. It also comes from continuous self-monitoring, oversized faces, restricted movement, and the sense of performing for a grid. Traditional layouts invite participants to check their own tile repeatedly. Even when no one is speaking, everyone remains visually prominent.

Around’s compact presentation reduced that pressure. A cropped, lightweight representation can communicate presence and reaction without displaying an entire room or demanding constant camera-ready behavior. For a 45-minute working session, even a modest reduction in self-monitoring can matter. If a participant checks a conventional self-view once every 30 seconds, that is potentially 90 attention shifts during one meeting. A less dominant self-view cannot eliminate distraction, but it can remove one of its triggers.

This design also supported the informal character of collaborative sessions. Public comments from users described team “campfires,” expressed affection for the software’s visual design, and emphasized a sense of play. Those reactions are relevant because interface tone influences behavior. A highly formal environment encourages presentation mode; a lighter environment can make experimentation, interruption, and rapid feedback feel more natural.

For teams evaluating the original product concept, www.around-com.com/ represents a useful case study in how video can function as ambient team presence instead of a virtual boardroom. Its central proposition was not that meetings needed more features, but that collaboration needed a smaller and more considerate meeting layer.

The Product Strategy Behind Its Appeal

Around’s positioning was unusually specific. It focused on hybrid-remote teams that create, collaborate, and celebrate together. Those verbs reveal three different usage categories: production, coordination, and culture. Many business communication tools handle the second category well, but treat production as screen sharing and culture as an occasional background effect. Around attempted to support all three within the product’s basic interaction model.

Several elements reinforced that strategy:

The breadth of platform support was strategically important. A collaboration product loses value quickly if participation depends on one operating system or one browser. Supporting two major desktop systems, four named browser families, and two mobile platforms covered the principal environments used by modern knowledge workers. Browser access also lowered the barrier for guests, while installed applications could serve recurring team members.

The site offered Google account continuation alongside downloads, signaling an emphasis on fast entry. Every extra enrollment step increases the chance that a participant arrives late or abandons setup. In a team of ten, saving only one minute per person during initial access preserves ten person-minutes before the meeting has even begun.

What User Reactions Reveal About Product Fit

Testimonials are not controlled studies, but the language used by Around’s early advocates is still informative. Users did not praise only resolution, uptime, or administrative controls. They called the software beautiful, delightful, and joyful. One user said the team had moved all meetings to it; another characterized it as the first video-calling product built for people who meet to get work done.

Those comments suggest that Around’s differentiation operated on two levels. The functional level concerned usable screen space, distributed audio, and hybrid inclusion. The emotional level concerned comfort and personality. Software that succeeds on only the second level may be charming but disposable. Software that succeeds only on the first may be adopted yet resented. Around’s strongest product signal was that users frequently discussed both.

The claim that there was “no going back” is also revealing. Communication software has high switching friction because every participant needs access and teams develop habits around calendars, links, and meeting norms. Strong willingness to move an entire meeting schedule therefore indicates more than casual curiosity. It suggests that the experience was different enough to justify coordination costs.

Still, user enthusiasm should be interpreted carefully. Around was not necessarily a universal substitute for every enterprise conferencing requirement. Large broadcasts, formal webinars, regulated environments, and complex administrative deployments can demand a different feature mix. Its clearest advantage appeared in small and midsize working sessions where active collaboration mattered more than stage-managed presentation.

Why the Miro Acquisition Made Strategic Sense

Miro and Around approached the same problem from complementary directions. Miro provided a shared visual workspace where distributed teams could organize ideas and create artifacts. Around provided a communication layer intended to remain present without taking over the workspace. Combining those perspectives supports a broader vision in which conversation and creation occur in one continuous environment.

The economic logic is straightforward. When a team uses separate tools for its canvas and its call, attention is divided between two interfaces, and product value is divided between two vendors. Bringing communication closer to the collaborative surface can reduce switching and make sessions feel more coherent. Even saving 15 seconds across 20 context switches during a workshop returns five minutes of attention. Across four weekly workshops, that becomes roughly 17 hours per year for a ten-person team.

The acquisition notice stated that Around had joined Miro to help shape the future of team collaboration. That wording places the product’s significance beyond a standalone calling application. Its ideas—compact presence, equitable hybrid participation, and communication integrated with creation—can influence how collaborative platforms are designed even if the original service changes over time.

Around’s lasting lesson is that video meetings do not need to imitate conference rooms. Hybrid teams benefit when every person has an individual presence, shared work remains visually central, and audio technology quietly handles the complexity of mixed locations. By treating the call as a supporting layer rather than the main event, Around offered a credible alternative to the oversized grid—and showed why better collaboration sometimes begins by making the meeting itself smaller.