Home/About

About

An engineering company that recruits, operates and advises.

Lumensoft Networks was built to bridge two industry gaps its founder experienced from the buyer’s side. Everything about how the company is structured follows from that.

Founded 2024Spokane, WA · nationwideLumensoft Networks CORP

Why the company exists

Two industry gaps, seen from the buyer's side.

After more than a decade in enterprise networking—ending as Director of Enterprise Architecture & Compliance at a major U.S. transportation organization—Our Founder experienced two persistent gaps from the buyer's perspective.

Finding qualified network engineers often meant screening candidates who looked strong on paper but couldn't demonstrate the technical depth the role required, leaving senior engineers to perform the technical validation the staffing firm was expected to provide. At the same time, many consulting engagements naturally centered on the technologies the provider delivered, rather than starting with the organization's operational goals.

Neither reflects poor intent. They are outcomes of how the industry is structured. Staffing firms specialize in recruiting, not engineering. Service providers build practices around the platforms they implement. Lumensoft Networks was founded in 2024 to bridge both gaps by combining technical leadership with engineering delivery.

How that shows up in the business

Structure, not intention.

Validation by someone still doing the work

The person who validates candidates and scopes engagements is a practicing Solution Architect. Technical judgment that is not currently in use decays quickly.

Advisory separated from delivery

Consultancy is advisory-only, permanently. Removing the implementation upsell is the only way an assessment can be trusted.

No platform resale

Cisco, Avaya and Microsoft environments are all served and none is sold. We have no product line to protect.

Guarantees scoped to one track

Each guarantee names the engagement model it applies to. A guarantee that does not name its boundary is a marketing sentence.

The three service lines

Co-equal and deliberately distinct.

Co-equal and deliberately distinct. Recruitment gives you the people. Professional & Managed Services does the work for you. Consultancy decides what work should be done.

What we will and will not tell you

The boundary, stated plainly.

We do not publish client names, testimonials, case studies, headcount or rate cards. Some of that is confidentiality, and some is that a young company quoting impressive numbers should be treated with suspicion.

We do publish an anonymized delivery record, the platforms actually in use, the founder's operating history, and the exact boundary of every guarantee.

Common questions

Frequently asked questions.

How large is Lumensoft Networks?

We do not publish headcount. If a requirement exceeds what we can staff to the standard we hold, you will be told during the discovery call rather than after a contract is signed.

The company was founded in 2024. Why depend on it?

Because the relevant experience predates the company. The delivery record — a 42-location, 8,100-user PBX replacement and a 10,000+ user migration with 911 continuity preserved — reflects work led before Lumensoft existed. The company is new; the engineering behind it is not.

What happens if your Solution Architect is unavailable?

Solution Architect Validated™ is a defined process rather than one person's calendar, and engagements are staffed with named delivery ownership. The practice carries more than one Solution Architect, and the work is assigned rather than owned — if the architect on your engagement becomes unavailable, another picks it up from the same written assessment. Founder involvement is by exception on enterprise-scale accounts.

Are you a US company?

Yes. Lumensoft Networks CORP is a US entity headquartered in Spokane, Washington, serving clients nationwide.

Do you work with organizations that already have an MSP?

Routinely. Most engagements sit alongside an incumbent and own one specific function while the incumbent keeps everything else.

Related services

Where to go next.

The origin explains the structure. The three service lines are that structure in practice, and each is set out on its own page.

The fastest way to evaluate us is a technical conversation.

Thirty minutes with a practicing Solution Architect. Bring the environment and the constraint, and you will get a direct answer about fit.