Setup test

La Growth Machine Setup Test: One CSV Record, Two Previews and Export

Setup test completed · Trial · one identity

Published 2026-10-25 · Report updated 2026-10-26 · Tested by Jimmy Dwyer

Jimmy Dwyer · Publisher and responsible editor
Jimmy runs StackVouch and is responsible for this article's conclusions, disclosures and corrections. About Jimmy · LinkedIn

We may earn a commission if you buy through links on this page. Affiliate disclosure.

No paid sponsorship. La Growth Machine did not review this article before publication.

Read the La Growth Machine buying review →

The result at a glance

Observed resultBuying implication
Two messages and subject retained after reload and navigationDraft persistence verified; timed execution untested
One supplied CSV record imported; completion said 1 lead updatedInput staging/upsert, not contact discovery
Two mock previews rendered JimmyOne complete record in two mock previews; missing-name fallback and duplicate reimport were not tested. Scope differs from our other setup reports.
Downloaded CSV: one row, 43 columns; Not enrichedTrial export worked for this account; no usable contact detail retrieved
Trial custom-workflow prompt said PRO; pricing FAQ said UltimateSetup test complete; paid-tier entitlement remains unresolved

The findings apply only to the dated account workflow and stated conditions. See the full limits section before generalizing them.

This test checked two recipient previews. Missing-name fallback and duplicate reimport were not tested; the tasks differ from our other setup reports and do not form a head-to-head comparison.

On this page

Purpose and test conditions

On October 23, 2026, we prepared a LinkedIn-to-Email campaign in Jimmy’s self-service La Growth Machine trial without launching it. Billing showed one of one identity slots used, Trial, and a November 6, 2026 trial end. Campaigns displayed 14 days left. The recorded draft operations did not connect or disconnect a channel.

Our sample was one supplied record for Jimmy’s own profile, one campaign configuration and two unsent messages. We tested input handling, saved content and recipient-specific previews. We did not test live outreach or compare data accuracy.

Account setup and evidence boundary

Jimmy opened the self-service trial on October 23, 2026 and connected his own real LinkedIn account that day; no automation ran before or after connection. The recorded setup operations began after authentication, so the evidence log does not cover signup or the initial LinkedIn connection. Unlike the Dripify, Waalaxy and HeyReach tests, this test started with LinkedIn already connected. Email remained disconnected.

Operations and results

Operation Observed result Buying implication
Start from a template Created LinkedIn > Email – 1 Follow-up and saved a clearly named test configuration A templated campaign could be prepared without connecting Email
Inspect the flow Template retained four-day connection branches, a Has Pro Email condition and a 30-minute Wait Stored logic is inspectable; its execution was not measured
Save content Two native firstname message drafts plus an Email subject survived reload and navigation away/back Preparation and persistence verified
Preview before import Required a nonempty campaign audience Preview needs at least one audience record
Map one CSV record All three columns matched; we enabled Remove column header before continuing Check header treatment before counting imported people
Complete import Named audience contained one record; completion showed 1/1 and 1 lead updated Input staging/upsert verified; no contact discovery implied
Preview the supplied record LinkedIn and Gmail-style Email previews rendered Hi Jimmy; Email subject retained First-name rendering verified for this one complete record; no sending result
Export File Ready notice followed by a downloaded, checked one-row CSV with 43 columns Trial data handoff verified for this account and sample
Inspect enrichment state Enriched Leads 0; exported status Not enriched; email/phone/company fields blank This was not an enrichment or accuracy test
Inspect access prerequisites Custom Workflow PRO upgrade prompt; Email connection needed to run the selected template Trial access and paid-plan entitlement must be evaluated separately

The saved LinkedIn body was:

Hi {{firstname}}, this is an unsent StackVouch LGM setup-test draft.

The Email subject and body were:

StackVouch unsent LGM setup test

Hi {{firstname}}, this is an unsent email branch for the StackVouch LGM setup test.

The four-day conditions and 30-minute Wait came from the template and were retained after reload. We did not change the flow topology, run the timers or observe an acceptance/reply branch. The final campaign remained unlaunched. Campaigns described it as drafted and still offered a launch action; that action was not used.

Saved LinkedIn draft with the native firstname token
October 23, 2026: reopened unsent LinkedIn draft retained the native firstname token after reload

One supplied record and the export

The input had three columns—firstname, lastname, linkedinUrl—and one data row for Jimmy. The mapping dialog reported zero unmatched columns. Its Remove column header control was initially off. We enabled it and checked that only the data row remained before importing.

The completion message reported one of one and one lead updated. That wording does not establish a newly discovered person or an independently matched profile. After navigation and reload, the same one-record audience remained associated with the campaign.

The downloaded UTF-8 CSV contained one row and 43 columns, totaling 877 bytes. It preserved the supplied names and LinkedIn URL. Professional/personal email, phone, role, company and location were empty; the enrichment status was Not enriched. System metadata and an unverified gender field were also populated. We did not establish that field’s origin or correctness and do not count it as useful enrichment.

The audience UI displayed Email 0%, Phone 0% and zero enriched leads. Its Has profile 100% indicator reflected a supplied URL in this one-record audience; it is not a coverage or accuracy rate. No lookup, enrichment or credit purchase was requested.

One input record, with no email, phone or enriched leads
October 23, 2026: one supplied record, Email 0%, Phone 0%, zero enriched leads; supplied profile URL is not a coverage result

Gender field: documentary context, not a verified result

