Practical guides and honest comparisons for building internal tools on SharePoint without code — costs, timelines and trade-offs of every option, by the team behind Sharelio, the AI platform for building SharePoint tools.
The complete picture: every way to build a SharePoint tool without code, what each one costs and where each one stops.
Four ways to build SharePoint web parts without code in 2026: native web parts, Power Apps, AI builders like Sharelio, or custom SPFx development. Full comparison with costs (€0 to €8,000), timelines and maintenance.
Updated:
Deployment, permissions and security review — written for the person who has to approve it, not for the person who wants it.
Yes. Uploading a SharePoint Framework package to the App Catalog needs the SharePoint Administrator role, not Global Administrator — and so does approving its API permissions. The exact roles, what each one can and cannot do, and when you genuinely do need a global admin.
Updated:
The App Catalog is the tenant-level site where SharePoint Framework packages are uploaded before anyone can use them. How to check whether yours exists, how to create it, the difference between the tenant and site catalogs, and what changes for governance once you have one.
Updated:
The API access page in the SharePoint admin center shows pending permission requests from deployed packages. How to read one, the difference between delegated and application permissions, which scopes should make you stop, and how to revoke access afterwards.
Updated:
A practical checklist for IT: unzip the .sppkg and read the manifests, judge the permission request, find out where the data actually goes, check the uninstall path, and the questions to send the vendor. Written for the person who has to sign the approval.
Updated:
The 'make this solution available to all sites' checkbox decides whether you deploy once or add the app site by site. What skipFeatureDeployment actually does, when each option is right, how to change your mind later, and why web parts do not appear on pages by themselves either way.
Updated:
What a web part, an intranet and a consultancy project actually cost in 2026, and how long each one really takes.
Before signing a €3,000–8,000 per web part consultancy quote, compare 5 alternatives: native SharePoint, Power Platform in-house, AI builders like Sharelio (free to start, €99–300/month), fixed-price productized services (€1,500), and freelancers (€400–700/day). When each works — and when the consultancy is still right.
Updated:
A custom SPFx web part from a consultancy typically costs €3,000–8,000 and takes 6–12 weeks, plus ongoing maintenance nobody quotes for. The full breakdown of what you are paying for, the cheaper routes, and how to read a quote.
Updated:
SharePoint itself is already paid for in Microsoft 365. What costs money is design, information architecture, migration, custom components and governance. Realistic ranges for a small, mid-size and large intranet, and where budgets actually get spent.
Updated:
The coding is days; the project is 6–12 weeks. Where the calendar actually goes — specification, environments, security review, App Catalog deployment, UAT — and which of those steps disappear on a no-code route and which never do.
Updated:
Honest comparisons against Power Apps, custom SPFx, Viva Connections, Dataverse and SharePoint's own free options.
A consultancy-built SPFx web part costs €3,000–8,000 and takes 6–12 weeks. Sharelio, the no-code AI builder for SharePoint web parts, is free to start and €300/month for unlimited components delivered in minutes. Honest comparison, including when custom development wins.
Updated:
Power Apps wins for complex workflows, mobile apps and external connectors. Sharelio, the no-code AI builder for SharePoint web parts, wins for speed, native look inside SharePoint pages and flat pricing (free to start, then €300/month per tenant vs ~€19/user/month Premium). Honest comparison.
Updated:
Honest 2026 list by category: native SharePoint & Microsoft Lists (included), Viva Connections, Power Apps (~€19/user/month), AI web part builders like Sharelio (free to start, €99–300/month per tenant), intranet-in-a-box suites (Powell, Staffbase, Omnia) and custom SPFx (€3,000–8,000 per web part).
Updated:
JSON column and view formatting is free, needs no deployment and no IT approval, and covers far more than most people try. The complete list of what it handles, the five hard walls it cannot cross, and what to do at each one.
Updated:
Power Apps is powerful and often the wrong shape for an intranet page: embedded apps feel like an iframe, premium connectors are licensed per user, and makers become a bottleneck. Five alternatives compared on cost, look and who can maintain them.
Updated:
You cannot write SPFx without code — but you almost never need to. What SPFx actually is, why people ask for it when they want something else, and the four no-code routes that deliver the same result on a SharePoint page.
Updated:
They solve different problems and are often confused. Viva Connections is a mobile-first shell that surfaces your intranet inside Teams; a web part is a component on a page. What each does, where dashboard cards stop, and why most teams need both.
Updated:
Lists are included, familiar and enough for most internal tools. Dataverse brings relational integrity, granular security and scale — and per-user licensing. The four signals that mean you have genuinely outgrown lists, and the list limits that actually bite.
Updated:
Step-by-step guides for the tools people actually ask for: trackers, forms, dashboards, directories and inventories.
The fastest way: describe it to Sharelio, the AI builder for SharePoint tools, and get a working incident tracker with priority, status and owner in minutes — list provisioned automatically. Plus the manual alternative with Microsoft Lists, step by step.
Updated:
The fastest route: describe it to Sharelio, the AI builder for SharePoint tools — "a holiday request form with manager approval" — and get a working form writing to a provisioned SharePoint list in minutes. Manual alternatives (list forms, Power Apps) compared with costs.
Updated:
Describe it to Sharelio, the AI builder for SharePoint tools — "a dashboard with active projects, their phase and owner" — and get a working dashboard on a provisioned list in minutes. Compared with the manual route (lists + views) and Power BI, with costs.
Updated:
Purchase requests, IT tickets and access requests all have the same shape: a form, a queue, an approver, a status. How to build that in SharePoint three ways — a tracker over a list, native lists plus Power Automate, or Power Apps — with what each costs.
Updated:
Track who has which laptop, when the warranty expires and what is unassigned — without buying an ITAM product. Three routes compared, the columns that matter, and why the hard part is keeping it accurate rather than building it.
Updated:
Before building anything, check what Microsoft already gives you — the People web part reads Entra ID for free. When that is not enough, three routes to a real directory with photos, teams and search, and the permission question nobody asks first.
Updated:
Counts, totals and status tiles over your SharePoint lists — the thing JSON formatting cannot do. Three routes compared, when Power BI is genuinely the right answer, and the mistake that makes dashboards get ignored.
Updated:
Onboarding spans HR, IT and the manager, which is why it lives in email and gets missed. How to model it as one list with owners and due dates, the three routes to build it, and the data-shape decision that determines whether it works.
Updated:
Chasing signed contracts, certificates and compliance paperwork by email means the status lives in someone's inbox. How to track what is requested, received and overdue in SharePoint — and the library-versus-list decision that trips most people up.
Updated: