Web Platforms and Portals
Websites and portals that load quickly, work for everyone and keep changing with the business.
Why It Matters
A website is often built once and then left alone. Content, prices and services move on, but the site does not. The team then works around its limits or starts again.
Portals and public services carry more risk than a brochure site. A slow page loses a customer, a form that fails blocks a payment, and an inaccessible screen excludes people who need the service.
What We Do
Customer and Partner Portals
Secure places where customers and partners check orders, pay and update their details without calling.
Public Sector E-Services
Forms and services people can complete without calling or visiting an office, with a clear save and return path.
Front Ends and Design Systems
Shared parts and front-end code that keep every page consistent and cut the cost of the next one.
Multilingual and Right-to-Left Sites
Sites that read naturally in each language and direction you serve, including right-to-left scripts.
What Changes for You
Every Visitor Can Finish the Task
Pages load on a slow connection and work on a phone, a keyboard or a screen reader.
The Site Stays Current
Staff publish content and change services without a release project, while the design stays consistent.
New Services Arrive Safely
Shared parts and automated checks let you add a service without breaking the pages people rely on, and a failing check stops the release.
How the Work Runs
The work moves in releases, and each release serves a real audience. You see the site on a phone and a slow connection before it goes live.
Discover
We agree the audiences, the tasks and the first release. We review the current site, its traffic and the support requests it creates. You give us access to users, analytics and brand rules, and you decide the first audience to serve.
Design
We map each task and test a prototype with real users. You approve the content model and the structure, and you decide which content moves across and which can be retired.
Build
We build the pages, forms and content tools in short cycles. Every part is checked on a phone and a slow connection. You review each release and decide what goes live.
Hand Over
We document the parts, train your editors and stay after launch. Editors get a written guide to the pages and forms they own. You decide who owns content and support.
Team and Engagement Options
Pick the team that fits the service and your own staff. The scope, editors and support owners are agreed before work starts.
A Product Team
A web team that stays with the service and learns your content and audiences. It handles design, build and improvements.
A Fixed Scope
A defined site or portal with the result and date agreed first. You approve any change in writing before it is built.
Team Extension
Our front-end and back-end engineers join your team. They follow your standards, reviews and release process.
Platforms and Technologies
We build on the cloud and tools your web team can support. The sites run on the cloud you choose, such as Google Cloud, AWS or Microsoft Azure. TypeScript is a programming language, React and Next.js build the front end, and Node.js runs services. PostgreSQL stores data, Figma is the design tool, and WCAG is the accessibility standard we test against.
- Languages
- TypeScript
- Frameworks
- React
- Next.js
- Node.js
- Databases
- PostgreSQL
- Cloud
- Amazon Web Services
- Microsoft Azure
- Design and accessibility
- Figma
- WCAG 2.2
Naming a product does not mean a partnership with its vendor.
Industries
Education and Workforce Upskilling
EdTech platforms, serious-training simulations and national workforce upskilling academies, built accessible and in the learner's language.
Public Sector
Citizen portals, case management, payments and integrations with government registries, designed to recognised accessibility guidelines.
Retail and Omnichannel Commerce
POS integration, stock and price sync, card payments, loyalty and e-commerce for retailers with many sites.
Questions
What buyers ask before they rebuild a site or portal.
How do we start a new site or portal?
We agree the people to serve, the tasks that matter and the first release. You give us access to users, content and systems, and we return a written scope. The first release goes live when you approve it.
How long does a site take?
The scope, content and integrations set the pace. A large portal is split into releases, so value arrives before the whole site is finished. Content, approvals and third-party systems are the usual causes of delay. We agree the first release before work starts and show progress every cycle.
What makes a site cost more?
The number of audiences, languages and services, plus the systems we connect. Content migration and accessibility work add effort. We set the first release and its effort before you commit.
Do we own the site and its content?
Yes. You own the code, the content and the design files. Your editors can publish without calling us. Any capable team can continue the work.
How do you make a site accessible?
We design to the accessibility standard from the first screen. Each release is checked with a keyboard and a screen reader, not only by a tool. People with different needs test the tasks that matter most.
Tell Us What You Need to Run, Build or Secure.
Describe the service, the systems and the pressure you are under. The right team takes it from there.