Key takeaways
Best fit
Teams preparing coordinated LinkedIn and Email steps around named sending identities.
Core strength
LinkedIn and email sequences
Main tradeoff
Cost scales per sending identity and billing commitment; extra credits and add-ons can increase the bill.
Paid pricing
€60/month per sending identity on Monthly billing; €50 monthly equivalent billed annually (Basic, November 6, 2026)
Hands-on testing
Trial · one identity · Setup test completed
October 23, 2026: Jimmy’s self-service Trial, one sending identity and his own real LinkedIn account, connected that day before the recorded setup operations; no automation ran before or after connection. One supplied self-profile CSV, one unlaunched LinkedIn-to-Email template, two saved drafts and two mock previews; downloaded one-row, 43-column CSV inspected. Email remained disconnected. No launch, requested enrichment, CRM transfer or purchase.
| Test observation | Buying implication |
|---|---|
| Two messages and subject retained after reload and navigation | Draft persistence verified; timed execution untested |
| One supplied CSV record imported; completion said 1 lead updated | Input staging/upsert, not contact discovery |
| Two mock previews rendered Jimmy | One 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 enriched | Trial export worked for this account; no usable contact detail retrieved |
| Trial custom-workflow prompt said PRO; pricing FAQ said Ultimate | Setup test complete; paid-tier entitlement remains unresolved |

What we did not test
- Channel authentication/connection, launch, actual profile visits, invitations, messages or Email delivery.
- Timed branches, acceptance/reply execution, missing-name fallback, reply stopping, inbox ownership or team permissions.
- Custom workflow, paid-tier enforcement, CRM/API/webhook transfer and recovery.
- Duplicate reimport, malformed CSV, lookup, requested enrichment, independent identity/contact accuracy or coverage.
- Paid checkout, tax, renewal, cancellation, complete credit ledger, long-term account safety or head-to-head performance.
These are limits of this assessment, not findings that the product cannot perform the tasks.
Pricing
Public EUR pricing rechecked November 6, 2026 for one sending identity: Basic €60, Pro €120 and Ultimate €180 per month on Monthly billing; Annual monthly equivalents €50/€100/€150. The corresponding twelve-month calculations are €600/€1,200/€1,800, not tested invoices. An identity is a sender, not every invited teammate. More identities can change the rate through volume discounts; obtain the selected total including add-ons and retained mailbox, LinkedIn and CRM costs. No paid checkout or entitlement test was performed.
| Plan | Monthly / identity | Annual monthly equivalent, one identity | Credits / identity / month | Free team members |
|---|---|---|---|---|
| Basic | €60 | €50 | 1,250 | 3 |
| Pro | €120 | €100 | 2,000 | 25 |
| Ultimate | €180 | €150 | 5,000 | Unlimited |
View November 6 public pricing screenshots


These are one-identity public EUR configurations. Invited collaborators and sending identities are separate: the current FAQ lists 3 free team members on Basic, 25 on Pro and unlimited on Ultimate. More identities may qualify for a different rate. Confirm the selected annual commitment, extras and retained services; no invoice or team-permission test was performed.
Current plan descriptions and historical limits
November 6 pricing comparison: custom sequences and the multichannel inbox are listed on Pro/Ultimate. CRM sync is included on Ultimate and a lower-tier add-on; API is included on Pro/Ultimate and a Basic add-on. The trial FAQ describes ready-to-use templates and says to ask support for custom sequences. This later documentation is clearer than the October conflict, but it does not retest paid access.
October 23 trial and October 25 document history
Jimmy opened the self-service trial and connected his own LinkedIn on October 23; no automation ran. Billing showed one identity and a November 6 end date. The unlaunched template required Email connection. The October pricing/FAQ descriptions conflicted about the custom builder and finite versus unlimited enrichment; those are historical observations. The current page supplies a finite credit schedule. No later human support reply or origin of the exported gender field was verified.



