Lian Wu runs on Macs with Apple silicon (M1 or later) only. An Intel build would mean a second binary to sign, test and support, and I had no idea whether anyone wanted it. So instead of building it, I'm measuring it.
What I did
Under the FAQ answer "Which Macs does Lian Wu run on?", I added one line: "Using an Intel Mac? Let us know. Your request helps us decide whether to build an Intel version. We can't promise one yet." The same FAQ appears on the home page, the buy page and Help, in all four languages the site supports.
"Let us know" opens Help with an email link already filled in: subject "Intel version", body "Mac model and year: ". No form, no new backend. The original system requirements didn't change.
How I count
The number that matters is email threads with the subject "Intel version". Clicks on the link are tracked too, but only as a hint: a click doesn't mean someone wrote, and people who write may block analytics. Sending an email takes a minute of someone's time, so it's a stronger signal than a click.
I also kept that sentence out of the FAQ's structured data. Search results should only say what Lian Wu supports today, not what it might support.
What I learned
The cheapest test is a sentence. Before building a version, a form or a waitlist, ask in the place people already look for the answer.
Count the action that costs the person something. Emails over clicks.
Say clearly what you're not promising. "We can't promise one yet" keeps the test from turning into a commitment.