# SharePoint intranet development: custom web parts and ERP data inside the Microsoft 365 you already pay for

A SharePoint intranet is a company portal built on SharePoint Online, inside the Microsoft 365 tenant the organization already licenses. Goldenroz develops the parts that configuration does not cover: web parts written in the SharePoint Framework (SPFx) with React and TypeScript, dashboards fed by the ERP, Power Automate flows and Microsoft Graph calls. The work is for organizations of roughly 100 to 2,000 employees and starts at $25,000 at a fixed price per phase. Goldenroz is an independent firm, not a Microsoft partner, and does not resell licences.

**From $25,000, fixed price per phase**

Updated: 2026-11-15. By Shai Goldenberg.

## What usually goes wrong

- **The built-in web parts stop short:** News, quick links and document libraries work out of the box. The page that should show open purchase orders or machine downtime has no web part that can do it.
- **ERP data lives behind the firewall:** The numbers managers want sit in SQL Server on the company network. SharePoint Online is in the cloud and cannot read them without a planned and approved path.
- **Flows built by one person:** Approval flows run under the account of an employee who built them. When that person leaves, the flows fail and nobody knows what they did.
- **Scripts pasted into pages:** Older customizations were added as embedded scripts. They break on updates and bypass the permission model.
- **A hired developer who left no source:** A previous SharePoint developer deployed a package to the app catalog. The source code is not in any repository you control.

## What is included

- **SPFx web parts:** Custom web parts and extensions written in the SharePoint Framework with React and TypeScript, packaged and deployed through your tenant app catalog.
- **Dashboards on portal pages:** Charts and tables for each role, placed on the pages people already open, with data filtered by the signed-in user.
- **ERP integration over REST APIs:** Where the ERP exposes a REST API, the web part or a small middle service calls it with a service identity. Each integration is scoped against the API that exists and priced as its own line.
- **SQL Server through the on-premises data gateway:** For data that stays on your network, Power Automate flows read SQL Server through the Microsoft on-premises data gateway and write the result to a SharePoint list the page displays.
- **Power Automate flows:** Approvals, notifications and document routing, owned by a service account, documented and with error handling.
- **Microsoft Graph and handover:** People, calendar, Teams and file data read through Microsoft Graph with the minimum permissions approved by your administrator. Source code is delivered in your repository with build and deploy instructions.

## What the SharePoint Framework is and when SPFx is the right tool

The SharePoint Framework, known as SPFx, is Microsoft's supported way to add custom code to SharePoint Online pages. A web part is written in TypeScript, usually with React, runs in the browser in the context of the signed-in user and is deployed as a package that a tenant administrator approves.

SPFx is the right tool when the page must show something SharePoint does not hold, such as ERP data, or when the interaction is more than a list view can give. It is the wrong tool when a list, a view and a flow would do the job. A good SharePoint developer writes as little custom code as the requirement allows, because every web part must be maintained when Microsoft updates the platform.

We state this plainly: Goldenroz does not present delivered SPFx projects as evidence. What Shai brings is four years of running IT at an industrial company with about 400 users, including Microsoft 365 in a hybrid setup with on-premises servers and Azure, licence management and Power Automate automations, together with production experience in TypeScript and React.

## SharePoint intranet examples: what the custom parts look like

Buyers who search for SharePoint intranet examples usually want to know what is possible beyond the template. Typical custom parts are a home page with a personal task and approval list, a procedures page that shows each employee which documents await their confirmation, a production or sales dashboard read from the ERP, a leave balance read from the HR system and a people finder with skills and locations.

Each of these is a mix of standard SharePoint lists, one or two flows and a web part for the display. Structure, permissions and migration are a separate discipline, covered by our [SharePoint consulting](https://goldenroz.com/sharepoint-consulting/) page. The page you are reading is about the development work that sits on top of a sound structure.

## SharePoint alternatives and when to leave the platform

SharePoint Online is a cloud service. If part of your content may not be stored in a cloud tenant, or if the portal is mostly live operational data with complex screens, a custom application is usually the better route. We describe it under [employee portal development](https://goldenroz.com/employee-portal-development/).

The opposite case is common too. A company that needs news, documents and a few forms should stay with configuration and skip custom code. Where a requirement would fight the platform, we say so before any code is written and price the alternative.

## What it costs

Every project is split into phases. Each phase has a fixed scope and a fixed price, agreed before work on it starts. Hosting, licences and third-party services are paid directly by you.

- Business system, first phase and smaller systems: From $25,000 (Fixed price per phase)
- Larger systems: $100,000 and up (Web, mobile and several integrations, scoped one phase at a time)
- Maintenance and support: Quoted separately (Agreed after launch, not required)
- Scoping call: $0 (One hour with Shai)
- Code ownership: Yours (Repository in your organization from day one)

## Who it is not for

- Organizations that need a certified Microsoft partner or references from delivered SPFx projects.
- An intranet that needs only news, links and document libraries. Standard SharePoint configuration covers it without development.
- SharePoint Server farms kept on-premises with classic customizations. We work on SharePoint Online.

## Questions buyers ask

### What is SPFx?

SPFx is the SharePoint Framework, Microsoft's development model for custom web parts and extensions in SharePoint Online, Teams and Viva. Code is written in TypeScript, runs in the browser as the signed-in user and is deployed through the tenant app catalog.

### How much does a SharePoint intranet cost?

Development work at Goldenroz starts at $25,000 at a fixed price per phase, quoted after a free one-hour scoping call. Microsoft 365 licences are bought by you directly from Microsoft or your reseller and are not part of our price. The main cost drivers are the number of custom web parts and the number of systems to integrate.

### SharePoint vs custom intranet: which should we choose?

Choose SharePoint when you already run Microsoft 365, the content is mostly documents and news, and cloud storage is acceptable. Choose a custom intranet when data must stay on your own servers, when the portal is mainly screens over ERP data, or when you want no dependence on a licence. Many organizations combine the two.

### Can a SharePoint intranet show data from our ERP?

Usually, if the ERP has a REST API or its database is SQL Server that we are allowed to read. Cloud APIs are called directly, and on-premises SQL Server is reached through the on-premises data gateway with Power Automate. We check each system during scoping before quoting.

### Are you a Microsoft partner?

No. Goldenroz is an independent firm, holds no Microsoft partner status and sells no licences. If your procurement rules require a certified Microsoft partner, we are not the right supplier.

### Is SharePoint good for an intranet?

For an organization already on Microsoft 365 it usually is: sign-in, permissions, search and document storage are in place, and news, pages and libraries need configuration and no code. It fits less well when the portal needs heavy custom screens, complex data entry or users outside the tenant, and that is where we price a custom build next to it.

### What is the difference between SharePoint and SharePoint Online?

SharePoint Online is the cloud service inside Microsoft 365, run and updated by Microsoft. SharePoint Server is the version an organization installs and runs on its own servers. This page is about SharePoint Online; content that must stay on site is handled in a hybrid design.

---
Page: https://goldenroz.com/sharepoint-intranet-development/
Book a free one-hour call: https://calendly.com/daniarozin/daniel-rozin-consultation-1-hour-clone