Documentary follow-up, October 25, 2026: LGM’s published DPA dated July 21, 2025 lists Genderapi for gender enrichment on client instructions (Appendix B, page 13). Gender-API’s documentation describes estimates from a first name, optionally a country, with a probability score. This documents a possible service capability, not the origin or correctness of our exported field. LGM has been asked which step/provider populated it and whether it can be disabled, omitted, corrected or deleted. Human confirmation is pending; no value from the record is published.

Sources: LGM DPA, Appendix B, page 13; Gender-API first-name endpoint documentation. These were checked October 25, separately from the October 23 product test.

What the previews establish

Before import, Preview requested a nonempty audience. After the single record was attached, both branches rendered the supplied first name as Jimmy. The Email preview also displayed our saved subject.

These are editor previews. The Gmail-style screen used placeholder sender and recipient addresses, not discovered email addresses or a connected mailbox. Example conversations, job titles and timestamps in the preview frame are mock interface content. They do not show actual delivery, received messages or verified profile details. Missing-name fallback behavior was not tested.

LinkedIn mock preview rendered the supplied first name
October 23, 2026: mock LinkedIn preview rendered Jimmy from the one supplied record; no message sent
Email mock preview retained the subject and rendered the supplied first name
October 23, 2026: mock Email preview rendered Jimmy and the saved subject; placeholder addresses are not discovered email

Trial, pricing and access limits

Billing showed one Trial identity and a November 6, 2026 end date. No card, subscription or billing setting was changed.

Trial identity and dated end-of-trial display
October 23, 2026: one Trial identity and November 6 trial end; no billing action

The official pricing page was checked with EUR and both billing selectors on October 23. Monthly Basic/Pro/Ultimate displayed €60/€120/€180 per identity. Annual displayed €50/€100/€150 as monthly equivalents, implying €600/€1,200/€1,800 for twelve months by arithmetic; these are not tested invoices. The pricing FAQ distinguishes an invited member, who can help manage work under an identity, from a licensed identity used to launch campaigns under its own connected accounts.

Monthly selected: EUR 60, 120 and 180 per identity
October 23, 2026: EUR Monthly selected, Basic 60, Pro 120, Ultimate 180 per identity/month
Annual selected: EUR 50, 100 and 150 monthly displays per identity
October 23, 2026: EUR Annual selected, monthly equivalents 50, 100 and 150 per identity; no invoice verified

The same pricing FAQ excludes custom sequences from the standard trial, consistent with our upgrade prompt. However, it places the builder at Ultimate while the pricing card and account label use Pro. The paid-tier conflict remains unresolved. The account also labelled CRM Ultimate; we did not connect a CRM or test entitlement enforcement. Trial limits are not findings that the product lacks those capabilities.

Selected template required an Email connection before running
October 23, 2026: the selected template required an Email connection to run; no connection or launch attempted

Documentation conflict, checked October 25, 2026: the pricing cards list Basic 250, Pro 400 and Ultimate 1,000 enriched leads per month, while the pricing FAQ describes enrichment as unlimited. The scope of unlimited operations and the allowance-consuming fields remains unconfirmed. See the official pricing cards and FAQ and the dated Monthly/Annual captures above.

Buying implications

There is now first-hand support for importing one known record, preserving a templated multichannel draft, rendering a supplied first name in two previews and exporting the record during this trial. These checks are relevant to teams preparing a coordinated LinkedIn-and-Email workflow before launch.

The purchase still depends on the required paid-tier features, complete identity cost and acceptable platform-policy dependency. The Identity step required an Email connection for this template. An onboarding banner later described the campaign as drafted and ready for launch; it was not a live operational readiness test. Demonstrate the intended channel connections, reply stopping and ownership before treating saved setup as an executed process.

What we did not test

No mailbox/CRM connection, sending, profile visit, invitation, timed execution, acceptance/reply branch, withdrawal, inbox handoff or team permissions. No custom workflow, missing-name fallback, duplicate reimport, malformed CSV, enrichment, independent identity/contact verification, paid checkout, tax, billing changes, cancellation, long-term account safety or head-to-head performance test.

Only the named campaign, two unsent message drafts and one self-profile audience were prepared. Auto-enrichment remained Off; Exit on reply was a displayed default, not an observed live result. No support message was sent during the October 23 setup test. The separately dated October 25 factual inquiry is recorded below.

Risks and limits

LinkedIn prohibits unauthorized software that automates activity on its platform. LGM’s availability and our setup observations do not establish LinkedIn permission or account safety. This test ran no automation and measured no long-term restriction risk. Check your organization’s rules and LinkedIn’s policy on prohibited software and extensions before deciding whether to use automation.

Re-test and correction history

  • October 23, 2026: Original one-record setup test: two saved drafts, two mock previews and one checked CSV export; campaign unlaunched.
  • October 25, 2026: Added the signup/LinkedIn account history, clarified the different starting conditions and untested fallback/duplicate cases, consolidated independence disclosure and removed the ambiguous counter claim. Added dated documentary sources and support follow-up. Editorial/documentary revision; no new campaign, sending or enrichment test.

October 25, 2026: Jimmy contacted LGM’s in-app support about the custom-workflow tier, 250/400/1,000-versus-unlimited enrichment wording, and the exported gender field. Fin, the AI agent, repeated both Pro custom-sequence and Ultimate builder descriptions, did not reconcile the allowance, and did not establish the field’s origin. It confirmed that someone would review the questions. No human answer has been received; no article was submitted for approval or account change requested.