Evidence scope
We saved a Classic follow-up with a native first-name token, a two-day wait and a stored fallback. One CSV record for Jimmy’s own profile imported and exported with its three supplied values intact. Reimporting the same file produced one unchanged duplicate and no additional recipient. Preview and launch required a sender, so this session ended at setup.
The sample and connected-account conditions differ across StackVouch reports. These observations support specific preparation steps, not an accuracy, performance or safety ranking.
Account conditions
We selected OutFlo to extend the LinkedIn outreach setup checklist used in our earlier reports.
The authenticated workspace started with zero campaigns and zero connected LinkedIn accounts. The account displayed eight days remaining and an expiry of November 2. We did not connect LinkedIn or a mailbox. The saved evidence does not confirm the signup date; we do not infer it from a rounded countdown. The public pricing FAQ describes the standard trial as eight days with Growth features for up to three connected accounts; the account’s own plan label was Free Trial.
We used one supplied profile, Jimmy’s own, and one clearly named campaign: StackVouch OutFlo Setup 2026-10-26 - DO NOT LAUNCH. We did not search for other people or request new contact data.

Operations and results
| Operation | Observation | What this establishes |
|---|---|---|
| Create a campaign | One named draft; no sender | Draft creation before connection |
| Use native step navigation | Sequence, leads and review accessible while Next remained disabled | Preparation accessible; sender checks still apply |
| Save a Classic follow-up | Native first-name token and two-day delay survived reload | Configuration persistence |
| Save native fallback | Use a fallback value set to there, retained on final reopen | Stored setting; runtime replacement untested |
| Import one CSV | One new lead, zero rejected | Input handling for three recognized columns |
| Reimport identical file | Zero new, one unchanged duplicate, zero recipients added | One exact repeat in the same campaign |
| Export and inspect file | One row, three columns, all supplied values preserved | Bounded data handoff |
| Open Preview | Imported lead available; no sender available | Sender required for this preview |
| Inspect Review & Launch | Missing-sender warning; confirmation and action disabled | Validation before launch |
| Inspect final state | One Draft, one lead, no account assigned | No campaign execution |
Saved message and fallback
We inserted First Name using OutFlo’s native picker. The saved message was:
Hi {linkedin_firstName}, this is an unsent StackVouch OutFlo setup-test draft.
The follow-up retained two days after connection acceptance with no reply. The displayed minimum was three hours. We verified the stored delay, not timer execution or stop-on-reply behavior. Classic remained selected and the AI Outreach Agent switch remained off.

The token’s fallback dialog offered a replacement value, a blank value or skipping the lead. We selected a replacement of there. After confirming the outer Save draft completed, a real reload and later navigation retained that choice. An earlier return to the default did not recur under that sequence; its cause remains unknown and it is not a reproducible defect finding.

CSV import, exact repeat and export
The input had one data row with LinkedIn URL, First Name and Last Name. The import accepted those headers without a mapping screen. Completion showed one submitted row, one unique valid lead, one new lead and zero rejected rows.

Uploading the identical file again into the same campaign reported zero new leads, zero merged rows, one unchanged duplicate, zero rejected rows and zero recipients added. Reload still showed one row. We did not test changed values, fuzzy matching, URL variants or duplicates across campaigns and workspaces.

Jimmy downloaded and inspected the export. It contained one data row and the same three unique headers, totaling 95 bytes. All three values matched the input exactly. It added no email, phone, company or other contact fields. This verifies preservation of supplied input, not profile matching, enrichment, coverage or accuracy. The raw CSV stays private.
Preview and launch prerequisites
After import, Preview listed the supplied lead but showed no accounts and asked for an account first. We did not use Configure LinkedIn data, request enrichment or enter simulated profile data. No personalized preview result was obtained.

Review & Launch displayed the schedule and a missing-sender warning. The displayed weekday schedule had weekends unchecked. It was inspected without changing or executing the schedule. The confirmation and launch action were disabled.

