Partner programme
Deliver SharePoint web parts in days, and stop owning the code
This page is for Microsoft 365 consultancies, CSPs and implementation partners — the people who quote €3,000–8,000 for a custom SPFx web part and then carry it for years.
Sharelio is a rendering engine your client installs once. You keep the relationship, the delivery and the invoice; what you stop keeping is a bespoke codebase that has to be rebuilt every time Microsoft moves the framework.
The real cost of a bespoke web part is not building it
Everyone in this business knows the first project is profitable and the fifth one is not. The margin does not disappear in the build — it disappears afterwards.
- The framework keeps moving. SPFx versions, Node versions, gulp replaced by Heft, domain-isolated web parts retired outright in April 2026. Every one of those is unpaid work across every client you ever delivered to.
- Every client is a fork. The same tracker built five times is five repositories, five build pipelines and five things that break on different days.
- The developer who wrote it leaves. And the code is now a liability with your logo on it.
- Small requests are unsellable. A client wants one extra column. It is two hours of work and a €600 invoice nobody wants to send or receive.
What changes
| Bespoke SPFx | On Sharelio | |
|---|---|---|
| Time to first delivery | 6–12 weeks | Days |
| What you maintain | A codebase per client | Nothing — one engine, versioned by us |
| Framework upgrades | Your problem, on every project | Ours, once, for everybody |
| A change request | A quote, a sprint, a deployment | A configuration change, live immediately |
| Your client's security review | Your custom code, audited from scratch | One package with a published dossier |
| Where your margin comes from | Billable hours | The relationship and the recurring subscription |
What you get
- Multiple tenants from one account, so you can work across your client base without a login per customer.
- Your client's branding: components inherit the tenant's own theme, and each organisation can carry its own brand preset.
- A security dossier you can forward. The package manifest, the permission list and the subprocessors are published at sharelio.com/security. You do not have to answer your client's IT department alone.
- An installation page written for their administrator, so the deployment conversation does not consume your project hours.
- Commercial terms agreed with you, not published here. They depend on volume and on who invoices the end client — that is a conversation, not a price list.
The obvious objection, answered
You have seen that we sell a done-for-you web part at €1,500, and you are wondering whether we are your supplier or your competitor.
Fair question, and the honest answer is: that service exists because we needed real projects to build the product against, and it is deliberately narrow — one component, fixed scope, no discovery, no change management, no integration work, no relationship. It is the floor of the market, not the market.
What we do not have is your client. We are not going to run their intranet programme, sit in their steering committee or know why their approval process is the way it is. If that is what you sell, we are not competing — and the price you have just seen is the anchor that makes your quote look reasonable, not the one that undercuts it.
What we are not asking you for
- No exclusivity. Keep building bespoke where bespoke is the right answer.
- No certification, no fee, no minimum volume.
- No public commitment. You do not have to announce anything, and you do not have to tell your client whose engine it is if that is not how you work.
What we do want is one real project, with a real client and a real deadline, and your honest verdict afterwards.
How it starts
- A conversation. Thirty minutes. You tell us what you deliver today and what it costs you; we tell you where Sharelio does and does not fit.
- A pilot. One component, one of your clients. We are on it with you — this is the part where we over-deliver, because your second project depends on it.
- Terms. Once we both know what the work actually looks like, we agree the commercial side with numbers instead of guesses.
What partners ask
Can we resell it under our own brand?
Components inherit your client's own SharePoint theme and each organisation can carry its own brand preset, so what the end user sees is their intranet, not our product. How the commercial relationship is presented — your invoice or ours, your name or ours — is exactly the kind of thing we agree in the conversation rather than fixing on a web page.
Do we have to be a Microsoft CSP?
No. Any consultancy, integrator or freelancer who delivers SharePoint work can start. Being a CSP matters for how billing flows to the end client, and that is worth discussing, but it is not a requirement to run a pilot.
What happens to the components we built if we stop working with you?
The data was never ours: it lives in your client's SharePoint lists and stays there. The components stop rendering, because the configuration is served by us. Nothing is deleted, nothing is held hostage, and the package uninstalls cleanly from the App Catalog.
Our clients' IT departments are strict. Is that a problem?
It is usually where we win. One standard SPFx package, a single delegated read-only permission, no Microsoft Graph access and no custody of their data is a much shorter security review than bespoke code written by a supplier. The full dossier is public so you can send it before the meeting.
Can we get access to try it before talking to anyone?
Yes. The free plan needs no sales conversation and no card, and the installation page and security dossier are public. Talk to us when you want to run something with a real client.
Let's talk
Tell us what you deliver today. We reply personally, and the first conversation is about whether this fits you at all — not a pitch.