I'm Naveen Goyal. I design, build and maintain custom WordPress plugins — integrations, WooCommerce features, admin tools and REST APIs — for US companies and the agencies that serve them. You work directly with the person writing the code, and every milestone lands on your staging site before it goes live.
Most US projects reach me with one of these briefs. Each is scoped in writing before any code is written.
A feature your site needs that no marketplace plugin does cleanly: booking rules, member portals, custom post types with real admin UX, Gutenberg blocks, scheduled jobs.
WordPress talking to your CRM, ERP, accounting or fulfilment system — HubSpot, Salesforce, QuickBooks, ShipStation or an internal API — with authentication, retries and logging so failures are visible.
Checkout rules, B2B pricing, custom order statuses, subscriptions-style flows and payment gateways such as Stripe, Authorize.net, PayPal or Square, built on WooCommerce's hooks so updates don't break them.
An abandoned or fragile plugin rebuilt to current standards without losing existing data or settings — including PHP 8 compatibility fixes and conflict debugging.
Internal screens your team uses daily: reports, bulk actions, import/export, approval queues. Fast on large datasets, with capabilities and nonces on every action.
If you sell or publish a plugin, I package it the way the WordPress.org review team expects: sanitised input, escaped output, prefixed code and a readme that passes review.
I'm based in India but work a US Eastern shift: 8:30 am to 8:30 pm ET. That covers the whole East Coast working day and West Coast teams until 5:30 pm Pacific, so calls, questions and reviews happen in your normal day. If something urgent breaks, I stay on after 8:30 pm until it's fixed.
Times shown in US Eastern · I work a US Eastern shift from India, 8:30 am to 8:30 pm ET, and later when something urgent needs fixing
These come up on most US builds, so I plan for them from the first call rather than patching them in at launch.
Destination-based sales tax across states is rarely a job for WooCommerce's built-in tax tables. I connect stores to services such as Stripe Tax, TaxJar or Avalara and make sure tax is calculated where it should be: cart, checkout, invoices and refunds.
Front-end output and admin screens built to WCAG 2.1 AA practices — labelled form fields, keyboard access, visible focus and sensible heading order — so a new plugin doesn't add accessibility problems to your site.
Plugins that store personal data hook into WordPress's built-in export and erase tools, which helps when you handle access or deletion requests under state privacy laws such as California's CCPA.
Hire me directly with a written scope and milestone invoices, or through Upwork if your finance team prefers escrow and US-style invoicing.
No anonymous logos. These are public, and you can test them yourself.
Free, maintained and reviewed by the WordPress.org plugin team. Read the code before you hire me.
A custom pricing engine, B2B wholesale portal, automated order statuses and performance work, built as three standalone plugins with custom tables.
Read the case study →
A live app for running a WooCommerce store from a phone: orders, products, stock and customers, connected to WooCommerce through its REST API.
hub.maalabs.in ↗You know the scope, cost and next deliverable at every stage.
A 30-minute call in your morning about the problem, your stack and how you'll measure success. No charge.
A short spec with the features, edge cases, milestones and a fixed or milestone-based price, agreed before work starts.
Each milestone is deployed to your staging site with notes on what changed and how to test it.
Production deploy, documentation and a support window. Ongoing maintenance is available if you want it.
Yes. I work remotely with US businesses and agencies. You get a written scope, milestones on your staging site, and I work US Eastern hours, 8:30 am to 8:30 pm ET, so calls happen in your normal working day. I'm based in India and don't have a US office.
It depends on scope, integrations and how much admin UI is involved. You get a fixed or milestone-based quote in writing after the discovery call. This cost breakdown explains what drives the price.
You do, completely. Once the project is paid for, full ownership of the code and intellectual property passes to you in writing. There are no licence fees and no lock-in, and the plugin lives in your repository from the first commit. Open-source libraries it uses keep their own licences.
It's built on documented hooks and APIs, never core-file edits, and tested against current WordPress and PHP versions. The same approach keeps my 11 WordPress.org plugins working through core updates.
Yes, always. I sign your NDA before you share client details, designs, credentials or code, at no extra cost. I can also work inside your Git, project tool and Slack, so nothing confidential has to leave your systems.
Both. A lot of work is extending, debugging or rescuing an existing plugin. I review the code first, so you know what you're dealing with before you commit to a quote.
Send the brief, even if it's rough. I'll reply within one working day with questions, a suggested approach, or an honest "this isn't a fit".
I read every enquiry myself and reply within one working day with questions or a next step.