Side-by-side

Stop Writing Manual SOPs.

Capture any workflow — browser or desktop — and turn it into a step-by-step guide in seconds.

Manual SOPs✕

How to Create a Sales Order in Salesforce

Objective:

To create a sales order in Salesforce from an existing account and opportunity.

Steps:

  1. 1. Log in to Salesforce
  2. 2. Click on the "Sales" app
  3. 3. Click on "Accounts"
  4. 4. Search for the account
  5. 5. Click on the account name
  6. 6. Click on "New" under Opportunities
  7. 7. Fill in the opportunity details
  8. 8. Click "Save"
  9. 9. Click on the opportunity
  10. 10. Click on "New" under Quotes
  11. 11. Select a quote record type
  12. 12. Fill in the quote details
  13. 13. Click "Save"
  14. 14. Click on "New" under Orders
  15. 15. Select the quote
  16. 16. Fill in the order details
  17. 17. Click "Save"
  18. 18. Verify the order

Notes:

  • • Make sure all required fields are filled.
  • • If you can't find the account, create a new one.
  • • Contact your admin if you see any errors.
  • ✕Screenshot every click manually
  • ✕Re-do the whole doc when the UI changes
  • ✕Inconsistent voice across authors
  • ✕Nobody owns the maintenance
InstaGuide.ai SOP✓

Create a Sales Order in Salesforce

18 steps · 5 min read · Salesforce

  1. 1

    Log in to Salesforce

    Go to https://login.salesforce.com and sign in with your credentials.

  2. 2

    Click on the 'Sales' app

    From the App Launcher, select the Sales app.

  3. 3

    Click on 'Accounts'

    Navigate to the Accounts tab from the navigation bar.

  4. 4

    Search for the account

    Use the search bar to find the account you need.

  5. 5

    Click on the account name

    Open the account record by clicking on the account name.

And 13 more steps…

Instantly captured. Perfectly documented.

  • ✓Every click captured automatically
  • ✓InstaGuide writes the step descriptions
  • ✓Visual Process Flow diagram included
  • ✓Re-capture single steps when UI changes

Definition

What is a Standard Operating Procedure?

A Standard Operating Procedure (SOP) is a step-by-step playbook for a recurring task — onboarding, refunds, month-end close, incident response. The operating system of a well-run team.

The hard part isn't writing one. It's the maintenance — apps change, screenshots rot, processes drift. Teams who do SOPs well are the ones who can keep them current cheaply.

The pain

Why teams stop writing SOPs

Screenshots are slow

Stop, crop, paste, caption — 30 times. A morning gone before you write a word.

Apps span web + desktop

Browser-only tools leave half your steps blank when workflows touch Salesforce, Outlook, Excel.

They go stale fast

App UIs change quarterly. Maintaining an SOP often costs more than writing it.

Inconsistent quality

Five authors, five styles. New hires read each one differently.

Versioning is a mess

Forked docs, three half-updated versions, nobody knows which is current.

Nobody owns them

Without a named owner, SOPs rot. By month 6, half are wrong.

The InstaGuide way

How InstaGuide writes SOPs automatically

Three steps from blank page to polished SOP.

1

Capture the workflow once

Open the extension or desktop app. Every click is captured with a screenshot and optional voice narration.

2

InstaGuide writes the step text

Claude (or Azure OpenAI / Gemini / Snowflake) generates imperative step descriptions and groups steps by app.

3

Edit, share, export

Tweak any step inline. Share with permissions. Export to PDF or HTML.

Real SOPs

Example SOPs captured with InstaGuide

Real workflows captured with InstaGuide. Click any one for the full step-by-step.

Google Workspace

How to share a Google Doc with edit access

Share a Google Doc so a teammate can edit it directly, without making it public.

Google Workspace

How to set up an out-of-office reply in Gmail

Configure Gmail to auto-respond while you're away — including who to contact in your absence.

Google Workspace

How to add a guest to a Google Calendar event

Add an external or internal guest to a calendar event and control what they can do.

Microsoft 365

How to set up an email signature in Outlook (web)

Create and apply a default email signature in the web version of Outlook.

Microsoft 365

How to share a OneDrive folder with a teammate

Share a OneDrive folder so a teammate can read or edit everything inside it.

Microsoft 365

How to schedule a Teams meeting with external attendees

