













Three things came out of the launch comments, and all three are live.
The town says why. When a check finishes, up to 100 of the people it reached get one more question. Those who scrolled past or got annoyed pick a reason, and those who liked it say what stopped them. For a post, those who stopped also say what they would comment. The page splits the reasons into ones about the text and ones about the audience, so you can tell a weak opening from the wrong readers. Jev also answers a few yes or no questions about the text itself:
Is there a concrete number, name or example?
Is it clear what the reader should do?
For a listing, does the first sentence say what is for sale?
Your own audience, in words. Describe whom the text is for, and only the residents who fit read it. "People who work in IT and are into startups" is 238 people, "people over 60" is 1,398. The town has no data on cities or company stages, so words about those do not count. The Audience tab shows how Jev read the description.
I pasted in a cold outreach subject line I'd actually sent and it flagged the exact thing a real reader would roll their eyes at - too much throat-clearing before the actual ask. Having a pool of simulated readers react before I publish anything is a genuinely useful gut-check step that's normally missing until you get real (and much slower) feedback.
It would help to see a breakdown of which persona segments reacted negatively and why, not just an aggregate glad-vs-annoyed number - right now I can't tell if a low score means the hook is weak or just that it doesn't land with one specific audience.
Wordtune polishes the sentence itself but doesn't tell you how a reader will actually react to it. Jevtown is closer to a reader-reaction test than a grammar/style pass, which is the piece I was actually missing.
Hi Product Hunt.
Most Jev demos ask the model for one decision: moderate this comment, route this email, score this ticket. I wanted to see what ten thousand decisions about the same text look like, so I built a town and put Jev in every house.
You write a post, a listing, a product or a headline. The 600 residents it should matter to read it first, and it travels further only while more of them are glad than annoyed. A weak text dies in the first wave for half a cent. A good one reaches all 10,000 in 14 seconds for about ten cents.
The test that convinced me: I wrote one iPhone listing two ways. The version that lets the buyer pay on inspection reached 2,100 residents and 142 wrote to the seller. The advance-payment-only rewrite reached 600 and stopped, with 204 of them suspecting a scam.
Three things I measured before building any of it, in case they help someone else building on Jev:
1. 200 personas in one request answer the same as one asked alone, so batching costs nothing in accuracy.
2. Reversing the order of the options shifts answers by 0.062, two and a half times the noise between two identical calls. So the order is fixed and never shuffled.
3. Asking "what is the highest price this buyer would pay" turns 90% of people into buyers. Writing the base rate into the question gives 48%, which matches what they actually do elsewhere in the same run. The calibration is real, but it calibrates the question you wrote.
No sign-in, no accounts. Ukrainian and English, and the language of your text picks the town.
Try it: https://jevtown.ivanhabor.com
The 30-second film of the two listings: https://youtu.be/Ktm2qwW7JAo
I would most like to hear about texts where the town got it wrong.
@ivangabor What kind of text has surprised you the most so far when the town gave an unexpected result?
@oliver_graf1 "Good morning everyone." I sent it through the first wave together with five other weak texts, spam and a scam listing among them, and expected all six to die there. Five did. "Good morning everyone" got through by a hair, which is about how such posts do in real feeds.
@jenniferdavis No, Jevtown doesn't measure reading time. For each resident, Jev answers one question: what is the most this person does with the post? It returns probabilities for scrolling past, reading, liking, reposting, following and blocking. The closest thing to attention is the share who stopped instead of scrolling past.
@jordantaylor58 Thanks! A text that doesn't land stops at the first wave of 600 residents in 2 to 4 seconds. One that reaches all 10,000 takes about 14 seconds.
@harrywilson No, not against real audiences. I checked two things. When I made the same 40 residents gardeners, 93% of them stopped at a post about tomato seedlings. When I made them programmers, 15% did. And the rule that decides whether a text travels further separated all six weak texts I tried, including spam and a scam listing, from six normal ones.
You can compare Jev with one real person, yourself. At jevtown.ivanhabor.com/me you describe a resident, ideally you, and say what they'd do with 12 posts. Then you get 8 new posts. You answer first, then Jev answers for your resident without seeing those answers, and the page shows how many of its answers matched yours and how many would have matched from the description alone.
These are still simulated readers, so the numbers are best used to compare two versions of the same text.
@robbalian Thanks, glad you like the UI! An AI detector asks Jev about the text. Jevtown asks it what each of 10,000 residents would do with the post, and the answer depends on who they are. When the same 40 residents were gardeners, 93% stopped at a post about tomato seedlings. As programmers, 15% did.
What's new in Jevtown: why the town passed, your own audience, and an MCP server
https://youtu.be/cDokxlOpKac?si=x2XQNJ2fWgAksFxn
Three things came out of the launch comments, and all three are live.
The town says why. When a check finishes, up to 100 of the people it reached get one more question. Those who scrolled past or got annoyed pick a reason, and those who liked it say what stopped them. For a post, those who stopped also say what they would comment. The page splits the reasons into ones about the text and ones about the audience, so you can tell a weak opening from the wrong readers. Jev also answers a few yes or no questions about the text itself:
Is there a concrete number, name or example?
Is it clear what the reader should do?
For a listing, does the first sentence say what is for sale?
Your own audience, in words. Describe whom the text is for, and only the residents who fit read it. "People who work in IT and are into startups" is 238 people, "people over 60" is 1,398. The town has no data on cities or company stages, so words about those do not count. The Audience tab shows how Jev read the description.
An MCP server. Jev writes no text, but an agent can. With the server, Claude or another MCP client writes variants, compares up to five on the first wave and follows the best one through the town. It runs on your own Jev key.
Before shipping, I tested every new question with paid runs and dropped three that did not hold up: how far people read, whether a text reads as written by AI, and whether a post puts its main point first. The numbers are in docs/measurements.md.
Try it: https://jevtown.ivanhabor.com
@leomartin357 Thanks! Not on the site. Everyone posts to the same town of 10,000 residents, and about 800 of them are into startups. A post for founders reaches many of them first, because the first wave goes mostly to the people the text should matter to most. When the run finishes, you can filter the reactions by the startups interest and see what those residents did.
For a town of founders only, you'd need your own copy. The code is open under MIT, and the residents are generated in one file, public/shared/personas.js, where you can change the jobs and interests.
@leomartin357 Would you rather describe the founders yourself, or have the crowd built from your real followers?
@leomartin357 You can now. Open Audience in the composer and describe the readers in words, for example "people who work in IT and are into startups". Only the residents who fit read the text, 238 of the 10,000 for that description. The town knows work, age, interests, money and what people shop for. It has no company stage or B2B, so "tech founders of early-stage B2B SaaS" becomes everybody who works in business. The Audience tab shows how Jev read your description.



Jevtown
This is in now. When a check finishes, the town is asked why. The people who scrolled past or got annoyed each pick a reason, such as "not for them", "the opening does not hook", "hard to believe" or "off-putting tone". The page then splits the answers into those about the text and those about who was reading it, so you can tell a weak hook from the wrong audience. The Got annoyed tab names the group most often annoyed, and the people who liked it say what stopped them.