ACCEPTING PROJECTSOPEN

$ ./connect.sh

Contact

06 / 06

Have a product to build, a system to scale, or a hard engineering problem? Let's connect.

> PRIMARY CHANNEL

$ ./connect.sh --help

Engagements I take on:

  1. --01SaaS and software product development, MVP to full platform
  2. --02REST APIs and backend architecture
  3. --03Database design (PostgreSQL, MongoDB, MySQL)
  4. --04Deployment on AWS
  5. --05Third-party integrations (payments, auth/SSO, accounting APIs, CRMs)
  6. --06Performance fixes and rescue projects
  7. --07GenAI features built into real products
  8. --08RAG systems over your own documents and data
  9. --09Agentic workflows, tool calling and custom MCP servers
  10. --10Custom web apps, back end to front end (React, Node.js, NestJS)

How a project starts

  1. Define the problem

    Start with what has to be true when the work is done: who it is for, the constraints, and what already exists. Scope comes before architecture.

  2. Agree the architecture

    Data model, services and where the work runs, agreed before the build starts, so trade-offs are made on purpose rather than discovered later.

  3. Build and deliver

    Separate development, test and production environments with CI/CD, so every release is tested before it reaches users — working directly with you throughout.

Questions

Where are you based?
Lahore, Pakistan, on UTC+5.
Do you take contract or freelance work?
Yes. I have taken on independent client engagements since October 2024, alongside my role at 10Pearls, and I am currently accepting projects.
Can you work on an existing codebase?
Yes. Performance fixes and rescue work on existing systems are part of what I take on, and my current role is building and maintaining production services on AWS.
Can you add AI features to an existing product?
Yes: LLM-backed features, RAG over your own documents and data, and agentic workflows with tool calling and custom MCP servers — built in Python and run like any other backend service, with budgets for cost and latency.
What should I include in a first message?
What you are building, who it is for, what exists today (codebase, stack, hosting), and any deadline. A few sentences is enough to start.