Hiring a SharePoint or Microsoft 365 Developer? What to Check Before You Start
Microsoft documentation checked 7 min read
Jud Mackrill on Unsplash
Topics: SharePoint Development, SPFx, Microsoft 365, Power Platform
You need something built in SharePoint or Microsoft 365, and nobody on your team has the time or the skills to build it. Maybe it’s a dashboard, an approval process, or a connection to another system. Maybe it’s an old web part that stopped working after the person who wrote it left.
So you start looking for a developer. The hard part is telling a good one from a risky one before any money is spent. A general web developer can write good code and still build something that’s hard to deploy, asks for far too much access, or breaks the next time Microsoft changes something.
I’ve worked with SharePoint for more than 16 years, from the on-premises days to SharePoint Online, SPFx and the Power Platform. Below is what I’d want a client to check before hiring me or anyone else.
The short answer
- Decide first whether you need custom code at all. A lot of requests can be solved with built-in SharePoint features or Power Platform.
- Write down the problem, the users, the data and the licences before your first call. A good developer will ask about all of them.
- Ask how they handle permissions, deployment, updates and handover. The answers tell you more than a portfolio does.
- Start with a small, paid, clearly scoped first piece of work, not a large fixed project.
Do you actually need custom development?
Microsoft 365 gives you several ways to solve the same problem. The right choice depends on the requirements, licensing, security and who will maintain it:
- Built-in SharePoint features: lists, libraries, views, column formatting, pages and web parts that already exist. No code to maintain.
- Power Apps and Power Automate: forms, approvals and workflows that trained power users can change later.
- SPFx (SharePoint Framework): custom web parts and extensions, often built with React and TypeScript, for richer interfaces and deeper SharePoint integration.
- Microsoft Graph and Azure Functions: Microsoft Graph provides APIs for working with Microsoft 365 data and services. Azure Functions can run server-side automation and integrations that shouldn’t depend on a user’s browser.
A good developer will start by asking which of these fits, and will sometimes tell you that you don’t need them at all. If you’re weighing SPFx against Power Apps for an intranet, I’ve written a longer comparison of SPFx and Power Apps.
What to prepare before you contact a developer
You don’t need a full specification. One page covering these points will make the first conversation far more useful:
- The problem: what happens today, and what goes wrong. “Requests get lost in email” is more useful than “we need an app.”
- The users: who uses it, roughly how many, and whether anyone outside your organization needs access.
- The systems: where the data lives today (SharePoint lists, Excel, an ERP, a line-of-business database).
- Licences: which Microsoft 365 plans you have, and whether anyone has Power Apps premium licences. This can change the answer.
- Permissions: who should see what, and who in your organization can approve an app’s access to company data.
- The result you want: how you’ll know it worked.
- Who will support it: your IT team, an IT provider, or the developer on a support agreement.
Questions to ask a SharePoint or Microsoft 365 developer
These questions separate someone who knows the platform from someone who has only built websites.
“What would you use for this, and why?” Listen for an explanation of the options above, not one favourite tool used for everything.
“What access will your solution need, and who approves it?” When an SPFx solution needs additional API permissions, those requests are declared in its package. Deploying the package to the app catalog creates requests that an administrator with the appropriate role can approve or reject. Microsoft’s documentation notes that these grants aren’t isolated to the solution that asked for them: they’re shared with other SPFx solutions in your tenant. So a developer should ask only for what the solution needs, explain each permission, and be ready to justify it to your admins. For background apps, ask whether they can limit access to specific sites using Sites.Selected instead of access to every site.
“How will it be deployed?” SPFx solutions go into the app catalog. Ask whether it will be available to every site or only some, and who in your organization does the upload.
“What happens when Microsoft updates SPFx or Node.js?” SPFx versions support specific versions of Node.js and other tools, as listed on Microsoft’s SPFx compatibility page. A solution built today may need upgrades as its dependencies, development tools and support requirements change. A good developer will tell you that up front and plan for it.
“How do you handle large lists and heavy use?” SharePoint Online and Microsoft Graph throttle apps that send too many requests, returning errors that tell the app to wait and try again. Code that works with 50 test items can fail with 50,000 real ones.
“Where does the code live, and who owns it?” For custom work, the source should be accessible in your organization’s repository. Make sure the agreement clearly covers code ownership, third-party components and your right to maintain or extend the solution.
“What will we have when you’re done?” Look for source code, short notes on what was built and which permissions it uses, a deployment package with the steps to deploy it again, and a handover session for the people who will support it.
Red flags
- They suggest custom code before asking about the problem. Code that didn’t need to exist still has to be maintained.
- They ask for broad permissions with no explanation. “Just give it full control of all sites” should get a no.
- The code stays with them. If you can’t get the source, you can’t fix or move the solution without them.
- No testing or rollback plan. Ask how they’ll test it, and how they’ll undo a deployment that goes wrong.
- Nobody owns it after launch. If no one in your organization or at your IT provider knows how it works, the first problem becomes an emergency.
- A firm fixed price for complex work without understanding the requirements or dependencies. A reliable quote needs a defined scope, clear assumptions and an explanation of what’s excluded.
An example: a purchase request approval
This is a made-up example, but it’s a typical request.
A finance team wants staff to submit purchase requests, managers to approve them, and finance to see everything in one place. Before writing any code, a few questions change the design a lot:
- If the requests can live in a SharePoint list and approvals happen in Teams or Outlook, Power Automate may be enough.
- If the form needs rules a list can’t handle, a Power Apps form may be the next step, as long as the licences allow it.
- If finance wants a richer dashboard on their SharePoint home page, an SPFx web part reading that list could make sense.
- If approved requests must be written into the finance system automatically, an Azure Function using an app registration with limited access may be needed.
The same request could be a straightforward configuration job or a much bigger build. Asking these questions before quoting helps avoid paying for the wrong approach.
What a sensible first engagement looks like
For anything bigger than a small fix, I’d suggest a small, paid first step:
- Discovery: a short review of the problem, your environment, licences and permissions, ending with a recommended approach.
- One scoped deliverable: a single feature or a working first version, with agreed acceptance criteria.
- Clear responsibilities: who approves permissions, who deploys, who tests, and who signs off.
- Handover expectations: agreed up front, not at the end.
This keeps the risk low for both sides. You find out how the developer works before committing to a larger project, and the developer gets the information they need to give you a realistic plan.
If you’re looking for help
This is how I work on SharePoint and Microsoft 365 projects, from small fixes to complete solutions. You can see what I build, and some open-source examples, on my Microsoft 365 development page. If you specifically need SharePoint Framework work, see SPFx development.
Need an integration or automation your team can maintain?
I build Microsoft Graph, Azure Functions, SPFx, and Power Platform solutions with source control and documentation from day one, so your team can run them after handover.
Free SharePoint planning resource
Solving the technical issue is only part of the Microsoft 365 problem.
Use the checklist to review the governance, permission, ownership, and support decisions that often determine whether a SharePoint solution succeeds long term.
Download the ChecklistSharePoint architect & Microsoft 365 consultant • 16+ years of experience
If you have questions about your SharePoint environment, feel free to reach out.