Maybe he wants to avoid the cost of a paying a service to act as his representative in the Union as required by Article 27 if GDPR applies to his business under Article 3(2).
Whether Article 3(2) applies is somewhat subjective and a big part of it is intent. Blocking EU IP addresses and/or requiring people to say they are not in the EU before allowing them to use your site would help prove that you did not intend to serve people in the EU.
Or maybe he's worried about IP addresses. Regulators in Europe has said they are personal data that is covered by GDPR. If you have to give IP addresses the full GDPR treatment that could be a major hassle for a small organization.
So again if you aren't definitely intending to serve EU visitors blocking them can bolster the case that you don't fall under Article 3(2).
Whether Article 3(2) applies is somewhat subjective and a big part of it is intent. Blocking EU IP addresses and/or requiring people to say they are not in the EU before allowing them to use your site would help prove that you did not intend to serve people in the EU.
Or maybe he's worried about IP addresses. Regulators in Europe has said they are personal data that is covered by GDPR. If you have to give IP addresses the full GDPR treatment that could be a major hassle for a small organization.
So again if you aren't definitely intending to serve EU visitors blocking them can bolster the case that you don't fall under Article 3(2).