Freelance SharePoint Developer in Canberra

It depends on the work. A short fix or a single web part is priced very differently from a full intranet build, and I quote each job on its scope rather than publishing a rate card. Working directly with a freelance developer removes the consultancy margin from the engagement, but I will not promise it is always cheaper. Send me what you are trying to do and you will get a straight estimate with the assumptions written down.

Yes. Small projects are welcome: one web part, a permissions clean-up, a broken flow, a day of advice. There is no minimum engagement size, and a small job done well is usually how a longer working relationship starts.

Almost always. Most work is in a tenant that already exists, with content, permissions and customisations that have accumulated over years. I start by understanding what is there before changing anything, and I work within your change control and governance rather than around it.

Yes, and it is often cheaper than rebuilding. Common jobs are SPFx solutions that stopped working after a tenant or Node update, web parts that are slow, permissions that have drifted, and code left behind by a developer or vendor who is no longer around. I will assess it honestly and tell you whether it is worth repairing or whether you are paying to maintain a dead end.

Yes. I have led intranet builds for government departments serving thousands of users, and a business intranet uses the same platform with fewer constraints. The build covers information architecture, the permissions model, the publishing process and any custom SPFx web parts, so the intranet is still usable when it has years of content in it.

Yes. Ongoing support can be a monthly retainer for small changes and fixes, ad-hoc development when something comes up, or a standing arrangement to back up your internal IT team. It gives you a SharePoint developer on demand without employing one.

Yes. I am based in Canberra and work with Canberra and ACT organisations directly, and I work remotely with organisations anywhere in Australia. SharePoint work suits remote delivery well, and everything happens in your Microsoft 365 tenant regardless of where I am sitting.

SPFx is the SharePoint Framework, Microsoft's supported way to write custom code that runs inside SharePoint Online and Microsoft Teams. It is built with TypeScript and usually React. You need it when the built-in web parts cannot do what the business needs. You do not need it for a site that out-of-the-box features already cover, and I will say so if that is the case.

Yes. Approvals, document workflows, notifications, scheduled jobs and hand-offs between teams are built with Power Automate, and with Microsoft Graph or Azure Functions where a flow is the wrong tool. The aim is to remove the manual steps and the email chains, not to add another system people have to check.

Yes. SharePoint can be connected to finance, HR, CRM and line-of-business systems through Microsoft Graph, REST APIs, Power Automate connectors and Azure integration. Which one is right depends on the system, the volume of data and how current it needs to be, and that is part of the solution design.

Yes. That includes migrating classic or on-premises SharePoint customisations to SharePoint Online, upgrading old SPFx solutions to the current framework, and replacing unsupported patterns with supported ones so the solution survives Microsoft's updates.

Usually both, and with MDT they are the same person. A consultant works out what should be built and how it fits your organisation; a developer builds it. Splitting the two across a consultancy is where designs that cannot be built come from. I do the design and the build, so the advice is grounded in what will actually work in your tenant.