Scripe helps you show up consistently and authentically on LinkedIn — without spending hours figuring out what to write. Whether you’re a solo founder, a team leader, or a content strategist, Scripe gives you a system that scales your voice, not just your output. This guide will help you get started.

​
Intro to Scripe

Get a high-level overview of the Scripe environment by watching our demo video:

​
Onboarding sessions

Join a live onboarding session to learn the essentials of Scripe and see demos of our product.
You can watch past onboarding sessions on Scripe’s Youtube →

​
Join our WhatsApp community

Meet other Scripe users to get advice and exchange tips in our Whatsapp Community.

​
Setting up Scripe

Everything in Scripe starts with a workspace. You’ll be asked to: You can always invite more people or upgrade later.
In Scripe, a Personal Brand refers to the LinkedIn profile you manage through the platform. You can manage multiple Personal Brands on the Team plan, and a single Personal Brand in the Starter and Professional Plans.
New Dashboard Banner Web

​
Step-by-step for individuals:

  1. Create your personal brand, connect it with LinkedIn, and install the Chrome Extension.
  2. Set up your content strategy (your role, goals, and audience).
  3. Add sources to your Knowledge Base so Scripe can learn more about you.
  4. Create your first post:
  5. Use the Calendar view to organize your content and track consistency.
  6. Use the Inspiration page to repurpose posts or follow creators.
    • Scripe subtly adapts your tone of voice to match the tone of your followed creators.
  7. Check your Analytics tab to learn what works and improve from there.

​
Step-by-step for Teams:

  1. Invite teammates to the team workspace.
  2. Set up each member’s role within the workspace.
  3. Set up up to 10 personal brands and follow the individuals’ set up.
  4. Understand how to work with the:
    1. Content Approval Workflow
    2. Company Calendar
    3. Company Analytics
Learn more about different ways to work as a team in Scripe, in our Team Workflows article →