How we work, in writing.
Most consultancies have a tribal sense of how to ship. We wrote ours down. Every engagement runs on the same operating posture: doctrine-driven code, scope-limited access, in-writing proposals, audit-ready documentation.
The six commitments
What clients can hold us to, regardless of engagement size.
Written proposals
Specific scope, specific deliverables, specific price — never "depends on what we find." If a project's shape is too uncertain to price, we propose a paid discovery instead, with a fixed-cost cap and a deliverable you can take elsewhere.
Scope-limited access
We touch only what we've agreed to touch. No roving credentials, no "we'll just SSH in to fix it," no production access we can't justify in writing. When a problem is outside our scope, we say so and refer.
Audit-ready documentation
Every choice we make is annotated in code. When your malpractice carrier, regulator, or new vendor asks why something is configured the way it is, the answer is in the code, not in our heads.
Real handoff
We aim for engagements you can run without us. The deliverable is documentation a competent successor can use to take over. If you eventually hire in-house IT, we hand them a clean baton — not a black box.
The engineer you meet is the engineer you get
The person on your scoping call does the work and answers the phone afterwards. Nobody is sold a senior engineer and handed a junior on day one, and there is no account manager in between relaying questions they cannot answer.
Findings the day we find them
Anything critical reaches you within hours, not in a report three weeks later — you cannot act on a problem you have not been told about. Everything else lands in the written report, and for security work we re-check what you fixed at no extra cost. A retest is part of the job, not an upsell.
The three-step engagement
Every engagement, regardless of vertical, runs through the same three steps. The conversation is short; the proposal that follows is specific.
- 1
Intake conversation (no commitment)
A 45-minute call about your current setup, current pain, and the obligations that shape your decisions. Mutual NDA before; we leave with enough to write a real proposal.
- 2
Written proposal
Specific scope, specific deliverables, specific price. Includes which of your existing tools stay vs. change, what the 90-day picture looks like, and what success looks like.
- 3
Implementation + handoff
We do the work; you get documentation that lets your next vendor (or in-house IT) run it without us. Optional ongoing retainer for monitoring + incident response.
We will tell you if we're not the right fit.
We don't pretend to be a fit for every problem. If your situation calls for a 50-person managed-service provider with a 24/7 NOC, we'll say so. If you'd be better served by a single senior contractor for the next quarter, we'll say so. The intake conversation is meant to surface that — and we'd rather lose a sale than take an engagement we can't finish well.
When we are the right fit, you'll know within the first conversation.
Everything above runs on infrastructure we operate ourselves. What that stack is — and the six axes it's held to — is documented in the PlausiDen ecosystem.
Want to know what this would cost you?
Not ready to book? Read the report we deliver and what it costs first. Both are published in full.