When the six don’t
fit your operation.
Most businesses fit somewhere on our engagement ladder — from the free Operational Snapshot to the Sovereign Operating System. Some do not. If your operation is unusual enough that none of the six is the right container, a custom engagement may be the answer. It is not a menu option. It is an application.
This engagement is built on the Infrastructure Doctrine, Perry Luzier's proprietary framework for removing the owner as the bottleneck so a business can grow past what one person can personally manage.
What is a custom engagement?
A custom engagement is a bespoke scope of work Luzran builds for an operation that does not fit any of the six standard engagements. It is defined case by case around your specific situation, and it is accepted only when the work genuinely fits our scope and the way we build.
This is the exception, not the default. The six standard engagements exist because they cover the overwhelming majority of owner-operated service businesses. Reach for a custom engagement only when your operation is structurally different enough that forcing it into one of the six would compromise the outcome.
Because every custom engagement is scoped from scratch, it starts with an application rather than a checkout. You tell us what you are trying to build; we decide whether it is something we can build well. If it is not a fit, we will tell you — and often point you to the standard engagement that is.
You don’t fit the box — and forcing it would cost you.
The standard engagements are deliberately shaped. They assume a certain kind of operation, a certain kind of bottleneck, and a certain path from diagnosis to build. When your business genuinely sits outside those assumptions, the honest answer is not to jam you into the nearest option.
A custom engagement exists for exactly that situation — an operation with unusual structure, an atypical constraint, or a build that spans more than one of the standard engagements in a way that needs to be architected as one.
But custom does not mean anything goes. We only take on custom work that fits our scope and the Infrastructure Doctrine we build on. That discipline is what keeps the work good. It is why custom engagements are approved case by case, and why some applications are declined.
What a custom engagement involves.
Application Review
You apply with the shape of your operation and what you are trying to build. We review it against our scope before anything is scoped or quoted.
Fit Assessment
We assess whether the work fits how we build. If a standard engagement would serve you better, we say so — a custom engagement is only offered when it is genuinely the right container.
Bespoke Scoping
If accepted, we scope the engagement from scratch around your specific operation, constraints, and desired outcome — not a template.
Doctrine-Grounded Build
However unusual the scope, the work is still built on the Infrastructure Doctrine — the same framework and standards behind every Luzran engagement.
Case-by-Case Terms
Investment and timeline are defined by the scope of your specific build, agreed before any work begins.
Full Ownership
As with every engagement, what we build is yours to own and operate — you are never locked in.
From application to accepted engagement.
Apply
Tell us about your operation and what you are trying to build. This is the application — not a commitment, and not a purchase.
Review
We assess fit against our scope and the Infrastructure Doctrine, and confirm whether a custom engagement is the right path or a standard one serves you better.
Scope
If accepted, we scope the engagement from scratch around your operation and agree the terms before any work begins.
Build
We build it on the same doctrine and standards as every Luzran engagement, and transfer full ownership to you.
What a custom engagement is — and is not.
By application
Custom engagements are applied for and approved case by case — not selected from a menu.
In scope
Accepted only when the work genuinely fits how we build. Some applications are declined.
Bespoke
Scoped from scratch around your operation — for businesses the six standard engagements do not fit.
Who should apply.
Frequently asked questions.
How is this different from the six standard engagements?
The six engagements cover the overwhelming majority of owner-operated service businesses. A custom engagement is the exception — a bespoke scope for an operation that genuinely does not fit any of them, scoped from scratch rather than chosen from a menu.
Do you accept every application?
No. Custom engagements are approved case by case and only when the work fits our scope and the way we build. If it is not a fit, we will tell you — and often point you to the standard engagement that is.
Why is it an application instead of a purchase?
Because every custom engagement is scoped from scratch, there is nothing to check out. You apply with what you are trying to build, we assess fit, and only then do we scope and quote it.
What does a custom engagement cost?
It depends entirely on the scope. Investment and timeline are defined by your specific build and agreed before any work begins.
Should I apply, or start with a standard engagement?
If one of the six clearly fits, start there — it is faster and proven. Apply for a custom engagement only when your operation is unusual enough that none of the standard options is the right container. When in doubt, a free Operational Snapshot will clarify it.
What happens after I apply?
We review your application against our scope, confirm whether a custom engagement is the right path, and if it is, scope the work with you before anything begins.
Related engagements.
Think your operation needs something custom?
Apply and tell us what you are trying to build. We review every application against our scope and will tell you honestly whether a custom engagement — or a standard one — is the right fit.
No sales pitch. No guilt trip. Just clarity on what's costing you.