Start with the campaign job and the correct plan

A useful first LinkedIn campaign has an audience, an action appropriate to the person's connection state and a named owner for replies. Decide those things before designing a long chain of follow-ups. The current Leadsforlinked catalogue places multi-step campaigns, inbox, reply tracking, Kanban and analytics on Starter at €29 monthly for one connected account. Diamond Pro at €79 adds AI sourcing, scoring and Responder. You do not need to choose Pro merely because a campaign has several steps.

The 100 free signup profiles, released in batches of 20 without a card, can help evaluate a source audience. They do not establish free access to the campaign workspace. A ready buyer with an existing audience can review the paid campaign plan directly. If the existing sender and inbox already meet the requirement, keep them: a new audience source and a new campaign tool are separate buying decisions. An accepted profile is not automatically ready for a connection request or a message.

Bring people you already selected into a campaign

If you already have the relevant people, begin with that audience. You do not need another extraction pack merely to choose the campaign workflow. Starter includes one connected LinkedIn account, campaigns, inbox, pipeline and analytics; Basic covers extraction and CSV, without those outreach features. Keep your existing source file so you can compare it with the receiving audience.

  1. Open the intended audience. In Audiences, open the collection you want to use. For an existing CSV, Add prospects → Import a CSV offers upload or pasted CSV data. The app documentation lists linkedin_url as required, first and last names as recommended, and fields such as company and headline as optional. Importing an address does not establish that missing fields will be enriched.
  2. Review the actual people and fields. Check the receiving rows, identities, company/role fit and existing conversations. A blank company value needs attention if company membership is part of your targeting. If you only have links buried in text, the local profile URL extractor can clean those addresses; it does not supply missing names or job information.
  3. Inspect the destination before confirming. Send to campaign opens a target-campaign selector. The reviewed interface offered both active and draft campaigns, with an active campaign selected initially. Select the intended destination by name and status. An active destination can already be running; choosing it deserves the same review as a launch.
  4. Decide whether this is a continuing source. The dialog's Wire continuously checkbox was checked initially. Its explanation says future additions to the audience, including imports, sourcing and AI Hunter, will also enter the campaign. Review that choice before the confirmation labelled Send; a one-time reviewed list and a continuing audience feed are different jobs.
  5. Check the campaign after the handoff. Inspect the receiving prospects, selected sender, sequence and working window. The dialog describes skipping people already in that campaign or active in another one, so do not assume every input row will enter. A draft campaign has a separate Start control. The inspected empty draft had neither prospects nor sequence steps and could not start; importing an audience alone does not establish readiness.

Interface reviewed on 18 October 2026 in a Diamond Pro account; the published campaign entry plan is Starter. Import, enrollment and sending were not executed during this interface review. Confirm your actual rows and campaign state; a CSV import, continuous feed and campaign launch are separate decisions.

The campaign page also has Import an audience, which lets you select an existing collection. Keep that receiving route separate from adding a new source or enabling future automatic enrollment. Once people are in the intended campaign, the connection and reply rules below determine which next action belongs in the sequence.

Build a follow-up for the relationship you already have

If you have already connected with the people you selected, the next job is to prepare a relevant message and handle its replies. Keep that audience and review each person's current relationship before adding an invitation step. People with pending invitations need a different path from confirmed connections. A successful import would not establish either state.

In the reviewed Campaigns builder, the available blocks included Send message, Connection accepted, Replied, No reply and Wait. An existing sequence showed a connection request, a connected condition, a message and later no-reply conditions before additional messages. This gives you concrete controls to inspect when translating your follow-up into a sequence; it is not a reason to copy that whole sequence for an audience that is already connected.

  1. Match the first action to the selected audience. For confirmed connections, review the message path rather than add a new invitation by default. Hold people whose connection state or existing conversation is unresolved. Check the selected sender and destination campaign before any enrollment.
  2. Give each message a separate purpose. Prepare the initial context and the information a later follow-up would add. The builder displayed first-name, company, headline and position variables. Compare those values with the actual receiving audience: where a required value is missing, rewrite the sentence or resolve the record before sending. A visible variable is not evidence that every profile supplies it.
  3. Inspect the condition before the next message. Review how Wait and No reply are configured in your account, including which branch leads to another action. A visible Replied block does not prove that a newly received reply cancels every already queued message. If stopping on reply is essential, resolve that behaviour before relying on the sequence.
  4. Separate preparation from activation. The reviewed builder exposed Save and the draft campaign had a separate Start control. Review the saved sequence, audience, working window and reply owner before activation. Sending an audience to an already active campaign is a different decision from preparing an empty draft.

These builder controls were inspected on 18 October 2026 in a Diamond Pro account. No workflow was saved or launched, and no condition, variable substitution or message delivery was functionally tested in that review. Starter's published campaign entitlement does not certify every control visible in that account.

Design the sequence around state

