Gutenberg Blocks

Custom Gutenberg blocks, one lean plugin

Ten block plugins for ten block types is how layouts break and editors give up. I build your whole block library into one lean plugin on the native WordPress block API, brand-matched and validated, so it survives every update.

Order the auditSee what’s included

Plugins running on 10,000+ sites, built to the same standards

Replies within 24 hours, usually the same day

What you are buying

From ₹25,000Starting price, GST included
From $299In dollars

Work delivered for, or alongside, teams at:

  • IBM
  • Adobe
  • HubSpot
  • Canva
  • monday.com
  • IATA
  • FreshBooks
  • Acer
  • ASUS
  • Airtel
  • BYJU’S
  • AppSumo
  • StellarWP
  • Copyleaks
  • Depositphotos
  • accessiBe

What it costs

Priced per block library, not per surprise.

The base price covers a small library of custom blocks in a single plugin. More blocks, InnerBlocks complexity, and dynamic data raise the quote before work starts, never after.

Custom block library
From ₹25,000 From $299per project
  • Content mapping: every repeated layout becomes a block or pattern
  • Native builds: block.json, React editor, PHP server rendering
  • InnerBlocks support for the flexible areas your team controls
  • Input validation and sensible defaults so layouts can’t break
  • One plugin, lean assets, no third-party dependencies
  • Docs and an editor walkthrough so adoption sticks
Build my blocks

Block patterns and variations for existing blocks are a smaller, cheaper job. Ask.

All prices include GST.

How this runs

You will know the price and the plan before I touch anything.

1

Map

We catalog every layout your team builds by hand: heroes, pricing tables, testimonials, product displays. If it’s a repeated pattern, it’s a candidate. If it’s a one-off, it isn’t.

You leave with: a block inventory with a fixed quote per block.

2

Prototype

I build working prototypes in the editor so your team tests with real content before production code ships. Controls get renamed and simplified based on how they actually use them.

You leave with: prototypes your editors have already tried.

3

Build

React for the editor, PHP for the front end, server-side rendering so Google reads everything cleanly. Tested across browsers, devices, and your existing theme.

You leave with: one plugin, tested against your live stack.

4

Train

The blocks deploy as a single plugin with documentation written for editors, not developers. I collect the first round of feedback and refine before signing off.

You leave with: docs, a walkthrough, and a refined first release.

A note from me

How I build blocks

The first thing I look at isn’t the design. It’s how your editors work today, because a technically perfect block nobody enjoys using is wasted money. Controls get labeled in your team’s language, not developer jargon.

I build on the native block API only: block.json, React, PHP rendering. No shortcode wrappers, no third-party frameworks that die in two years. Deactivate a badly built block plugin and your content collapses into shortcode garbage. Mine degrades to clean markup.

And every block validates its input. Wrong image sizes, missing fields, broken layouts, those get caught in the editor, not discovered on the live site.

— Gaurav

Before you write in

This isn’t for every site.

Worth starting

  • Your team rebuilds the same sections by hand on every new page.
  • You’re running multiple block plugins and paying for the conflicts.
  • Off-the-shelf blocks fight your design system instead of following it.
  • Editors avoid the site because the editing experience frustrates them.
  • You need dynamic blocks that pull real data: products, events, listings.

Look elsewhere

  • Your budget is under ₹25,000. A set of block patterns using core blocks gets you most of the way.
  • You need a whole theme, not blocks. That’s block theme development, a different project.
  • You’re committed to Elementor or Divi. Custom Gutenberg blocks won’t help inside a builder.
  • You need one block for one landing page. The setup overhead isn’t worth it, and I’ll say so.
  • You expect blocks to fix slow hosting or a bloated theme. They won’t, and I’ll point at the real problem.

If you want to:

  • Cut the plugin pile down to one lean library you control
  • Publish on-brand with blocks that look right by default
  • Keep editors happy with controls they understand at first glance
Build my blocks

Common questions

Not answered here? Ask directly and you will hear back within 24 hours.

Projects start at ₹25,000, including GST. That covers a small library of custom blocks delivered as one plugin. The per-block quote depends on complexity: a static testimonial block is cheap, a dynamic product grid with InnerBlocks isn’t, and you see the breakdown before work starts.

Builders add weight, lock your content into their format, and slow the site. Native blocks are part of WordPress core: lighter, faster, and portable. Your content stays clean markup, and editors work in the editor they already know.

Yes, that’s the point. Typography, spacing, colors, and components come from your system, so every layout is on-brand the moment an editor inserts it. No manual styling, no drift.

You’d be fine. The blocks are standard WordPress code in one documented plugin you own, built on the same block API core uses. Any competent WordPress developer can maintain or extend them, and that’s a design goal, not an accident.

Rarely. Good blocks are self-explanatory, with clear labels and guardrails that make the wrong thing hard to do. The handover includes short docs and a walkthrough anyway, so new team members onboard themselves.

Adjacent services

All services →
Gaurav Tiwari

About me

So, who’s writing your code?

A WordPress Core contributor with plugins running on more than 10,000 sites.

Development clients get the person who ships his own plugins, not a project manager.

I was a teacher before I was a developer. I taught mathematics to competitive-exam students, which is why I explain hard things plainly instead of hiding behind jargon.

What I am actually good at is the join: technical SEO, fast front-ends, and content treated as one system instead of three vendors blaming each other.

  • WordPress Core contributor
  • Plugins on 10,000+ sites
  • wp-mcp, listed on the LobeHub marketplace
  • 850+ clients since 2008
  • $38M+ client revenue influenced
  • Building for the web since 2008
More about meSee the full track record

List the layouts your team rebuilds every week.

Tell me which sections get built by hand over and over, and on what theme. I’ll reply with a block inventory and a per-block quote.

Message on WhatsApp

Replies within 24 hours, usually the same day