Skip to content
LongFi Solutions

Follow-Up For Alberto And Daniel

Questions on the DR&AV proposal

Thank you for sharing the proposal. Before LongFi can evaluate next steps, we need to clarify the operating model, revenue-share structure, Valley coordination, and 30 to 60-day success metrics.

Revenue-share clarity Content scope Valley coordination Pilot metrics
Context

We want to understand the proposal in operational terms.

The proposal combines content, LinkedIn outreach, lead qualification, reporting, and referral economics. To evaluate it properly, LongFi needs to separate the retainer scope from referral compensation and define how the work would fit with our existing outreach process.

Scope

Content and outreach

We need to understand exactly what is produced each month, who produces it, and what LongFi reviews before anything is published or sent.

Workflow

Valley coordination

LongFi already uses Valley for LinkedIn outreach, so any new LinkedIn workflow needs a clear role, ownership model, and handoff process.

Economics

Revenue-share boundaries

The 30% share needs clear attribution and must account for other participants who may also be part of the economics.

Valley

How would your LinkedIn AI Agent fit with Valley?

Valley is currently part of LongFi's LinkedIn outreach workflow. We want to avoid duplicate prospecting, unclear attribution, inconsistent messaging, or account-risk issues.

Possible support role
  • Improve Valley campaign targeting and prospect segmentation.
  • Create content that warms prospects before Valley outreach.
  • Help write and test better connection, follow-up, and objection-response copy.
  • Use reply data to refine outreach angles and reporting.
Items to prevent
  • Two systems contacting the same prospect without coordination.
  • Revenue-share claims without clear attribution.
  • Messages sent from Jose's profile without LongFi review.
  • Automation that creates LinkedIn account risk or brand inconsistency.
Clarifications

Questions for Alberto and Daniel

These questions are intended to help both sides define the engagement clearly before any decision is made.

1. Revenue share and attribution

  1. Is the 30% based on gross carrier revenue or net LongFi revenue?
  2. Does your 30% include any venue, portfolio owner, MSP, or connector share, or would it stack on top of those economics?
  3. What specifically counts as a client you bring through content, LinkedIn, email, or direct introduction?

2. Content creation and review

  1. Of the 12 to 18 monthly pieces, how many are videos, written posts, case studies, and sales assets?
  2. Who creates the strategy, scripts, captions, edits, and final approvals?
  3. How much of the content is AI-generated versus human-produced or human-reviewed?

3. Outreach, Valley, and pipeline

  1. Would your LinkedIn AI Agent replace Valley, plug into Valley, or support Valley with targeting, copy, and optimization?
  2. What prospect segments, titles, and problems would you lead with for outreach?
  3. How many LinkedIn connection requests, messages, emails, and follow-ups would you send per week?
  4. What safeguards prevent account restrictions, duplicate outreach, or low-quality automated messages?

4. Pilot, proof, and ownership

  1. What exactly will be live by day 30?
  2. What would count as a successful 60-day proof of concept?
  3. Who owns the content, lead lists, AI workflows, prompts, dashboards, and campaign data if the engagement ends?
Decision criteria

What LongFi needs to clarify before next steps.

The key items are practical: scope, approval rights, attribution rules, Valley integration, and economics. Once those are defined, LongFi can determine whether the right structure is content support, outreach optimization, referral partnership, or a narrower pilot.

Commercial structure

Separate the retainer from referral economics.

The monthly retainer should be tied to deliverables, workflow, and reporting. Referral compensation should be separately defined, attributable, and compatible with LongFi's partner obligations.

Operating model

Define review, ownership, and handoff.

Before launch, both teams should know who approves content, who manages outreach, how Valley is handled, when Jose is involved, and what data LongFi receives each month.

Loading form...

Loading form...