Skip to content
Customer Story

A Customer Portal That Supports, Teaches, and Takes Action

How we built PTG a custom web app on Next.js and Firebase so customers get support, learning resources, and a clear way to make requests in one place.

The challenge

Customers Needed a Home Base, Not Another Inbox

PTG saw a clear gap after the sale. Customers needed a reliable place for support, learning resources, and requests. Those needs were real, but they were spread across channels that made every team work harder than they should.

Off-the-shelf portals force a shape that rarely fits. PTG needed something purpose-built: a resource that helps customers help themselves, and that also gives support, marketing, and sales a shared surface to work from.

Before

Customer needs lived across email, docs, and ad hoc follow-ups

Need

One resource for support, learning, and requests

Gap

No shared system bridging support, marketing, and sales

Requirement

A custom web app that fits PTG, not a generic portal template

What we built

One Portal. Three Jobs Done Well.

A customer-facing web app that handles support, learning, and requests without making customers piece the experience together themselves.

01Customer Portal

A Custom Web App Built Around PTG Customers

PTG needed more than a help page or a bolted-on ticketing widget. We built a dedicated customer portal: a place their customers can return to for support, learning, and requests, designed around how PTG actually works with its accounts.

  • A branded portal customers recognize as part of PTG

  • One home for post-sale relationships instead of scattered tools

  • A foundation that can grow as PTG adds programs and products

02Support & Learning

Support and Learning Resources in One Place

Customers needed answers and education without waiting on a ticket for everything. The portal puts support and learning resources side by side so people can self-serve when they can, and escalate when they should.

  • Guided support paths that reduce repetitive back and forth

  • Learning resources that stay close to the moment of need

  • Less friction for customers who just want to move forward

03Requests

Request Workflows That Reach the Right Team

When customers need something specific, the portal turns that into a clear request. Support, marketing, and sales each get what they need from the same signal instead of chasing context across inboxes.

  • Structured requests instead of scattered email threads

  • Handoffs that carry context across support, marketing, and sales

  • A cleaner loop from customer need to internal action

The multiplier

Built to Bridge Support, Marketing, and Sales

The portal is a customer resource first. It is also a shared operating surface. Support gets clearer requests. Marketing stays closer to what customers are trying to learn. Sales stays connected to the account after the close.

That is what makes it more than a help desk clone. It is a tool designed for how PTG actually serves customers across the company.

The value

What PTG Walked Away With

01

One place for the customer relationship

Support, learning, and requests live together so customers are not bouncing between tabs and tools.

02

A bridge across three teams

The portal connects customer support, marketing, and sales around the same customer signals.

03

Built on a modern stack

Next.js and Firebase give PTG a fast, flexible app they can operate and extend without a heavy platform tax.

Stack·Next.js·Firebase

Want Results Like PTG?

If your customers need a better home for support, learning, and requests, we can build the portal that fits how your teams actually work.

STRS Dev
Step 1 of 4

What best describes you?