# Prepare a service offer with the right owner, scope and request expectations

Original constructed teaching cases. No real accounts, participants, interviews or customers. Read the complete matching guide and do not substitute these examples for missing evidence.

S1 — Constructed owner mismatch: a team needs a shared company offer, but a member started a personal setup. Decision: stop before publication and verify eligible organization ownership. Outcome: a correct plan; no promise that an already-created personal service can simply be transferred.

S2 — Constructed pricing error: the draft headline says “Complete reporting audit for 80” while the field is a starting hourly rate and currency/scope were not supplied. Decision: remove the fixed-project claim and choose an accurate stated hourly basis or Contact for pricing. Outcome: a clearer offer, not a fabricated quote or accepted contract.

S3 — Constructed notification gap: an email announces a service request, but opening it shows no such request. LinkedIn says requests can close or reach their response limit, and another request may now be displayed. Decision: inspect the current actual request and avoid replying to an assumed earlier brief. Outcome: unavailable original request, not a lost verified customer.

## Complete supporting draft or discussion guide

Name the input, output, scope and excluded outcome. Constructed offer: “I review one supplied reporting worksheet and return a field dictionary plus a list of unresolved definitions. Source access must already be authorized. This review does not recover private LinkedIn metrics or certify business impact.” Replace every detail with work you can genuinely provide.

If displaying a starting hourly rate, name it as a starting basis, not a promise that an entire project costs that amount. LinkedIn distinguishes that field from a final price and offers Contact for pricing. A clearer scope is more useful than adding an unsupported turnaround, customer logo or performance guarantee.