Custom development · Fixed quote
Custom SharePoint web part development
Tell us what your intranet is missing. We clarify data sources, features and permissions, then provide a fixed quote with the agreed scope and schedule.
Describe your project and request a quote- 01
Describe your idea
A few sentences are enough — screenshots or sketches help.
- 02
Receive a fixed quote
Within 48 hours you get scope, price and timeline. No obligation.
- 03
Get your web part
Delivered as a .sppkg with deployment guide and 12 months of updates.
When does a custom SharePoint web part make sense?
A custom web part makes sense when standard components and ready-made products do not cover a specific workflow. Start with the information people need, the actions they should take and who may edit each record. We clarify those requirements before development begins.
What determines the development cost?
Cost depends on data sources, roles and permissions, interactions and edge cases. A read-only view of a SharePoint list is a different project from a multi-step approval workflow using Microsoft Graph. Describe your existing lists, required views and user actions. The fixed price and delivery schedule apply to the scope agreed in the proposal.
What will you receive?
Delivery includes an SPFx package (.sppkg) and instructions for deployment through the SharePoint App Catalog. The interface is designed for English and German and follows the SharePoint theme. Twelve months of updates are included. Data migration, additional integrations, a separate mobile app or an external service are included only when explicitly agreed.
Where do the web part and your data run?
Our default is a solution running inside your Microsoft 365 tenant. It uses SharePoint REST or Microsoft Graph with the intended permissions. There is no external Lyron application server for your business data and no built-in tracking. If a requirement calls for an additional service, we discuss it before you commission the work.
Who approves permissions and installs the package?
Your SharePoint administrator deploys the package through the App Catalog. Required Microsoft Graph permissions are documented and must be approved by an authorised administrator. Roles, data access and behaviour when consent is missing are part of the planning. A web part does not replace access controls on its data sources.
How is the solution checked before use?
We agree acceptance criteria for the relevant views, actions and failure cases. Plan a test on a SharePoint page using representative data and the intended user roles. Include empty lists, missing permissions and behaviour after publishing the page. Product updates arrive as new .sppkg versions for your administrator to install.
What should your request include?
Describe the purpose, user groups and data sources. Include two or three typical tasks, required filters, approvals and your preferred timeline. Sample data without personal or confidential information is sufficient for an initial assessment. Do not enter credentials or production customer data in the request form.
Could a ready-made web part already cover your needs?
Compare the existing products first. A phone book, leave planner or policy web part may already support your workflow. Each product page explains its features, limitations, permissions and one-time tenant price.
- Policy Acknowledgement Pro
Read policy PDFs in the web part, require acknowledgement per policy, and track exact revisions.
- Leave Planner Pro
Leave requests, approval by the Microsoft Entra ID manager, balances and a team absence calendar inside SharePoint — one price per tenant instead of per-user fees, and the data stays in your own lists.
- Phonebook Pro
Find a colleague. Make the connection. Phone-number search, personal favorites and contacts to take with you, right in SharePoint.