The final list showed Draft, a lead display of 0/1 and no assigned account. We did not launch the campaign.

Trial credits and dated pricing
Billing showed zero AI Credits and zero AI Preview Credits, with no credit transactions. Its explanatory text says each connected account receives 500 AI Credits and 50 AI Preview Credits once, without refreshing on renewal or reconnection. That is the displayed policy; eligibility, grants and usage charges were not exercised. A successful CSV export and an empty AI ledger do not establish a universal free-export entitlement.

We checked official pricing and the account Billing screen on October 26. Growth was set to one account, Booster to 25 accounts with zero extras. Both screens showed the same amounts below. Currency was displayed as $; currency code, tax and checkout were not verified.
| Plan/configuration | Monthly | Quarterly: monthly display / full cycle | Yearly: monthly display / full cycle |
|---|---|---|---|
| Growth, one account | $49/month | $42/month / $126 every three months | $37/month / $444 yearly |
| Booster, 25 accounts | $699/month | $595/month / $1,785 every three months | $525/month / $6,300 yearly |
| Scale | $2,199/month | $1,870/month / $5,610 every three months | $1,650/month / $19,800 yearly |
Full-cycle amounts were explicitly displayed and agree with multiplication by three or twelve. They are not tested invoices. The official pricing page, checked October 26, 2026, says keep this rate while your subscription stays active
. Its cancellation FAQ says returning after cancellation uses the then-current price. These are advertised rate-retention terms; checkout and exceptions were not tested. We changed only its price calculator from one to two accounts ($98/month) and back; no sender or subscription was added.


The account’s Booster card priced an additional five-account block at $125/month, $318.75/quarter or $1,125/year. We did not purchase an extra block. Scale’s Unlimited wording is qualified by the official FAQ: up to 300 LinkedIn accounts under fair use, with support contact needed above that. We did not test capacity or limits enforcement.


Buying implications
OutFlo let us prepare a Classic draft, preserve a native fallback setting, handle one exact duplicate and export supplied input before connecting a sender. Those are useful checks for preparing a campaign, with explicit limits on what they establish.
Buyers still need to validate sender connection, actual personalization, reply stopping and inbox operations under their intended configuration. Pricing depends on account count, billing commitment and fair-use terms. We observed an empty Unibox only; client separation, permissions, reply ownership and offboarding remain untested.
Risks and limits
LinkedIn’s automated-activity guidance, checked October 26, says it does not allow third-party software that scrapes or automates activity on its website. OutFlo’s activity controls and protection descriptions do not establish LinkedIn approval or guarantee account outcomes. This disconnected setup test measured neither account safety nor enforcement risk.
What we did not test
Sender authentication or synchronization; messages, invitations or profile visits; send-time fallback and preview substitution; wait execution, acceptance and reply branches; Smart sequences, AI agents or enrichment; malformed CSV, changed duplicate values or bulk import; CRM/API/MCP; multi-user permissions, isolation, assignment or offboarding; paid checkout, tax, cancellation, renewal, trial expiry or large-account capacity. No accuracy ranking or head-to-head execution comparison was performed.
The sample CSV template was not inspected. The actual campaign export was separately inspected and verified.
Re-test and correction history
- October 26, 2026: first bounded setup session; one self-profile, one exact reimport, one inspected export, saved message/delay/fallback, sender prerequisites and dated pricing. Initial fallback anomaly did not recur after confirmed outer save; retained as uncertainty rather than a product defect.
Sources
- OutFlo pricing and trial/fair-use FAQ, checked October 26, 2026 with Monthly, Quarterly and Yearly selected.
- Authenticated OutFlo campaign editor, Campaigns, Accounts, Unibox and Billing, observed October 26, 2026. Selected screenshots accompany this report; these are account-specific observations.
- LinkedIn automated activity guidance, checked October 26, 2026.
