Get in Touch With Our Team
Have questions about a tool we have reviewed? Want to suggest a tool for evaluation? Looking for partnership opportunities? We would love to hear from you.
Send Us a Message
Other Ways to Reach Us
General Inquiries
For questions about our reviews, methodology, or website.
hello@saassoftwaretools.comTool Submissions
Want your tool reviewed? Send us details about your product.
tools@saassoftwaretools.comPartnership Opportunities
Interested in working with us? Let us discuss collaboration.
partners@saassoftwaretools.comResponse Time
We aim to respond to all inquiries within 24 to 48 hours during business days. For urgent matters, please mention "URGENT" in your subject line.
Frequently Asked Questions
How can I get my tool reviewed?
Send us an email with details about your tool, target audience, and how it differentiates from competitors. We evaluate all submissions and prioritize based on reader interest.
Do you accept sponsored content?
We do accept clearly labeled sponsored posts. However, sponsored content is separate from our independent reviews and does not influence our rankings.
I found an error in a review. How do I report it?
Please use the form above and select "Correction or update" as the subject. Include specific details about the error and we will investigate promptly.
Why We Value Your Feedback
SaaS Software Tools exists to serve the SaaS community. Your feedback helps us improve our reviews, expand our coverage, and ensure our content remains relevant and accurate. Every message we receive is read by a real person on our team.
We particularly appreciate hearing about your experiences with tools we have reviewed. Real-world feedback from practitioners helps us validate our assessments and surface nuances we might have missed. If you have had a notably positive or negative experience with any tool in our database, we want to know about it.
For those looking to have their tools reviewed, we evaluate submissions based on relevance to our audience, differentiation from existing solutions, and reader interest. While we cannot guarantee coverage for every submission, we do review each one carefully and appreciate the opportunity to discover new tools that could help our readers.
Thank you for being part of the SaaS Software Tools community. Your engagement makes this resource possible.
Helpful Things to Include
The page or comparison you are writing about, and the specific statement at issue.
What you observed in a trial or product, if you are challenging a claim.
Your role and stage at your company — the shape of a useful answer differs for a founder of five versus an ops lead at two hundred.
Whether you are asking as a reader, a vendor contact, or the working press.
How Fast We Reply
Corrections and accuracy challenges get the fastest read, because an inaccurate page is the worst artifact this site can produce.
Vendor pitches requesting a ranking change are read last, and do not change verdicts.
What This Site Cannot Do
We cannot test every integration a specific stack depends on, so some questions get answered with documentation links rather than direct verdicts. When a reader question exposes a gap in a page, the page gets fixed rather than defended.
We do not recommend vendors we have not seen execute at least one representative workflow, and we say when a category is outside our direct experience.
How a Correction Is Processed
First, the statement on the page is matched to what it originally claimed, and where the claim came from.
Second, the vendor's current product or documentation is checked directly, because that is the source we relied on.
Third, if the correction verifies, the page changes and carries the correction note; if it does not verify, the page stays and the discussion is closed with what evidence would reopen it.
What Not to Send
Bulk template pitches, link-exchange requests, and "we noticed your rankings" emails are treated as correspondence, not editorial input. Sending a report does not obligate a page change, and we do not negotiate verdicts.
If a vendor dispute would require secret knowledge that only a demo account can settle, publish publicly or provide verified access; we do not act on unverifiable assertions.