Bianca W.

Most Microsoft 365 problems aren't technology problems. The tools are there. The licences are paid for. The process is just still running on manual steps and a spreadsheet someone will eventually overwrite. I'm a citizen developer. I bridge the gap between the business problem and the build that fixes it. Not by logging a ticket and waiting. By understanding what's actually broken and building the thing that solves it. I started in 2012 with Excel and VBA, then SharePoint Lists, then the Power Platform, then Office Scripts and TypeScript when the platform ran out of road. Each version was the answer to a problem the previous one couldn't solve. I didn't plan to become a developer. I just kept running out of ways to make Excel do things it wasn't designed to do. What I help with: - Power Platform builds. Power Automate flows, Power Apps, Office Scripts. Anywhere from a single automation to a full multi-user system with its own data model, interface, and analytics. - SharePoint and M365 enablement. Intranets that people actually use, governance that doesn't require a PhD to follow, and information architecture designed around how your team works, not how IT wishes they worked. - Adoption and training. If you've rolled out M365 and half your team is still working the old way, I've run adoption programs for 2,000+ staff and I know the difference between a training event and a change that sticks. - Excel and automation. When the right fix is a well-built spreadsheet or a formula someone should have written years ago, I'll build that too. I'm Microsoft Certified (PL-300) and I've shipped a product to Microsoft AppSource. I document everything I build at bianca.codes, practical blueprints for business-side people who've been told something isn't possible by someone who hasn't tried. If your tools aren't working like they should, let's talk.