Begin with a small, explicit purpose. For example, a fictional consultancy wants to ask relevant peers whether one documented operational problem affects their work. The invitation has a reason for that person, the first eligible message adds context, and any later follow-up has a distinct purpose. A connection request is not the same action as a message to an existing connection. An ignored invitation does not become permission to use another message channel.

  1. Check the person's identity, selected sender and existing conversation.
  2. Choose the action compatible with the connection state.
  3. Specify the prerequisite for the next action, such as acceptance and no intervening reply.
  4. Define what pauses or exits the sequence, including a stop request and an existing active sequence.
  5. Name the person who takes over when a reply or ambiguity requires attention.

Timing belongs to this brief, alongside working hours and runner requirements. Choose it from the actual purpose and supported controls. This guide does not prescribe a universal number of steps, a guaranteed completion time or a safe daily send quota. More steps can create more queue decisions without creating a better reason to contact someone. Keep the first version understandable enough that the reply owner can explain every scheduled action.

Worked queue: preserve the observations before acting

The fictional Cedarline case has one authorized sender and eight planning observations. It uses an explicit teaching policy: scheduled pitching exits on a reply; a stop request excludes further pitching; an unresolved connection state or another active sequence holds the proposed action. These are the case's chosen rules. The exercise is not a recorded campaign run or proof of automatic stop behaviour in any product.

Ari is an existing connection with no reply and no competing sequence, so the proposed first contextual message fits the policy. Bo is not connected and has no pending request or reply, so an invitation can be considered. Cal's existing request is pending: sending a connection-only message is held. Drew replies before the queued follow-up and goes to the named human owner. Em asks to stop and is excluded. Fin is already in another active sequence; Gia's connection state is unknown. Both are held. Hale is an existing connection with a confirmed next action and no intervening reply.

The result retains all eight original observations: three eligible next actions, one reply handoff, three holds and one exclusion. A handoff is separate from an eligible scheduled action. A reply asking a question is not automatically positive intent; a decline is not a reason to keep pitching. When the audience is refreshed, preserve the old decision and compare new evidence rather than erase the previous reply or owner.

Fictional teaching observations; all originals remain in the downloadable exercise.
ObservationEvidenceDecision
Q01 · AriCurrent connection and no intervening reply; first contextual message is proposed.ELIGIBLE
The proposed action fits the stated connection prerequisite and reply policy.
Q02 · BoNo existing or pending request; invitation is the proposed action.ELIGIBLE
The proposed action fits the stated connection prerequisite and reply policy.
Q03 · CalPending request does not meet the connection-only message prerequisite.STATE_HOLD
The proposed action lacks a resolved compatible connection state.
Q04 · DrewQuestion arrived before the follow-up; Rowan owns the response.HANDOFF
Exit scheduled pitching and hand the reply to the named owner.
Q05 · EmExplicit request to stop pitching.STOP
Explicit stop request excludes pitching under this case policy.
Q06 · FinAlready active in another sequence; proposed action conflicts.SEQUENCE_HOLD
Resolve existing active sequence participation.
Q07 · GiaCurrent connection state is unresolved.STATE_HOLD
The proposed action lacks a resolved compatible connection state.
Q08 · HaleConfirmed next action and no intervening reply.ELIGIBLE
The proposed action fits the stated connection prerequisite and reply policy.

Make reply ownership visible

Decide who reviews the inbox, what information they need and when a scheduled action must be stopped or re-evaluated. Put the campaign name, sender, person identity and latest relevant message beside the next action. The owner should be able to see whether a colleague already responded, whether the person asked to stop and whether a pending invitation changed state. A pipeline stage by itself may not contain that conversation context.

Starter includes the inbox and pipeline. Pro includes AI Responder: the reviewed interface offers response libraries with tone, objective, product context and custom rules, plus a separate approval queue. Check the chosen reply mode before enabling automatic responses. A generated reply or a sentiment label does not establish consent, a meeting or purchasing authority. If AI assistance is part of your requirement, write down the permitted response scope and escalation owner. If it is not required, a simple campaign with human reply handling can be the appropriate paid job.

Use Inbox for the conversation and Pipeline for progress

The reviewed Inbox exposed All, Replies and AI pending filters. Use the reply view as a starting point for the named operator's review, then read the actual conversation before choosing an answer. Check whether the person is asking for information, declining, referring you elsewhere or requesting no further contact. The inspected Inbox was empty, so this review did not establish reply synchronization, filter accuracy or a completed response.

For human handling, decide the next response from the conversation and check any remaining scheduled follow-up before proceeding. Confirm how the current account lets you prevent an inappropriate next action; do not assume that opening a thread or changing a stage cancels it. If a reply needs specialist input, preserve the question and name the person responsible for answering it rather than generate another pitch.

