Case Study / SaaS · Visual Collaboration Software
Miro
Square feet across two floors - designed, built, and managed
Austin and San Francisco under one team, one standard
Full RF and capacity design before any hardware was quoted
Prepared by TechProComp Managed IT | Austin, Texas
Executive Summary
Miro is a visual collaboration platform used by distributed teams to brainstorm, run workshops, map customer journeys, plan sprints, and design products together on a shared infinite canvas. It was founded in 2011 by Andrey Khusid and Oleg Shardin under the name RealtimeBoard, and has since become one of the defining tools of the distributed-work era.
As of 2025 the platform served more than 90 million users across over 250,000 organizations worldwide, including the large majority of the Fortune 100. In January 2022 Miro raised a $400 million Series C at a $17.5 billion valuation, co-led by ICONIQ Growth and Accel. The company operates hubs on multiple continents and is co-headquartered in San Francisco and Amsterdam.
Austin has been one of Miro’s fastest-growing locations and its largest hub in the United States. That last detail is what makes this engagement worth writing about. There is a particular kind of pressure that comes with building the network for a company whose entire product is real-time collaboration – the office is not a back-office utility, it is the product experience reproduced in physical space.
TechProComp was engaged to design, build, and manage that environment end to end: two floors, 65,000 square feet of downtown Austin, covering open collaboration areas, conference rooms, phone booths, and social spaces. The work started with a full design phase – RF planning against the actual floor plans and construction materials, capacity modeling zone by zone – before anyone quoted hardware.
The engagement did not end at handoff. TechProComp manages the network at both U.S. sites, Austin and San Francisco, under one team working to one standard – so a problem in San Francisco is handled by people who already know exactly how Austin is built.
At a Glance
Client
Miro
Industry
SaaS - visual collaboration software
Company Size
Roughly 2,500 employees worldwide
Headquarters
Co-headquartered in San Francisco and Amsterdam
Location
Austin, Texas - the company's largest hub in the United States
Engagement
Full network and wireless design, build, and ongoing management - two floors, 65,000 sq ft, downtown Austin - plus ongoing network management of the San Francisco office
Primary Goal
Build an office network that can carry a full floor of simultaneous live collaboration - and keep behaving that way as the hub grows
Outcome
Two floors designed, built, documented, and now managed alongside San Francisco to a single standard, with performance measured against published network and support targets
When the Network Is the Product Experience
Miro’s people do not use an office the way a traditional company does. Every conference room runs live multi-user sessions on Miro’s own canvas, layered on top of video calls with colleagues in Amsterdam, San Francisco, and Sydney. Design reviews happen with a dozen people editing the same board at the same time. The office is not a place where people quietly answer email – it is a high-density, always-on collaboration environment where the network is the product experience.
The Stakes
If the Wi-Fi drops during a workshop, it is not an inconvenience. It is a room full of people watching a collaboration company fail to collaborate.
Coverage and Capacity Across Two Floors
65,000 square feet of open collaboration areas, conference rooms, phone booths, and social spaces - each with a very different density and interference profile.
Density, Not Just Coverage
A floor plan that looks fine on a heat map can still collapse when 200 people join simultaneous video calls from the same open area. Capacity planning and channel design matter more than raw signal strength.
Real-Time Traffic as the Primary Workload
Video, voice, and live collaboration are unforgiving. Jitter and packet loss show up as a degraded meeting long before they show up on a monitoring dashboard.
An Enterprise-Grade Security Posture
A software company at this scale is a meaningful target. Segmentation between corporate, guest, IoT, AV, and building systems is not optional.
Room to Scale With Headcount
Austin has grown aggressively. Infrastructure sized to exactly today's number is infrastructure you rebuild next year.
Consistency Across Two U.S. Sites
Austin and San Francisco needed to behave the same way, be managed the same way, and be supportable by the same team.
Core Problem
A high-density, always-on collaboration environment had to be built from an empty floor plate - where the network is not a utility behind the work but the medium the work happens in, and where every design decision gets made months before anyone moves in and is expensive to unwind afterward.
The Mandate
Design the network before selecting the hardware, against the actual floor plan and materials
Engineer wireless for density zone by zone, not uniformly across a floor
Design and manage to published real-time media thresholds, not generic office benchmarks
Segment corporate, guest, IoT, AV, and building systems from day one
Size capacity for where the hub is going, not the move-in headcount
Manage Austin and San Francisco as one environment, to one standard
From Floor Plan to Managed Network
The engagement followed TechProComp’s standard methodology – design first, build second, manage continuously. We do not pull cable and then work out the architecture.
-
1
Design Before Deployment
RF planning against the actual floor plans and construction materials, capacity modeling against expected user density zone by zone, and a network architecture reviewed against how Miro's teams actually use the space - all documented and approved before hardware was quoted.
-
2
Build Across Two Floors
Complete structured cabling, switching, wireless, and edge infrastructure across 65,000 square feet - designed, installed, tested, and documented as one program of work.
-
3
Engineer Wireless Zone by Zone
Coverage engineered per zone rather than uniformly, because a phone booth and an all-hands space are different problems that a single template cannot solve.
-
4
Segment and Secure by Default
The same 12-layer security framework every TechProComp client gets, with the network segmented by function from day one - corporate, guest, IoT, AV, and building systems isolated rather than sharing a single flat space.
-
5
Manage Across Austin and San Francisco
Monitoring, patching, firmware lifecycle, capacity review, incident response, and change management at both U.S. sites, under one team working to one standard.
Solution Delivered
Designing and Building the Austin Hub
The Austin build started with a design phase, not a hardware order. Every decision was made against the actual floor plan, the actual construction materials, and the way Miro’s teams actually use the space.
01 / RF and Capacity Design
Designed against the building, not a template
- RF planning against real floor plans and construction materials
- Capacity modeling against expected user density, zone by zone
- Architecture reviewed against real collaboration workflows
- Documented design approved before hardware was quoted
02 / Full Build-Out Across Two Floors
65,000 square feet, designed to documented
- Complete structured cabling across both floors
- Switching, wireless, and edge infrastructure installed
- Tested and validated against the design
- Full documentation delivered with the network
03 / Zone-by-Zone Wireless
A phone booth is not an all-hands space
- Coverage engineered per zone rather than uniformly
- Channel design and capacity planning for high density
- Open areas sized for simultaneous video sessions
- Conference rooms, booths, and social spaces profiled separately
04 / Segmentation and Security by Default
The 12-layer framework, from day one
- Corporate, guest, IoT, AV, and building systems isolated
- No single flat space shared across functions
- TechProComp’s 12-layer security framework applied in full
- Enterprise-grade posture sized to Miro’s profile
The Standard
A network can pass a coverage survey and still fail a Monday morning. Coverage is a map question. Capacity is a behaviour question, and it only shows up when the room is full.
The Standards We Design To: Network Performance
Anyone can claim a network performs well. These are the numbers we design and manage to, drawn from established standards – ITU-T recommendations for real-time media and long-standing enterprise wireless design practice – not from internal opinion.
Real-Time Media
- One-way latency – under 150 ms. The ITU-T G.114 threshold for high-quality interactive voice. Past 400 ms, conversation stops feeling natural.
- Jitter – under 30 ms. Variation in packet arrival. Jitter buffers absorb some of it, but every millisecond they absorb is added to total delay.
- Packet loss – under 1%, under 0.5% for voice. Above 1%, loss becomes audible and visible. TCP applications start degrading from retransmissions well below that.
Wireless Design
- Signal at cell edge – -67 dBm or better, -65 dBm in high density. The industry baseline for reliable voice, HD video, and dense enterprise deployments.
- Signal-to-noise ratio – 25 dB minimum. Signal strength alone means nothing if the noise floor rises with it. SNR is what actually predicts a stable connection.
- Average channel utilization – under 40%. The single best early indicator of a capacity problem. Coverage can look perfect while the channel is saturated.
- 802.11 retransmission rate – under 15%. High retries from clients with strong signal is the signature of contention, not coverage.
- Usable throughput per user – 5-10 Mbps minimum in planned zones. Capacity is designed per zone against expected concurrent users, not averaged across a floor.
The Standards We Design To: IT Support Performance
Network standards describe the infrastructure. These describe the service around it. Support performance is where most managed service relationships quietly break down, because the targets are set once in a contract and then never reported on again.
- Infrastructure availability – 99.9% or better on core network and connectivity. Measured, not assumed. Availability that is not monitored is a guess.
- Critical incident response – defined by contract, measured every month. A response target only means something if attainment is reported back to the client.
- First-contact resolution – tracked and trending upward. The clearest signal of whether documentation and engineer capability are actually improving.
- Mean time to resolution – tracked by priority, reviewed quarterly. Averages hide the problem. Resolution time has to be broken out by severity to be useful.
- SLA attainment – reported to the client, not held internally. If a client has to ask whether targets were met, the reporting has already failed.
- Recurring incident elimination – root cause on repeat issues, not repeat fixes. Ticket volume that never falls is a sign that symptoms are being closed and causes are not.
- Client satisfaction – captured per ticket and reviewed in the QBR. Aggregate scores are easy to be comfortable with. Individual bad experiences are where the information is.
Reported, Every Quarter
Every TechProComp client receives a Quarterly Business Review with leadership covering what shipped, what broke, what it cost, and what comes next. Performance against these targets is part of that conversation, in writing, every quarter.
Managing Two Sites as One Environment
One Team, One Standard
The engagement did not end at handoff. TechProComp manages the network at both U.S. sites – monitoring, patching, firmware lifecycle, capacity review, incident response, and change management. A problem in San Francisco is handled by people who already know exactly how Austin is built.
Built to Grow Into
Austin has grown aggressively, and the infrastructure was sized against where the hub is going rather than the headcount on move-in day. Infrastructure sized to exactly today’s number is infrastructure you rebuild next year.
Design Before Deployment
Full assessment, documented architecture, and a quarter-by-quarter plan before anyone quotes hardware – so the decisions that are expensive to unwind get made on paper, not on site.
Engagement details are summarized for case-study purposes and must be reviewed and approved by the client before external publication.
Standard Office Build vs. The TechProComp Build
| Area | Before TechProComp | After TechProComp |
|---|---|---|
| Design Process | Hardware selected first, with the architecture worked out during installation. | Full RF, capacity, and architecture design completed and documented before hardware was quoted. |
| Wireless Coverage | Uniform access point placement from a template heat map. | Coverage and capacity engineered zone by zone against real density and interference profiles. |
| High-Density Performance | A floor that passes a coverage survey and then collapses when the room fills. | Channel design and per-zone capacity planning sized for simultaneous video across open areas. |
| Real-Time Traffic | Video and voice treated as ordinary traffic; users notice degradation before monitoring does. | Latency, jitter, and packet loss designed and managed against published thresholds. |
| Security | A single flat network shared by corporate, guest, IoT, AV, and building systems. | Segmented by function from day one under the 12-layer security framework. |
| Scalability | Infrastructure sized to move-in headcount, rebuilt at the next growth step. | Capacity headroom designed in, so growth does not trigger a rebuild. |
| Multi-Site Support | Each office built and supported differently, with local knowledge trapped on site. |
Austin and San Francisco built and managed by one team to one standard. |
| Service Reporting |
SLA targets set once in a contract and never reported on again. | Availability, response, resolution, and satisfaction reported to leadership every quarter. |
| Internal Team |
Product engineers pulled into corporate network problems. | Miro's engineering organization stays on the product; the network has a dedicated owner. |
Design Process
- Before TechProComp
- Hardware selected first, with the architecture worked out during installation.
- After TechProComp
- Full RF, capacity, and architecture design completed and documented before hardware was quoted.
Wireless Coverage
- Before TechProComp
- Uniform access point placement from a template heat map.
- After TechProComp
- Coverage and capacity engineered zone by zone against real density and interference profiles.
High-Density Performance
- Before TechProComp
- A floor that passes a coverage survey and then collapses when the room fills.
- After TechProComp
- Channel design and per-zone capacity planning sized for simultaneous video across open areas.
Real-Time Traffic
- Before TechProComp
- Video and voice treated as ordinary traffic; users notice degradation before monitoring does.
- After TechProComp
- Latency, jitter, and packet loss designed and managed against published thresholds.
Security
- Before TechProComp
- A single flat network shared by corporate, guest, IoT, AV, and building systems.
- After TechProComp
- Segmented by function from day one under the 12-layer security framework.
Scalability
- Before TechProComp
- Infrastructure sized to move-in headcount, rebuilt at the next growth step.
- After TechProComp
- Capacity headroom designed in, so growth does not trigger a rebuild.
Multi-Site Support
- Before TechProComp
- Each office built and supported differently, with local knowledge trapped on site.
- After TechProComp
- Austin and San Francisco built and managed by one team to one standard.
Service Reporting
- Before TechProComp
- SLA targets set once in a contract and never reported on again.
- After TechProComp
- Availability, response, resolution, and satisfaction reported to leadership every quarter.
Internal Team
- Before TechProComp
- Product engineers pulled into corporate network problems.
- After TechProComp
- Miro's engineering organization stays on the product; the network has a dedicated owner.
What Miro Gained
A Network Built for the Product: The office behaves the way Miro's canvas does - live, dense, multi-user, and uninterrupted.
Capacity That Survives a Full Room: Density planning, channel design, and per-zone throughput targets instead of a coverage map that only holds up when the floor is empty.
Security Built In, Not Retrofitted: Corporate, guest, IoT, AV, and building systems segmented from day one under a 12-layer framework applied to every client, regardless of size.
One Team Across Two U.S. Sites: Austin and San Francisco built and managed to a single standard, so support is never a question of who happens to know that office.
Focus Where It Pays: A world-class product engineering organization and a world-class corporate network team are two different companies. Miro's engineers stay pointed at the first one.
Why This Project Was Successful
- The architecture was designed and documented before any hardware was quoted.
- Wireless was engineered against real density profiles zone by zone, not spread uniformly from a template.
- Real-time media – the actual workload – set the performance targets, not generic office benchmarks.
- Security segmentation was built in from day one rather than retrofitted after occupancy.
- Capacity headroom was sized against Austin’s growth curve, not the move-in headcount.
- Austin and San Francisco are managed by one team to one standard, so nothing lives as site-specific tribal knowledge.
- Performance against published network and support targets is reported to leadership every quarter, in writing.
The TechProComp Difference
A company at Miro’s scale can hire network engineers. Many at that scale still do not – because a world-class product engineering organization and a world-class corporate network team are two different companies, and the second one is a distraction from the first.
What TechProComp brings to an engagement at this level is a design-first methodology – full assessment, documented architecture, and a quarter-by-quarter plan before anyone quotes hardware – a 12-layer security framework applied to every client regardless of size, and multi-site consistency, so the network in San Francisco is never a mystery to the people supporting Austin.
And the 0-0-0 model: no onboarding fees, month-to-month agreements, no cancellation penalties. We hold the account by continuing to earn it.
What Was Delivered
- Full RF and capacity design against actual floor plans
- Network architecture documented and approved before procurement
- Complete structured cabling across two floors
- Switching and edge infrastructure installed and tested
- 65,000 square feet of downtown Austin delivered end to end
- Wireless engineered zone by zone for density
- Channel design and capacity planning for simultaneous video
- Corporate, guest, IoT, AV, and building systems segmented
- 12-layer security framework applied in full
- Capacity headroom designed in for continued growth
- Ongoing management of the Austin and San Francisco networks
- Monitoring, patching, and firmware lifecycle managed
- Incident response and change management under one standard
- Performance measured against published network and support targets
- Quarterly Business Review with leadership
Building or expanding an office?
If you are taking down new space – one floor or ten – the network decisions get made months before anyone moves in, and they are expensive to unwind afterward. TechProComp designs, builds, and manages office networks for growing companies across Texas and beyond. We start with a full assessment and a documented architecture, and we do not require a long-term contract to begin.