Official current pricing and feature comparison. Monthly and annual displays, volume discounts and add-ons should be checked for the intended identity count. Original product-test date: October 23, 2026.
How La Growth Machine credits change the real cost
November 6 public description: Basic/Pro/Ultimate include 1,250/2,000/5,000 credits per identity/month. A LinkedIn profile costs 1 credit, an email 5 and a phone 20, charged when data is found; top-ups are €0.01/credit. The displayed equivalents are 250/400/1,000 emails, not the same number of credits or a verified allowance increase.
Continue reading
The older unlimited wording is historical documentary context, not the current allowance. Our October 23 CSV export did not request enrichment or audit the usage ledger; current export charging, rollover, pooling and unsuccessful-request rules remain untested.
Is there a useful free evaluation path?
Jimmy opened the self-service fourteen-day trial on October 23, 2026. That day, Billing showed one of one identity slots used and a November 6 end date. The recorded operations did not change billing, add a card or test cancellation. Custom workflows showed an upgrade prompt; template setup did not establish paid-tier entitlements.
The buying decision
Use the observed preparation checks below alongside the operating cases still requiring a demonstration. A saved template is not a completed multichannel campaign.
| Task | What to validate | What we tested |
|---|---|---|
| Template and persistence | Reopen messages, subject, branch conditions and delays before launch. | Two drafts and subject persisted after reload and navigation. Default four-day branches, Has Pro Email and 30-minute Wait retained; no timed execution. |
| Input and export | Check header mapping, retained rows, duplicates and the exact exported fields. | Enabled Remove column header; one supplied record staged/upserted. Downloaded CSV: one row, 43 columns, Not enriched. No duplicate reimport. |
| Personalization | Check complete and missing fields in preview, then demonstrate send-time behavior. | Both mock previews rendered Hi Jimmy. Email addresses and surrounding conversations were placeholders. Missing-name fallback and delivery untested. |
| Channels and ownership | Demonstrate authorized connections, reply stopping, handoff and CRM recovery at the quoted tier. | Selected identity required Email connection to run. No connection, launch, live reply, CRM transfer or team-permission test. |
| Custom workflow access | Obtain the exact paid-tier entitlement in writing. | October 23 trial labelled Custom Workflow PRO; no custom workflow or paid-tier enforcement test. November 6 public comparison lists Pro/Ultimate; this later documentary check is not product execution. |
Risks and how to validate
Official descriptions explain a coordinated prospecting workflow; they do not establish improved conversion, record accuracy or long-term account safety. LinkedIn prohibits unauthorized automation. This review does not turn vendor protection language into permission or an independent safety finding.
One supplied record for Jimmy’s own profile was staged; completion said 1 lead updated. Export preserved the supplied names and URL; email, phone, role, company and location were empty and status was Not enriched. The populated gender field was unverified and is not counted as useful enrichment. Has profile 100% reflected the supplied URL, not a coverage rate. 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.
How to validate La Growth Machine on your own ICP
List required sending identities, supervising members, channels, workflow builder and CRM direction. Attach the quoted feature list and complete annual commitment. Demonstrate reply before the next step, missing personalization, duplicate records, an absent owner, a disconnected identity and failed CRM update. These are proposed validation tasks, not results of our setup test.
Integrations
November 6 pricing comparison places the multichannel inbox, custom sequence builder and API on Pro/Ultimate; API is also listed as a Basic add-on. HubSpot/Pipedrive CRM sync is included on Ultimate and available as an add-on on Basic/Pro; Workspaces are add-ons. This is current pricing-page evidence. The October 25 integrations/inbox wording and October 23 account label were earlier observations, not tests of today’s permissions. Confirm the quoted configuration, fields, sync direction, overwrite and recovery behavior; no CRM/API connection was tested.
Customer support
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.
Continue reading
It confirmed that someone would review the questions. No human answer is documented in that October 25 exchange; no article was submitted for approval or account change requested. November 6 public pricing research supplies a current credit schedule and Pro/Ultimate custom-sequence listing; it is not a human support answer and does not identify the exported gender field’s origin. No later support reply was checked in this update.
Pros and cons
Pros
- Two native first-name drafts and the Email subject survived reload and navigation.
- A supplied CSV record could be staged and used in both recipient previews before launch.
- Trial export produced a checked one-row CSV preserving the supplied fields.
Cons
- Cost scales per sending identity and billing commitment; extra credits and add-ons can increase the bill.
Methodology
- 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.
- One supplied self-profile CSV, one unlaunched template and two unsent messages; persistence, previews and one-row/43-column export checked on October 23, 2026. Missing-name fallback and duplicate reimport were not tested.
- No launch, requested enrichment, Email connection, CRM transfer, paid checkout or account-safety result. No product-wide performance score or representative user consensus.
- EUR Monthly and Annual prices were observed October 23. The pricing/integration/inbox wording, DPA and Gender-API documentation were checked October 25; that documentary follow-up does not change the product-test date.
- October 25 correction: clarified account history and scope, separated product cost from documentation conflicts, removed the ambiguous counter claim and recorded factual support contact. No additional product execution test.
- November 6, 2026: rechecked public pricing, identity/member definitions, credits and plan comparison. Current documentary terms replace the earlier unresolved wording in buying advice; original October observations, field-origin question and product-test date remain unchanged. No new product execution test.
Final verdict
La Growth Machine completed our bounded setup checks: one supplied record, two retained previewed messages and an inspected trial CSV export. It is a candidate for preparing coordinated outreach, subject to identity-based cost and the required paid features. Current public descriptions place custom sequences in Pro/Ultimate, but no paid-tier access, launch, enrichment, delivery, reply ownership or account-safety outcome was tested. Demonstrate those operating cases before buying.
Best for
- Teams preparing coordinated LinkedIn and Email steps around named sending identities.
- Buyers who want to inspect saved drafts and supplied-record previews before connecting channels.
- Operators prepared to confirm tier access and demonstrate reply ownership before rollout.
Not ideal for
- Organizations whose rules exclude unauthorized LinkedIn automation.
- Teams whose existing sender and inbox already cover their workflow without added coordination.
- Buyers who need an unambiguous public entitlement matrix before evaluating.
Visit La Growth Machine Check official pricing
We may earn a commission if you buy through links on this page. How our links work.
If LinkedIn-only preparation is enough for the initial workflow, compare La Growth Machine with Waalaxy →
Continue your evaluation
Compare the closest options, then explore costs and switching trade-offs.
- Waalaxy vs La Growth Machine 2026: Pricing, Channels & Workflow DepthCompare Waalaxy's per-user tiers with La Growth Machine's identity-based multichannel workflow, enrichment and plan-specific controls.
- Best LinkedIn Outreach Tools for Agencies in 2026: Client Operations ComparedChoose agency outreach software around client separation, sender costs, reply ownership and offboarding—not just campaign volume.
- Best LinkedIn Automation Tools for Small B2B Teams in 2026Choose a LinkedIn tool around account ownership, required channels and handoff. Five dated setup reports show preparation tasks;…
- 4 Waalaxy Alternatives for Branching, Shared Senders and Channel Preparation (2026)Compare alternatives only where Waalaxy misses a required task. Separate supplied-list evidence, branch preparation, sender coordination and the…
Evidence
Sources & verification
Key product facts on this page were checked against the sources below. Pricing, plan names and feature entitlements can change.
- 1lagrowthmachine.com — Pricing (opens in a new tab)
- 2lagrowthmachine.com — Multichannel Inbox (opens in a new tab)
- 3lagrowthmachine.com — Integrations (opens in a new tab)
- 4lagrowthmachine.com — Dpa La Growth Machine 20250721 (opens in a new tab)
- 5gender-api.com — Query By First Name (opens in a new tab)
- 6linkedin.com — A1341387 (opens in a new tab)
Frequently asked questions
Did StackVouch test La Growth Machine hands-on?
Yes, Setup test on October 23, 2026: Jimmy’s real LinkedIn was already connected; one supplied profile, two saved mock previews and one checked 43-column CSV export. No campaign was launched.
Did this test retrieve contact details?
No. Exported email, phone and company fields were blank and status was Not enriched. The unverified gender field does not establish useful enrichment, accuracy or coverage.
Does CSV export use credits?
Export completed in this trial. We did not audit the charging rules or itemized ledger and cannot make a universal zero-credit claim.
Which plan includes custom workflows?
The public comparison checked November 6 lists the custom sequence builder on Pro/Ultimate. The trial FAQ says templates are included and custom sequences require a support request. This updates the earlier document conflict; paid-tier enforcement was not retested, and no new human support answer is documented.
Is an invited member a paid sending identity?
No: the November 6 public FAQ distinguishes paying senders from free collaborating team members, with limits of 3 on Basic, 25 on Pro and unlimited on Ultimate. Only identities launch campaigns. We did not test team permissions or account billing.
Did the previews verify delivery or fallback?
No. They rendered one complete supplied first name in mock interfaces. Missing-name fallback, duplicate reimport and live sending were not tested.