The reviewed Pipeline displayed stages including Replied, Discussion and Converted, with a Customize stages control. Use stages to record progress under your team's definitions, while keeping the conversation as the basis for the next action. A reply alone does not establish a meeting or a sale. No card movement or automatic stage update was tested.

Compare the Leadsforlinked outreach platform and Starter plan if you want campaigns, replies and pipeline in one workspace. The product page separates that paid workflow from the free profile-CSV option.

For this one-account campaign and human-reply workflow, review Starter at €29 per month on monthly billing. The current catalogue includes campaigns, Inbox, Kanban and analytics; AI Responder belongs to Diamond Pro. Choose the actual billing period and review the current account offer before subscribing. A lead pack covers profiles and does not unlock these campaign features.

Confirm the controls your sequence requires

The published platform describes smart send delays. Check the controls available in the actual selected plan and current runner: connection prerequisites, reply checks, scheduling windows, duplicate participation, pause behaviour and return after interruption. Record any required weekend handling or invitation withdrawal separately. A general delay feature does not establish every timer or branch your brief needs. Leave unsupported settings unresolved rather than substitute a guessed number.

Runner requirements also matter. A browser-dependent workflow and a cloud executor have different operating conditions. Kanbox documents native campaign sequences and workspaces, while its pricing page describes cloud execution. For the tool you choose, resolve whether a browser must remain open, what happens during interruption and where queued actions resume. Fit those conditions to your working window before relying on unattended execution.

LinkedIn says invitation limits apply to Basic and Premium accounts, and pending, ignored or reported invitations can lead to restrictions. Its automated-activity guidance prohibits third-party scraping and automated website activity. Smart delays do not establish platform permission or guaranteed protection. The practical decision is the required workflow and its constraints, rather than a claimed detection-avoidance timer.

Complete the launch brief

The blank brief records audience purpose, source, selected account, current relationships, intended message purpose, prerequisite, stop rule and reply owner. Add the supported working window and runner requirement, then record unresolved controls. Keep a separate list of exclusions and existing campaign participants. If a requirement cannot be met with the current tool, hold activation or use a manual route rather than hide the missing condition in a larger sequence.

The local planning aid applies the published plan ladder to your selected requirement; it does not activate a campaign. The worked queue and downloadable decisions are reusable for reviewing a launch with a colleague. Keep the untouched observations beside the decision ledger. If you change the policy—for example, who owns a reply or which connection state permits an action—record the revision and replay every affected row.

Map your requirement to the published plan

This local worksheet applies the displayed monthly gates. It does not connect an account or execute a workflow.

A stated requirement is your brief, not evidence that a product has fulfilled it. See the current catalogue for the existing plan route.

Download the worked case and blank brief

The case labels and partitions describe this fictional policy. They do not establish actual export headers, product events or executed handoffs.

Move to the workspace your workflow needs

Choose Starter when the job is one-account campaigns, inbox and pipeline. Choose Pro when the additional AI sourcing/scoring/reply workload is real, and Plus when its monitoring or three-account scope is required. Published limits do not establish support for more than three accounts. Confirm that scope before selecting a plan. A price quote should state the currency, billing period and account unit, not only the lowest advertised entry amount.

If you still need a relevant audience, test the actual supported source with the 100-profile free entry and inspect its identities and fields. Keep the native source or established sender that already completes its stage. Ready campaign buyers can review the current paid catalogue without treating free extraction as a campaign trial. The outcome to inspect is a workflow with correct next actions and owned replies; neither a worksheet nor a scheduled message is evidence of a booked conversation.

Frequently asked questions

Can I start with an existing LinkedIn-profile CSV?

Yes, the current app offers CSV upload or pasted data inside Audiences → Add prospects → Import a CSV. Its documentation requires linkedin_url. Review the receiving people and fields before choosing a campaign; a URL alone does not establish enrichment. Starter is the published entry plan for campaigns, inbox and pipeline.

What should I check before Send to campaign?

Check the destination campaign name and draft or active status, plus the Wire continuously choice for future audience additions. The reviewed interface initially selected an active campaign and continuous wiring. A draft has a separate Start control; these interface observations are not an executed import, enrollment or sending test.

Do I need Diamond Pro for a multi-step campaign?

Starter at €29 monthly publishes campaigns, inbox, reply tracking, Kanban and analytics for one connected account. Pro adds AI sourcing/scoring and Responder; select it for that additional job.

What should happen when someone replies?

The worked case exits scheduled pitching and hands the conversation to its named owner. Configure and verify the actual selected tool’s supported controls; the paper exercise is not proof of runtime behaviour.

Is there a universally safe daily invitation number?

No safe numerical quota is established here. LinkedIn applies invitation restrictions and prohibits third-party automated website activity; smart delays do not establish permission or guaranteed protection.

Can I use the free profiles to test a campaign?

The free offer evaluates actual audience/source data. It does not establish a free campaign trial. A ready campaign buyer can review Starter directly, while keeping an existing source or sender that already fits.