Show new starters the right doc the moment they open the tool.

Using your existing onboarding docs — Notion, SharePoint, Scribe, wherever they live. No migration. No new content to create.

A small prompt in the corner of the page, offering the guides you linked. Works in Chrome and Edge.

Decides from the page URL alone. Never reads page content. Deploy via Chrome & Edge policies.

  • Power BI
  • SharePoint
  • Teams on the web
  • Other HTTPS web apps

A Marq · example

When someone opens

expenses.tallybook.app/claims/*

WingMarq offers
  • Claiming expenses in Tallybookharbourfinch.sharepoint.com/sites/people/expenses-guide
  • Your first claim — 2-minute walkthroughscribehow.com/shared/first-claim

Shown to everyone with the extension connected to your workspace. The guides stay where they are; their permissions still apply.

One Marq, from the portal to the page.

The real WingMarq portal and extension, recorded in a fictional demo workspace. 37 seconds, no sound.
What the video shows
  1. In the WingMarq portal, add a page address and a link to a guide you already have.
  2. Connect the browser extension once with your workspace key.
  3. Open the matching page: the WingMarq prompt appears.
  4. Choose the guide from the prompt. It opens where it lives.

You wrote the onboarding docs. Your new starters aren't reading them.

Your onboarding handbook is in Notion. The runbooks are in SharePoint. The walkthroughs are in Scribe. Your new starter is in the tool, stuck on the same question their predecessor was stuck on six months ago — and the doc that would have helped sits two clicks deeper than they ever look.

01

The doc is for the org. The new starter is in the tool.

Your onboarding documentation was written for the team, in the team’s tools. The new starter is on day eleven, on a Salesforce screen they’ve never seen before. The doc exists. It is two clicks deeper than they will ever look.

02

New starters don’t know what to search for.

Search assumes you can name the thing you’re looking for. In their first 90 days, your new starters often can’t. They guess, ask their buddy, or wait. Each of those is slower than the doc you already wrote would have been.

03

Buddies and Slack channels don’t scale.

The buddy is in a meeting. The #new-hires channel is embarrassing to use twice. Your hiring manager is the third escalation. Every new starter who arrived this year is paying the same tax on the same questions, and your time-to-productivity number reflects it.

❌ Without WingMarq

😤

New starter opens Salesforce on day eight, hits a confusing field, can’t remember which Notion page covered it. Asks their buddy. Waits two hours for an answer.

📉

Your team wrote the SDR playbook in Scribe last quarter. Three new hires have started since. None of them have opened it.

🔁

Hiring manager answers the same five questions for every new starter. Three months later, that new starter answers the same five questions for the next one.

✓ With WingMarq

📍

New starter opens the same Salesforce screen. The Scribe walkthrough you wrote six months ago is waiting in the corner of the page. They find it without leaving the tool or asking anyone.

✓

Your team publishes a new SDR playbook. The next new hire who opens Salesforce sees it on day one. You didn’t have to remember to send it.

⏱

That’s the aim: a shorter ramp, a buddy who gets back to their own job, and a handbook that actually gets used.

Most teams already have the onboarding documentation. Almost none of their new starters read it at the moment it would have helped. The problem isn’t the content. It’s finding it when the work is actually happening.

Built by a consultant with 20 years in defence and engineering. Read the full story →

Three parts, and nothing to rebuild.

No new content to write. No migration. No developer needed. WingMarq is the layer that closes the gap between the doc exists and the new starter encounters it.

  1. 01 You

    Point WingMarq at the docs you already have

    For each tool your new starters use, paste the URL pattern and the doc you want them to see. The doc stays in Notion, SharePoint, Scribe, Loom, Confluence — wherever it already lives.

    Each Marq is a URL pattern plus one or more existing doc links. Nothing to build inside the tool.

  2. 02 IT

    IT installs the extension once

    Standard Chrome and Edge managed deployment via group policy. Each person then connects once by pasting your workspace key. The review is short because the extension reads only the page address and never reads page content.

    Same rollout pattern as any extension your IT team already approves. Works on Chrome and Edge.

  3. 03 New starters

    New starters meet the doc when they open the tool

    When a new hire opens Salesforce, Power BI, SharePoint, your help desk — anywhere you’ve curated a Marq — a small WingMarq prompt appears in the bottom-right corner, offering the relevant doc. No searching. No asking. No remembering it exists.

    The doc opens in a new tab when clicked. Your existing tool of record stays the source of truth.

A new sales hire’s first week

Sara joins on Monday. On Tuesday she opens Salesforce for the first time — a prompt in the corner offers the SDR playbook your team wrote in Scribe last quarter. On Wednesday she opens the weekly forecast report in Power BI — the explainer your senior analyst published in Notion shows up. On Thursday she opens your help desk tool and sees the escalation runbook your support lead keeps in SharePoint. None of those docs moved. Nobody had to remember to send them.

See the four setup steps
📊Power BI
📁SharePoint
💬Teams on the web
🌐Other HTTPS web apps

Three things that change the onboarding calculus.

Your existing docs

Your docs work, finally.

You’ve already written the onboarding documentation. WingMarq surfaces it at the page your new starter is on — without you moving a single doc out of Notion, SharePoint, Scribe, or wherever it lives. You keep your existing tools. You keep your existing content. WingMarq is the layer that closes the gap between the doc exists and the new starter reads it.

Works with any URL — Notion pages, SharePoint docs, Scribe walkthroughs, Loom videos, Confluence, Google Docs, internal wikis. We don’t ingest, host, or copy your content.

IT approval

The contextual help layer IT actually approves.

WingMarq reads the page address — the same string in the URL bar — to decide what to show. It doesn’t look at the contents of your tools, your reports, or anything a user types. No page-content scraping. No integrations to provision. What IT reviews is short: the extension’s permissions and the few data fields it sends, documented in our IT guide.

Standard Chrome and Edge managed deployment via group policy. Digital adoption platforms are built to work inside your applications — walkthroughs, highlights, in-app analytics — which is a broader product to review. WingMarq does one narrower thing on purpose.

Built for new starters

Helpful when it's new. Easy to dismiss when it isn't.

WingMarq is at its strongest with new starters, who don’t yet know what to search for. It shows the same prompt to everyone with the extension connected to your workspace: it doesn’t know who is new or when they joined.

People who already know the tool close the prompt, and it stays away for the time you set on that Marq (one day by default, up to 30 days). It never covers the page: it sits in the corner and opens a guide only when clicked.

Not a smaller WalkMe. Not a worse Notion. A different shape entirely.

vs WalkMe, Pendo, Userpilot, Appcues

The enterprise adoption platforms

Digital adoption platforms are built to act inside your applications — in-product walkthroughs, highlights, in-app analytics — usually with guides authored in their own editor. That’s a broader product, with a broader review and budget to match. WingMarq reads only the page address, installs like any standard browser extension, and links to the docs you already have. For new-hire onboarding specifically, the adoption-platform feature surface is overkill — new starters need “where’s the doc for this?”, not a seven-step in-product walkthrough.

vs Notion, SharePoint, Confluence, Scribe

The documentation platforms

We’re not a documentation platform. We sit on top of yours. Whatever you’ve already written stays where it is — we just put it in front of the new starter at the page where it matters. The honest pitch: keep paying Scribe and Notion; pay us to make sure new starters actually meet what you’ve written.

vs Glean, Sana, Microsoft Copilot

AI search

AI search is a great power tool for people who know what to ask. In their first 90 days, your new starters don’t. They don’t know what to search for, what the thing is called, or that there even is a doc. WingMarq pushes the relevant guide to them when they land on the tool — without them having to phrase a query. Push, not pull. For people who don’t yet know what to ask, push wins.

vs “We just send them a Notion doc”

Doing nothing

You sent the doc on day one. They didn’t open it. They opened it briefly, didn’t recognise the bits they’d need later, closed it. Three months in, they’re still asking your team the questions the doc would have answered. WingMarq puts the relevant page in front of them at the moment they’re on the tool it explains — without asking them to remember it exists.

Three new starters, three first-week moments.

The mechanic is the same in every case: a URL pattern you curated, a doc you already wrote, surfaced when a new starter lands on the page. None of the docs below moved.

New sales hire

Salesforce, on day eight

Opens an opportunity for the first time, isn’t sure what the stage gates mean. The SDR playbook your team wrote in Scribe last quarter is offered in the corner of the page. They can open it without leaving the tool — and without asking their buddy who’s on a sales call.

New analyst

Power BI, on the Q3 forecast

Opens the weekly revenue dashboard, hits a metric they don’t recognise. A prompt in the corner offers the explainer your senior analyst published in Notion — exactly the “what does this mean and how should I read it” doc that nobody ever links them to. It’s there the first time they need it.

New support agent

your help desk, on the first escalation

Lands on a ticket type they’ve never seen before. If your help desk puts the ticket type in the page address, the escalation runbook your support lead keeps in SharePoint is offered on that page. They have the runbook in front of them before they ping the lead. The next new starter who lands on the same ticket type sees the same runbook — without anyone having to remember it’s there.

Built so IT can review it quickly.

The single most important thing about WingMarq’s architecture, in a paragraph short enough to forward to your IT counterpart: we read only the page address, we don’t look at what’s on the page, and your existing documentation stays in the systems where it already lives.

Reads the page address only.

The extension decides what to show from the page address alone. It doesn't look at the contents of your reports, your CRM, your dashboards, or anything a user types on the page. The only thing it adds to the page is the small WingMarq prompt. No page-content scraping.

No customer content ingested or hosted.

Your docs stay where you keep them — Notion, SharePoint, Scribe, OneDrive, Confluence, Loom, wherever. We store URLs and metadata. We do not store, copy, or process the contents of what those URLs point to.

Standard Chrome and Edge managed deployment.

Roll WingMarq out the way you roll out any extension your IT team already approves — Chrome Enterprise policy, Edge group policy. No new tooling. No bespoke integration. Each person connects once by pasting your workspace key into the extension's settings.

Built to defence-environment principles.

WingMarq was built by a consultant with twenty years inside DV-cleared defence and engineering environments. Least privilege, data minimisation, zero assumptions about what you’re comfortable sharing. We aren’t claiming certifications we don’t hold; we’re building to the principles we’ve worked under for two decades.

Start free, scale when ready.

Get started with the Free plan — no credit card required. Upgrade to Teams when you need more Marqs and hands-on support.

Free

£0

Free forever · No card required

  • ✓Up to 10 Marqs
  • ✓5 guides per Marq
  • ✓Invite colleagues to connect the extension
  • ✓Works on HTTPS web apps in Chrome and Edge
  • ✓Chrome & Edge extension
  • ✓Analytics: last 7, 30 or 90 days
Get Started Free

Teams

£29

/mo

or £19/mo billed annually

  • ✓Everything in Free, plus:
  • ✓Up to 50 Marqs
  • ✓5 guides per Marq
  • ✓Priority support
  • ✓Free onboarding session with That Data Guy
Get Started

Custom

Tailored to your organisation

  • ✓Everything in Teams, plus:
  • ✓Higher Marq limits, up to 20 guides per Marq
  • ✓Dedicated onboarding support
  • ✓Direct support from the WingMarq team
  • ✓Volume licensing
Talk to us

Want hands-on help deploying WingMarq? Book a session with That Data Guy.

Your onboarding docs are already written. Make sure your new starters meet them.

Start free. Curate your first few Marqs. Watch the next new starter encounter the docs they would never have found on their own.

Free to start · No credit card required · IT-friendly install