Pearl District · Tulsa, OK Creative agencies, breweries, small professional services, and studios along the 6th Street corridor run almost entirely on Microsoft 365, Azure, and SaaS. The gap is usually between the cloud stack and the hundred-year-old building it lives in. We close it. Local team · ~4 mi from our Lewis Ave office · 20-min avg. resolution time
Free IT Risk Assessment
(918) 270-6600
IT Support for the Pearl District — Cloud-First Shops in Warehouse-Retrofit Space
Service Area
Pearl District, Tulsa
The Reality on the Ground The Pearl District runs a very different IT stack than its neighbors Downtown. Where a BOK Tower law firm still has an on-prem DMS, a typical Pearl tenant — a creative agency on 6th, a coworking setup near Peoria, a small software shop — lives almost entirely in Microsoft 365, Google Workspace, Azure, Slack, Notion, and whatever SaaS the team chose last quarter. The server room is a browser tab. The buildings don’t agree. The Pearl’s character is early-1900s warehouse and industrial space converted for offices, studios, and breweries. Brick-and-timber shells, twelve-foot ceilings, tall windows — and original knob-and-tube pulled out a decade ago, but with whatever data cabling the first tenant decided to run still snaking through the exposed trusses. Fiber, when it exists, was dropped during the retrofit and hasn’t been touched since. The result is a cloud-first business sitting on a legacy physical layer. When something goes wrong, the vendor you need to talk to isn’t Microsoft — it’s whoever handled your conduit in 2014. That’s the gap we live in: keeping cloud-first teams productive while the building itself is trying to be a building from 1912.
What IT actually looks like in the Pearl.
Environment Snapshot A rough model based on onboarding audits inside Pearl warehouse-conversions. Your walkthrough will quantify yours more precisely.
Pearl District IT, by the numbers.
Typical biz size
6–35
employees per tenant
Device density
3–5
managed endpoints per seat
Peak load window
Tue–Thu
10 AM – 4 PM, weekday creative sprints
Avg network age
5–8 yr
from the original retrofit
What We Actually See Not a generic service list — these are the calls that actually come from Pearl warehouse retrofits.
The six IT problems we fix most often in the Pearl.
M365 / Google account takeovers
Creative teams share freely with freelancers and vendors. OAuth consent prompts get clicked. A compromised account in a small agency is worth more than people think — both for data and for supplier invoicing fraud.
Big-room WiFi that fails
Warehouse conversions are 3,000+ sq ft with brick walls and exposed beams. One router in the corner does not cover it. Standups work; a client presentation on Teams in the far corner does not.
Upstream chokes on creative files
A 4K render upload, a Dropbox sync of an entire video project, a design team pushing to the cloud at 3 PM. Most Pearl ISPs are sold on download speeds; creative work is an upstream problem.
Third-party / freelancer access sprawl
SharePoint, Figma, Adobe, Slack — everyone’s been added to everything for a project that ended two years ago. External access is where data leaves, not an inbox.
BYOD everywhere, management nowhere
Macs, PCs, personal phones, personal laptops on guest WiFi that is also the office WiFi. Endpoint protection coverage is a guess. Offboarding is whatever the departing contractor decides to do.
Retrofit wiring mysteries
The data drops the landlord installed during retrofit are undocumented. Half the wall ports are dead. The live ones aren’t labeled. Every new hire becomes a 40-minute cable hunt.
Failure Order When the weekday creative sprint hits — mid-morning Tuesday through Thursday afternoon — systems fail in a predictable order. Knowing the order is how you harden the right layer. The chain usually breaks at WiFi or upstream first, but the damage that compounds is almost always on the identity and access side. Fix both — proper APs and real identity + endpoint management.
What breaks first in a Pearl warehouse retrofit.
WiFi coverage edges
Open-plan warehouse space has dead zones that a single AP can’t cover. The corner meeting area drops first. Client calls happening there are the first complaints.
Upstream saturation
Creative files upload for hours. Adobe, Figma, Dropbox, Frame.io. The ISP upload pipe fills, latency spikes, everybody’s Zoom goes choppy regardless of what else they’re doing.
Cloud productivity stalls
SharePoint / Google Drive sync hangs. Slack calls degrade. The “cloud-first” promise starts to feel a lot like an on-prem network with worse visibility.
Identity stress
Users get frustrated, re-auth fatigue sets in. MFA prompts get ignored or auto-approved. Consent phishing finds its moment. The weakest link is not a server — it’s a tired designer.
Data egress goes unnoticed
A former contractor still has SharePoint access. Files leave the tenant quietly. You find out months later when a competitor shows up with suspiciously similar work.
A Real Pearl Scenario The kind of call that starts as “our WiFi is slow” and ends as “how many old contractors still had access to our client folders?” ~25 users (w/ contractors) · M365 E3 + Google Workspace + Adobe · AT&T Fiber “Teams calls are dropping in the big conference corner, uploads take forever, and SharePoint keeps asking for MFA even for people who’re already signed in. Also, we’re not sure who actually still has access to our Dropbox.” One consumer AP for a 3,400 sq ft open warehouse with brick walls. Gig-down / 100 Meg-up fiber — creative uploads saturating the pipe every afternoon. Thirty-one external guests in their M365 tenant, four with access they’d had since 2021. No MFA on two shared service accounts. The “MFA loop” was Microsoft’s Conditional Access correctly catching impossible-travel events the team had been dismissing. Deployed four Ubiquiti UniFi APs on a proper channel plan, switched the ISP plan to symmetrical gig fiber with traffic shaping for uploads, rolled Entra ID Conditional Access + MFA cleanly across the tenant, audited and revoked stale external access, moved shared accounts to managed service identities, and added MDR-backed endpoint protection on every Mac and PC including BYOD. Because “we’re cloud-first so we don’t need IT” is the single most dangerous sentence spoken in Pearl District offices. Cloud-first means identity IS your network. If you aren’t managing identity, you aren’t managing anything.
A creative agency in a 6th Street warehouse, mid-sprint.
18-person creative agency, 6th St retrofit
The call
What we found
The fix
Why this page exists
Infrastructure & Environment The network you deploy depends heavily on the retrofit you inherited. Here’s what the Pearl actually offers. The Pearl is a retrofit district — the key variable is when the retrofit happened, not when the building was built. First-wave warehouse conversions. Data runs by whoever the original tenant hired, often visible, rarely labeled. No real IDF, typically a closet with a router and a cable tray. Common issue: undocumented cable paths, exposed conduit, no structured cabling at all. The bulk of the district. Cat5e / cat6 pulled during the retrofit, fiber handoffs brought in, but usually single-tenant assumptions with no provisioning for future separation. Common issue: one flat network, no VLAN structure, data drops in wrong places because the space got reorganized. Modern cat6, clean IDFs, sometimes fiber to the suite. Purpose-built for small tenants or coworking. Common issue: well-wired building, single ISP assumption. Design for failover or you’re one fiber cut from a dead day.
What you’re working with along 6th Street.
ISPs available
Building stock
Business density
Pearl District infrastructure, by building era
Pre-2010 retrofits
Early conversions
2010–2018
Pearl’s growth-era retrofits
2019+
Recent infill & new builds
Operational Risk Not incidents — conditions. Baked into the cloud-first / brick-building combination.
Three structural risks every Pearl tenant carries.
Upstream concentration
Creative workflows are upload-heavy. A gig-down plan tells you nothing about 20 people pushing renders simultaneously. Designing for download is designing for the wrong problem in the Pearl.
Contractor & guest sprawl
Freelancers, vendors, and clients get added to M365, Google, Slack, Figma, Dropbox. Nobody tracks who leaves when. The sprawl is the breach, whether or not anyone’s attacking.
Identity-as-perimeter exposure
No on-prem, no VPN, almost no firewall to hide behind. Your perimeter is the login screens on M365, Google, Slack, and Adobe. If MFA and conditional access aren’t right, there’s nothing else to catch a bad login.
Services, Mapped to the Pearl Not everything we offer — just the parts that actually matter for a cloud-first business in a retrofitted warehouse. The Pearl sits inside a broader pattern. See how we support Tulsa business districts as a cluster — the same playbook, tuned to your specific district.
What we typically put in place for a 6th Street tenant.
Identity & M365/Azure hardening
Entra ID / Azure AD tuned properly: MFA, conditional access, OAuth consent control, guest-access lifecycle, inbox-rule monitoring. The part of your stack that actually matters when everything is SaaS. Learn more
Warehouse-grade WiFi
Ubiquiti UniFi or Cisco Meraki designed for open-plan warehouse space — brick walls, high ceilings, and every square foot actually being used. VLAN separation for guest / staff / IoT, with dual-ISP failover where the building allows. Learn more
Endpoint management for Mac-heavy shops
MDR-backed endpoint protection across Mac and PC, Intune / managed Apple-ID configurations for creative teams, and device posture checks tied to Conditional Access. Works with how designers actually work. Learn more
Help desk that answers by chat
20-minute average resolution time during business hours, a Tulsa team, and tech support that works the way creative teams actually work — Slack-first, quick, and willing to drive to 6th when the fix needs hands on cable. Learn more
Local Anchors We work throughout the Pearl District, including: Nearby Neighborhoods
Where we show up in the Pearl.
We also cover these adjacent areas.
Pearl District FAQ Yes, and arguably more than an on-prem business does. Cloud-first means identity IS your network — and if MFA, Conditional Access, OAuth consent, and guest-access hygiene aren’t being managed, there’s nothing else between your work and whoever’s trying to take it. Most Pearl tenants we audit have 20+ stale external accounts with real access. Most ISP plans are asymmetric — gig down, 50-100 Meg up. A Pearl creative team is upload-bound, not download-bound. Once the upstream saturates, every downstream user on a Zoom / Teams call sees latency spike. The fix is symmetrical fiber (available from AT&T and Cox on certain plans) plus QoS that protects real-time traffic above bulk transfer. AT&T Fiber has strong coverage across most of the Pearl and is our usual recommendation for upload-heavy tenants. Cox Business is widely available and a good secondary. Consolidated is in select retrofitted buildings. For any revenue-critical tenant, we design dual-ISP with automatic failover — and LTE as tertiary in locations where the second fiber option isn’t lit. Yes. Pearl District shops are heavily Mac-oriented and we run mixed Mac/PC fleets with proper endpoint management, MDR, disk encryption, and posture-based Conditional Access. If your current IT provider’s answer to “we use Macs” is a shrug, that’s a sign. Our office is at 51st & Lewis — roughly ten minutes to the Pearl outside rush hour. For business-hours emergencies we target a 20-minute average resolution time remote and under 45 minutes on-site when a fix requires hands on hardware. For most Pearl clients in that range, flat-rate managed IT + cybersecurity starts at $200 per user per month, depending on the number of contractors/guests in the tenant and the security posture you need. Quoted after a walkthrough. No. Our standard managed IT agreement is month-to-month. We’d rather earn your business every month than hold you to a three-year contract you regret in year two.
Questions we get from Pearl tenants.
We’re entirely in the cloud — do we really need managed IT?
Why do creative uploads tank our whole network?
Which ISPs are actually reliable in the Pearl?
We’re mostly Mac. Can you actually manage Macs?
How fast can you be on-site in the Pearl?
What’s a realistic monthly cost for a 10–30 person Pearl agency?
Do we have to sign a long-term contract?
No pressure If you’re in a Pearl District retrofit and something in this page sounds familiar, the next step is simple: a short conversation and, if useful, a walkthrough of your identity posture and the building itself. Month-to-month. Cancel anytime. Local Tulsa team.
Start with a walkthrough. No commitment.
Book a Call
(918) 270-6600
