Capacity and Continuity
Who does the work, what happens when a project needs more hands, and what happens if that engineer is unavailable.
84EM is built around a single accountable software engineer, Andrew Miller, who has 30+ years of industry experience. That is the differentiator, and it raises a fair question: what happens when a project outgrows one calendar, or when that engineer is unavailable.
Who does the work
Andrew Miller, 84EM’s principal software engineer, is the point of contact and the accountable party from scoping through deployment. The engineer who scopes a project architects it, writes it, and ships it. There is no middle layer relaying messages, and no handoff to a junior team after the sale.
When others are brought in
For larger or cross-discipline engagements, 84EM brings in a trusted network of vetted engineers, designers, and specialists. They are personally known rather than sourced on demand. Communication and accountability stay with the principal software engineer throughout. Adding capacity does not add a layer between the client and the person answering for the result, and at no time is the capacity added without the client’s written consent.
How contractors are vetted
Every contractor is known personally by 84EM, works under a signed NDA, with QA and final sign-off by the principal software engineer. Where subcontractors or agency partners will have access to client systems or data, their involvement is disclosed to the client before work begins. They handle client data under confidentiality terms consistent with 84EM’s own. At no time are they brought in without the client’s written consent.
Short absences
Short absences, illness or vacation, pause the work rather than hand it to someone unfamiliar with it. Clients are told in advance wherever the absence is planned.
Long absences
84EM has a vetted network of agencies and contractors who can cover an engagement temporarily or take it over outright. Because the full project record is maintained as the work happens, a successor needs a brief onboarding rather than a reconstruction, and nobody inexperienced inherits the work.
What the client holds
Clients keep repository access, documentation, and credentials for the whole engagement. Nothing depends on 84EM releasing them. All custom code is owned by the client, with full repository access, documentation, and no lock-in.
Put in writing
Everything above is how 84EM works, and it can go into the contract rather than staying a promise. That includes a key personnel clause naming Andrew Miller, with substitution only on written consent.
Frequently asked questions.
Will I work directly with the engineer doing the work?
Yes. 84EM's principal engineer is the point of contact and the accountable party from scoping through deployment. For larger engagements, a network of developers and specialists is brought in, but communication and accountability stay with the principal engineer.
Does 84EM subcontract work?
For larger or cross-discipline engagements, 84EM brings in a trusted network of vetted engineers, designers, and specialists. All professionals known personally, not sourced on demand. Every contributor works under a signed NDA, with code review and final sign-off by the principal engineer who stays the point of contact and the accountable party throughout the engagement.
What happens if 84EM is unavailable?
84EM has a vetted network of agencies and contractors, personally known rather than sourced on demand, who can cover an engagement temporarily or take it over outright. Because the full project record is maintained as the work happens, a successor needs a brief onboarding rather than a reconstruction, and nobody inexperienced inherits the work. Clients keep repository access, documentation and credentials throughout, so nothing depends on 84EM releasing them. Short absences, illness or vacation, pause the work rather than hand it to someone unfamiliar with it, and clients are told in advance wherever the absence is planned.
Have a project in mind?
Send the details and you will hear directly from the engineer.









