You keep control of every account.
Stillmark works from accounts in your name, on your tenants and repositories. Stillmark never uses shared credentials. When the engagement ends, you disable the accounts and nothing else changes.
Before a vendor touches your production systems, you need to know how it behaves. These are the rules Stillmark works by. They are in the master agreement too, but they are easier to read here.
01 Method
Stillmark writes down what you run, what connects to what, and who owns each part.
Risks are ranked by impact on the business, so the first fix is the one that matters most.
One change at a time, tested, with your written approval before it reaches production.
Every change goes in the change log. Every system gets a runbook.
Each month, retained clients see hours used, open risks, and what comes next.
02 Deliverables
Two of the documents every client gets. These are templates, with no client data.
Template
Template
03 Rules
Stillmark works from accounts in your name, on your tenants and repositories. Stillmark never uses shared credentials. When the engagement ends, you disable the accounts and nothing else changes.
Any significant change to a production system gets an email approval before it goes in. You control deployments. Stillmark does not release payments, approve files, or bypass controls.
Anything over eight hours becomes its own statement of work.
Documentation is a deliverable. Each system ends up with a runbook the next person can follow. Continuity means the knowledge is not only in one head, including Stillmark’s.
Retainers state how quickly Stillmark acknowledges an issue by priority. They do not promise a fix time. A fix can depend on systems and vendors outside Stillmark’s control. Stillmark is not on site full time, and the agreement says so.
Fees are fixed by the month or by the project. Hourly work is billed in 15-minute increments. Every invoice line is in the proposal.