Web portals · Web applications · Websites

Custom web portals and web solutions

When a process outgrows spreadsheets and email, and no off-the-shelf tool fits it.

We build web portals and web applications for the work that happens outside your Microsoft 365 tenant - where customers, suppliers and field teams need to sign in, see exactly what they are allowed to see, and get something done.

A web portal is an application that runs in a browser. Your people, your customers or your suppliers sign in and see only what belongs to them: their orders, their documents, their numbers. Nothing to install, no licence per user, the same screen on a laptop and on a phone.

It is the same work we have been doing for years - data models, business rules, integrations - only the interface is a browser instead of Power BI or PowerApps. Which of the three is right for you is a question we answer before the offer, not after.

What we build

Customer and partner portals

Order status, documents, price lists, requests and approvals for people outside your organisation - who cannot be given a Microsoft 365 licence, and should not be given a mailbox full of PDFs either.

Internal web applications

Entry, review and approval screens for a process no standard product covers: production tracking, planning, registers, custom workflows. Built on your database, with roles and a record of who changed what.

Reporting portals

Power BI embedded in your own portal, behind your own login and row-level security, so a client or a branch sees their data and only their data.

Integrations and APIs

A portal rarely stands alone: ERP, Business Central, webshop, CRM, warehouse. We connect them over APIs and scheduled jobs, and write down in advance what happens when one of them is down.

Websites and landing pages

Corporate sites, product pages and campaign landings - static, fast, with content editing for your marketing team and without a stack of plugins that has to be patched every month.

Moving off WordPress

A migration where every old address still leads somewhere, so rankings and saved links survive. We did it to our own site: 32 known plugin vulnerabilities became zero, because there is no longer a server to break into.

Agentic coding: why this is faster than it used to be

Most of the code is now written by AI agents working inside our repository, against a written recipe - our standards for structure, SEO, GDPR, accessibility and speed. Architecture, code review and testing stay with our engineers. The agent is fast, but it is not accountable, so nothing reaches you unread.

What changes for you is not the technology. It is the schedule, and the cost of changing your mind:

  • A working first version in days, on your real data, instead of a deck of screens.
  • A change after delivery is a task, not a new project - so the site or portal keeps up with the business.
  • Every project follows the same written recipe, so quality does not depend on who happened to be free that week.
  • Code, repository, domain and hosting accounts are in your name from day one.

Technologies and tools

We keep the stack deliberately small and boring. Fewer moving parts is what makes a page load in under a second and survive a year without maintenance.

Front end and content
AstroTypeScriptReactGit-based CMS
Hosting and delivery
Cloudflare PagesCloudflare WorkersGitHubGitHub Actions
Data
Azure SQLSQL ServerMicrosoft FabricREST / OData
Integrations
Power BI EmbeddedPower AutomateDynamics 365 Business CentralMicrosoft 365

A static site has no server to attack and no plugins to patch. Anything dynamic - logins, data, writes - goes through APIs we control, not through a plugin somebody published three years ago.

How a project runs

  1. 1 Business brief
  2. 2 Structure and design
  3. 3 Data and integrations
  4. 4 Build
  5. 5 Testing and content
  6. 6 Go-live and handover

A website is measured in weeks, a portal in months - and both start with a version you can click through early, not at the end.

Web portal, Power Platform, or both?

This is the first thing we settle, because the wrong answer is expensive - in licences or in development days.

The right choice for internal work.

  • Users are your employees and already have Microsoft 365 licences.
  • The process lives close to SharePoint, Excel, Dataverse or Business Central.
  • Speed of delivery matters more than a bespoke interface.
  • This is our core business and, for internal apps, usually the cheaper answer.

The right choice when the users are outside.

  • Customers, suppliers, candidates or the general public - people you will not buy licences for.
  • The number of users is large or unpredictable, and per-user licensing stops making sense.
  • You need your own design, your own domain and pages Google can index.
  • The interface has to work on any device, with no app store and no tenant of yours.

In practice, the most common answer.

  • One database, two front ends: a portal facing outward, PowerApps and Power BI facing inward.
  • Business rules live in the database, so both sides answer the same way.
  • You avoid licensing external users and stay fast internally.

Only need a website? That has a brand of its own.

Not every job needs a portal. A craft business or a small company usually needs a fast, well-written site for a fixed price - so we built a separate brand for it, and the offer stays simple and honest on both sides.

Tell us what the process looks like today and we will say honestly whether it needs a portal, an app, or neither.

Get a quote
Microsoft
Certified Trainer & Data Analyst Associate
10+
Years with modern Microsoft tools
7+
Years with the Power BI environment
90+
Satisfied domestic & international clients
Get in touch

Request an offer

Tell us what you need and we'll get back to you shortly. We'll know your message is about Custom web portals and web solutions.

References

A selection of the domestic and international clients we have worked with.