Persona X™ Brand

    Brand

    Give your team a shared voice and clear boundaries on what to claim. Create the piece you need, check it against your rules and review it before it goes out.

    01

    Set the boundaries once.

    Start with what your team can say and how it should sound. Keep approved claims, caveats and brand rules together.

    Keep every draft within your approved claims

    Set approved, conditional and prohibited claims. Keep caveats attached to drafts.

    Documentation
    EVERY CLAIM HAS A LANE
    * Reviewed with qualified experts
    Blocked
    DRAFT
    One-pager
    *
    Your team sorts claims once. Drafts pull only approved claims, conditional ones bring their caveat, and prohibited ones never get through.

    Give every project the same voice

    Share fonts, colours, tone and rules across every project.

    Documentation
    ONE GUIDE, EVERY PROJECT
    Brand guideWorkspace
    Aa
    Voice: lead with the outcome.
    Colours, fonts, voice and rules live in one workspace guide. Every project reads it, and none can change it on its own.
    02

    Make something buyers can use.

    Bring strategy and buyer context into decks, pages and posts. Work from the same voice rather than starting from a blank page.

    Turn buyer context into a piece you can use

    Build decks, one-pagers and pages from strategy and approved claims.

    Documentation
    ONE CONTEXT, EVERY FORMAT
    Your context
    ExampleYour plan, personas and approved claims become a deck, a one-pager and a page. All three come from the same context, so they say the same thing.

    Take on-brand drafts through to publication

    Review, publish or schedule LinkedIn posts and WordPress articles.

    Documentation
    NOTHING PUBLISHES WITHOUT A YES
    Draft
    Needs approval
    Scheduled
    Published
    Your yes
    LinkedInGive every buyer the proof they need.
    WordPressWhy buying groups stall in Q4
    Posts and articles are drafted from your personas, plan and voice. Nothing is scheduled or published until someone on your team says yes.
    03

    Review before it represents you.

    Check the draft for overclaims, resolve team feedback and approve the revision. Your team decides what changes.

    Catch overclaims before they go out

    Check claims, voice and sources. You decide which flagged lines change.

    Documentation
    EVERY LINE CHECKED AGAINST YOUR RULES
    DRAFTLinkedIn post
    Map the questions each buyer asks.
    Guaranteed to shorten every sales cycle.
    Built on your own calls and notes.
    Surfaces funding signals for RHTP teams.
    Give every buyer the proof they need.
    –
    Score
    Checking…
    Claims1 overclaimVoicePassSources1 caveat
    ExampleEvery line is read against your claims, your voice and your sources before you see the draft.

    Turn team feedback into a reviewed revision

    Turn comments into proposed changes. Approve revisions; reviewers resolve comments.

    Documentation
    COMMENT ON THE EXACT LINE
    One-pager
    Comment #1on the headline
    MRMaya RLead with the outcome.
    JLJon L@Mayaswapped in the approved headline.
    ExampleReviewers pin comments to the exact line, reply with an @mention and resolve it once it is fixed.

    The work connects.

    Start from buyer context, then keep useful finished work available to the team.

    Frequently asked questions

    One place for your voice, colors, fonts and rules. It applies to every project in your workspace, so artifacts look and sound the same across them.

    Yes. Add them to the guide and they render in your artifacts.

    A claim you can say only with a caveat attached. Persona X carries the caveat into every draft that uses the claim.

    It reads each draft against your approved claims, your voice and your sources, then scores it from 0 to 100. Lines that overclaim are flagged, and you decide what changes.

    You can publish or schedule a LinkedIn post from Persona X, and publish blog articles to WordPress. You review each one first.

    You and your team. A person reviews every deliverable before it goes anywhere.

    Bring the claims you already use

    Sort approved, conditional and prohibited claims, then build a first draft.