Choosing a video-meeting platform is rarely just a matter of comparing camera quality and participant limits. The more important question is whether the software supports the way a team actually works. Around was designed for hybrid and remote groups that meet to create, collaborate, and celebrate together, rather than for organizations that simply need a digital conference room. Its interface, audio approach, device strategy, and playful atmosphere were all intended to reduce the fatigue associated with conventional video calls.
That positioning makes Around especially relevant to design teams, startups, creative studios, and other groups that spend substantial time working together on screen. However, there is an important strategic factor to examine before adopting it: Around was acquired by Miro to help shape the future of team collaboration. A buyer therefore needs to assess not only Around’s original product strengths, but also how its features, availability, and long-term direction may fit into Miro’s broader collaboration ecosystem.
Why Around Treated Video as Workspace Infrastructure
Traditional conferencing products often make the call itself the center of attention. Large rectangular video feeds occupy most of the display, controls compete for space, and shared work is placed inside or behind the meeting window. That design is appropriate for presentations, interviews, and formal discussions, but it can become intrusive when several people need to edit a document, review a design, or use a collaborative canvas at the same time.
Around took a different approach. It presented itself as video calling for people who meet to get work done. The distinction matters because collaborative teams may spend 10, 20, or even 30 hours per week connected to colleagues. Saving only 5% of the visual space or reducing a few seconds of friction per interaction appears minor in one meeting, yet the cumulative effect can become significant across hundreds of sessions.
The product’s compact visual treatment was intended to keep colleagues present without allowing their video feeds to dominate the desktop. In practical terms, this meant that a designer could remain aware of teammates while continuing to work in a design application, or a product group could talk while focusing on a shared artifact. Around’s philosophy was that video should provide social context while the team’s work remained central.
User reactions highlighted this difference. Public testimonials described the software as beautiful, joyful, and unusually well suited to productive meetings. One user summarized the appeal by calling it “the first video calling software built for people who meet to get work done.”
Such statements are subjective, but their consistency is informative: users were responding not merely to technical call quality, but to the emotional and spatial design of the experience.
The Audio Model Addressed a Real Hybrid-Meeting Problem
Around’s most consequential idea was not cosmetic. The service promoted a hybrid setup in which everyone could join from an individual device, keep microphones active, and avoid the echo that normally makes this arrangement impractical. This directly addressed one of the hardest problems in mixed-location meetings: creating equal participation for people in the room and people joining remotely.
In a conventional conference-room configuration, several on-site employees gather around one camera and one microphone. A remote colleague appears on a distant screen, while the people in the room can see one another naturally. The result is an information imbalance. Local participants notice gestures, side conversations, and facial reactions that may be invisible or inaudible to the remote participant. Even when six people attend the same meeting, the five in the room can function as one dominant group while the sixth person struggles to enter the discussion.
Putting every attendee on a separate laptop can improve visual equality, but it usually introduces feedback, echo, or duplicated audio. Around promoted audio technology designed for this exact situation. Its goal was to let two or more people sit near one another, join independently, and speak with all microphones on. A testimonial on the company’s site described two people participating on-site and one online while everyone retained the same experience and “power of voice,” without echo.
This is more than a convenience feature. If each person occupies an individual position in the call, remote participants no longer have to interpret an entire room through one wide-angle camera. Names, expressions, and speaking turns become easier to distinguish. The model can also reduce dependence on expensive room hardware: rather than requiring one specialized conference system, a team can use the laptops and mobile devices it already has.
Before standardizing on this method, however, an organization should test it under realistic conditions. Two laptops in a quiet room are less demanding than eight devices in an open workspace with hard surfaces and background conversation. Teams should run several pilot meetings, compare intelligibility for local and remote participants, and measure how often people need to mute manually. A claimed zero-echo workflow is valuable only if it remains reliable in the rooms where employees will actually use it.
Platform Access and the Consequences of Miro’s Acquisition
Around advertised access across macOS and Windows, major browsers including Chrome, Safari, Edge, and Firefox, and mobile devices running iOS and Android. That breadth was useful for mixed-device organizations because it reduced the chance that a contractor, client, or employee would be excluded by operating-system choice. Google account continuation was also offered, lowering sign-in friction for teams already using Google-based identity and productivity tools.
For anyone evaluating the product now, the acquisition context is as important as the original platform list. The project announced that it had been acquired by Miro, the visual collaboration company, with the stated aim of helping shape the future of team collaboration. That is a logical combination: Around focused on human presence and conversation, while Miro is associated with shared visual work. Together, those capabilities point toward meetings in which discussion and collaborative artifacts occupy the same workflow rather than separate applications.
The practical starting point for reviewing the product and its official messaging is https://around-com.com/, but a procurement decision should go beyond the landing-page experience. Teams need current answers about which applications remain downloadable, how existing accounts are handled, what support channels are active, whether standalone functionality is changing, and which capabilities may be incorporated into Miro. An acquisition can strengthen a technology by providing scale and integration, but it can also change the roadmap that early adopters originally selected.
This is where numerical evaluation helps. A team with 40 employees holding an average of three collaborative meetings per day may generate roughly 2,400 participant-sessions in a 20-workday month. Even a small change in reliability, joining time, or meeting fatigue is multiplied across that volume. Conversely, a workflow disruption affecting only 2% of sessions could still create nearly 50 problematic participant experiences per month. Buyers should therefore distinguish between an appealing demonstration and dependable performance at organizational scale.
Security and administration deserve similar scrutiny. Cross-platform access is valuable, but companies should verify current identity controls, data-handling terms, recording behavior, retention options, and administrative visibility. The requirements of a five-person creative studio differ sharply from those of a regulated enterprise. Around’s distinctive interface may satisfy users immediately, while legal, IT, and compliance teams still need documentation that reflects the product’s present ownership and service model.
A Practical Fit Test Before Teamwide Adoption
Around’s strongest use case was collaborative work rather than one-way broadcasting. Teams that spend meetings co-editing, brainstorming, reviewing creative assets, or maintaining an informal remote presence are more likely to appreciate a lightweight interface. Groups that primarily conduct webinars, formal training sessions, or large external presentations may assign greater value to moderation, attendance reporting, recording, and event-management features than to compact video presence.
The first test should compare Around with the organization’s current tool using the same participants and task. One group might conduct a 45-minute design review in each platform, then rate audio clarity, ease of joining, screen obstruction, turn-taking, and fatigue on a 1-to-5 scale. If eight participants complete the comparison, the team receives 40 scored observations across five categories for each platform. This will not produce laboratory-grade evidence, but it is more useful than relying on enthusiasm from a single demonstration.
The second test should recreate the most difficult hybrid arrangement. Place several local participants in the same room, have each join on an individual device, and include at least two remote colleagues. The remote attendees should evaluate whether they can identify speakers, interrupt naturally, and follow side comments. Local attendees should note any echo, delay, or pressure to share one device. Around’s central hybrid-work promise is meaningful only if remote participants experience genuine parity rather than merely receiving more video tiles.
The third test concerns workflow compatibility. Employees should confirm that the meeting interface leaves enough space for the software they use most, whether that is a visual canvas, code editor, browser-based document, or design tool. Mobile and browser participation should also be tested instead of assuming that every attendee will install a desktop application. A platform with four broad access routes can still produce inconsistent experiences if one route lacks an essential control or performs poorly on managed hardware.
Finally, decision-makers should evaluate continuity. Because Around became part of Miro, the relevant question is no longer simply whether users like the original product. It is whether the current service direction supports the organization’s next 12 to 24 months. Migration effort, account administration, employee training, and potential integration with Miro should be included in the calculation. A tool that saves each employee only three minutes per day could recover about 20 hours per month across a 20-person team, but those gains can disappear if the organization must repeatedly adjust to uncertain product changes.
Around earned attention because it challenged several assumptions of conventional video conferencing. It treated calls as a layer around the work, emphasized individual participation in hybrid rooms, supported a wide range of devices, and introduced a sense of play that many business tools avoid. Those qualities explain why users publicly described moving all their meetings to it and why the product attracted Miro’s interest.
The best pre-adoption decision is therefore neither automatic enthusiasm nor automatic caution. Teams should validate the audio model in their own rooms, confirm present platform availability, examine the implications of Miro ownership, and compare measurable workflow outcomes against their existing system. If Around reduces visual crowding, preserves equal speaking power, and fits the organization’s collaboration stack, it can represent a genuinely different meeting model rather than another interchangeable video-call application.