The async standup was invented to replace the synchronous standup. Inherited in the design was the standup's actual purpose — perform progress in a small paragraph, daily, in front of your team. Most async standups are still that, just slower and in text.
Pyloq treats the check-in as a blocker surface, not a status performance. The question it asks is not "what did you do yesterday." The question is "what is blocking you, and when do you expect to be done?" The first question produces prose. The second produces information the PM can act on.
The check-in runs on each PM's own schedule, for each PM's own projects, because blockers do not appear on a company-wide clock. What comes back is surfaced to the PM, not broadcast to the team. A blocker that used to cost a week now costs a message — and the PM sees it the moment it appears.