Top of the Rim does not keep a rate card, a package menu, or a monthly plan that every organization is asked to buy. That kind of price pretends the work is the same from one client to the next. It is not. The environment is different. The question is different. The size of the job is different. The price follows that difference.
Two clients can use the same words and still be describing two different jobs. Both may say they need help with Active Directory, Windows Server, patching, or an audit. One of them may need a defined look at one control. The other may need the design rebuilt, the change carried out, and a record an examiner can follow. Charging those two clients the same number would be wrong in both directions. The smaller job would be paying for work it did not ask for. The larger job would be priced as if it were a short review. TOTR will not do either of those things.
There is also no discount that turns a large job into a small price, and no minimum that turns a small job into a large price. If the work is narrow, the price is the price of that narrow work. If the work is wide, the price is the price of that wide work. The client is not fitted to a product. The work is fitted to the client.
How an engagement is priced
The price is the cost of the work that was actually described. It is not a fee pulled from a list because the client picked a label. A label such as "Active Directory" or "patching" or "audit" does not tell you how long the job is, how much access it needs, how many systems are in scope, or what finished looks like. Those facts are what the price is built from.
A simple review is the smallest shape. Someone needs a defined question answered. The scope is that question, the systems that question touches, and a written result. The work stops when the question is answered. It does not quietly become a redesign. A client who needs that review should pay for that review. They should not pay as if they had hired a full program.
One thing is a single problem with an edge you can point at. A patch ring that is not holding. A privileged group that is wrong. A trust, a migration of one domain, a baseline on one class of server. The job is that problem. It may take real engineering, and it may take more than an afternoon, but it is still one problem. It is not the rest of the environment. The price covers that problem. It does not cover a portfolio the client did not bring.
In-depth services go further than a look and further than one fix. This is the design, the change, and the proof that the change held. It takes more time. It takes more access. It takes more writing. It costs more because it is more work, not because the client was placed in a higher tier on a menu. A client who needs that depth should not be quoted the price of a simple review, and a client who needs the review should not be quoted the price of that depth.
A complete portfolio workup is the wide job. Identity, Windows Server, patch operations, hardening, and the evidence are looked at as one body of work, not as a single ticket. That is the largest scope TOTR takes. It is priced as that scope. It is not a stack of small-review fees added together until the number looks serious, and it is not a small client being asked to fund a program they did not request. If that is the work, that is the price. If that is not the work, it is not the price.
The same rule runs through local IT assistance. A practical job, on-site or remote, is priced as that job. It is a separate lane from Tier 3 engineering. It is not dressed up as a portfolio engagement so the invoice can be larger, and a Tier 3 engagement is not cut down into ticket clearing so it can be sold at a review price. The lane and the scope set the price. The label on the website does not.
What the discovery call settles
The discovery call is where those differences get named, before anyone is asked to pay for the wrong job. Chuck asks what is actually in front of you. What is broken, what has to be ready, how large the environment is, what the deadline is, and what finished means. A simple review and a complete portfolio workup do not leave that conversation as the same proposal.
You talk to the engineer. The person who hears the scope is the person who does the work. There is no sales layer in the middle, turning a package into a quote that does not match the environment. If the honest answer is that you need one thing, that is what you will be told, and that is what you will be priced for. If the honest answer is that the work is in-depth, or that it is a full workup, that is what you will be told too.
The call is also where the edges get written down. What is in the job. What is not. Which systems, which sites, which questions. A price without that edge is a guess. TOTR does not guess a number and then discover the environment later. The environment is described first. The price comes after that description, and it belongs to that description.
If the first description was incomplete, the price is not silently stretched to cover the new facts. A larger environment, a second problem, or a move from a review into a build is a new scope. It gets its own conversation and its own price. The original client is not punished for having asked a smaller question. The larger job is not forced to live inside a number that was never meant for it.
What the work includes
What you pay for is the work in the scope, done by the engineer who scoped it. For a review, that is the review: the question, the look, and a result you can read. For one problem, that is the problem brought to a finish you both named. For in-depth services, that is the design, the change, and the record of what changed. For a complete portfolio workup, that is the wide job across the areas that were included, not a tour of every product Microsoft sells.
What you do not pay for is work that was never in the scope. A simple review does not include a forest redesign. A single patch-ring repair does not include an organization-wide hardening program. A local IT visit does not include a Big 4 evidence package unless that package was the job. The other way is just as firm. A portfolio workup is not delivered as a short opinion and then billed as if the short opinion were the whole engagement.
On-site and remote do not change that rule. The practice is based in Overgaard, Arizona, with a location in North Phoenix. The work can be on-site or remote. Travel, remote access, and where the engineer sits are part of how that particular job is delivered. They are not a reason to put every client on the same price. Two clients in the same city can still have completely different jobs, and they will be priced as those jobs.
If you already know the shape of the work, say so on the call. If you do not, that is a fine reason to book it. The point of the conversation is to tell those shapes apart, and then to price the one you actually need.