Case studies PPFAS

Building public websites, portals and internal tools at PPFAS

At PPFAS I built and launched two public websites, gift.ppfas.com and wealth.ppfas.com, and built the separate PPFAS Gift investment platform, which is integrated with a third-party payment gateway and supports international payments. The static pages and management portals I built let business teams manage workflows without depending on a separate tech team. Across the websites, the Gift investment platform and the portals I built, the combined fixed-cost saving is ₹20+ lakh.

Built and launched at PPFAS Oct 2024 – Present
Status
Two public sites launched; internal portals in production use
When
Oct 2024 – Present
Role
Assistant Manager – Web Developer (since Apr 2026)
Cost saved
₹20+ lakh in fixed costs, combined across seven builds; ₹10+ lakh in annual recurring cost
PPFAS work, as recorded: business teams (Marketing, Compliance, Operations and other teams) and a separate tech team; layouts and email templates planned in Figma and Photoshop; built at PPFAS: gift.ppfas.com, the PPFAS Gift investment platform (integrated with a third-party payment gateway), wealth.ppfas.com, the amc.ppfas.com management portal, a compliance and QC portal, the main PPFAS/AMC website, the document and content self-service system, an event-management system with QR scanning and door-list functionality, and the Career portal. Together, these builds, apart from the event-management system and the Career portal, saved a combined ₹20+ lakh in fixed costs; the event-management system and the Career portal together saved ₹10+ lakh in annual recurring cost; management portals let business teams manage workflows themselves, with reduced dependency on the tech team. Business teamsMARKETING · COMPLIANCEOPERATIONS · OTHER TEAMS Tech team DEPENDENCY REDUCED DEPENDENCY PLANNED IN FIGMA AND PHOTOSHOPlayouts · email templates SELF-SERVE BUILT AT PPFAS gift.ppfas.comGift investment platformwealth.ppfas.comamc.ppfas.com management portalCompliance and QC portalMain PPFAS/AMC websiteDocument self-service systemEvent system (QR, door list)Career portal ₹20+ lakhFIXED COSTS,COMBINED ₹10+ lakhANNUALRECURRING COST
  1. Problem Business teams depended on a separate tech team to manage workflows.
  2. Thinking Interfaces, website designs and email templates planned in Figma and Photoshop before implementation.
  3. Solution Two public site launches, the PPFAS Gift investment platform, and management and internal portals.
  4. Execution Built on Laravel, React, PHP, WordPress and AWS, with automated (CI/CD) deployment.
  5. Impact ₹20+ lakh in fixed costs, combined across seven builds, and ₹10+ lakh in annual recurring cost saved.
  6. Learning Each saving is attributed to named builds, and the portals, payment workflows and email templates are used in production operations.

1 Problem

01 · Context

Two site launches, an investment platform and internal portals since October 2024

PPFAS (Parag Parikh Financial Advisory Services) is a mutual fund company. Its primary business is investment through mutual funds. It also has additional businesses: Gift, which enables investment in foreign companies through the mutual fund company, and Wealth, which provides portfolio management services (PMS) and broader family wealth management.

I work at PPFAS in Mumbai as Assistant Manager – Web Developer, building websites, portals, an investment platform and internal systems.

I joined PPFAS in October 2024 as a Web Designer (October 2024 to March 2025), became Executive – Web Developer (April 2025 to March 2026) and have been Assistant Manager – Web Developer since April 2026.

When I joined, I was part of the Marketing team, and I reported to the Head of Marketing and Communication. I later moved to the Technology team, and I now work with and report to the CTO.

Three PPFAS websites are public: gift.ppfas.com and wealth.ppfas.com, which I built and launched, and amc.ppfas.com, for which I created a management portal.

Only those public sites are linked. Internal and authenticated tools are described here, not shown.

02 · Problem

Two problems: dependence on a tech team, and a recurring cost

Business teams at PPFAS depended on a separate tech team to manage their workflows.

A separate annual recurring cost is the problem behind two systems: the event-management system, with its QR scanning and door-list functionality, and the Career portal.

gift.ppfas.com and wealth.ppfas.com were completely new websites, built from scratch.

Publishing documents, before and after the self-service system

Business teams regularly need to publish regulatory documents, factsheets, flyers and presentations.

Before

  1. The business team emailed the file to me.
  2. I uploaded the file to S3 manually.
  3. I edited the website code.
  4. I uploaded and deployed the changes manually.
  5. Where the same document was referenced in several places on the website, I also maintained its link in each of those places manually.

After

  1. A user selects the file.
  2. They specify what type of file it is.
  3. The system uploads the file directly to S3.
  4. The document link is updated throughout the website, wherever that file is used.

I created this self-service system. It turned the process into a one-click, self-service workflow instead of the tech team manually uploading the file, modifying code and maintaining several document links. This reduced dependence on the tech team.

For events, the process involving email, door lists and checking attendees was previously manual or involved a paid solution.

03 · Users and stakeholders

The management portals are built for business teams

The management portals enable business teams at PPFAS to manage workflows themselves.

The self-service content and document system is used by Marketing, Compliance, Operations and other business teams.

The QR and event system, which I thought of and created, is now operated and managed by the Marketing and Sales teams. At an event, around 3–4 Sales and Marketing users use the door-list functionality and manage records for the people attending, and around 4–5 users scan attendee QR codes and mark attendance. The Marketing team also uses the system to send promotional emails and track attendees.

The people attending are unit holders and investors, at events organised by PPFAS.

2 Thinking

04 · Approach

Planning in Figma and Photoshop before implementation; management portals for business teams

Who manages business teams’ workflows, before and after the management portals:

Before

  1. Business teams have workflows to manage
  2. Separate tech team business teams depend on it to manage them

