Opulence.
Web, Webshop & App Development

Web Applications & SaaS Platforms

Custom portals, dashboards and multi-tenant SaaS with authentication, billing and admin built in.

Large organisations often need software that doesn't exist yet: a customer portal, a partner platform, an internal tool that replaces spreadsheets or a product to sell. We build web applications with the foundations already solved, such as authentication, roles, billing, audit logs and admin, so effort goes into what makes the product yours.

Delivery is phased with rejection gates. Each phase ends in working software on a staging environment you can use, and the code lives in your repository throughout.

How we're different
  • Phases end in usable software, so you can stop, pause or change direction with something in hand.
  • Security review by our cybersecurity practice is part of the build, not a later audit.
  • Documentation and CI/CD mean an in-house team can take over without a cliff edge.
Who this is for
  • A bank, insurer or utility replacing a customer portal that was built a decade ago and is now a security concern.
  • A logistics or automotive group that needs a partner or dealer platform its existing vendors do not offer.
  • A corporate venture launching a software product to external customers under the group's name.
Signals you need this now
  • Critical operations run on spreadsheets and email that only a few people understand.
  • A vendor product covers most of the need and the gaps are becoming the business.
  • The current application is unmaintainable and the team that built it has gone.
  • Security or compliance review has flagged the portal and there is no plan.
Scope of work

What is included.

  1. 01

    Product specification

    User stories, data model, integrations and non-functional requirements agreed before build.

  2. 02

    Architecture

    Stack, hosting, multi-tenancy, security model and scaling plan.

  3. 03

    API and back end

    Documented APIs, background jobs and integrations with automated tests.

  4. 04

    Front end

    Accessible, responsive interface built from a component library.

  5. 05

    Platform features

    Authentication, roles, billing, notifications, audit and admin tools.

  6. 06

    Hand-over

    Documentation, CI/CD, monitoring and training for your team.

Method

Four steps, no surprises.

  1. 01

    Specify

    Workshops and prototypes to fix scope, data model and priorities.

  2. 02

    Architect

    Technical design, environment setup and a walking skeleton.

  3. 03

    Build

    Feature phases with tests, demos and acceptance at each gate.

  4. 04

    Release

    Security check, performance test, launch and hand-over.

How the engagement runs

From first meeting to steady state.

  1. 01Weeks 1 to 3

    Specification

    Workshops and prototypes fix scope, data model, integrations and non-functional requirements.

  2. 02Weeks 4 to 6

    Architecture and skeleton

    Technical design, environments, CI/CD and a walking skeleton through every layer.

  3. 03Months 2 to 5

    Feature phases

    Working software delivered in phases with tests, demos and acceptance at each gate.

  4. 04Month 6

    Release and hand-over

    Security test, performance test, launch and documentation for the team that takes over.

What we measure
  • Time from specification sign-off to first usable release on staging.
  • Task completion and error rates for the users the product serves.
  • Findings from the pre-release security test, tracked to closure.
  • Share of the platform documented and covered by automated tests at hand-over.
Who is on the engagement
  • Technical lead
  • Senior full-stack engineers
  • Product designer
  • QA engineer
  • Delivery lead
Deliverables
  • Product specification and data model.
  • Documented API and back end.
  • Front-end application.
  • Automated test suite and CI/CD.
  • Documented hand-over and training.
Engagement terms

Applications are delivered as fixed-scope phases following a specification sprint of two to three weeks. A first release typically takes three to six months. After launch, a retained team continues for features and support, or the platform is handed to in-house engineers with our support during transition.

FAQ

Web Applications & SaaS Platforms, in plain terms.

TypeScript across the stack with Next.js or Nuxt on the front end and Node.js or Python services behind, on Postgres. We choose differently where a requirement demands it.

Yes, after a technical review. We will say whether it is worth extending or better replaced in stages.

Threat modelling during specification, secure defaults in the platform features and a penetration test before major releases.

You choose: a retained team from us, a hand-over to your engineers or a mix. Either way, the code and infrastructure are yours.

Next step

Ready to talk about web applications & saas platforms?