NetView × Norvision JV Portal — V12 DOOH + Fiber + App Financial Engine

Unified Inputs

High-level knobs that impact every business line. Then refine in each dedicated tab.

Live calculator

Communities Live (count)

10
communities

Screens per Community

5
screens

Homes per Community (avg)

350
homes

Time Horizon for Exit Multiple (years)

5
years

Exit Multiple on EBITDA

12.0
x EBITDA

OPEX & Teams

Operating costs across the combined organization: sales, ops, customer support, ad ops, admin.

Baseline Monthly Operating Expense (OPEX)

$45,000
/mo

Incremental OPEX per Community

$1,200
/comm/mo

Sales Commission (% of DOOH + Vendor Revenue)

10.0%
rev

Property/Community Revenue Share (% of DOOH Ad Revenue)

15.0%
ad rev

Tip: Treat this “Unified Engine” as the main narrative. Then use DOOH/Fiber/App tabs to show how each stream independently produces value — and how the stack becomes a higher-multiple platform.

Monthly P&L Summary

Auto-generated from your settings. Scroll for a breakdown and ramp schedule.

All lines combined

Total Revenue

$0

Gross Profit

$0

EBITDA

$0

Run-rate Exit Value

$0

Line Item	Monthly	Notes

EBITDA multiple slider updates “Exit Value” instantly. Use this to frame why the combined stack (DOOH + App + Fiber) is not valued like a simple ISP or simple ad network.

DOOH Revenue Engine

Screens inside communities drive guaranteed attention. Model ad inventory, occupancy, CPM, and vendor sponsorship.

Digital Out‑of‑Home

Average Ad Impressions per Screen per Day

1,200
impr/day

Ad Inventory Occupancy (sold %)

55%
sold

Effective CPM ($ per 1,000 impressions)

$18.0
CPM

Vendor Sponsorship Packages

Modeled as flat monthly retainers (exclusive slots, category placements, seasonal campaigns).

Active Vendors per Community

10
vendors

Average Vendor Monthly Fee

$750
/vendor/mo

Ad Ops Cost (% of DOOH Ad Revenue)

4.0%
ad rev

Screen Hardware & Maintenance (memo)

Capex is not in EBITDA by default. You can include an optional “capex reserve” line in the engine.

Hardware Cost per Screen (Capex memo)

$2,500
per screen

Maintenance per Screen per Month

$22
/screen/mo

Optional Capex Reserve (% of DOOH total revenue)

5.0%
rev

DOOH model includes two revenue streams: programmatic CPM revenue (impressions × CPM × occupancy) and vendor sponsorship (flat fees). OPEX + commissions + revenue share are handled in the unified engine.

DOOH Output

Monthly view. Use this to show why the screen layer increases multiple and de-risks churn.

DOOH only

Programmatic Ad Revenue

$0

Vendor Sponsorship Revenue

$0

Maintenance + Ad Ops

$0

DOOH Gross Profit

$0

Metric	Value	Comment

If Norvision leadership wants “how do we sell it”: show DOOH as high-margin recurring media with community-protected placement, not random street billboard inventory.

Fiber Revenue Engine

Model subs, ARPU, take rate, and service costs. (This is a simplified engine for the JV portal.)

Connectivity layer

Fiber Take Rate (%)

55%

Fiber Monthly ARPU

$85
per sub

COGS per Subscriber per Month

$18
/sub/mo

Support Cost per Subscriber per Month

$4.0
/sub/mo

Churn (annual) — used only for narrative KPI

7.0%
/yr

Capex build is not modeled here; this portal is oriented to the integrated revenue stack and EBITDA power, not a full infra finance model.

Fiber Output

Monthly view of subscribers, revenue, and gross profit after direct costs.

Fiber only

Subscribers

0

Fiber Revenue

$0

Direct Costs

$0

Fiber Gross Profit

$0

Metric	Value	Comment

Resident OS Revenue Engine

