Why I used JobSweep
Before offering the Crierwick helpers to anyone else, I tested each one on JobSweep. It is my own live product, run from the UK. I used one business, one person and my own computer. I tested each helper against the jobs the same kind of helper does in rival products. That gave me work about a real product to inspect, rather than a made up brief.
JobSweep searches nine UK job sites at once. It shows each site's own list and a combined list in which each job appears once. People can save jobs and set email alerts for daily or weekly delivery at their chosen London time. They apply on the original job site. JobSweep does not take their application or write the advert.
What the writing helpers made
I gave the blog helper a JobSweep article to write. It produced an 825-word piece called "How to judge a job advert before you apply", with pictures added. Export depended on my approval. I could read the article and look at the pictures before deciding whether it was ready to leave the test.
The social helper planned a month of JobSweep posts on an approval calendar. It also scheduled LinkedIn posts for set times after approval. The email helper drafted two welcome emails, a newsletter and a win-back email. These were drafts and plans for me to inspect, not evidence that anyone received a message or saw a post.
What the replies helper made
I also tested the replies helper on JobSweep. It wrote answers to common questions, sorted a support queue and drafted support replies. I could check what it would say before any reply went out. That matters for a product where the distinction between searching for a job and applying for it must stay clear.
JobSweep's public pages say who runs it and explain its limits. Its Privacy page says it never asks for a name, phone number, CV or password, and that it has no advertising or tracking. Those are concrete statements about my product. I wanted to see the replies as written, because a support draft is only useful if I can check what it tells someone.
Why nothing was sent
Every email and post in these tests went to a test outbox. The outbox showed exactly what would go out. Nothing was sent or posted. That applies to the welcome emails, newsletter, win-back email and social posts, including the LinkedIn schedule. An approval calendar and a scheduled time were part of the test, not a live publication.
I used the outbox to inspect the work at the point where it would otherwise have reached someone. The blog article also needed my approval before export. I can describe what each helper made, but I cannot describe these tests as a campaign sent to JobSweep users. The test produced work for review.
What has not passed
My pass rule was that a helper had to pass every job on its list. The search ranking helper did not pass, so it is not part of Crierwick yet. I am keeping that result separate from the drafts the other helpers produced. A useful article, calendar or reply draft does not make a different helper ready.
This was a test on my own product, on my own computer, with nothing sent or posted. It showed me the actual articles, plans, emails and replies the helpers could make for JobSweep. It also left a clear limit: I cannot count the search ranking helper as passed under the rule I set.
Before launch: in my tests every post, email and reply went to a test outbox that shows exactly what would go out, and outside accounts were practice ones. Your own accounts connect at launch.
Drafted by the Crierwick blog helper on 26 October 2026 from facts I gave it, then checked against those facts. A draft until I have read it.