Video conferencing became essential for distributed work, but necessity did not make every meeting tool pleasant to use. Around was created around a sharper question: what if a video call helped people work together without turning the meeting itself into the main event? The service positioned its product as a workspace for hybrid and remote teams, with an emphasis on natural conversation, shared attention, and a lighter emotional load.
Its public message was unusually direct: meetings did not have to “crush your soul.” Around presented video calls as a way for teams to create, collaborate, and celebrate together, while reducing the visual and technical friction associated with conventional conferencing. That positioning made the product relevant to teams that spent many hours in calls but wanted those calls to feel closer to an ordinary work session.
The problem Around tried to solve
Traditional video meetings tend to place every participant inside an identical rectangular tile. This layout is easy to understand, but it can make a group conversation feel like a broadcast. Participants watch a grid, wait for turns, monitor their own image, and often struggle to distinguish the person speaking from the surrounding interface. The larger the meeting, the more noticeable the effect becomes.
A hybrid meeting creates an additional imbalance. People sitting together in one office can naturally share a room, read small gestures, and speak at normal volume. A remote colleague may appear as one small tile on a large screen, with room echo and inconsistent microphone levels making participation harder. The technical setup can therefore influence whose ideas receive attention.
Around’s design responded to this problem by treating the call as a working environment rather than a digital conference room. Its goal was to give people in different locations a comparable experience, whether they were joining from a home office, a shared workplace, or a room with several colleagues. The service was aimed at teams that wanted meetings to support actual work instead of interrupting it.
Why the audio model mattered more than the video grid
The most distinctive technical idea associated with Around was its approach to group audio. The product promoted a setup in which everyone could remain on their own device, keep microphones active, and still avoid the echo normally caused by several connected computers in the same physical space. That combination addressed one of the most persistent hybrid-work problems: giving each person a separate voice without creating an unpleasant feedback loop.
In a conventional setup, two people in the same room may need to mute one device, share one microphone, or accept that the remote participant will hear a delayed version of every sentence. Around’s stated approach aimed to preserve individual participation. A person joining from home and a person sitting beside a colleague could both remain part of the same conversation with less acoustic interference.
This design also had a social effect. When every participant can speak through an independent audio channel, the meeting is less dependent on the person controlling the room’s central microphone. That supports what one user described as the “power of voice” in a discussion: the ability to participate directly, regardless of physical location. The benefit is especially clear in workshops, design critiques, planning sessions, and informal team conversations where quick exchanges matter.
The product’s public examples emphasized the same point in practical terms: two people could be together on site while another person joined online, yet all three could have a similar experience. Removing echo was not merely a sound-quality improvement. It helped prevent the remote participant from becoming a passive observer of an in-person conversation.
Around-com.com represented a meeting product with a clear point of view
The service was available for macOS and Windows, and it also supported modern browsers including Chrome, Safari, Edge, and Firefox. Mobile applications were listed for iOS and Android. That range mattered because a collaboration product must fit the devices teams already use. A meeting platform that works only in a single desktop application can create friction before the conversation even starts.
Around also offered a free trial and account entry through Google, alongside downloads for different platforms. These details suggested a low barrier to evaluation: a team could test the meeting experience without first redesigning its entire communication stack. The product was positioned for regular work, so ease of installation and access was part of the overall proposition rather than a minor convenience.
For readers assessing the product’s original approach, around-com.com is best understood as the name associated with a specific philosophy of collaboration: make the call quieter in the background, more inclusive across locations, and more compatible with focused work. The value was not simply that it enabled people to see one another. Its promise was that the software could change how a team behaved during a meeting.
How the experience differed from ordinary conferencing
Around’s design language focused on unusual, human-centered calls rather than a standard collection of meeting controls. The published site used phrases such as “video calls loved by extraordinary teams” and described meetings as spaces for creating, collaborating, and celebrating. That wording reflected a product strategy built around atmosphere as much as utility.
Several consequences followed from that strategy. First, the call could feel less like a formal appointment and more like a shared work session. Second, the interface could encourage people to concentrate on the discussion instead of staring at their own camera preview. Third, informal team rituals could become part of the same tool. A public customer example described a team “campfire,” showing how users applied the platform to social connection as well as project work.
These details help explain why user reactions were often emotional rather than purely functional. Comments described the software as beautiful, delightful, and enjoyable. One user said that the service passed the “KonMari test” by bringing joy to the software experience. Such statements do not prove that every team would prefer the product, but they do show that Around competed on a dimension many business tools ignored: how the application made people feel after several hours of use.
What the user feedback reveals about adoption
The available testimonials point to three recurring outcomes: teams moved more meetings into the product, hybrid participants felt better included, and users noticed the difference quickly. One customer wrote that their organization had moved all its meetings to Around and that the meetings had improved. Another said that once people began using the service, they did not want to return to their previous tools.
Those comments should be read as qualitative evidence rather than a statistically representative survey. Still, the consistency of the themes is useful. Users were not praising a single isolated feature. They referred to the overall experience, including audio, visual design, ease of use, and the feeling that the application had been built for people who meet to get work done.
The product also appealed to teams that disliked the sameness of mainstream meeting software. Public comparisons from users placed Around above familiar names such as Google Meet, Microsoft Teams, Zoom, and Skype. These comparisons were personal preferences, not benchmark results, but they indicate that Around created a recognizable category in the minds of its early audience.
Its appeal can be summarized through the following practical measures:
- Audio: separate devices could remain active in the same physical space with reduced echo.
- Participation: remote and in-person colleagues could contribute through individual microphones.
- Access: desktop apps, major browsers, and mobile platforms covered the main ways teams joined calls.
- Use cases: the product supported focused work, collaboration, celebrations, and informal team rituals.
- Adoption signal: users reported moving regular meetings into Around rather than using it only for occasional events.
Together, these points describe a product that treated meeting quality as a combination of technical performance and social balance. A call could be stable yet still fail if one group dominated the discussion. Around’s proposition was that better audio architecture and a less intrusive interface could improve both dimensions at once.
Why the hybrid-remote focus remains relevant
Hybrid work exposes weaknesses that are easy to overlook in fully remote teams. When everyone joins separately, the technical conditions are usually similar. When some people share a room and others connect from elsewhere, the meeting has to reconcile different acoustic spaces, cameras, social cues, and levels of attention.
Around’s answer was to make the individual participant the basic unit of the meeting while still supporting shared physical locations. That is a subtle but important design decision. It avoids forcing every participant in an office to behave as one anonymous group, while also avoiding a situation in which remote attendees are reduced to a screen at the edge of the room.
The implications extend beyond meetings. A team reviewing a presentation can give each person a clear voice. A product group can brainstorm without asking remote colleagues to interrupt a room conversation. A manager can run a check-in where participation does not depend on sitting closest to the microphone. These are small changes in mechanics, but repeated across several meetings per week they can affect who speaks, who is heard, and who remains engaged.
The approach also explains why Around’s messaging emphasized inclusion without relying on a long list of enterprise features. Its central promise was experiential: a hybrid meeting should feel like one shared conversation. If the software could reduce echo, support independent participation, and keep the interface from overwhelming the work, it addressed a problem that feature counts alone could not measure.
The product’s place after its acquisition by Miro
Around-com.com publicly stated that Around had been acquired by Miro to help shape the future of team collaboration. That announcement changes how the service should be evaluated today. Around is significant not only as an independent video-calling product, but also as an example of design thinking that could influence a broader collaborative workspace.
Miro is associated with visual teamwork and shared canvases, while Around brought a focused perspective on live conversation. Combining those ideas points toward a more connected model of collaboration: teams may move from discussion to visual work, from planning to execution, and from formal meetings to informal interaction without switching between disconnected experiences.
The acquisition also places Around’s original product decisions in a wider context. Its audio technology, support for mixed physical locations, and attention to meeting atmosphere were all attempts to make collaboration more human. Those principles remain useful even when the original application is considered as part of a larger company or product direction.
Around stood apart because it did not define success as putting more people into a call. It focused on what happened once they arrived: whether voices were balanced, whether the room created an advantage for some participants, and whether the software made the work feel heavier or lighter. That focus gave around-com.com a clear identity in a crowded video-conferencing market, and it explains why the service earned such strong loyalty from teams that adopted it.