Services / Web platforms

Web platforms built for year five.

Portals, marketplaces and operations software where many roles touch the same data. We design the data model first, so the fifth year is as easy to change as the first.

Is a custom platform the right call?

If two or more of these sound like you, off-the-shelf software is probably costing you more than it saves.

What we build

Six shapes of web work we deliver often. Every one of them is running in production for a client today.

Role-based portals
01

Role-based portals

Different dashboards, permissions and approval steps per role, on one data model.

Running at C2G by RLG, 13 stakeholder roles
Marketplaces
02

Marketplaces

Two-sided platforms with listings, offers, verification and award flows.

Running at Home Offerz
Operations tools
03

Operations tools

The admin software staff use all day: bookings, members, locations, reporting.

Running at Expansive staff portal
Real-time dashboards
04

Real-time dashboards

Live device or event data, alerts and history in one screen, pushed over WebSocket.

Running at E-Fire USA
B2B trading platforms
05

B2B trading platforms

Orders, pricing, documents and settlements between businesses across borders.

Running at Onion Trading Platform, Netherlands
Content platforms
06

Content platforms

CMS-driven sites with courses, help centres and an admin your team can run.

Running at Instahyre resources and LMS
Booking websites
07

Booking websites

Brand sites that take bookings: live room availability, packages and reservations.

Running at Puro Surf · Rose Nordic · Sedona Investing
Online stores
08

Online stores

WooCommerce and Shopify stores with the order types your business actually has.

Running at Channie's · Beaustre
Real-time collaboration
09

Real-time collaboration

Video, chat, shared documents and scheduling in one product.

Running at Xloon

Thirteen roles. One platform.

RLG runs e-waste collection and trading across India on C2G, the platform we have built and run since 2021. Collectors, recyclers, compliance staff and finance each see their own workflow. Approvals that used to travel by email now live in configuration.

2021Building since
13Stakeholder roles
2Platforms, web and mobile
Read the RLG · C2G case study →

How an engagement runs

The same people stay with you from the first workshop to launch day. No handoffs between strategy, design and engineering.

Weeks 1–2

Scope and architecture

Requirements workshop, data model and integration map, then a written fixed scope.

  • Stakeholder interviews
  • Data model and API design
  • Stack rationale in writing
  • Fixed-scope proposal
Weeks 2–4

Design and prototype

Wireframes and high-fidelity screens for the key journeys, clickable before anyone codes.

  • Information architecture
  • Design system foundations
  • Clickable prototype
  • Sign-off on flows
Weeks 4–14

Build in sprints

Two-week sprints with a demo at the end of each. You get a staging link from week one and direct access to the engineers.

  • Demo every two weeks
  • Continuous integration
  • Staging access throughout
  • QA alongside development
Weeks 14–16

Launch and handover

Production deployment, load testing, a 30-day warranty and the full codebase and documents in your name.

  • Production deployment
  • Performance and load testing
  • 30-day warranty
  • Code and documentation handover

Time and scope

10–20 weeks

Typical timeline

A focused MVP with login, roles and the core workflow ships in 10 to 14 weeks. Multi-role portals with several integrations run 16 to 24.

Roles, integrations, data

The number of user roles, the systems we connect to and how much existing data moves over decide the size. We map all three before quoting.

Scope in writing

Every engagement starts with a written scope and a week-by-week plan. Changes go through a change note, so nothing grows quietly.

What you can hold us to

Data model before screens

Most platform rewrites trace back to a data model nobody planned. We design it with your team first, then build the screens on top.

Security from the first sprint

Role-based access, audit trails and encrypted data at rest come by default. Our delivery runs under ISO 27001-certified processes.

Integrations that survive updates

ERP, CRM, payment and accounting integrations get their own adapters and tests, so an upstream change does not take the platform down.

AI-ready, not AI-washed

When a workflow benefits from document reading, matching or summaries, OMKA.AI plugs into the same platform. When it does not, we say so.

The stack

Picked during scoping, based on your systems and who will maintain the product after us.

Frontend

Server-rendered where SEO matters, SPA behind login.

ReactNext.jsTypeScriptTailwind

Backend

APIs, business rules and integrations.

Node.jsPHP / LaravelPythonGraphQL

Data

Chosen by access pattern.

PostgreSQLMySQLMongoDBRedis

Infrastructure

Sized to your traffic.

AWSDockerCloudflareCI/CD

Questions we get asked

Can you take over a platform someone else started?

Yes. We audit the codebase, document the technical debt and tell you plainly whether to continue or rebuild. Often the answer is to keep most of what you have.

Should we use Next.js or plain React?

Next.js for anything public-facing where search and load speed matter. Plain React is fine for internal tools behind a login. We decide in the scoping weeks, based on your needs.

Who owns the code?

You do, from the first commit. Repositories sit in your organisation or are transferred at handover, with documentation.

What does the 30-day warranty cover?

Defects in delivered code that make the product behave differently from the agreed scope. New features and third-party outages are outside it.

Do you support the platform after launch?

Yes, on an optional monthly retainer for fixes, small features and monitoring. Several of our clients have stayed on retainer for years.

Tell us what you
want to build.

You will speak with an engineer who has shipped this kind of work, and get a straight read on scope, timeline and whether we are the right fit.

Other practices

Mobile appsiOS and Android apps with the backend, admin and store release handled by the same team.AI and automationWe put AI inside the workflows your team already runs: reading documents, matching records, routing work and drafting replies.UI/UX designResearch, flows and high-fidelity screens in Figma that engineers can build without a follow-up meeting.Cloud and DevOpsCloud setup, deployment pipelines and monitoring that make releases routine.SEO, AEO and GEOSearch now has two front doors: Google results and AI answers.