PlaysbyMoat8
Back to the library
The workflow guideMarketing

Offer a personalized professional-profile audit

Turn a team’s profile-review expertise into a self-service diagnostic that provides useful recommendations and introduces a relevant event or service.

6 implementation stepsIntermediate

How this works

Turn a team’s profile-review expertise into a self-service diagnostic that provides useful recommendations and introduces a relevant event or service. A profile diagnostic should return specific, observable improvements before introducing a related service. It becomes untrustworthy when it invents an audience score, infers private performance, or applies a generic prompt without a documented review rubric.

Evaluate only the permitted public or supplied profile material against a fixed set of criteria. Produce evidence-linked suggestions with examples the owner can edit. The lead magnet's offer should follow naturally from the diagnosed task, while contact collection and outreach remain separate authorized steps.

Before you start

Review rubric

Define concrete criteria such as audience clarity, proof, and next action.

Profile access

Use supplied screenshots or permitted public content; record unavailable sections.

Relevant offer

Choose an event or service that genuinely addresses the identified improvement.

Prepare the inputs

profile_material
Required

Text, screenshots, or public reference

Confirm the material belongs to the requested review scope.

goal
Required

Desired audience and action

Ask if the goal is unknown.

rubric
Required

Criteria with examples

Avoid unsupported numerical scoring.

content_sample
Required

Recent permitted posts

Record sample size and dates.

contact_fields
Required

Optional lead data

Collect only what the approved workflow requires.

Implementation, step by step

  1. Confirm the profile goal

    • Identify who should understand the profile and what useful action they should take.
    • If the owner has not stated a goal, frame findings conditionally rather than inventing one.

    Checkpoint: A clear diagnostic scope.

  2. Collect visible evidence

    • Extract the headline, description, proof points, and next-action elements from available material.
    • Mark inaccessible analytics or sections as unknown.

    Checkpoint: A profile evidence record.

  3. Apply the rubric

    • Evaluate each criterion using observable text or design evidence.
    • Keep absence, ambiguity, and poor fit separate; explain judgments rather than generate an opaque score.

    Checkpoint: A criterion-by-criterion review.

  4. Draft actionable improvements

    • Suggest specific rewrites or additions tied to the owner's stated goal.
    • Use only supplied achievements and facts; placeholders must remain obvious.

    Checkpoint: An editable recommendation set.

  5. Connect the useful next step

    • Offer a related resource or service after presenting the diagnostic value.
    • Avoid pressure tactics and do not imply the audit proves the user needs a purchase.

    Checkpoint: A relevant optional call to action.

  6. Prepare delivery and measurement

    • Deliver the review through the authorized interface or as a local file.
    • Track completion and later usefulness separately from lead capture.

    Checkpoint: A diagnostic package with honest status.

Decisions along the way

The profile serves several audiences

Prioritize the owner's stated goal or propose separate variants.

Proof of an achievement is missing

Ask for evidence or use neutral wording.

Recent posts are unavailable

Limit the audit to profile-level observations.

What you will produce

profile-audit.md

Markdown

Gives the owner usable edits.

Include: goal · criterion · evidence · recommendation · example · unknowns

diagnostic-record.json

JSON

Supports consistent repeat reviews.

Include: request_id · material_version · rubric_version · delivery_status

Check the result

  • Trace each criticism to visible evidence.
  • Verify suggested achievements are supplied facts.
  • Check the recommendation fits the stated audience.
  • Ensure unknown analytics are not presented as poor performance.

When something goes wrong

A page cannot be read

Accept screenshots or a text export and disclose the narrower scope.

The model invents a credibility metric

Remove it and return to qualitative rubric evidence.

The result becomes a generic sales pitch

Restore specific recommendations before the optional offer.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Audit a consultant profile for operations buyers.

Inputs

Synthetic example. Synthetic headline says Experienced professional; description mentions approved experience with inventory planning but no next action.

Expected result

Synthetic expected result. Suggest a headline naming inventory planning and a clear contact action. Do not invent years of experience, client names, or revenue results.

Run a small pilot

Start small

A few profiles with distinct goals and complete review permission.

Record the baseline

Record manual review effort and which suggestions owners accept.

Agree success criteria

Agree specificity and factual-accuracy criteria before scaling delivery.

Stop or revise

Stop if the workflow requires inaccessible personal data or cannot establish the intended goal.

Keep the scope clear

  • Public visibility does not authorize unsolicited outreach.
  • The diagnostic evaluates supplied material, not personality or professional worth.

Check before using

Check data access, rubric quality, false assumptions, and relevance. Keep marketing registration clear and avoid implying guaranteed reach or career outcomes.

Business activities

  • Handle inbound enquiries

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: User-provided profile reference · Profile-quality rubric · Product or event positioning

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