SQL Chat VS iWrity

iWrity's answer:

iWrity runs on a points economy instead of a pay-per-review model. You read another author's book, leave an honest Amazon review, and earn points. Those points then buy reviews for your own book from other verified readers.

Reviewers are never paid and nobody is asked for a positive rating. The opinion stays the reviewer's own.

Around that sits a set of KDP research tools: a category finder, a niche finder, a price advisor, a description generator and a listing health check. Most tools hand you data. iWrity also hands you the readers.

iWrity's answer:

Most review services either charge per review or drop your book into a mailing list and hope someone opens it. iWrity pairs two authors who both want the same thing, so the pool of readers grows with the community instead of with an ad budget.

The free plan stays free, with no card required and no countdown. Paid plans start at $19 a month and add the research tools, expert publisher feedback and support for the non-US stores (UK, DE, FR, ES, IT, CA, AU), where reviews are hardest to come by.

Feedback on your listing and manuscript comes from a publisher with a six-figure track record, not from an automated score.

iWrity's answer:

Self-published authors on Amazon KDP. Mostly people running their own imprint rather than writers with a traditional publisher behind them.

Two groups dominate. First, new indie authors who have a finished book, a live listing and zero reviews, which is the point where sales stall before they start. Second, working indies with a backlist who need a steady flow of honest reviews on every new release instead of a one-off push.

A large share publish outside the United States or sell into the UK, German, French, Spanish, Italian, Canadian and Australian stores, where reviews are far harder to collect.

iWrity's answer:

iWrity grew out of our own publishing work. We put out illustrated non-fiction, and every launch hit the same wall: a finished book, a live Amazon listing, and no reviews. Paid review services break Amazon's terms. Asking friends does not scale and does not read as honest either.

So we built what we needed. Authors read each other's books and leave real reviews, and a points balance keeps the trade even, so nobody takes more than they give.

The KDP research tools came second. They started as the spreadsheets we were already keeping on categories, pricing and niche demand, and it made no sense to keep them to ourselves. The company is run from the Netherlands by a very small team.

iWrity's answer:

• Next.js (React, TypeScript) for the front end and the API routes
• Tailwind CSS for the interface
• Firebase, with Firestore for data and Firebase Auth for accounts
• Stripe for subscriptions and billing
• Vercel for hosting and deploys
• Amazon Product Advertising API for book and listing data
• Resend for transactional email