About JB Consulting

Here is why this company exists at all. Slide decks are where the thinking happens.
Every organisation we have ever worked with keeps its most valuable explanations in slide decks. The architecture diagram that finally made sense. The onboarding session that everybody says was excellent. The strategy that nobody can quite paraphrase but everybody refers to. It is all in there.
And then it sits in a file. Attached to an email, buried in a SharePoint folder, presented once to eleven people and then effectively deleted. Meanwhile somebody in another department is rebuilding the same explanation from scratch, because they had no way to find the first one.
The usual instinct is to blame PowerPoint, or to tell everybody to stop making decks. We think that is backwards. People use slides because slides work. They are fast, they are visual, and everybody already knows how to make one. The problem is not the authoring tool. The problem is that the output stops at the file.
So we build the missing half. You keep making slides exactly the way you do now, and we turn what comes out into content that is readable, listenable, watchable, searchable, embeddable and accessible. That is the entire company.

So who will you actually be working with? First, John Baluka, who handles engineering, the products, and integration work.
John has spent thirty-plus years building software on the Microsoft stack. C#, .NET, Blazor, Azure, and a long and fairly unglamorous familiarity with the Office APIs, which turns out to be exactly what this particular problem needs.
Most of his career has been spent helping development teams move forward: migrating legacy ASP, Visual Basic, Access and Web Forms applications onto something maintainable, and advising teams on where the Microsoft ecosystem is actually going rather than where it was five years ago.
He writes about that at MovingToBlazor.com, he speaks and runs workshops, and he built MultimodalSlides because he got tired of watching good decks disappear.
He is also the one who will tell you that your speaker notes are not good enough yet. That is not rudeness. The notes are the narration, so they are the single biggest lever on how good the output is.
You can find him at JohnBaluka.com, on LinkedIn, at MovingToBlazor.com, or by email at John at JohnBaluka dot com.

Second, Laura Fine, who handles Microsoft 365, content and delivery.
Laura works at the point where Microsoft 365 meets the people who actually have to use it. SharePoint, Teams, OneDrive, and the content that sprawls across all three. She knows what really happens to a document library after eighteen months, which is a far more useful qualification than it sounds.
On an engagement she owns the side that is not code. How your content is structured, where it should live, who approves it, and whether your team will still be running the process confidently once we have gone. She is the reason our integration work includes training rather than a handover document.
And she is the one who will ask who owns this content in two years. That question has saved more projects than any piece of technology we have shipped.
You can find Laura on LinkedIn.

There are six things we have decided not to compromise on, and they explain most of how an engagement with us actually feels.
One: you keep your tools. We will never ask your organisation to migrate to a new authoring platform, learn a proprietary editor, or abandon its templates. Slides get made in PowerPoint, Google Slides and Canva, and we meet you there.
Two: you own the output. What we deliver is standard HTML, CSS and JavaScript on your domain. There is no runtime licence, no per-seat fee, and nothing that stops working if you stop paying us. If we vanished tomorrow, your content would still be there, and any web developer could maintain it.
Three: we would rather train you than retain you. Every integration engagement includes teaching your team to run the pipeline without us. Open-ended retainers are comfortable for a consultancy and expensive for a client, so they are not our default.
Four: we will talk you out of it. We publish a free product that handles the simple version of this problem, and we point people at it. We have never talked a client up a pricing tier, and we have told people to stick with a PDF when a PDF was genuinely fine.
Five: accessibility is not a phase two. Text alternatives, semantic structure, keyboard navigation and audio all come out of the same pipeline as everything else. It is not a line item you can cut, because it is not separable from how the thing is built.
And six: we say what we do not know. There are no invented testimonials on our site and no borrowed logos. AgileSlides is described as in development because it is in development. And if we have not solved your exact problem before, we will tell you that on the call rather than after the contract.

A word on how the company is actually arranged, because people ask.
JB Consulting is the company. DoMoreWithSlides.com is where we do the slide work: the three products, and the hands-on engagements around them.
John also does broader Microsoft-stack advisory and development work under his own name at JohnBaluka.com, and writes about Blazor migrations at MovingToBlazor.com. If your problem turns out to be a software problem rather than a slide problem, that is the same phone call, not a referral to somebody else.
And every engagement, whichever side of that line it falls on, carries a one hundred percent work guarantee. If we do not deliver what we agreed to deliver, you do not pay for it.