Set up a Microsoft Teams meeting and invite people outside your organization.

Browse all real-world SOP examples

By the numbers

What InstaGuide replaces in SOP creation

18×

Faster to write

5 min vs 90 min per SOP

0

Manual screenshots

Every click captures itself

1

Step to update

Re-capture single steps when UI changes

Best practices

How to write an SOP that your team will actually follow

Seven principles that separate the SOPs teams actually follow from the ones that rot.

  1. 1

    Pick a recurring task with a stable end-state

    SOPs are worth writing when the task happens often AND the outcome is consistent.

  2. 2

    Identify the audience

    Write to the day-one new hire. Their skill level sets the detail.

  3. 3

    Capture the workflow end-to-end, not in pieces

    If your task spans 5 apps, capture all 5 in one session — that's how it actually happens.

  4. 4

    Write step descriptions in imperative voice

    “$1” beats “$1” Faster to scan.

  5. 5

    Annotate only what matters

    Circle the right button. Blur sensitive data. Skip everything else.

  6. 6

    Assign an owner

    Without a named owner, SOPs rot. The owner keeps it accurate.

  7. 7

    Review on a schedule

    Quarterly review. Re-capture only the steps that changed.

Works with every application

SalesforceSAPHubSpotServiceNowWorkdayQuickBooksZendeskOracleNetSuiteMicrosoft 365

FAQ

Questions teams ask about SOPs

A Standard Operating Procedure (SOP) is a documented set of step-by-step instructions for completing a recurring task — like onboarding a new hire, processing a customer refund, or running a month-end close. SOPs reduce variance, speed up training, and make it possible to audit how work actually gets done. The format is usually a numbered list of steps, each with a clear action, supporting screenshot or visual, and any decision points or exceptions called out.
The traditional SOP-writing process is the painful part: do the task once, take screenshots, paste them into a Doc, annotate each one, write the step description, repeat for every revision. InstaGuide eliminates the screenshot work entirely — you perform the task once with the extension or desktop app running, and it captures every click, generates a screenshot for each step, and writes the step description. A 30-step SOP that used to take 90 minutes now takes about 5.
An SOP describes a recurring business process — onboarding, refund handling, invoicing — and is usually for cross-functional or operational use. A runbook is a tighter, technical version typically used by engineering or IT for incident response, deployments, or system operations. Both follow the same step-by-step format and InstaGuide handles either equally — the only difference is the audience.
Docs and Notion are blank canvases — every SOP starts from scratch and requires you to manually take screenshots, paste them in, write each step. InstaGuide skips all of that: capture the workflow once and the SOP is written for you, with screenshots, click indicators, and AI descriptions. You can export to PDF or HTML for those who prefer reading in Docs, but the source-of-truth SOP lives in InstaGuide where it's searchable, editable per step, and never goes stale due to a missed re-screenshot.
Yes — every step's text is editable inline. You can also pick which AI provider generates the descriptions at the organization level: Claude, Azure OpenAI, Google Gemini, or Snowflake Cortex. This matters when your security team has approved certain providers but not others, or when you want to keep AI processing inside an already-procured vendor.
Yes. Every step's action text, description, and annotations are editable inline. You can also insert a new step at any position, re-capture just a single step that changed (without redoing the whole flow), and ask InstaGuide to regenerate if the wording needs a refresh. The Visual Process Flow diagram auto-updates as you edit.
10 SOPs forever on the free plan. Insta (our in-app assistant) writes the step titles, descriptions, and guide summary, then runs an auto-correction & review pass — all on Free. Paid personal plans: Starter is $13/month for 25 SOPs (adds PDF + HTML export and process flow diagrams); Pro is $29/month for 100 SOPs (adds voice narration, Ask Insta Assistant, and change tracking — includes a 15-day free trial). For teams, Business is $39/user/month with a 5-user minimum (200 SOPs, guide sharing & teams, priority support — includes a 30-day free trial). Enterprise has unlimited SOPs plus Builder/Viewer licensing, custom branding, SSO/SAML, BYO cloud storage, BYO AI provider, and public iframe embed — contact sales for a quote.

Stop writing SOPs by hand

Your first 10 SOPs are free. Capture a workflow once and InstaGuide writes the rest — screenshots, step descriptions, and a Visual Process Flow diagram included.

Create your first SOP freeTalk to sales