Valley automates the research and messaging. OutFlo gives GTM teams control over how the campaign runs.

01 · Customer problem

AI writing can still sound artificial

• Many customers reported that Valley's AI writing sounded very AI.
• Repeated training did not make the messages follow the preferred style.
• The platform kept reverting to its own writing style, while the reported results were nonexistent and the product felt expensive.

Valley customer feedback on personalization

“Maybe the personalization is one of the reasons. I mean, I didn't like the personalization. I mean, I want more personalization.”

Personalization was a buying requirement, not a cosmetic feature. OutFlo keeps AI assistance inside a workflow the GTM team can inspect, adjust, and control.

02 · Customer problem

AI does not always follow instructions accurately

• Customers have tried different training approaches, but Valley continued producing messages in its own style.
• Valley users have said the AI messaging became inaccurate and did not follow the instructions provided.
• The issue is not whether Valley can generate a message. It is whether the team can trust the message to follow the campaign brief every time.

Customer who moved from Valley to OutFlo

“It's not accurate, and it's messing up. It's just not following the exact instruction that we give.”

03 · Customer problem

No sequences to build is useful until the team needs to inspect the decision

• Valley supports follow up sequences, autopilot, pause on reply, manual approval, and automatic selection between connection requests and InMails.
• Valley shows a cross channel path from connection request to follow up, InMail, and email.
• Valley's sequence model is presented as basic and does not show a freely editable visual decision graph or a complete condition library.

Team evaluating newer automation

“Using their automation part of it. So I said, screw it. You know? It was wasting more time using it like that than it was us manually doing it ourselves.”

04 · Customer problem

A unified inbox is stronger when it is connected to the operating system

• Valley provides a unified inbox across connected accounts with sender, campaign, response, ICP, date, and tag filters.
• It shows conversation history, prospect research, ICP score, reply categories, and drafted responses.
• The inbox still needs to connect to campaign state, sequence steps, account status, and performance diagnosis for agency operations.

05 · Customer problem

Account safety needs visible controls and a recovery path

• Valley emphasizes pacing, human like activity, dedicated IPs, safety rails, and stopping at LinkedIn limits.
• Valley describes Chrome extension based session connection, while its safety workflow is also described as cloud side execution.
• The product claims a strong safety record, but an agency still needs visible account state and a recovery workflow when LinkedIn interrupts an account.

06 · Customer problem

Personal outreach needs more than text generated in the right voice

• Valley focuses on research backed messages, voice matching, connection requests, follow ups, InMails, and drafted replies.
• Valley does not show a native voice note campaign action in its product and campaign workflow.
• Voice notes can make a campaign feel more personal when the sender wants to move beyond automated text.

07 · Customer problem

Cost and value become a problem when the output does not justify the seat

• Customers described Valley as expensive.
• Customers also said the results were nonexistent and that lead usage across users was not flexible.
• The wider customer feedback also identified cost and value as a recurring concern.

08 · Customer problem

The interface can become difficult during setup

• Customers have reported lag during heavy onboarding.
• Other customers have said some steps were difficult to use.
• The product can be easy to start and still become harder to operate when the team is managing more accounts, campaigns, and approvals.

09 · Customer problem

MCP should understand the operating workflow, not only produce an answer

• Valley includes API, Clay integration, and MCP as integration capabilities.
• Valley describes lead research, message generation, campaign questions, API access, and webhook workflows.
• The detailed operating tool surface is not shown for sequence inspection, inbox mutation, individual lead controls, or account recovery actions.

10 · Customer problem

Sender scale only matters when one campaign can use it

• Valley supports multiple LinkedIn accounts in one workspace, but each account is treated as a separate seat.
• The lower Everything plans show one connected LinkedIn account, while Scale is described as five to fifty seats.
• Valley does not clearly explain whether several sender accounts can be assigned to one campaign and rotated automatically.

11 · Customer problem

Lead filtering is incomplete when territory matters

• Customers specifically complained that Valley could not filter leads by location.
• Teams with regional, territory, or account based targeting can therefore receive leads that do not belong in the campaign.
• When the audience is wrong, deeper research and better copy do not recover the wasted outreach capacity.