App monetization: vendor marketplace, affiliates, featured placements, premium modules.

MyCommunity replacement

Monthly App Adoption (% of homes)

60%

ARPU Uplift from App (adds to fiber ARPU narrative KPI)

18%

Marketplace Take Rate (% of vendor spend)

8.0%

Avg Marketplace Spend per Active User per Month

$20

Featured Vendor Placements (count per community)

6

Avg Featured Placement Fee (monthly)

$300

App Ops Cost per Community (monthly)

$350

This tab is structured for your Canada client too: community guide + Q&A + vendor approvals + bookings. The model treats the app as a monetization layer that increases both revenue and defensibility.

Resident OS Output

Monthly view of marketplace revenue + featured placements net of app ops costs.

App only

Active Users

0

Marketplace Revenue

$0

Featured Placements

$0

App Ops Costs

$0

Metric	Value	Comment

Distributions Engine

Configure profit distribution after OPEX and reserves. Outputs monthly distributions by party.

Waterfall-ready

Monthly Reserve (% of EBITDA retained)

15%

Distribution Frequency

Monthly

Ownership / Split

Set distribution splits. (You can keep HoldCo at 70 / Norvision 30, and model David inside HoldCo.)

Norvision Distribution Share (%)

30.0%

HoldCo Distribution Share (%)

70.0%

David Johnson share inside HoldCo (%)

5.0%
of HoldCo

Distribution model: Distributable Cash = EBITDA × (1 – Reserve). Then split between Norvision and HoldCo. HoldCo then splits into David vs Morgan remainder.

Monthly Distributions

Based on your current EBITDA. Adjust reserve and split to match JV terms.

Cash to partners

Distributable Cash

$0

Norvision

$0

HoldCo

$0

David (inside HoldCo)

$0

Recipient	Monthly	Annualized	Notes

For “old-school Norwegian” leadership temperament: this tab is built to be clean, predictable, and auditable — simple inputs, clear outputs, no fluff.

Scenario Library

Save named scenarios (Base / Conservative / Aggressive / Canada Licensing / 30 Communities, etc.).

Persistent (local)

Scenario Name

Use clear names

Load Scenario

Scenarios are stored in your browser’s local storage by default (so the portal remains static and never 502s). For true multi-user shared persistence, connect this same UI to Supabase later.

Scenario Comparison (3-Up)

Load up to three scenarios and compare revenue/EBITDA/exit side-by-side.

Investor-ready

Scenario A

Scenario B

Scenario C

Chart Metric

Scenario	Revenue	EBITDA	Exit Value

Admin Center

Approve access requests, manage users, and review local activity logs (static mode).

Super Admin

This portal ships in Static Mode to prevent Netlify 502/503 issues (no functions required). Admin actions persist locally. For production multi-user tracking (heatmaps/session replay), integrate an analytics provider or Supabase.

Access Requests

These are stored locally when someone clicks “Request Access”. As Super Admin you can approve and generate credentials.

Timestamp	Name	Company/Role	Email	Message	Action

User Directory

Create / edit users (local mode). Share their login credentials to grant access.

New User Email

New User Password

Role

Email	Role	Last Login	Actions

Activity Log (Local)

Tracks tab navigation + scenario loads on this browser. For true multi-user analytics, integrate later.

Audit-friendly

Timestamp	User	Action	Detail

Deck Mode

A clean walkthrough view you can screen-share. Uses the same live data as the engine.

Presentation

The JV Narrative

1) DOOH inside communities captures attention and vendor spend.
2) Resident OS increases engagement + conversion + marketplace revenue.
3) Fiber connectivity anchors recurring subscription revenue.

Together, this becomes a platform with multiple monetization channels and a stronger multiple than any one stream alone.

Use the tabs to go deep, then return here for executive-level summary.

Revenue

$0

EBITDA

$0

Exit Value

$0

Communities / Screens

0 / 0

This view is designed to “feel” like NetView: cinematic, simple, and high signal.