AvailableTaking on new platform builds

I build platforms that run businesses.

I'm Sannan Malik, a full-stack engineer. I design, build and run multi-tenant SaaS end to end: product, backend, web, mobile and the production server. One person, no handoffs.

RemoteReplies within 24 hoursUS · EU · GCC · South Asia
6Platforms live in production
4Industries: health, fintech, education, AI
3Languages shipped, including right-to-left
1Person from schema to server

Selected work

Case studies

Whole platforms, not pages. Each one is designed, built, deployed and operated by me.

HealthOS 24Healthcare ERPMulti-tenantKSA compliance
Live

A hospital ERP that runs OPD to finance across many hospitals and branches, in three languages

OPD, IPD, pharmacy, lab, radiology, billing, HR and finance in one multi-tenant platform. It's built for Saudi regulations (ZATCA e-invoicing, NPHIES insurance, Wasfaty e-prescriptions, Nafath identity) with a full English, Arabic and Urdu interface.

Role
Architecture, full build, hosting
Stack
React · NestJS · PostgreSQL RLS · Redis · MinIO
Hard part
Tenant isolation enforced in the database
MeridianAgentic AISaaSSEO
Live

An AI-agent platform that runs the whole SEO lifecycle, with a human approving each change

It connects a website and covers every step: crawl and audit, Search Console and GA4 data, competitor and keyword research, strategy, content and publishing. AI agents do the work, and nothing goes live until a person approves it in the command centre.

Role
Product, architecture, full build
Stack
Next.js · NestJS · PostgreSQL · Redis · LLM agents
Hard part
Safe agent autonomy with approval gates
Pakistan Tech ForumEventsFlutterTwo portals
Live

One backend for a mobile app, a member portal and an admin portal that manage international delegations

A Flutter app for delegates, a portal for members and companies, and an admin portal for organisers, all sharing one API and one design system. It handles events, delegations, payments, refunds and networking.

Role
Mobile, web, API, deployment
Stack
Flutter · Next.js · NestJS · Prisma · PostgreSQL
Hard part
Three clients, one source of truth
FintechWhite-label

Forex Broker OS

A back-office for brokers in which each broker's domain decides who can sign in. Access is denied by default, sessions are checked against the database on every page, and every change is protected against cross-site request forgery.

EdTechAndroid

Skool21

A school platform: a Next.js web app, a realtime API, a media library with direct secure uploads, and an Android app with its own release pipeline.

TelemedicineRealtime

AskDoc

Patient and doctor apps with an admin panel. It covers bookings, earnings, large medical-file uploads, and realtime chat and calls.

Proof, not promises

What I've shipped

01

Live, not mockups

Every platform above serves real users on infrastructure I set up and look after myself.

02

Regulated industries

Healthcare with Saudi government integrations, and fintech where security can't be skipped.

03

Web, mobile and AI

React and Next.js, Flutter and Android, and LLM agents. Whatever the product needs.

04

Built for other languages

Arabic and Urdu right-to-left layouts, translated end to end, not added as an afterthought.

How I help

From an idea to a platform
that runs.

Multi-tenant SaaS, built properly from day one

Tenants, roles, billing and audit trails are designed into the data model from the start, not patched in later. You get a codebase you own and a deployment that's already running.

  • Architecture and data model
  • NestJS / Node APIs on PostgreSQL
  • React / Next.js web apps
  • Authentication, roles, permissions and tenant isolation
  • Payments, government and third-party integrations
  • Production deployment and monitoring

How it works

From brief to production

  1. Scope

    Users, flows, data and the riskiest unknowns, written down and agreed with a fixed quote.

  2. Prototype

    A clickable, coded prototype so decisions get made on something you can actually use.

  3. Build

    Weekly releases to a live staging site. You test the real product, not screenshots.

  4. Launch & run

    Production launch, monitoring and handover docs. I stay on for whatever comes next.

A note from me

One engineer.
Build and run.

Most platforms fail in the gaps: between the designer and the developer, the developer and DevOps, or the agency that built it and the team that has to run it.

I take those gaps out. I design the data model, write the API, build the web and mobile apps, and deploy them to servers I manage. The person who scoped your project is the one fixing it at 2 AM.

That's why my clients' platforms are in production and not stuck in staging.

Sannan MalikFull-stack engineer

The honest comparison

Why one engineer, not a team?

Working with meAgencyOffshore team
Who builds itThe senior engineer you spoke toJuniors, after the sales callVaries by who's assigned
After launchSame person runs and fixes itA separate support contractUsually you're on your own
HandoffsNone. Design, code and servers are one jobDesign to dev to DevOpsYou manage them
CostFixed quote, agreed up frontRetainers and change ordersCheap until rework piles up
CommunicationA direct line, no account managerThrough an account managerTimezone roulette

The stack I ship with

Tools

TypeScriptReactNext.jsNestJSNode.jsPostgreSQLPrismaRedisMongoDBSocket.IOFlutterAndroidMinIO / S3CaddyClaudeOpenAI

FAQ

Questions, answered

What kind of projects do you take on?

Platforms with real business logic: multi-tenant SaaS, ERPs, marketplaces, booking systems, internal tools and AI products. If it needs a database, user roles and a server, it's a good fit.

Do you only build, or do you also host and maintain?

Both. I can deploy to your cloud or run it on infrastructure I manage, with monitoring, backups and ongoing fixes.

How do you price?

A fixed quote agreed before work starts, based on a written scope. If the scope changes, we agree the change in writing before I build it.

Can you take over an existing codebase?

Yes. I start with an audit of the code, security and infrastructure, then a plan to stabilise it before adding features.

Will I own the code?

Yes. Everything lives in your repository from day one, with documentation for whoever works on it next.

How do we start?

Book a call or send an email describing what you're building. You'll get a written scope and a fixed quote.

You've reached the end, so…

Tell me what you're building.

I'll come back with a scope, a timeline and a fixed quote.

Book a call hello@sannanmalik.com