Week Two Is When Projects Stall — and It's Not a Technology Problem
Ownership decides. Management implements. The gap between those two seats is where digital initiatives lose momentum — unless you set the expectation before the friction shows up.
If you don't own your data & digital infrastructure, your vendors do.
Here's How We Handle It
The pattern is predictable: ownership decides, management implements, and the gap between those two seats is where digital projects lose momentum. The decision-maker isn't in the room when the wires get pulled. The management team didn't ask for the project and gets handed it mid-quarter.
We pre-brief ownership on what management will push back on, before management pushes back. Set the expectation before the friction shows up.
We operate the layer ourselves — owner-controlled, but run by us — so on-site engineers and property managers aren't asked to learn a new discipline mid-rollout. Different skill set, different lane, same owner standard.
We work in Crawl / Walk / Run phases that respect lease-up timing, turnover windows, and existing CapEx cycles. No rip-and-replace.
The friction doesn't disappear. It just stops being yours to absorb.
Asset Management vs. Property Operations
Ownership / asset management
Accountable for NOI, refi, exit, and investor narrative. Needs defensible operating data — not another vendor dashboard.
Property management & engineering
Runs the building day to day. Should not become the integrator for segmented OT, exports, and governance unless that's the job they were hired for.
Crawl · Walk · Run
Phased delivery around real-world constraints — not forced big-bang cutovers.
Clarify on one asset
Map ownership, credentials, and leakage before you fund a rollout.
Prove the operating model
One property, one standard — evidence your team and capital partners can repeat.
Encode the portfolio standard
Productize the play so intelligence compounds instead of restarting at every address.
Accuracy vs. Model — Keep Them Separated
When invoices or field teams challenge the engagement, we don't litigate the business model in email threads.
Track A — accuracy / ops. Line items, dates, scope: did the invoice match the SOW, was the field tech on site the date we said, did the cabling run cover the units we listed. These are operational and they close fast — within a business day or two — because they're verifiable against documentation and field reports.
Example of a Track A issue: "Invoice line 7 shows 14 access points; the deployment plan called for 12." → Pull the as-built, confirm count, adjust the invoice. Done in hours.
Track B — commercial model. Owner-level decisions on pricing, minimums, CapEx ownership, revenue share, exit terms. These are not invoice questions — they're investment-thesis questions, and they belong on a scheduled owner call with the people authorized to change the deal.
Example of a Track B issue: "Why is the ancillary revenue share 60/40 instead of 50/50?" → That's a model question, not an accuracy question. It doesn't get answered by the field team or by an invoice adjustment; it gets answered by the owner and OpticWise principals on a scheduled call with the contract open.
The two tracks get confused most often when a Track B question lands in a Track A inbox (the AP team, the building engineer). Our job is to route it before the wrong people start litigating the wrong thing.
No Hostage Data
Export rights, admin credentials, and documentation live with the owner standard — portability is the design philosophy, not a departure penalty. See how that shows up in owner economics.
What's your data & digital infrastructure actually earning?
One building. 45–90 minutes. No software pitch. No rip-and-replace.
- What data & digital infrastructure you actually own — and what your vendors do
- Where recoverable NOI is sitting in your buildings — and what it's worth at refi or exit
- Where operational burden stacks up against your KPIs, and which plays close the gap
- The top 3 monthly plays you'd actually run — utilities, insurance, occupancy