Pranatah Tech Solution

About the project

Pranatah Tech Solution is a software services company where I ran the software department. Its site is also a dashboard where staff build quotations and track the business.

Pranatah Tech Solution is a software services company. From January to September 2025 I was In-charge of its Software Department: I ran the software side and the team, and built the company's site.

The site has two faces. Visitors see the company's services, blog and contact forms. Staff log in to a dashboard where telecallers turn leads into quotations, admins approve them, and the business can see how it's doing.

How it works

1. 1

   A lead arrives

   Visitors reach out through the site's forms.

2. 2

   Build a quotation

   A telecaller builds it step by step: service, sub-service, add-ons, then a discount.

3. 3

   Approve

   An admin reviews and approves the deal. Admins can't change the root user.

4. 4

   See the business

   Reports show quotation status, revenue and user activity, exportable as PDF or CSV.

Under the hood

Web

Next.js 15 with tRPC and TanStack Query.

Login and roles

NextAuth with Google or email; four roles checked in the API and in the menu.

Data

Prisma on Postgres. Service categories in the database become dashboard pages.

Reports

Recharts, with PDF export through jsPDF.

What I did

• Set up the server layer: tRPC with Prisma on Postgres, and admin tools to edit the home page content
• Google and email login with NextAuth
• Four roles (user, telecaller, admin, root), checked on the server and in the menu. Admins can't change the root user
• The quotation flow: service, sub-service, add-ons, discount, then approval, and a list of quotations
• A reports page with quotation status, revenue and user activity charts, exported as PDF or CSV
• Dashboard pages built from service categories in the database, so new services need no new code
• Aurafy, the team's portfolio generator: I fixed a hydration error and cleaned up its deploy setup. The app itself was built by saiabhiramjaini and Aashish Jaini
• Fixed Vercel deploys, and turned on analytics in production only
• Reviewed and merged the team's pull requests

What was new

• Role checks on both sides: on the server, and in what each person sees
• My first time running a department, not just a codebase

Problems I hit, and how I fixed them

1. 01

   Google sign-ins had no user ID in the token, so the API couldn't find the user.

   Fix Read the login session on the server and look the user up by email.

2. 02

   Telecallers were locked out of quotations: the role was misspelled in the check.

   Fix Fixed the role type and the check.

3. 03

   Logging actions in Next.js middleware ran the database client where it can't run, and broke.

   Fix Turned it off there.

4. 04

   Vercel builds failed on dependencies and server-only modules.

   Fix A cleaner install step and fallbacks for those modules.

Screenshots