Every message that lands in our inbox gets read by a real person on our team. No ticket queues, no chatbots pretending to be support staff. Whether you spotted an error in a review, want to argue with a conclusion, or represent a vendor with something to add, here is exactly how to reach us and what happens next.
hello (at) choosesaas (dot) com
Plain email is the fastest route. We do not run a contact form because forms break, lose attachments, and hide behind CAPTCHAs. A regular email thread keeps the full history in one place and lets us forward it to whoever on the team actually knows the answer.
If a score or a conclusion in one of our SaaS tools comparisons does not match your experience, tell us which page and which section. We can walk you through how we derived our analysis from the underlying specs, pricing, and aggregated user reviews. Disagreement is welcome — sometimes a reader's real-world data point is more useful than anything we could derive in-house.
Pricing changes weekly in this market. If a plan price, a feature limit, or a free-tier quota on any page is out of date, send the page URL and what the current numbers are. Factual corrections go live within one business day, and we note the change at the bottom of the updated page.
If you work for a company we cover, or one we should cover, include the words "vendor inquiry" in your subject line. We accept review access and demo accounts, but payment for coverage is off the table — read our affiliate disclosure for how the money side actually works. Sponsored posts are clearly labeled or rejected.
Journalists looking for data from our coverage or a quote on the SaaS tools market can reach us at the same address. Put "press" in the subject line and we will prioritize it. We can usually turn around a comment or a data request within 24 hours on weekdays.
A real answer, not an auto-reply: within 2-3 business days for most messages. Corrections that we can verify against a vendor's public pricing page usually go faster. Press requests get same-day treatment when possible. Weekends and Chinese public holidays add a day or two.
To get a fast, useful reply, include three things: the URL of the page in question, what you think is wrong or missing, and (for vendors) a link to the official documentation that backs your correction. Messages with those three pieces skip the clarification round-trip entirely.
A few things land in our inbox that we will never be able to help with. We do not provide technical support for products we review — if your SaaS tools subscription is broken, the vendor's own support team is the right channel, and we link to every vendor's support page from our reviews. We do not give individual purchasing consultations for free beyond what is already published. And we do not sell or rent our email list to anyone, ever.
Missing a comparison you expected to find? Our editorial calendar is driven largely by what readers ask for. Send the two tools you want to see compared — or the buying decision you are stuck on — and if enough readers ask for the same thing, it moves up the queue. Several of our most-read guides started as a single reader email.
We accept a small number of guest contributions per year from practitioners — people who have actually administered business software categories inside a real company. If you have professional experience and a point of view that disagrees with something we have published, pitch us. Rates and terms are discussed by email.