Home/About/Projects

Delivery record

A young company quoting impressive client logos should be treated with some suspicion.

So we publish none. What follows is the anonymized delivery record and the governance applied to every project — both of which can be tested in technical conversation.

Reference architecture governanceHLD and LLD producedZero-downtime cutover discipline

How projects are governed

The design is challenged before it is built.

STEP 01

Technical discovery

The environment as it is, not as the documentation claims it is.

STEP 02

Cost estimate and funding case

An independent estimate you can take to your own budget process.

STEP 03

Design review board

The design is challenged before it is built, not after.

STEP 04

Reference architecture, HLD and LLD

Documented to a standard that survives staff turnover.

STEP 05

Governed change and handoff

Change control through delivery, with documented operational handover.

Enterprise voice modernization at scale

10,000+ users, continuity preserved.

A major U.S. transportation organization, 10,000+ users, with an Avaya PBX estate approaching end of life. Microsoft Teams Direct Routing coexistence via AudioCodes SBC, with per-floor ALI mapping for E911 location accuracy. Cutover completed with no disruption to safety-critical operations and PSAP line continuity preserved throughout.

Multi-site legacy PBX replacement

42 locations, 8,100 users.

42 locations, 8,100 users, replacing a Fujitsu and Siemens estate. Standardized on a single Avaya IP Office platform with Kari's Law and RAY BAUM'S Act compliance delivered across every site, and vendor qualification against HIPAA, PCI and FISMA requirements.

Enterprise UC and network design

Across multiple enterprise environments.

Across multiple enterprise environments: Cisco Hosted Collaboration, WebEx Calling, Nexus NX-OS, VMware vCenter and UCS — including protocol-level diagnostics across SIP, H.323, MGCP and T.38.

Common questions

Frequently asked questions.

Can we speak to a reference?

References are handled case by case at the appropriate stage, with the client's consent. We do not publish them.

Was this delivered by Lumensoft as a company?

The record reflects work led by Lumensoft's founder, including engagements that predate the company's 2024 founding. We say that plainly rather than implying corporate history the company does not have.

Do you take projects of this scale now?

Scale is assessed against the specific requirement during discovery. If we cannot staff it to the standard we hold, you will be told before a proposal.

What documentation do we receive?

Reference architecture, high-level and low-level design as scoped, plus operational runbooks at handover.

Related services

Where to go next.

The delivery record is evidence rather than a service. Where a project resembles your own situation, the service page for that work explains how it is bought.

Test the delivery record in conversation.

Bring the technical detail you would want a vendor to be able to answer.