David Godibadze, network resilience consultant

David Godibadze

I work with a small number of businesses each quarter to identify where their network will fail next, and fix it before it does.

Focused on U.S. businesses with 20–200 employees where downtime has real business impact.

Focus

My work centers on network resilience. That means identifying where systems are likely to fail, how failures propagate, and what actually needs to change to reduce business impact.

What I Don't Do

I don't provide general IT support, managed services, or break-fix troubleshooting. I don't take ad-hoc calls or negotiate scope informally. If you need someone to reset passwords or manage day-to-day operations, I'm not the right fit.

Network Resilience Assessment

8 questions. Under 2 minutes. No technical detail required. The questions below are scored in the browser to show where your network is most likely to fail under pressure.

QUESTION 1 OF 8
When internet access goes down, what happens to the business?
  • Work continues with minor disruption
  • Some teams or systems stop working
  • Most operations stop
QUESTION 2 OF 8
When internet problems start, how predictable is the outcome?
  • We know what is affected and how long recovery usually takes
  • The impact varies each time
  • We usually find out when people complain
QUESTION 3 OF 8
When a serious outage happens, how long until the business is usable again?
  • Minutes
  • Hours
  • Unknown until it happens
QUESTION 4 OF 8
Based on your experience with outages or incidents, what typically causes the longest delay?
  • Waiting on something outside our control
  • Figuring out what was wrong or what to do
  • We are not sure
QUESTION 5 OF 8
How dependent is recovery on one specific person being available?
  • Not dependent
  • Somewhat dependent
  • Entirely dependent
QUESTION 6 OF 8
When something breaks internally, how contained is the impact?
  • Limited to a small group or area
  • Multiple teams are affected
  • The whole office feels it
QUESTION 7 OF 8
When problems start, how do you usually find out?
  • We are notified before users are affected
  • Someone notices and reports it
  • Multiple people report issues
QUESTION 8 OF 8
When something breaks, how quickly do you know what failed, not just that something failed?
  • Quickly enough to act without guessing
  • Eventually, after investigation
  • Usually unclear

This assessment highlights risk patterns. It does not replace a technical review.

Scoring runs in your browser. Answers are not sent anywhere. If scripting is off, you can still request a network resilience review.

Request a Network Resilience Review

How Engagements Work

Every engagement follows a defined process. No exceptions.

1. Request a review
Submit the form below. I review every request personally.
2. Paid initial assessment, $1,500
A 75-minute evaluation of your current network resilience. The assessment fee is not credited toward project work.
3. Scoped proposal
Based on the assessment, I deliver a written proposal with specific findings, recommended changes, and pricing. No ambiguity.
4. Project delivery
Fixed-price execution against the agreed scope. No open-ended billing. No scope creep.

What I Evaluate

Single points of failure Cascading failure paths Recovery predictability Detection gaps Human dependency External connectivity exposure

The goal is a network where failures are contained, recovery is predictable, and downtime doesn't compound.

This Is Not a Fit If

  • You need IT support, managed services, or someone to configure, deploy, or fix something
  • You want a free consultation, product recommendation, or "quick look" at your setup
  • You're comparing hourly rates or need someone available for ad-hoc calls
  • The person submitting cannot authorize budget or infrastructure decisions
  • Your team has fewer than 20 employees or downtime doesn't materially affect revenue

Request a Network Resilience Review

Expect a response within 3 business days.