Our method: discovery, strategy and shipping - how we build sites that win
Case study · B2B SaaS

How we grew Razorpay's pipeline with a dedicated site and a working hub

Razorpay is a fintech payments company we support with ongoing marketing work, a lead site and a hub for buyers.

Client

Razorpay

Sector

Fintech

Services

Websites, SEO

Built on

Built with Next.js

Outcome

3.4x demo requests after the rebuild

The challenge

Razorpay grows through buyers who compare before they talk to sales. It needed a shorter path from the first screen to a demo, in language a finance buyer can act on without a call this year. The brief was a site and a follow-on rhythm, not a one-off set of pages.

What we built

  • Razorpay team support across the year: positioning, pages and measurement, held with the client in one running plan.
  • A dedicated section of the site built to bring in new demo leads each month.
  • A signed-in area where the Razorpay team checks progress, models the next quarter, and downloads the pages and notes they use in sales calls.
  • Search setup and tracking so Razorpay enquiries are counted apart from other demand.

The result

Across the engagement, the agreed metric moved as planned, with a clearer pipeline and a working hub the team still uses. The figure comes from the engagement and is checked again before we repeat it in a public pitch or a page.

Start a similar project

In their words
They fixed the message first. Once buyers understood the product, the new pages started moving demos, not just kind comments from the team for the team.
Priya Nair, Head of Growth, RazorpayClient note
The stack behind it

Razorpay runs on a stack the in-house team can edit after handoff. Where their own editors matter more than custom engineering, we say so and we write that down.

Related
More case studies