SharePoint Development & Administration + InfoPath

For a long time, Microsoft's pitch was straightforward: not every business problem needed traditional software development. With Power Apps and Power Automate, teams could build forms, workflows and internal tools faster, with less reliance on professional developers and more control in the hands of business users. That shift made sense. SharePoint Online had moved away from many of the old customisation models that once gave developers broad freedom, and organisations still needed ways to extend Microsoft 365. Power Platform stepped into that gap and became the default answer for a huge range of "build it quickly" scenarios. But in 2026, the old trade-off looks different. AI coding agents are reducing the cost and friction of pro-code development. At the same time, many organisations are discovering that low-code does not remove complexity - it relocates it. Governance, environments, licensing, maintainability and long-term solution design still matter. So the real quest...

The low-code wave and the "citizen developer" promise Low-code/no-code platforms rose on a simple thesis: the demand for business software (forms, workflows, lightweight apps, departmental tools) outstripped the supply of professional engineering time, so organisations needed a way to deliver "good enough" solutions faster, with guardrails, and with more direct involvement from business users. This wasn't only a Microsoft story. Industry research and commentary in the late 2010s framed low-code as a major shift in how enterprises build software, often citing predictions that low-code would become a large share of application development activity. In parallel, analysts consistently described low-code as a speed lever that can "empower citizen developers", while also warning that hype and mismatched expectations can cause disappointment if governance, suitability, and long-term costs are ignored. Within Microsoft 365, the "citizen developer" na...