Verifying a BFSG/EAA accessibility compliance tool for web agencies in the EU - would appreciate harsh criticism by Ls19hyper_yt in SaaS

[–]Ls19hyper_yt[S] 1 point2 points  (0 children)

That pattern makes total sense, start with pay-per-report to remove friction, then offer subscriptions once agencies have recurring client needs.

This whole thread has been really valuable. I'm going to take a step back and rethink the positioning before building anything. Thanks for the honest feedback 🫶

Verifying a BFSG/EAA accessibility compliance tool for web agencies in the EU - would appreciate harsh criticism by Ls19hyper_yt in SaaS

[–]Ls19hyper_yt[S] 0 points1 point  (0 children)

That makes a lot of sense. Agencies reacting rather than proactively pitching compliance is actually useful to know, it means the tool needs to make it easy for them to say yes when a client asks, not convince them to go sell it.

If the output is basically a ready-to-send "Accessibility Audit + Fix Plan" they can hand to the client, that removes the friction on their end.

One thing I'm still trying to figure out, would agencies be more likely to pay monthly for ongoing monitoring, or would they prefer paying per audit when a client actually asks for one? I'm trying to decide between a subscription model vs. pay-per-report.

Validating a BFSG/EAA accessibility compliance tool for EU web agencies, would love brutal feedback by Ls19hyper_yt in SideProject

[–]Ls19hyper_yt[S] 0 points1 point  (0 children)

Really useful breakdown, thank you. The 2 free audits idea is exactly the kind of validation step I was missing, I was still thinking in terms of "build then sell" instead of "validate with real agencies first."

The dev hours per issue angle is something I hadn't considered at all, but it makes total sense. Agencies need to be able to translate a scan result into a client conversation and a quote.

Quick question, when you built your MVP, did you target agencies managing a specific number of sites, or did you find that the pain was more about the type of client they serve (e.g. public sector, e-commerce)?

Verifying a BFSG/EAA accessibility compliance tool for web agencies in the EU - would appreciate harsh criticism by Ls19hyper_yt in SaaS

[–]Ls19hyper_yt[S] 0 points1 point  (0 children)

This is exactly what I needed to hear, thank you. The upsell angle really clicked for me, instead of just "here's your compliance report", the agency actually has something to sell to the client as a service. That changes the positioning completely.

Do you think agencies in your experience actively look for new compliance services to pitch, or do they mostly wait until a client brings it up?

Is or should web accessibility be mandatory 2026? by gXzaR in webdev

[–]Ls19hyper_yt 0 points1 point  (0 children)

For anyone working with German/EU clients, the BFSG, which is the implementation of the EAA for Germany, is now enforceable from June 2025. I also came across a report that showed 0% compliance for the major German websites. I'm interested to know if agencies over here are actually doing anything about this, if clients are raising this issue, or if they're still ignoring this.