Skip to content
Gaurav Nagpal
Open to new projects

Mohali, India · IST · UTC+5:30

Full-stack developer, AI builder & technical lead

I turn complex
ideas into
products that work.

Ten years building SaaS products, AI features and automation. Independent, hands-on — from the first conversation about the problem to the system that solves it.

Working with founders and agencies across Australia, Canada, the UAE and the UK.

Five things that have to agree before software is any good. Touch or focus one.

01/Proof

Proof, not promises.

UpworkVerified on Upwork
Upwork rating
5.0

Across 11 reviews

Contracts delivered
15

Long engagements, not one-off tickets

Hours tracked
2,651

Billed through Upwork

Years building
10+

PHP and JavaScript ecosystems

UpworkFigures from the Upwork profile — contracts, hours and feedback recorded by the platform.

02/What I build

Four capabilities,
one engineering practice.

Not separate services — parts of the same job: understand the problem well enough to build what actually solves it.

AI that earns its place in the product.

I start from the task someone is actually doing, then decide whether a model belongs — and where it needs a guardrail, fallback or human in the loop.

  • OpenAI
  • Anthropic
  • Gemini
  • RAG
  • Tool calling
  • Assistants grounded in your own content
  • Structured outputs downstream code can trust
  • Tool calling and retrieval wired into existing systems
  • Clear cost, latency and failure behaviour before launch

05/Open source

Small tools. Real problems. Publicly available.

Two WordPress plugins on WordPress.org. Gaps in other people's software, closed properly and maintained in the open.

WordPress

WordPress.org · v2.3.6

Attributes Coupon for WooCommerce

WordPressWordPressWooCommerceWooCommerce

Extends WooCommerce coupons so store owners can restrict discounts by product attributes and tags — inside the coupon screen they already use.

  • Restrict coupons by attribute or tag
  • Uses the existing coupon restriction panel
  • Works with simple and variable products
  • Combines with standard WooCommerce coupon rules
  • Percentage or fixed amount
Active installs
200+
Rating
5.0 from 12 reviews
Status
Maintained since 2016
WordPressExplore on WordPress.org

Coupon restriction

WordPressWooCommerce

attribute = Colour: Sand OR tag = Summer

  • Linen shirt

    Discounted
    • Colour: Sand
    • Tag: Summer
  • Wool overcoat

    Full price
    • Colour: Charcoal
    • Tag: Winter
  • Cotton tee

    Discounted
    • Colour: Sand
    • Tag: Summer
  • Leather boots

    Full price
    • Material: Leather
One rule, applied across the catalogue by attribute and tag
  • PHP
  • WordPress
  • WooCommerce
  • WPML / WCML
WordPress

WordPress.org · v1.1.0

GNX Workflow Sync

WordPressWordPressClickUpClickUp

Connects WordPress publishing to ClickUp. Choose post types and lists — tasks follow the content lifecycle.

  • Creates ClickUp tasks when selected post types are published
  • Updates linked tasks when content changes
  • Deletes linked tasks when content is trashed
  • Due date and priority from the editor
  • Optional backfill for existing published content
Rating
5.0 from 2 reviews
Status
Released 2026
WordPressExplore on WordPress.org
  1. 01WordPress

    WordPress content

    Post, page or custom post type

  2. 02

    Publishing event

    Published, updated or trashed

  3. 03

    Sync logic

    Maps content to a ClickUp list

  4. 04ClickUp

    ClickUp task

    Created, updated or removed

WordPressContent lifecycle in WordPress drives the task lifecycle in ClickUpClickUp
  • PHP
  • WordPress
  • ClickUp API

Install counts and ratings come from WordPress.org and change over time.

06/The engineering playground

How the tools fit together.

What I work with — not a claim of mastery over every line. Exploring is kept separate from established.

Frontend

Established

Interfaces that stay fast. Server Components by default; client JS only when needed.

  • React
  • Next.js
  • TypeScript
  • JavaScript
  • Tailwind CSS
  • React Native

Applied in — PGZoo, MapInch, Celebary and agency builds

07/How I work

Six steps, and the fifth one never really ends.

