Independent technical assessments for organizations with complex infrastructure, aging systems, or major technology decisions ahead.
I evaluate existing environments, identify architectural and operational risks, develop practical alternatives, and help you move from uncertainty to an actionable implementation plan. The assessment is a deliverable in its own right: it stands on its own whether or not Shrug does any of the work that comes out of it.
Why commission an assessment
Most organizations can describe symptoms. Few can hand a new CIO, a board, or a budget committee an evidence-based description of what they actually run, where it will fail, and what the realistic options cost. An independent assessment gives you that: a documented baseline, a prioritized risk register, and recommendations you can defend, produced by an engagement that doesn’t double as a platform sales pitch and doesn’t report to the team being reviewed.
It also works in the other direction. If you have an incumbent provider or an internal team you’re happy with, an assessment gives them an outside reference point instead of a replacement. I’ve worked with internal IT staff and existing vendors rather than around them, and a good engagement usually ends with them stronger, not displaced.
What an assessment covers
Depending on the contracted scope, an assessment can include:
- Environment inventory and architecture baseline
- Review of configurations, operational procedures, and documentation
- Availability, performance, resilience, and recovery assessment
- An evidence-backed risk register, prioritized by impact
- Architecture options with tradeoff analysis, not a single prescriptive answer
- Lifecycle and cost modeling
- Vendor and contract responsibility review
- An implementation roadmap with sequencing and rough effort
- Executive and technical readouts, delivered separately if you need both
Not every assessment includes every deliverable. We agree on the scope before the work starts, and what you get is what the contract says.
What you own
The documentation and recommendations are yours, subject to the contract. That’s the point of paying for an independent review: you keep the baseline, the risk register, and the roadmap whether or not any implementation follows, and whoever does the eventual work, internal or contracted, starts from what the assessment established.
How engagements are structured
Focused Technical Review
One bounded system or concern: a storage estate, a network, a backup and recovery setup, a migration plan that needs a second opinion. These have published starting prices on the consulting packages page.
Comprehensive Infrastructure Assessment
Cross-system or institution-wide review: documented findings across the whole environment, architecture alternatives, lifecycle planning, and an executive readout. These are scoped individually and quoted as fixed-price proposals; they don’t come out of a package price.
Implementation & Modernization
Remediation, platform deployment, migration, and operational transition, for the work you decide to commission after (or without) an assessment. This is where I started and where most of my hands-on experience lives.
Ongoing Engineering & Operations
Advisory and co-managed work, and separately scoped operational responsibilities, where the engagement continues past a project boundary.
Beyond these, OSPO++ and crisis-response engagements are scoped separately; see the services page for both.
If implementation follows
If you decide you want Shrug to do the work, great. The assessment becomes the foundation: the baseline is already documented, the risks are already prioritized, and the roadmap is already written. I’ll scope the implementation as its own engagement with its own milestones and acceptance criteria. But no assessment comes with an obligation to buy anything, and no proposal assumes I’m the one who implements it.