Great guides exist. Nobody can find them.

I'm James Riggall — founder of WingMarq, Power BI consultant at JR Data Solutions, and the person behind That Data Guy.

20 years of engineering. Then data.

My career started in control and instrumentation engineering — nearly two decades of fault diagnosis and systems thinking in regulated environments where accuracy is non-negotiable.

From there I moved into the defence sector as a capability manager and analyst, DV-cleared, working across the full Microsoft suite — Power BI, SharePoint, Teams, Power Apps — with senior leaders who needed to make fast, informed decisions.

One of the simplest things I did that made the biggest difference? Screen sharing with senior leaders to set up their bookmarks — so they could get to the right reports, the right dashboards, the right docs faster. It wasn't a product. It was just me, helping people operate smoother, faster, and better.

And every time, it made an immediate difference.

Then the feedback started coming in

Through That Data Guy, I've spent years creating content around Power BI, Microsoft 365, and tools like Scribe — helping teams build better guides and documentation. The feedback from those videos kept saying the same thing:

“We've got great guides. But when someone's actually on the page, they can't find them.”

That hit home — because I'd already solved this problem before, just in a completely different world.

Two worlds, one product

When the feedback from the Scribe videos started piling up, it clicked. The problem those teams were describing was the same thing I'd been doing manually in defence — helping people find what they need, right where they need it.

Teams everywhere build great documentation. Scribe guides, SOPs, Notion pages, SharePoint docs. The content exists. But there's a gap between those guides existing and people actually finding them at the moment they need them.

WingMarq fills that gap. It surfaces the right guide at the right moment — on Power BI, SharePoint, Teams, timesheets, internal tools, or any web app your team uses. No searching, no tab switching. Just contextual guidance, exactly where work happens.

That's the engineering mindset applied to a content problem: build the system once, and it works every time someone lands on the page.