Web Application Development - Django and React

Eighteen years of building software, seven of them on Upwork across 28 jobs and 1,686 billed hours, with a Job Success Score above 90% and full marks on 27 of those 28 jobs.

Work that is public and checkable: PLMIS, the Plastic Business Registration MIS for the Government of Punjab’s Environment Protection and Climate Change Department - React, Django and Postgres on Google Cloud, with an approval workflow, statuses and role-based access, live at plmis.epapunjab.pk. An air quality monitoring dashboard for the same department. This site and the AI product behind it are also mine, end to end.

What is harder to advertise: I write down what did not work. If an estimate is slipping you hear it that week, not at the deadline.

What's included in the package

Database design that survives year two

The schema is the decision you cannot cheaply undo, so it gets thought about first.

Django REST backend

Auth, roles and permissions, an admin your team can actually use, and an API documented enough to build against.

React and TypeScript front end

Typed end to end, so a change to the API breaks the build rather than production.

Deployment you own

Cloud Run, Docker, CI - handed over with the credentials and the runbook, not held hostage.

Tests where they earn their keep

On the money paths and the rules that matter, not a coverage number for its own sake.

How the installation goes

Agree what version one is

The most useful thing I do early is argue for a smaller first release. Half the features in a first spec are guesses about what users want.

Schema and API first

Data model, then endpoints, then screens. Building screens first is how a project ends up with a database that cannot answer the questions the business asks.

Ship weekly to a real URL

You see it deployed every week, not at the end. Written progress daily, including what did not work.

Harden, then hand over

Roles, backups, error handling, a runbook, and a walkthrough of the code with whoever keeps it after me.

Frequently asked questions

Can you take over a project someone else started? ▾

Often, yes - that is a large share of my Upwork work. First I read the code and give you an honest assessment, including if the right answer is to rewrite part of it. I would rather say that in week one than discover it in month three.

Do you work with our existing team? ▾

Yes. I have run a distributed team as a development manager, and I am comfortable as one contributor among several or as the person holding the plan.

What are your hours? ▾

Lahore, UTC+5, 30-40 hours a week. That covers the whole European working day, all of the Gulf, and five to six hours of overlap with US Eastern and Central.

PHP, Laravel, Node? ▾

I have shipped all three and still will. My deepest daily stack is Python with Django or FastAPI plus React and TypeScript, and I will say so rather than quietly bill you while I learn something.

Other things I build

AI Integration and RAG - Answers From Your Own Documents

Retrieval-augmented AI that answers from your documents and cites the page it used, or says it does not know. Built and run in production, not a demo.

Automation and Integrations - WhatsApp, Stripe, QuickBooks, Airtable

Connect the systems your business already runs and automate the work in between. WhatsApp Business API, Stripe, Twilio, QuickBooks, Airtable and Google Workspace.

Data Pipelines and BI - BigQuery, dbt, Power BI

Move your data somewhere it can be asked questions, and build the dashboards on top. BigQuery, dbt, Airflow, Power BI and Looker Studio, shipped for clients since 2019.

The work behind these is public: the AI product, its live demo, the cited answer pages it produces, and the research paper measuring it.