Evaluation framework
Every full evaluation covers nine areas. For each, we record what is available, on which plan, with what limits, and how we know. “Not verified” is a valid result; silence is not.
- Client accounts and permissions
- How client workspaces are separated, how many each plan includes, and what team members and clients can access.
- CRM and pipelines
- Contacts, pipelines and stages, custom fields, duplicates, import and export.
- Marketing automation
- Workflow triggers and actions, templates, and any per-run charges.
- Communication channels
- Email, SMS, calls, chat and social inboxes: built in or third-party, and what they cost.
- Forms, landing pages and scheduling
- Forms, funnels, websites, booking calendars and payments.
- Reporting and integrations
- Agency and client reporting, native integrations, API and webhooks by plan.
- White-label and reselling
- Branding, custom domains, branded apps, rebilling usage and reselling the platform.
- Migration, setup, training and support
- Onboarding requirements or fees, migration help, documentation and support channels.
- Total cost and constraints
- Plans, add-ons, usage, contracts, minimum spends and cancellation terms.
We do not use star ratings or overall scores, and the facts never name a universal winner: which product fits depends on your requirements.
Separately, we declare one editorial preference. For agencies that want an integrated CRM and marketing automation platform, our preferred starting point is HighLevel. HighLevel is also our only affiliate partner, so we name that relationship wherever we state the preference. It appears only in comparisons that include HighLevel, in its own labelled section with the other product’s strengths and HighLevel’s costs and limits. It is not a test result, and it does not change prices, plan limits, feature availability, cost estimates or the comparison builder.
Evidence types
Every material fact carries one evidence type and the date it was checked.
- From Arel’s own use
- Firsthand experience that Arel has confirmed in writing, with its scope. Having used a product does not, by itself, support any specific claim.
- Tested by SaaSpectre
- A documented, repeatable test with date, plan, steps and result. We only say “tested” when such a record exists.
- Vendor documentation
- The vendor’s pricing pages, help articles or terms. This shows what the vendor states, not that the product performs as stated.
- Third-party report
- A named, attributed outside source. Never presented as our own finding.
- Unverified
- Anything else. Unverified claims are not published as fact.
For vendor documentation, we record where each fact appears on the vendor’s page and when we checked it, and we check it again when the page is reviewed. The pages published so far rely on vendor documentation and are labeled that way.
How we calculate costs
- Same requirements. We choose the lowest published plan that meets a scenario’s must-haves, including client accounts and team size.
- Same billing. Monthly and yearly billing are never mixed. A yearly price is one charge per year; any monthly equivalent is labeled as such.
- Everything you would pay. We add extra seats, required add-ons and one-time fees, and usage from stated assumptions.
- Unknown is not zero. If a cost is not published, the estimate is marked partial and lists the exclusion, or we say it cannot be estimated reliably.
- No currency conversion, no tax. Prices are shown in the vendor’s currency, as displayed to a US visitor, without tax.
- Savings only like for like. We show savings only between billing options of the same plan.
- No unexplained “best value”. We name a lowest-cost option only with stated criteria and complete estimates.
Freshness
- Prices, limits and usage rates are re-checked at least every 30 days.
- Trial and offer terms are re-checked at least every 14 days.
- Feature availability is re-checked at least every 90 days; policies every 180 days.
When a price passes its re-check date, the page that shows it is withdrawn until it is checked again. “Updated” dates change only for meaningful revisions, not for rebuilds or typo fixes.
Corrections
When we find or are told about an error, we check the primary source, correct the shared data so every page updates, and add a note to the page’s change history for material corrections. Vendors can submit corrections too; they are verified like any other report and give the vendor no editorial control.
Commercial independence
SaaSpectre earns money through some affiliate links, which are labeled. Whether a product has an affiliate program, or what it pays, plays no part in which products we cover, how we assess them, or which one fits a scenario. Read the affiliate disclosure.