What a profile establishes

SendCost is an independent purchasing directory for small B2B teams evaluating email-related software and infrastructure. A profile describes a particular task, available evidence and relevant cost dimensions. It does not certify a vendor, test every integration or promise that a tool will achieve a business outcome. We keep descriptive facts separate from our judgment about whom a tool may suit.

A source-check date records when the referenced material was inspected. It is not the source publication date, a guarantee that a vendor has not changed terms since then or a claim that SendCost personally used the product. When no hands-on test has been performed, we do not imply one.

Evidence must match the field

A specific plan allowance needs a source that names the plan and unit. An official product page can establish an advertised feature, while pricing, help documentation or a written quote may be needed for limits and billing. A feature appearing somewhere in a vendor catalog does not show that the chosen subscription includes it. We retain source links so you can check the current context.

If two official sections conflict, we record the conflict or leave the value unknown. We do not choose the lower price simply because it produces a more appealing comparison. Source quantity is not a score; an extra generic link does not resolve a missing plan-specific answer.

Compare the same procurement task

Sending software, data enrichment, verification, mailbox infrastructure and diagnostics have different purposes. Same-task comparisons use compatible fields and retain plan and billing context. A data-credit pool is not scored against a monthly sending allowance. A combined budget can include both categories, but that is cost composition rather than proof that one replaces the other.

Contacts held in software, new data obtained, sequence messages and connected accounts remain separate dimensions. Unknown values do not become zero, unlimited or confirmed compatibility. A comparison may reasonably conclude that your current tools are sufficient or that a decision must wait for a missing answer.

Corrections and commercial independence

Use a profile’s correction route to identify the field, proposed change and supporting official source. A domain-control claim permits a representative to suggest updates; it does not let that representative approve the facts. Editors can request evidence, retain an unresolved label or reject unsupported statements.

Free standard submissions and paid priority human reviews face the same evidence criteria. Sponsorship is visibly marked and occupies a disclosed placement; it does not change ordinary editorial ordering. Possible affiliate compensation does not determine whether an uncertain field is published as known. Review the commercial-disclosure document before following paid links or buying a service.

What to send when a single field looks wrong

Name the tool, plan, billing view and disputed field. Add the official URL and the exact allowance or term shown there, plus the date you inspected it. If two official sections disagree, include both instead of selecting the cheaper one. A source title is a navigation aid; the checked date records our inspection, not a hands-on performance test.

The directory’s unit filter finds plans with a documented numeric value for that unit. It does not prove the value is large enough for your workload. Billing and unit filters must apply to the same plan. Read the detail before combining account-wide, per-person and per-workspace quotes.

Sources and further reading

Source-based editorial research. Vendor terms can change; confirm the current contract before purchase.

Continue your research