StackVouch
How We Review Software
We evaluate software around the buying decision: the work it supports, who it fits, its limitations and the cost of using it in a real workflow.
Research and testing are different
A research-based review draws on product documentation, pricing pages and attributable external evidence. It does not imply that StackVouch opened an account or ran a campaign. A hands-on claim requires a documented activity and observations from that activity.
Product images supplied by a vendor are labeled accordingly. Vendor-published benchmarks and user-review themes remain attributed to their sources; they are not StackVouch test results.
What we assess
- Functionality: whether the documented capabilities cover the intended task, including plan restrictions.
- Ease of use: workflow complexity and documented controls; measured setup or task time only when actually observed.
- Pricing transparency: billing units, commitment, usage limits and unresolved commercial terms.
- Fit: team size, channels, existing tools and the reason for buying or switching.
- Product and fit limitations: evidence-supported constraints and the workflows they do not suit. Research gaps and source conflicts are listed separately as questions to resolve before purchase; missing evidence is not proof of a product defect.
Scores
We currently publish no numerical StackVouch product scores. Our reviews explain workflow fit, costs and limitations directly; a hands-on label does not establish an accuracy rating or comparative winner.
Prices and updates
The stated check date tells you when the cited pricing evidence was reviewed. A free plan is not the same as a trial, and a starting price is not a complete team budget. Confirm the plan, billing cycle, seats, usage allowances and add-ons before purchase.
An editorial wording update does not change a product's last-tested or fact-check date. Conflicting sources remain visible until the conflict is resolved.
From a published rate to a team budget
Our Apollo pricing table records both public billing options checked October 17, 2026. Three Professional seats at $79 per seat/month with annual billing imply $2,844 upfront for a year, before taxes and extras. Usage, retained tools and qualification work remain separate budget inputs.
The price check is distinct from our October 16 account workflow. A confirmed subscription amount does not establish email accuracy, delivery performance or the complete cost per usable contact.
Make the comparison your own
Use the same target sample or workflow for each finalist. Record what succeeds, what requires manual work and what the complete setup costs. Treat vendor claims about accuracy, deliverability or account safety as claims until the relevant evidence supports them.
Who designs and reviews the tests
Jimmy Dwyer designs and supervises our tests, reviews the evidence and takes responsibility for the published conclusions. Browser interaction and file analysis may use software assistance under his direction.
We use vendors’ own self-service free accounts or trials, declare a fixed sample and retain raw files privately. Reports identify the account plan, dates, sample, credits where observed, screenshots and what was not tested. Plans and starting conditions vary by report. Some tests use a disconnected draft, while Expandi began with Jimmy’s real LinkedIn account already synced; its initial setup was later supplied as account history. Sponsorship, special access and advance vendor review are disclosed in each report.
Published hands-on evidence
Test types
Workflow test. The product’s core function, such as search, lookup, enrichment or live outreach execution, was run on a stated sample, and the resulting output was inspected.
Setup test. Configuration, imports, drafts, previews, exports or other setup steps were checked, but the product’s core function was not executed.
Every Workflow test states its Sample / task scope. Sample sizes vary by report. Results from tests with different samples should not be compared directly.
Homepage Evidence Threshold, version V1
For search, lookup and enrichment tests, the V1 homepage evidence threshold is at least 10 distinct in-product results reviewed. A result counts as reviewed when it was returned by the predefined test query and inspected in the product, including results whose fields were locked, unavailable or missing. Retrieved, revealed, exported or populated records are not used to determine homepage eligibility.
This is an editorial evidence threshold, not a statistically representative sample size. We use 10 in V1 to exclude single-record anecdotes while keeping comparable testing feasible across free and trial plans. It may be revised as our testing methodology develops; revisions are recorded in the selection log below.
Homepage test selection
The homepage features the most recently published Workflow test that meets our homepage evidence threshold. “Most recently published” means the publication date of the test report. A test is eligible only if all of the following are true:
- The product’s core function was actually executed.
- The sample or task scope is published.
- For search, lookup and enrichment tests, at least 10 distinct in-product results were reviewed (see above).
- First-party test evidence that can be shown publicly, without personal data, exists.
- Untested items and the limits of the conclusion are listed.
- The full test report is published.
- Commercial relationships do not influence the selection.
Selection log
Selections are recorded by hand, newest first, after the homepage changes.
- October 25, 2026: Lusha Free Plan Workflow Test selected for the homepage under V1. Published October 20; ten in-product results were reviewed. Later RocketReach and Seamless.AI Workflow tests each used one tester-owned identity and do not meet the V1 10-result homepage threshold.
Hands-on reports published: 11 · Browse all test reports
- OutFlo Setup Test: Saved Classic Draft, One CSV Record and Exact Repeat
- La Growth Machine Setup Test: One CSV Record, Two Previews and Export
- Expandi Setup Test: Three Saved Steps, Branches and Preview Limits
- Seamless.AI Single-Profile Test: A Saved Lead and Three Invalid Email Candidates
- HeyReach Setup Test: One CSV Lead, Saved Fallback Text and a Sender Gate
- Reply.io Setup Test: Saved Sequence, Previews and Fallback Syntax
- RocketReach Self-Profile Test: No Match, an Input-Only CSV and Unchanged Free Lookups
- Lusha Free Plan Workflow Test: Two Emails, US Access Limits and Export Credits
- Waalaxy Setup Test: CSV Import, Duplicate Detection and an Unsent Draft
- Dripify Setup Test: Saved Sequences, Fallback Text and a Paused Import
- Apollo Professional Trial Workflow Test: 30 Contacts, Credits and Sequences
Follow each report for its exact scope. Test dates stay fixed when wording changes; documentation checks and editorial revisions have separate dates. Material corrections are recorded in the affected article’s revision history.
Commercial independence
Vendors do not pay for reviews, rankings or placement, and do not approve articles before publication. Eligible product links may earn a commission; see our affiliate disclosure.
Responsible editor: Jimmy Dwyer · Last updated: October 25, 2026.
Single-profile match requests are included in the Workflow test category only as bounded input/output observations. A missing self-profile, retrieved field, vendor confidence label or export row is not an accuracy or database-coverage measure. Plans, dates, populations and operations must match before a comparison can support a comparative result.
