Web system

A customer or dealer portal over systems you already run

Customers or dealers get information by emailing someone in your office. That person looks it up in two systems and replies. It is slow, it does not scale, and it is invisible to management.

Where it comes up

  • Wholesale and B2B commerce
  • Professional services
  • Education and e-learning
Read those sectors

Constraints that usually apply

  • Pricing and entitlement logic is customer-specific and full of exceptions
  • The portal cannot become a second source of truth: the ERP or practice system stays authoritative
  • Some users will never adopt it, so the old channel has to keep working
  • External access means authentication, rate limiting and audit from the start

Stack

ASP.NET CoreAngularTypeScriptSQL ServerRedisERP and accounting APIsAzure

Architecture

  • Angular or Next.js front end, server-rendered where SEO or first-load speed matters
  • ASP.NET Core API as the only thing that talks to internal systems
  • Read model cached for catalogue and status data, with writes passed through to the source system
  • Identity provider integration, per-customer roles and record scoping
  • Structured audit log of every read and write against customer data

Illustrative interface, drawn to show the screens involved

summaryactivity

A realistic build timeline

  1. Weeks 1–2

    Flows, roles and the entitlement model written down and signed off.

  2. Weeks 3–4

    One flow through every layer, on a staging URL, against real integration endpoints.

  3. Weeks 5–10

    Remaining flows, pricing rules, notifications and admin tooling.

  4. Weeks 11–13

    Load test at your peak, security pass, pilot group live alongside the old channel.

Indicative only. Real dates come out of discovery, and they move when your side is short of time as often as when ours is.

What you own at handover

All of it, and from day one rather than at the end. If you replaced us mid-project you would lose momentum, not assets.

  • Repository and CI pipeline in your organisation
  • Environment and infrastructure definitions as code
  • API documentation and integration field mapping
  • Runbook for the failures worth planning for

Is this a real project? It is the kind of system we build. Here is exactly how we would approach yours.