Understand the problem before proposing the solution.

  1. 01

    Understand the objective

    What needs to change, and how will you know it worked? Half the time this conversation shrinks the project.

  2. 02

    Find the simplest reliable solution

    I will tell you when a spreadsheet, an existing tool or a smaller build would do the job.

  3. 03

    Design the architecture and plan

    Data model, integrations, delivery sequence and trade-offs — written so you can evaluate them.

  4. 04

    Build and integrate

    Shipped in increments you can see. Direct communication with me, not an account manager.

  5. 05

    Test, deploy, monitor

    Pipelines, monitoring and enough logging to diagnose a problem without guessing.

  6. 06

    Keep improving it

    Businesses change and dependencies age. Several engagements have run for years because this step never ends.

What it is like to work together.

Direct communication
You talk to the person writing the code.
Transparent trade-offs
Every technical choice costs something. I will tell you what.
Pragmatic engineering
The best solution is the one your team can still maintain.
Ownership after launch
I stay interested once the system is live.

08/Client voices

The relationships that lasted.

The useful signal is a client still working with you years later.

  • WillowSpace

    Long-term SaaS development & support

    Multi-year development and maintenance of a live SaaS platform, continuing as the product evolves.

    UpworkSee on UpworkSummarised, not quoted
  • Automation client

    Make.com & Airtable

    A years-long automation relationship — scenarios built, extended and maintained as the process changed.

    UpworkSee on UpworkSummarised, not quoted
  • Full-stack client

    PHP application development

    Positive feedback on full-stack PHP delivery and communication throughout the project.

    UpworkSee on UpworkSummarised, not quoted

Some entries summarise the engagement rather than quoting verbatim. Original reviews are on Upwork.

09/The human behind the code

I like problems that look impossible until you take them apart.

I started in electronics and ended up in software. Same appeal: a system with rules you can learn, and a problem that yields if you stay patient with it.

The first decade was mostly PHP — a lot of it other people's code. That taught me to prefer solutions you can still understand three years later over clever ones.

Somewhere along the way the work stopped being about code. Clients don't want an API; they want to stop losing days to a process nobody has questioned. Hearing the business problem underneath the technical request changed my career.

Now I split time between my own products, long-running client work and agency teams. Owning a product teaches what maintenance costs; client work keeps you honest about deadlines.

I'm curious about AI and sceptical of most claims for it. I learn by building something small and seeing where it breaks.

Outside work I'm in Mohali with my family. The best technical decisions I've made were made on days I was rested.

10/Notes & experiments

Things I am working out in writing.

Nothing published yet — a labelled queue, not a magazine.

  • AI engineering

    Building AI features people actually use

    Most AI in products is decoration. What changes when you start from the task someone is doing instead of the model you want to use.

    Draft
  • SaaS

    The second year of a SaaS product

    Launch is the easy part. Notes on what breaks between month twelve and month twenty-four, and which early decisions cause it.

    Draft
  • Automation

    Automation that pays for itself

    How to tell which manual process is worth automating, and why the answer is usually two steps in the middle rather than the whole workflow.

    Planned
  • Integrations

    Integrations that don't rot

    Idempotency, retries, and designing a webhook endpoint for the day the other platform changes its payload without telling you.

    Planned
See the full writing queue

Five ways this usually starts.

You work directly with me — no account manager in between.

  1. A scoped product or feature build

    An MVP, a new module, or a rebuild of something that has outgrown itself.

  2. Full-stack development support

    A senior pair of hands inside an existing team or codebase.

  3. AI integration or workflow automation

    An AI capability that holds up in production, or removing manual work your team keeps absorbing.

  4. Ongoing engineering and maintenance

    A monthly retainer for features, upgrades, monitoring and incidents.

  5. Technical consultation or architecture review

    A focused read of what you have, what it will cost later, and what to fix first.

11/Work with me

Have a problem worth solving? Let's talk.

Pick a starting point, email me, or open WhatsApp. Every route reaches me directly.

Where should we start?

Tell me about the project

A couple of sentences is enough. I reply to real enquiries within a working day.

This site has no backend. Submitting opens your own email application with the details filled in, addressed to gaurav@gauravnagpal.com.

Or go direct

Mohali, India · IST (UTC+5:30) · Comfortable with AU, CA, UAE and UK hours