Operating Methodology

The Orbit Protocol™

A four-phase discipline for private network infrastructure: understand the property before specifying equipment, design before deploying, verify what was built, and hand over a documented system.

The sequence is constant; the depth of each phase scales with the property.

Start with an Initial Project Review

No charge · Non-binding · Ends with a recommended next step

The Orbit Protocol™ is The Orbit Tech's proprietary four-phase methodology for private network infrastructure: Terrain & RF Survey, Architecture Design, Precision Deployment, and Sovereignty Transfer — the documented handoff that leaves the owner in control.

It is a discipline, not a fixed package. The same method supports Executive Internet Continuity and Estate Networks alike.

Why the method exists

Connectivity failures are usually design failures.

Hardware gets blamed, but the decisions made before installation — placement, routing, capacity, documentation — determine how a system behaves under real use. When those decisions are improvised on-site, the owner pays for them later: the second visit, the unexplained dead zone, the network nobody can service because nobody wrote anything down.

Measured

Placement, routing, and equipment follow site measurement, so the design starts from how the property actually behaves.

Documented

Decisions, specifications, and as-built records are written down, so the system can be serviced without reverse-engineering the property.

Transferable

The records belong to the owner. A qualified professional who has never seen the property should be able to work from them.

The method in practice

See how the discipline translates into commissioned systems.

The methodology

Four phases, one discipline.

Each phase settles a specific set of decisions before the next one begins.

Phase 1

Terrain & RF Survey

Measured property conditions

Understand how the property actually behaves before anything is specified.

Fieldwork comes before equipment lists. Conditions are examined on the property — not estimated from a satellite map or assumed from a similar home.

RF measurement: Signal measured at the structures and proposed device locations — the environment the equipment must work in, not a manufacturer heat map.
Satellite obstruction analysis: Obstruction measured with inclinometer and Starlink app data, allowing for canopy growth so a February sightline still holds in July.
Building material assessment: Stone, brick, stucco, low-E glass, and metal roofing checked for signal loss against the actual construction, not industry averages.
Terrain and line-of-sight: For multi-building properties: elevation, tree lines, and seasonal foliage documented before any wireless bridge is specified.
Existing infrastructure audit: Current equipment, cable runs, electrical capacity, and rack or closet space inventoried. What is sound is preserved; weak points flagged.
Requirements interview: A structured conversation about usage, device counts, security, and expansion, so priorities become design constraints rather than surprises.

What you hold after this phase

A clear picture of the property's constraints before any equipment is proposed.

What varies by scope

A confirmed single-structure installation may need only a focused check of mount, path, and service entry; a multi-building estate warrants full RF and line-of-sight fieldwork.

Phase 2

Architecture Design

The plan before the build

Turn field data into a buildable design before installation begins.

Survey findings become a design: what will be installed, where, and why. Cable paths, device placement, and equipment selection are settled on paper first.

Depending on scope, the design addresses:

System design

Network topology
Equipment selection matched to conditions
Segmentation and network structure

Physical plan

Cable routing and pathways
Access point and mount placement
Building-to-building links where needed

Delivery

Implementation sequence
Cost definition
Phasing for construction or staged work

Nothing is ordered or mounted until the plan is approved.

What you hold after this phase

You can see what will be built, why, and in what order — before committing to implementation.

What varies by scope

Tightly defined work is captured in a detailed quote and work plan; complex, multi-building, or construction projects are where the full Infrastructure Architecture Plan earns its place.

Phase 3

Precision Deployment

Built and verified to the plan

Install what was designed — deliberately.

Mount positions, cable paths, and device placement are settled before tools come out. When conditions genuinely require a change, it is treated as a design change — reviewed against the plan, not decided from the top of a ladder.

Build to the design

The plan is the reference on-site, which avoids the familiar cycle of install, discover the mistake, and rebuild.

Verify as commissioned

Terminations are tested, coverage and roaming are checked against design intent, and configurations are recorded as the system is brought up.

Finish like it belongs

Cable runs concealed where the structure allows, penetrations sealed and weatherproofed, so the hardware disappears into the property.

What you hold after this phase

A commissioned system that matches its documentation.

What varies by scope

Verification is proportionate to the deployment — a failover system is exercised differently than a coverage system.

Phase 4

Sovereignty Transfer

Documented handoff and owner control

Transfer the system — and the understanding of it — to its owner.

The engagement ends with a documented handoff covering the credentials, configuration, records, and operating knowledge needed to run and expand what was built. Your infrastructure should not depend on any single installer's memory — including ours.

Representative handoff records:

As-built network topology
Device credentials and access
Configuration records
Commissioning and verification results
Manufacturer warranty documentation
Guidance for service and expansion

Ownership, in practice

You hold the credentials and the records, and any cloud service stays an optional choice rather than a hidden dependency. If you never call us again, another qualified professional should be able to take over service from the documentation alone.

What you hold after this phase

An owned, serviceable system with the paper trail behind it.

What varies by scope

Documentation reflects the system actually commissioned: a focused installation produces a focused record; an estate network produces a full as-built package.

Engagement paths

Begin where your project actually is.

Not every engagement needs the same depth of diagnosis or design, but every one starts the same way: a short conversation about the property.

Defined, single-structure work

When scope and conditions are already clear — a standard Starlink installation, a confirmed equipment replacement — the protocol compresses to a focused review, a Direct Quote, and a planned installation visit.

Explore the Direct Quote path

Existing conditions need diagnosis

When the property's behavior has to be understood first, the On-Site Infrastructure Assessment ($499 · approximately 60-90 minutes) formalizes the survey and ends with written findings and a recommended direction — 100% credited toward an approved Orbit Tech implementation project.

Review the Infrastructure Assessment

Complex or phased systems

Multi-building properties, renovations, new construction, and staged work warrant the Infrastructure Architecture Plan ($2,500-$5,000): a complete design engagement before implementation begins.

Review the Architecture Plan

Not sure which path fits? That is what the Initial Project Review is for. It is no charge and non-binding, and it ends with a recommendation: a Direct Quote, an On-Site Infrastructure Assessment, or an Infrastructure Architecture Plan.

Start with an Initial Project Review (571) 999-6915

Documented from survey to handoff. Availability depends on scope, location, and current scheduling.