Around was built around a problem familiar to hybrid teams: video meetings can make it harder to work together, even when everyone is technically present. The product presented itself as a video-calling experience for teams that create, collaborate, and socialize remotely. Its stated design goal was not simply to reproduce a conference room on a screen, but to make calls feel lighter and more inclusive across different working environments. Around-com.com now identifies the project as acquired by Miro, connecting that earlier focus on video calls with a broader effort to shape team collaboration.
That combination is worth examining because collaboration is not one activity. A team might need to share a decision, review a draft, solve a technical problem, or spend time together without a formal agenda. Conventional meeting software tends to put all of those moments into the same visual and procedural format. Around’s positioning suggested a different emphasis: make it easier for people to participate while they continue working together, rather than treating the call itself as the entire workspace.
What Around Set Out to Change About Video Meetings
Around described its audience as extraordinary teams working in hybrid and remote settings. Its central promise was that meetings did not have to be draining. That message speaks to a practical weakness of standard video calls: everyone is placed into a grid of faces, attention is pulled toward the screen, and even a short discussion can become a separate block of work. Around’s product concept focused on reducing that sense of separation between the meeting and the work the team was doing.
The site highlighted distinctive audio technology and described a setup in which people could join from their own devices with microphones on and without echo. That detail matters for hybrid teams. In a conventional conference room, several people may share one speakerphone while remote colleagues appear as small tiles on a display. The arrangement can make it difficult to tell who is speaking, and voices in the room may reach remote participants unevenly. A system designed to accommodate individual devices aims to give each person a more direct presence in the conversation, whether they are sitting together or joining from somewhere else.
The project also framed participation as a shared experience across locations. One user testimonial described a meeting with two people on site and another person online, noting that everyone could take part and that there was no echo. Testimonials are individual reports rather than independent performance tests, but the example identifies a real design requirement: a hybrid call should not give the people in the room a natural conversation while leaving remote attendees to listen from the margins.
Around’s public materials named desktop and mobile options, including macOS, Windows, iOS, and Android, and listed support for Chrome, Safari, Edge, and Firefox. Supporting different devices and browsers is not a minor detail for distributed teams. It can reduce the friction of inviting a colleague, joining from a temporary workspace, or switching devices when a laptop microphone stops working. The practical value depends on how well the software handles those transitions, but the platform range reflects the reality that teams do not all work from the same setup.
Why the Design Matters in Hybrid Work
Hybrid meetings often fail in ways that are less dramatic than a dropped call. Someone in the office starts a side conversation that remote participants cannot hear. A person joining from home has to interrupt to get a word in. A group stays connected for an hour, but people leave unsure which decisions were made. These are meeting-design problems as much as software problems. Tools can help by making voices easier to follow and participation more balanced, but teams still need clear facilitation and a reason to meet.
For example, consider a product team reviewing a feature with colleagues in an office and a designer joining remotely. If the office group uses one room microphone, the designer may hear the main presenter but miss comments from people farther away. If each participant can join from an individual device and the audio system is designed to avoid feedback, the conversation has a better chance of including those quieter contributions. The meeting lead still needs to invite input and summarize decisions; technology cannot do that on its own. But a more even audio experience removes one avoidable barrier.
Around’s emphasis on calls for people who meet to get work done also points to a distinction between presence and progress. A video call can make people visible without helping them think together. Teams may benefit from a format that feels less like a formal broadcast and more like a working session, particularly when the goal is to exchange ideas or resolve an open question. The product’s stated ambition to bring play into software is relevant here: a small change in atmosphere can make a routine check-in feel less mechanical, provided it does not distract from the task.
Teams assessing the project’s approach can use http://around-com.com/ as a reference point for its original positioning and the acquisition notice. The useful questions are concrete: which devices are supported, how audio behaves when people join from the same room, and whether the meeting format fits the team’s actual work. Reading the product’s claims alongside current availability information is important, since an acquisition can change how a product is maintained, presented, or integrated into a larger platform.
Putting the Approach Into Everyday Team Practice
A team does not need to redesign every meeting to test whether a more inclusive call format helps. Start with one recurring session where the current setup creates friction. A weekly planning discussion is a useful candidate because multiple people need to contribute, and the group can compare the quality of participation from one week to the next. Before the call, decide what outcome is needed: a prioritized list, a decision, or a set of unresolved questions. Then observe whether people across locations can follow and join the discussion.
In practice, a simple trial can look like this:
- Choose a meeting with a clear purpose and participants joining from more than one location.
- Ask everyone to connect using the device and audio setup they expect to use for regular work.
- Check whether speech is clear when several people are together in one room and others join remotely.
- Have the facilitator explicitly invite remote attendees into the discussion rather than relying on visual cues from the room.
- End by recording the decision, owner, and next step, then ask participants whether the conversation felt balanced.
This test separates product experience from meeting habits. If remote participants still struggle to contribute, the cause may be room acoustics, facilitation, unclear turn-taking, or a mismatch between the call and the task. If the audio is clear but the meeting produces no decisions, changing video software will not solve the underlying problem. Conversely, if people can hear one another reliably and participate without fighting the format, the tool may be supporting the team in the way its design intends.
Different meeting types also call for different expectations. A focused one-on-one may need little more than clear audio and a private conversation. A planning session benefits from an agenda and a visible record of commitments. An informal team gathering can be valuable precisely because it is not another status report. Around’s site included a user describing a team “campfire,” suggesting that its perceived use extended beyond formal business calls. That kind of gathering can help distributed colleagues maintain social connection, but it works best when attendance does not feel compulsory and the activity suits the team.
For managers, the most useful measure is not whether a call looks novel. It is whether the format improves access to the conversation without adding complexity. Track recurring complaints, such as people missing comments, echo in shared rooms, or confusion about who is speaking. Ask participants from different locations whether they could contribute at the right moment. Those observations are more informative than counting meeting minutes alone.
What the Miro Acquisition Means for the Project’s Context
The acquisition notice on Around’s site says Miro acquired the project to help shape the future of team collaboration. This places Around’s history within a wider collaboration strategy, but the announcement alone does not establish which features, products, or technical components are currently available. It is therefore useful to distinguish the product’s original promise from present-day status. The site’s description and user comments document how Around was positioned and experienced; they should not automatically be read as a guarantee of current service or unchanged functionality.
The strategic fit is understandable. Video calls are often where a team discusses work, while collaborative tools are where that work is organized, developed, or presented. Bringing those experiences closer together could reduce the context switching that makes remote work feel fragmented. For example, a design review might begin with a live conversation and continue around the same shared material, so participants do not have to reconstruct the discussion in a separate space. Whether an acquisition delivers that kind of continuity depends on execution, integration, and the needs of actual teams.
Around’s strongest contribution to the collaboration conversation is its insistence that meeting software should be designed for the people using it, not only for the transmission of video. Its focus on hybrid participation, individual devices, audio quality, and a less rigid meeting atmosphere addresses recognizable problems in distributed work. The acquisition by Miro gives that perspective a larger organizational context, while the public information available about the project remains a starting point rather than a substitute for checking current product details.
For teams evaluating collaboration tools, the practical takeaway is to look beyond feature lists. Test how a call works when some colleagues share a room and others join remotely. Notice whether the audio makes it easy to follow the discussion, whether the meeting format supports the task, and whether participants leave with a shared understanding of what happens next. Around’s history illustrates why those everyday qualities matter: a meeting tool can be judged not just by whether it connects people, but by whether it helps them work together on equal terms.