I think the Signature campaign is to establish themselves in the community before releasing the software, so that they are no more strangers when it is launched, it is a good step.
I still don't like that they've become very inactive recently, I might make an excuse for them that they're planning to answer every question when the project is already launched and being tested, so that people can confirm their claims as they reply and not just taking it with a pinch of salt. But It would've still helped to build confidence if they were still engaging to satisfy prospective clients curiosity.
The purpose of the signature team is a lot bigger than the interaction or bringing people to the ANN, but still, they come and either they saw the signature or not, they at least try to visit the ANN before even interacting with the project directly, and it is a wise idea.
So ANN is like a double edged situation here, because imagine if you as a newbie come to visit an ANN which is full of questions, people raising concerns, and no one from the official side is answering those questions. Then what will be your first thought? You will say at least these signature wearing people are active and giving their opinions. Maybe they will give their answers and comments, but does that count as accountability and updates from the team? No.
Therefore, the team has to come and manage some time, but I would not force this all on them yet because the deadline for the final release of the product is about to come, so they must be busy fixing things for us.