origen.
Origen / Services / Web SaaS · Platforms Vol. V · 2026

Web apps that hold up
when the user count does.

03.3 / Web

SaaS products, dashboards, and the internal platforms a business actually runs on — React or Angular, Firebase or AWS, chosen for your product rather than our résumé. Senior engineers build it, tests go in from the first commit, and the same people are still available when something needs changing in year three.

All four disciplines →
§ 01

What we build

Three shapes

Three kinds of web build, and the boring half of each one is scoped in from the start.

Build 01

SaaS products

Multi-tenant products with accounts, roles, billing, and an admin side your own team can run. The unglamorous half is where most SaaS builds come unstuck, so we scope it first.

Accounts · Billing · Admin
Build 02

Dashboards and data

Interfaces that make a complicated dataset legible — and fast enough to actually use. Charts people trust, exports that match them, and queries that stay quick as rows pile up.

Data viz · Reporting
Build 03

Internal platforms

The systems your operation runs on: field capture, workflow, approvals, integrations with whatever is already in place. Rarely glamorous, usually the highest-leverage software a business owns.

Workflow · Integrations
§ 02

How we work

Decisions, made deliberately

The expensive decisions in a web platform get made in the first three weeks. We make them on purpose.

01

The data model first

Tenancy, permissions, and the shape of your core records are the decisions you cannot cheaply undo. We settle them early, write them down, and tell you plainly which trade-offs we are deferring and what revisiting them would later cost.

Postgres · MongoDB
02

Boring, automated deploys

Continuous integration, preview environments, and a release that is a non-event rather than a Friday-afternoon risk nobody wants to own. If shipping is frightening, the team ships less, and the product stalls.

CI/CD · Preview envs
03

Readable by whoever inherits it

One day someone else will open this repository — a new hire, another partner, an acquirer’s technical reviewer. We write for that reader: conventional structure, real tests, and documentation kept current as we go rather than assembled at the end.

Tests · Docs
§ 03

Proof

Three from the shelf
Case 01

CreditNature — a measurable market for nature

Web platform · Data viz

The NARIA platform for a UK climate-fintech: turning ecological measurement into portfolio-grade data investors can act on.

ReactData vizPlatform
Read the case
Case 02

Right Now Response — repairs, coordinated in real time

Web · Realtime

A unified coordination platform where jobs, contractors, and status updates all stay in sync — the operational core of the business.

RealtimeWorkflowWeb
Read the case
Case 03

AgriLogiq — farm data, finally legible

Dashboards · Analytics

Analytics dashboards that turn scattered agricultural data into something a decision can be made from.

DashboardsAnalyticsData
Read the case
§ 04

Common questions

Straight answers

What do you build web apps with?

React or Angular on the front, Firebase or AWS underneath, Postgres or MongoDB for data. The choice follows your product and your team, not our preferences — if you already run Angular and Postgres, we do not arrive and insist on a rewrite.

Can you build the whole SaaS, including billing and admin?

Yes, and the admin side is usually where projects quietly fail. Subscriptions, plan changes, refunds, failed payments, tax, and an internal back-office your own team can actually operate — all of it is scoped in from the start rather than bolted on before launch.

Will it scale?

It will scale to where you are actually going, which is the honest version of that answer. We build for a realistic twelve-to-eighteen-month load with the expensive decisions — data model, tenancy, background work — made deliberately, and we tell you which ones we are deferring.

Do you work with an existing codebase?

Frequently. We audit what exists, write you a memo on what is worth keeping, and pick up from there. If your build has stalled or a vendor has gone quiet, the project rescue page describes how a takeover runs.

How do you handle data protection for UK and EU users?

Region-appropriate hosting, encryption in transit and at rest, least-privilege access, and an audit trail on the things that need one. We are engineers rather than your DPO, so we build to the requirements your counsel sets — and we raise it early, not at launch.

How do you price a web build?

After scoping, not before. The brief asks for a rough budget band so we can tell you early whether the scope and the number are in the same neighbourhood — and we will say so plainly if they are not. What you get back is a real figure against a defined scope, not an hourly rate to multiply.

Got a platform to
build?

Tell us what you’re building — it goes straight to Harley and Jonathan, and we reply within 24 hours. Already mid-build and behind? A rescue starts with an audit.