A video meeting can connect everyone while still leaving some people outside the conversation. That is the problem Around addresses: the gap between being present on a call and participating comfortably in shared work. Presented through around-com.com, the service focuses on hybrid and remote teams that need to create, collaborate, and spend time together without making every interaction feel like a formal conference.
Around’s proposition becomes especially concrete when several colleagues share a physical space and others join remotely. Its website describes a setup in which everyone uses their own device, with microphones on and no echo. For your team, that promise deserves more attention than a broad claim about “better meetings.” It targets a recognizable coordination problem: how to give people in different locations a comparable opportunity to speak, listen, and contribute.
The project’s website also states that Around has been acquired by Miro to help shape the future of team collaboration. That is relevant context when you evaluate the service, although the announcement alone does not establish specific integrations or future product plans. The useful starting point is the experience Around presents and how you would assess it against your team’s actual working conditions.
Around describes its calls as a place for hybrid and remote teams to create, collaborate, and celebrate together. Those three activities reveal the intended scope. The service is presented as more than a channel for status reports: it also aims to support working sessions and informal moments that help distributed colleagues feel like a team. You should therefore evaluate it against several types of interaction, rather than judging it solely by how well it handles a scheduled presentation.
The distinction matters because a presentation and a collaborative discussion place different demands on participants. In a presentation, most people can listen while one person speaks. During collaborative work, people need to interrupt politely, ask short questions, clarify an idea, and respond before the discussion moves on. If the audio setup makes those actions awkward, participation can become uneven even when everyone has a functioning camera and microphone.
Around’s emphasis on the human experience also appears in the testimonials reproduced on its site. Users describe enjoyment, visual appeal, and a sense that the software was built for people getting work done. These are subjective endorsements rather than controlled performance results. Still, they identify a meaningful evaluation question: does using the product make your team more willing and able to work together? A technically successful connection is only the beginning of a useful meeting.
The most specific capability highlighted in the supplied website material is Around’s audio technology for people using separate devices in the same location. Its claim is straightforward: everyone can keep their microphones on without producing echo. The site illustrates the idea through settings such as a modern workspace, a hotel suite, and a startup house. The common element is a group working together physically while maintaining a connection with colleagues elsewhere.
Without an effective arrangement, several nearby devices can create an uncomfortable listening experience. Teams may respond by muting most laptops or funneling the room’s conversation through a single microphone. Those workarounds can introduce their own difficulties: a person farther from the microphone may be harder to hear, and remote participants may struggle to follow quick exchanges. Around’s stated approach aims to reduce the need for that kind of compromise.
For your evaluation, translate the audio promise into observable behavior. Can a colleague at the far end of the table speak naturally? Can a remote participant ask a question without someone in the room managing microphones first? Does the conversation remain understandable when people respond quickly? The website supplies a clear product claim, but your room, devices, and network determine the conditions in which you need it to work. Test the actual arrangement you plan to use.
One testimonial on the site describes a meeting with two people on-site and one person online, emphasizing a shared experience, equal opportunity to speak, and an absence of echo. That example is useful because it gives you a small, realistic scenario to reproduce. You do not need a large deployment to investigate the central promise. A three-person session can reveal whether remote participation feels natural or requires constant accommodation.
“It’s the first video calling software built for people who meet to get work done.” — Patryk Zawadzki, in a testimonial reproduced on Around’s website
The quotation captures a user’s impression of the product, not an independently established claim of industry firsts. Its practical value is the standard it suggests: assess the call by the work your team can accomplish. A pleasant interface matters, but you also need to know whether people can resolve a question, develop an idea, or make a decision without repeated technical interruptions.
Use a short pilot with a defined task and a remote participant who can give candid feedback. Keep the exercise close to an ordinary working session, and evaluate these points:
This approach gives you evidence that is more useful than a favorable first impression. It also helps separate a product issue from a room-specific problem. If one arrangement performs poorly, identify the conditions before drawing a broad conclusion about whether Around suits your team.
The product information presented at around-com.com lists macOS and Windows, the Chrome, Safari, Edge, and Firefox browsers, and iOS and Android. For a distributed team, that breadth is relevant because colleagues may join from different operating systems and settings. You should still distinguish a listed platform from a verified fit for your workflow: the important question is whether each person can join and participate effectively using the device available to them.
The site provides download, login, and sign-up options, along with a free-trial invitation and a Google account continuation option. These details suggest an entry path you can evaluate before making a wider commitment. They do not, by themselves, establish the current terms of free access, feature limits, or organizational account controls. Confirm those details during your assessment, particularly if your team needs a consistent onboarding process.
Test access from the environments that matter to your organization. If most colleagues work on desktop computers but a few regularly join by phone, include both situations in the pilot. If browser participation is important, check the browsers your team actually uses. A service can list broad platform coverage while still requiring you to examine differences in the experience. The supplied material does not establish complete feature parity across every platform.
Give onboarding the same practical attention as call quality. A successful trial should show that an invited colleague can enter the right session, understand the basic controls, and contribute without extensive help. That is particularly relevant when your meetings include occasional participants. Around’s focus on comfortable collaboration is most valuable when the path into that collaboration is also manageable.
Around’s website connects its product to both productive work and team enjoyment. The testimonials include a reference to a Friday team “campfire,” while other users describe moving meetings to the service or appreciating its design. These examples support the product’s positioning as a place for different kinds of team interaction. They do not establish that every team will prefer it, but they give you concrete use cases to assess.
For working sessions, choose a task that depends on several people contributing. A proposal review, a planning conversation, or a discussion of competing approaches can expose participation problems more clearly than a one-way update. Watch for whether remote colleagues can respond at the right moment and whether people in the shared room remain attentive to them. Around’s audio approach is particularly relevant when the physical group would otherwise dominate the conversation.
For informal sessions, evaluate comfort and willingness to participate. A casual gathering succeeds when people can join the conversation without feeling that they are attending another rigid meeting. Around’s public messaging explicitly includes celebration, so this is a legitimate part of its intended use. You can assess whether the experience supports relaxed interaction while respecting that different colleagues have different preferences about social calls.
The testimonials in the supplied material are dated in 2021. They are evidence of reactions published at that time, rather than a complete account of the current product. Use them to identify what appealed to those users: enjoyable design, practical collaboration, and an improved sense of connection. Then check whether those qualities are present in the version and setup available to your team today.
The acquisition announcement gives Around a clear connection to Miro and its stated interest in the future of team collaboration. It does not provide enough detail to assume that an Around account includes particular Miro capabilities, that the products share specific controls, or that any particular roadmap commitment has been made. If those factors influence your decision, establish them directly through current product and account information.
Around’s site includes navigation for pricing, FAQs, downloads, and information about the company. For an adoption decision, use the current details in those areas to resolve questions the supplied material leaves open. You need to understand the applicable plan, any usage limits, and the support arrangements relevant to your team. If your organization has account-management or data-handling requirements, confirm those as well; the available description does not establish them.
Your strongest reason to consider Around is its specific response to hybrid participation: people sharing a room can use their own devices while remote colleagues remain part of the same conversation. Its broader appeal is the attempt to make working and spending time together feel more comfortable. Evaluate those promises with a small, representative group, then expand only when the results justify it.
A useful decision should rest on what changes for your colleagues. If remote participants can hear everyone, speak without extra coordination, and contribute throughout a working session, Around is addressing the problem its website sets out to solve. If those improvements do not appear in your environment, the branding and testimonials carry less weight. Let the quality of participation—and the work completed together—determine its place in your team.