After

  1. Business teams have workflows to manage
  2. Management portals business teams manage workflows themselves

3 Execution

05 · Solution

What I built, from public launches to internal portals

PPFAS Gift: site launch, investment platform and backend portal

I built and launched gift.ppfas.com.

I built the PPFAS Gift investment platform and integrated it with a third-party payment gateway, which handles the payment step, including international payment support. I did not build the payment gateway itself.

The work includes a compliance and QC backend portal I built for uploads and staff management.

I built the Gift website and platform from scratch, including the whole static website. I also created onboarding for the Gift distributor portal.

The Gift investment flow I built, at a high level

  1. The user comes to Gift.
  2. They choose an investment.
  3. They enter the required details.
  4. They complete onboarding and KYC.
  5. They make the payment, through the third-party payment gateway.
  6. The investment is processed.

wealth.ppfas.com launch

I built and launched wealth.ppfas.com.

It is a new website and product, built from scratch.

wealth.ppfas.com is the website for Wealth, the PPFAS business that provides portfolio management services (PMS) and family wealth management. My work on it focused on creating the static website.

amc.ppfas.com management portal

I created a management portal for amc.ppfas.com, covering:

  • backend-managed website workflows;
  • job portal features;
  • related internal portals.

The portal lets internal business users manage website content and related information themselves:

  • website pages and content;
  • announcements;
  • job openings;
  • banners;
  • articles and news;
  • fund-related information;
  • downloadable documents;
  • regulatory documents, factsheets, flyers and presentations.

Documents follow the self-service workflow shown under Problem: the user selects the file and specifies its type, the system uploads it directly to S3, and the document link is updated throughout the website wherever that file is used.

The portal is used by Marketing, Compliance, Operations and other business teams. Its purpose is to reduce dependence on the technology team by letting business users manage these things themselves.

Main mutual fund website and self-service content management

I redesigned the look and feel of the static pages of the main mutual fund company (AMC) website.

I created the content upload and management system for the main mutual fund company and for Gift. It lets Marketing and other business users upload documents and modify website content themselves, reducing dependence on the tech team. The publishing workflow it changed is shown under Problem.

The combined ₹20+ lakh saving across seven builds

I built static pages and management portals that reduced dependency on the tech team.

The ₹20+ lakh fixed-cost saving is one combined figure across these seven builds; it is not split between them:

  • the main PPFAS/AMC website;
  • the Gift website;
  • the Gift investment platform;
  • the Wealth website;
  • the amc.ppfas.com management portal;
  • the document and content self-service system;
  • the Compliance and QC portal.

Event-management system: QR scanning and door list

I built an event-management system, with QR scanning and door-list functionality. The ₹10+ lakh annual recurring cost saving is attributed jointly to this system and the Career portal.

The system is used for events organised by PPFAS that unit holders and investors attend. It covers ticket generation, sending tickets by email, generating QR codes, scanning the QR codes at the event, letting attendees in and keeping records of the people attending. It also includes the door-list functionality, promotional emails and attendee tracking.

The process involving email, door lists and checking attendees was previously manual or involved a paid solution. The QR system now provides a faster, scanning-based process.

It was first used for one event a year. It is now used for events held approximately every month, as well as the major AGM, which approximately 2,000–3,000 people attend.

I originally thought of and created the system; the Marketing and Sales teams now operate and manage it (see Users and stakeholders).

Career portal

The Career portal is a recruitment system with two user groups:

  • Applicants can view available job openings, open a job, fill out the application form and submit an application for the position.
  • HR users can create job postings, publish a job posting across PPFAS sister companies through the portal, and view the people who have applied for a job.

I thought of the Career portal and built the whole system myself, on my own.

Design before build

I designed email templates and website layouts in Figma and Photoshop before implementation. The email templates are used in production operations.

06 · Product decisions

Three choices visible in the work

  • Self-serve portals. Management portals let business teams manage workflows themselves.
  • Design before build. Website layouts and email templates are designed before implementation.
  • International payment support. The PPFAS Gift investment flow includes international payment support.
07 · Technical execution

A PHP and JavaScript stack with automated (CI/CD) deployment

  • Application code PHP, Laravel, React
  • Content management WordPress
  • Cloud and deployment AWS; automated (CI/CD) deployment workflows
  • Design Figma, Photoshop

4 Impact

08 · Outcome

₹20+ lakh in fixed costs and ₹10+ lakh in annual recurring cost saved

What the record says I built

Personal vs team split not yet confirmed.

  • gift.ppfas.com, built and launched
  • PPFAS Gift investment platform, integrated with a third-party payment gateway, including international payment support
  • Compliance and QC backend portal for uploads and staff management
  • wealth.ppfas.com, built and launched
  • amc.ppfas.com management portal, with job portal features and related internal portals
  • Static pages and management portals
  • Event-management system with QR scanning and door-list functionality
  • Career portal, which I thought of and built on my own
  • Email templates and website layouts, designed before implementation

Outcome

  • Fixed costs: ₹20+ lakh, combined across the main PPFAS/AMC website, the Gift website, the Gift investment platform, the Wealth website, the amc.ppfas.com management portal, the document and content self-service system and the Compliance and QC portal
  • Annual recurring cost: ₹10+ lakh, attributed jointly to the event-management system (QR scanning and door list) and the Career portal
  • Management portals that enable business teams to manage workflows themselves
09 · What the evidence showed

Public launches and internal tools, in production use

  • Public sites and internal tools. The work spans two public launches (gift.ppfas.com, wealth.ppfas.com) and internal portals such as a compliance and QC backend portal for uploads and staff management.
  • In production use. Internal portals, payment workflows, backend tools and email templates are used in production operations.
  • Not shown here. Feedback from the business teams, or how the savings were calculated. Usage figures appear only for the event-management system.

Next case study

All case studies