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.
Built for the first 90 days, when the help they want is the help they’ll actually read.
Reads the page URL only. No access to page content. Deploy via Chrome & Edge policies.
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 right there at the top of the page. They’re unstuck in 30 seconds, without leaving the tool.
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.
Time to productivity drops. The buddy goes back to their actual job. The handbook starts paying for itself.
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 →
Up and running
in three steps.
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.
A new sales hire’s first week
Sara joins on Monday. On Tuesday she opens Salesforce for the first time — the SDR playbook your team wrote in Scribe last quarter appears at the top of the page. 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.
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.
Marq is a URL pattern plus one or more existing doc links. Set up takes minutes per tool.IT installs the extension once
Standard Chrome and Edge managed deployment via group policy. End users never see a setup screen. IT approves it on the first call because the extension reads only the page address — no DOM access, no page content scraping.
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 — the relevant doc appears as a non-intrusive overlay. No searching. No asking. No remembering it exists.
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.
IT approval
The contextual help layer IT actually approves.
WingMarq reads the page address — the same string in the URL bar — and nothing else. It can’t see the contents of your tools, your reports, or anything a user types. No DOM access. No page-content scraping. No integrations to provision. The IT review is one call, not six months.
Built for the cohort
Built for the cohort that wants the help.
WingMarq is at its strongest with new starters — a defined cohort, a defined time window, a high tolerance for prompts, and a measurable outcome at the end. Deliberately not a permanent overlay. The cohort that wants the help cycles in and out. The product is built for that, not for everyone forever.
Not a smaller WalkMe. Not a worse Notion. A different shape entirely.
vs WalkMe, Pendo, Userpilot, Appcues
The enterprise adoption platforms
Adoption platforms do DOM manipulation, demand a six-month IT security review, cost six figures, and want you to rebuild every guide inside their editor. 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 the cohort that doesn’t 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 right there at the top of the page. They’re unstuck in 30 seconds 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. The explainer your senior analyst published in Notion appears alongside the report — exactly the “what does this mean and how should I read it” doc that nobody ever links them to. They get it on the first encounter.
New support agent
your help desk, on the first escalation
Lands on a ticket type they’ve never seen before. The escalation runbook your support lead keeps in SharePoint surfaces on the page. They handle the ticket cleanly. The lead isn’t pinged. 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 approve it on the first call.
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 see what’s on the page, and your existing documentation stays in the systems where it already lives.
Reads the page address only.
The extension reads window.location and nothing else. It cannot see the contents of your reports, your CRM, your dashboards, or anything a user types on the page. No DOM access. No page-content scraping. No JavaScript injection into the host page.
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. No new credentials or secrets to manage in your tools.
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 seats and advanced features.
£0
Free forever · No card required
- ✓Up to 10 Marqs
- ✓5 guides per Marq
- ✓Up to 2 team members
- ✓Works on any internal tool or website
- ✓Chrome & Edge extension
Teams
£29
/moor £19/mo billed annually
- ✓Everything in Free, plus:
- ✓Up to 50 Marqs
- ✓5 guides per Marq
- ✓Up to 20 team members
- ✓90-day analytics retention
- ✓Priority support
- ✓Free onboarding session with That Data Guy
Custom
Tailored to your organisation
- ✓Everything in Teams, plus:
- ✓Higher seat and Marq limits
- ✓Dedicated onboarding support
- ✓Direct support from the WingMarq team
- ✓Volume licensing
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
