Insta Boosters
A multi-page marketing site for an Instagram growth reseller, covering followers/likes/views/comments pricing tiers, WhatsApp-first ordering, and a full FAQ/testimonials/how-it-works funnel, with zero backend dependencies.
Overview
Insta Boosters is a marketing and ordering funnel for a small Instagram growth reseller run by Gaurav Rajani. It presents pricing tiers across seven service types (followers, likes, views, comments, story views, shares, reposts) each with its own price, quantity, and delivery blurb, and routes every conversion path to WhatsApp rather than a checkout flow, since the business itself operates entirely over WhatsApp DMs.
Why it was built
A client project for a reseller whose entire business already ran through Instagram DMs and WhatsApp with no web presence at all. The brief was a credible, fast marketing site that could rank and convert without introducing a backend, payment processor, or account system the client had no way to operate or maintain themselves.
Typed Pricing Tier Catalogue
Seven service types live in a single typed PricingTier array (site-data.ts) with key, name, icon, price, quantity, unit, and blurb fields, so the pricing page, home page preview, and any future service page all render from one source.
WhatsApp-First Conversion
Every CTA across the site funnels to a prefilled wa.me link built from a single waLink(message) helper, rather than a contact form or checkout, matching how the business actually takes orders today.
Dedicated FAQ / How-It-Works / Testimonials Pages
Rather than cramming trust content onto the home page, /faq, /how-it-works, and /testimonials are separate routes, letting each be linked directly from ad campaigns or DM replies.
Tech Breakdown
A fully static marketing site with no dynamic data needs no server at runtime; Next's App Router gives per-page metadata, a generated sitemap, and robots.ts for SEO with minimal code.
The only animation dependency in the project, used for scroll-reveal and the stat counter, kept deliberately as the single animation primitive rather than mixing in CSS keyframes and a JS library.
Utility-first styling across contact, FAQ, services, testimonials, and how-it-works pages without hand-writing a design system for a project this small.
The one small utility dependency, used for conditional class composition on interactive components like the pricing cards and accordion, rather than string-concatenating class names by hand.
- 1
Pricing content for a service like this needs to read as credible rather than spammy; the blurb field on each PricingTier exists specifically to explain delivery mechanics (e.g. 'delivered gradually so growth never looks suspicious') rather than just listing a number and price.
- 2
With every conversion path going to WhatsApp instead of a form, there's no server-side event to hook analytics to, so any future funnel tracking has to be done client-side against outbound wa.me link clicks.
A natural next step would be UTM-tagged WhatsApp links per traffic source so the client can see which channel actually drives orders, since there's currently no way to attribute a WhatsApp conversation back to where the visitor came from.
See it live
Check out the deployed site.