Writing
AI Prompt for Software Reviews
Review apps and SaaS like a pro: this AI prompt covers features, pricing, UX, and alternatives — the full software review template. Free to use.
The prompt
You are a SaaS reviewer who has tested hundreds of tools. Context: I am reviewing [SOFTWARE_NAME], a [SOFTWARE_CATEGORY] tool, for [AUDIENCE]. Pricing: [PRICING]. I tested it for [TESTING_PERIOD]. My notes: [TESTING_NOTES]. Tone: [TONE]. Task: Write the full software review: headline, 100-word verdict box (rating [RATING], best for, starting price), "what it is" overview, pricing breakdown (tiers, what's actually worth paying for, hidden costs), hands-on feature review organized by workflow (not feature-list order), UX and learning curve assessment, integrations that matter, 3 closest alternatives with one-line comparisons, pros/cons, and final verdict by user type. FAQ: 3-4 questions (free plan? cancel easily? support quality?). Format: Markdown, verdict box first, pricing section with bolded key numbers, comparison mini-table for alternatives. Constraints: Test the actual workflows a buyer would use — don't review from the marketing site. Call out pricing traps (per-seat scaling, add-ons) explicitly. Every claim from [TESTING_NOTES] or [VERIFY]. Note what you couldn't test. Disclose any affiliate relationship. Screenshots of YOUR testing beat stock images.
Variables to fill in
Replace each [variable] in the prompt with your own details:
[SOFTWARE_NAME] [SOFTWARE_CATEGORY] [AUDIENCE] [PRICING] [TESTING_PERIOD] [TESTING_NOTES] [TONE] [RATING]
Example input
Example: SOFTWARE_NAME = 'TaskFlow', SOFTWARE_CATEGORY = 'project management', AUDIENCE = 'small agencies', PRICING = 'free / $12/user/mo / $24/user/mo', TESTING_PERIOD = '30 days with a 5-person team', TESTING_NOTES = '<your notes>', TONE = 'no-nonsense practitioner', RATING = '4/5'.
How to use this prompt
Test with a real project, screenshot everything, generate the review, then re-verify pricing on publish day — SaaS pricing changes constantly.
Tips for the best results
- Review by workflow ('planning a sprint') not by feature tab — that's how buyers think.
- The pricing section gets the most scrutiny; be exhaustive there.
- Revisit the review after 6 months; tools change and readers notice.
Frequently asked questions
Should I use affiliate links in software reviews?
Yes, disclosed. Just never let commissions flip a verdict — readers detect it.
Free trial vs paid testing?
Test the paid tier if that's what you're recommending; free tiers often differ significantly.