What are LinkedIn Advice Sessions?
LinkedIn Advice Sessions are paid 1:1 virtual meetings that eligible Premium Business members can offer from their profiles. LinkedIn supplies an integrated path for selecting a time, paying, and receiving a calendar invitation. It does not define which problem the host should accept, what preparation makes the hour useful, or where advice ends. Those remain offer and delivery decisions for the creator.
Platform fact: LinkedIn describes Advice Sessions as paid advisory meetings offered directly from a host profile. The overview says bookers can choose a time, pay through Stripe Checkout, including Apple Pay, and receive confirmation and a calendar invitation. That is meaningful transaction infrastructure, but it is not evidence that a session is well scoped or that either party will achieve an outcome.
Who can host or book a LinkedIn Advice Session?
Hosting is currently limited to invited Premium Business subscribers in the United States. Booking is broader but still bounded: LinkedIn’s overview says bookers do not need Premium, while also saying they must have a verified profile and be in the United States. The host setup page likewise describes a limited U.S. rollout and U.S.-based, verified bookers. Creators should treat access as a pilot condition, not a general availability promise.
A host must complete Stripe identity verification and bank setup and connect Google Calendar during onboarding. LinkedIn says the booking button does not appear until required setup is complete. Eligibility and onboarding answer who can expose the booking flow; they do not answer who is professionally or ethically qualified to advise on a particular question.
What do pricing, availability, and the booking window allow?
LinkedIn lets an eligible host set meeting details and a price up to $500. Availability must be recurring weekly availability; the overview says single-day or one-off times cannot be set. Payments run through Stripe, payouts are delayed by 30 days for issue resolution, and the host receives the session amount minus Stripe’s fees after that delay. These are platform mechanics, not pricing guidance or a statement about the value of an offer.
The booking window is currently documented inconsistently. The Advice Sessions overview says bookers can choose time within a 30-day window, while the newer booker setup page says to choose within a two-week window. Treat the live product and current Help copy as controlling rather than designing operations around either number.
Cancellation and refund language also needs a current-product check. The FAQ describes refund conditions but also says beta cancellations or no-shows do not automatically trigger a refund and assigns the host responsibility after a host cancellation. Do not promise a precise refund path from this article; verify the current FAQ, terms, and checkout information before offering or booking.
Booking infrastructure is not an advice offer
The operational implication is simple: a booking button can make an undefined offer easier to buy. Duration, rate, recurring availability, checkout, and calendar invitations solve transaction coordination. They do not select the right customer, narrow the question, create a preparation standard, or prevent a booker from expecting implementation, ongoing access, regulated advice, or a guaranteed result.
This work begins after offer validation. The creator offer validation loop asks whether a narrow paid 1:1 offer has enough commitment evidence to deserve delivery. The Advice Session Contract assumes the creator has chosen that rung and now needs to define how one session will operate. It is delivery and fit architecture, not another demand test.
Use the Advice Session Contract before opening availability
The Advice Session Contract is Florus’s five-field operating framework for a paid 1:1 session: Question, Fit, Boundary, Preparation, and Follow-up. It records what the session is for, who it can responsibly serve, what it excludes, what must arrive beforehand, and what happens afterward. It is not LinkedIn policy, a legal contract, or a substitute for legal, tax, medical, financial, or other professional advice.
- Question: write one decision the session helps clarify, plus examples of questions that are too broad for the format.
- Fit: name the booker, relevant stage, prerequisite knowledge, and disqualifying situations that need a specialist or different engagement.
- Boundary: set duration, scope, exclusions, confidentiality posture, recording rule, rescheduling posture, and a clear no-outcome-guarantee statement.
- Preparation: request one primary question and only the documents or context the host can review safely within the allotted time.
- Follow-up: define the recap, resource, or next-step note included, the support not included, and how a separate project would be scoped.
What should creators define before offering a session?
Before offering a session, a creator should be able to publish the promise, fit test, exclusions, preparation request, follow-up artifact, and current cancellation or refund reference in plain language. They should also decide how sensitive files are handled, whether the meeting may be recorded, when advice must stop and refer to a qualified professional, and how a larger engagement remains separate from the paid call.
Keep that record in the same creator publishing source of truth that holds the public promise and approved boundaries. Price only after the delivery shape is clear, using the creator monetization ladder to check whether paid expert time matches the trust and proof already earned. The platform ceiling is not a pricing recommendation.
A hypothetical advice-session contract
This intentionally imperfect example is explicitly hypothetical. An independent operations educator is considering a paid 45-minute workflow review. The educator is not a customer, has not used Launchvibes or LinkedIn Advice Sessions, and has no reported booking, revenue, client, delivery, or performance result.
| Field | Working answer | Open edge |
|---|---|---|
| Question | Clarify one handoff bottleneck in an existing small-team workflow. | A full process redesign is too broad for one session. |
| Fit | Independent consultants with a documented current workflow and one named decision. | Teams seeking employment, legal, or security advice need another route. |
| Boundary | Review one workflow artifact; no implementation, vendor selection, or outcome promise. | The recording and sensitive-data rule is still unwritten. |
| Preparation | Send one diagram and one primary question 48 hours before the meeting. | There is no rule yet for late or unreadable material. |
| Follow-up | Receive a short decision recap and two next questions; no ongoing support. | A larger project would need a separate scope and agreement. |
Let LinkedIn handle the rails, not the promise
A creator can use platform infrastructure without outsourcing offer judgment to it. LinkedIn can coordinate the visible booking path for eligible hosts. The creator still owns whether the question fits, the boundary is legible, preparation is proportionate, and follow-up matches what the booker paid for.
Launchvibes may help organize upstream audience, profile, business, campaign, and platform planning before the creator defines a session offer. It does not connect to LinkedIn; set up Advice Sessions; manage calendars, availability, booking, payments, Stripe, permissions, cancellations, or refunds; deliver advice; verify expertise, compliance, or outcomes; or guarantee bookings, revenue, client results, or performance.
The useful sequence is offer choice, operating contract, then platform setup. A booking button makes time purchasable. The Advice Session Contract makes the promise reviewable before anyone pays.