- Home
- Services
- Apps and extensions
Web apps and Chrome extensions, designed and built
I build web apps in Next.js and Chrome extensions on Manifest V3, from screens you have already approved. Data lives in Supabase or Airtable, the logic runs through APIs, n8n and OpenAI, and every build ships with a walkthrough video and written docs.
Interactive 3D stack of five blocks showing the layers of a build: hosting, data, logic, interface and handover.
The 3D model needs WebGL. The stack: hosting, data, logic, interface, handover.
Hosting at the bottom, handover on top. Tap a block to see what it covers.
Shipped
Built, not just designed.
A web app, a Chrome extension and a voice agent, each with the stack it runs on. More in the work.
InboxCheck
A cold email deliverability checker. Paste a sending domain and get a plain-English list of what to fix.
Built with: Next.js 15 and a Cloudflare DNS engine, covered by 111 passing tests.
Read the case Chrome extensionStoreLens
Shows how any Shopify store is built: platform, apps, product count and pricing, in one click.
Built with: Manifest V3, a content script and service worker, licenses through the Gumroad API.
Read the case Voice agent and dashboardRealCommand AI
An AI receptionist that answers inbound calls, qualifies the caller and logs every lead for the team.
Built with: Vapi, n8n, OpenAI and Next.js.
See itWhat I build
Three kinds of build.
Which one you need depends on where your team already works.
Web apps
Dashboards, internal tools and customer-facing apps in Next.js, with Supabase or Airtable underneath.
Good for: lead dashboards, call logs, scanners, portals.
Chrome extensions
Popups and sidebars that sit next to the tools your team already lives in, like Gmail, GoHighLevel, Upwork or Shopify.
Good for: CRM lookups, research, lead capture.
n8n systems
The tools you already pay for, connected end to end, with OpenAI where something needs reading or writing.
Good for: lead replies, booking, logging, outreach. More on automation.
With every build
The handover is part of the build.
Clickable screens first
You approve the screens before anything gets built, so the build has no surprises.
Tested with real data
Your current tools connected and tested with real data, not a demo account.
Walkthrough video
A recorded walkthrough of what was built and how to use it.
Written docs
How it works and where everything lives, written down for whoever comes next.
Support window
A support window after launch for anything that needs adjusting.
Care, if you want it
Monitoring, fixes for anything I built, small changes and a monthly check-in call.
FAQ
Build questions
The technical bits, in plain English.
still stuck? just ask me
What do you build?
Web apps in Next.js, Chrome extensions on Manifest V3, and the n8n systems that connect them to your other tools.
Which stack do you use?
Next.js for web apps, Supabase or Airtable for data, Manifest V3 for Chrome extensions, n8n and OpenAI for automation, and Figma for design.
Can you build a Chrome extension for my team?
Yes. StoreLens, GHL Sidebar for Gmail, Client Vetter, MapPull Lead Extractor, Grant Watcher, LaneMath and the Skool Owner Toolkit are all Chrome extensions I have designed and built.
How long does a build take?
A single workflow or Chrome extension usually takes a few days. Larger systems ship in small working pieces, so you see progress within the first week.
What do I get at the end?
The working build, a walkthrough video, written docs and a support window after launch.
What happens after launch?
After the support window, a Care plan from USD 400/month covers monitoring, fixes for anything I built, small changes and a monthly check-in call. It is optional.
Got a tool your team
keeps wishing existed?
Describe it on a 15-minute call. You get a fixed quote after the call, before any work starts.
Rather just chat?
Message me on WhatsApp at +91 70588 56504 (opens WhatsApp). I'm in India (IST).