Engineering culture

We would rather be right than agreeable.

Cortex Web Studios exists because too much software is sold by people who will not have to build it. Our architects scope the work and stay accountable for delivering it, which changes what gets promised in the first place.

140+

Specialists across nine hubs

2016

Operating since

4.9/5

Independently verified client rating

Operating principles

Five commitments we are willing to lose work over

Honest counsel first

If configuring existing software costs less than building, we say so — even when building is the larger invoice. Being trusted over years beats winning one engagement.

Architects, not account managers

The person who scopes your work is accountable for shipping it. There is no handoff between the promise and the delivery, because that handoff is where projects go wrong.

You own everything

Source code, infrastructure definitions, design files, accounts and data transfer to you. We build no proprietary runtime that would make leaving expensive.

Evidence over assertion

Baselines are measured before work starts, so improvement claims are verifiable. A percentage without a starting number is marketing, not engineering.

Senior people, actually

We staff with senior engineers rather than fronting a principal and delivering with juniors. Our margin is lower and our rework is close to zero.

Security is not a phase

Threat modelling, access control and audit trails belong in architecture, not in a remediation sprint after a failed review.

Leadership

Who runs the practices

Each discipline is led by a practising engineer or designer who still reviews work, rather than a manager who has stopped building.

Adnan Rehman

Chief Technology Officer

Twenty years across distributed systems and platform engineering. Owns architecture governance and the technical standard every engagement is held to.

Sarah Keating

Head of Product Design

Leads research, design systems and accessibility practice. Believes most product problems are unresolved strategy problems wearing a UI costume.

Maryam Hussain

Director of AI Engineering

Applied machine learning and retrieval systems. Insists on an evaluation harness before anyone writes a prompt.

James Okonjo

VP Cloud & Reliability

Runs the platform and SRE practice across nine hubs, including the follow-the-sun on-call rotation and reliability engineering standard.

Technology

What we build with, and why it is boring

We deliberately choose mainstream, well-supported technology. Exotic tooling creates a hiring problem for you and a dependency on us — neither serves you well.

TypeScript Python Go Swift Kotlin Java Node.js Dart

Next.js React SwiftUI Jetpack Compose Flutter Django Spring Boot FastAPI

PostgreSQL Aurora Redis Kafka Elasticsearch pgvector Pinecone Supabase

AWS Google Cloud Azure Terraform Kubernetes Docker ArgoCD GitHub Actions

LangChain LlamaIndex PyTorch OpenAI API Gemini API Hugging Face n8n Temporal

Figma Storybook Google Analytics 4 HubSpot Klaviyo VWO SEMrush Hotjar

How we engineer

A four-stage accelerated lifecycle

The same sequence on every engagement, whether it runs six weeks or two years. Each stage has an exit condition, so nobody discovers a disagreement in month four.

STAGE 01

Discover

We map the business outcome, constraints and existing estate before proposing anything. Discovery ends with a costed plan, not a sales deck.

1–3 weeks

STAGE 02

Architect

Rendering strategy, data model, integration contracts and the non-functional requirements are settled and documented as decision records.

2–4 weeks

STAGE 03

Execute

Fortnightly increments against a visible backlog, with working software demonstrated every cycle rather than status reported.

6–24 weeks

STAGE 04

Scale

Load testing, observability, runbooks and knowledge transfer — then either you take it in-house or we operate it under an SLA.

Ongoing

Clutch verified 4.9/5

What working with us is like

Reviews collected independently from named client contacts after project completion.

The replatform paid for itself in the first quarter. What I did not expect was how much faster our own engineers started shipping once the architecture stopped fighting them.

Marcus ElleryVP Engineering, industrial marketplace

They told us to cut a third of our ad spend. Pipeline went up the following month. That conversation changed how we budget for growth entirely.

Priya RaghunathanChief Marketing Officer, B2B SaaS

Our crews stopped carrying paper. Job closeout went from next-day to before they leave the site, and the margin recovery on change orders alone justified the build.

Khalid Al-MansooriChief Operating Officer, field services

Claims intake used to be twelve people reading PDFs. Now it is two people handling exceptions, and accuracy went up rather than down.

Layla HaddadHead of Claims Operations, insurance group

We deploy forty times a week now. Two years ago it was a scheduled event with a rollback plan and a prayer. The cultural change was bigger than the technical one.

Tomas LindqvistVP Platform Engineering, fintech

Support tickets asking 'how do I' dropped by two thirds after the redesign. That was the entire business case, and they hit it in twelve weeks.

Anita ChowdhuryDirector of Product, logistics platform

Eleven regional systems became one. We close the month in two days instead of three weeks, and I finally trust the numbers I present to the board.

Robert NkemeluGroup CIO, logistics

The rebrand was the reason our Series A deck got read. Investors told us it looked like a company twice our size, which was exactly the point.

Sara BenaliCo-founder, proptech platform

They recommended we buy rather than build for two of the three systems we asked about. That honesty is why we gave them the third one.

Daniel FosterCTO, healthcare provider

Answers

About the studio

Around 140 people across nine hubs, with the majority of engineering capacity in Lahore, Islamabad and Karachi. We staff engagements with senior people rather than fronting a principal and delivering with juniors.

Architects run engagements, not account managers. The person who scopes your project is accountable for delivering it, which removes the gap between what was sold and what gets built — the single most common cause of agency disappointment.

Regularly. We have advised clients to buy off-the-shelf, to delay a rebuild, and to stop funding a channel we were being paid to run. Long retention is worth more to us than any single project.

As a phase, not an email. We use mainstream technology, document architecture decisions in your repository, pair with your engineers during the build, and run structured handover sessions before the engagement closes.

ISO 27001 certified and SOC-2 Type II aligned, with annual penetration testing of our own systems. Client-specific requirements — HIPAA, PCI-DSS, PDPL, CITRA — are implemented and evidenced per engagement.