THE BUSINESS CONTEXT
Solar projects begin with different questions. A homeowner may need help understanding a rooftop system; a business or institution may need a more complex technical and commercial proposal.
GRID NOVA ENERGY / SOLAR EPC / INDIA
From a digital presence
to connected operations.
A corporate website and a custom AI-powered business operations platform. One engagement, two distinct layers: how customers discover the business, and how its team can manage the work behind an enquiry.
Website liveAI platform · production deployment pending
Visit Grid Nova Energy ↗
CLIENT
Grid Nova Energy
Solar engineering, procurement & construction
HIGHLINE’S SCOPE
Corporate website
Custom AI & operational software
THE DISTINCTION
Public website deployed.
AI platform built and locally tested, per project handoff.
THE DESIGN & ENGINEERING RESPONSE
Give those customers clear entry points, then build a separate operations layer designed to organise enquiries, assist proposal preparation and keep staff in control of important decisions.
01 / THE PUBLIC EXPERIENCE
Understand the offer. Know the next step.
A service-led website
Corporate information, services, industries, project examples and leadership help a prospective customer understand Grid Nova’s work. The public rooftop journey explains the stages from enquiry through commissioning and subsidy follow-up.
Guided solar estimates
The supplied project brief describes a multi-step calculator with configured sizing, pricing and subsidy rules. Estimates are indicative, not binding quotations, final engineering designs or guaranteed savings.
Backend-dependent production calculation remains unverified.A route into a conversation
Enquiry and contact entry points help visitors take the next step. The implementation scope also includes appointment booking and Google Calendar integration.
Live availability and successful production bookings have not been independently verified.02 / THE OPERATIONS ARCHITECTURE
Specialised responsibilities. Coordinated work.
Architecture described in the supplied project brief. This diagram explains the platform’s design; it is not a live activity monitor or proof of a deployed end-to-end workflow.
Customer-facing requestsAuthorised staff workflows
COORDINATION LAYER
Orchestrator
Interprets the request, chooses the appropriate specialist and coordinates access to shared application data. Specialists do not directly invoke one another.
CUSTOMER ENQUIRIES
Nova / Sales
Turn a conversation into useful context.
Asks follow-up questions, collects requirements and supports qualification, lead prioritisation and duplicate detection. A qualified enquiry still needs staff judgement; Nova is not designed to independently close a sale.
AUTHORISED PREPARATION
Proposal Agent
Draft from approved information.
Assists with structured proposals using authorised technical content, configured pricing and commercial rules. Preparation and approval are separate: a draft does not authorise a customer-facing commitment or send.
STAFF ONLY
Memory Agent
Find the right business record.
Helps authorised staff retrieve information from shared records. Its access is separate from public customer chat, with restrictions intended to protect customer boundaries and confidential information.
03 / THE INTENDED JOURNEY
From enquiry to an informed decision.
A business-process design, not a production-verified sequence. The platform is intended to support these connected steps.
01
Receive
A customer brings a solar requirement through a supported entry point.
02
Understand
Nova gathers useful details and supports qualification.
03
Organise
The application structures lead information for staff follow-up.
04
Review
Authorised staff assess the opportunity and supporting information.
05
Prepare
The Proposal Agent assists with a draft based on approved inputs.
06
Approve
Commercial decisions and customer-facing commitments remain under authorised review.
04 / THE STAFF EXPERIENCE
Visibility for the people
responsible for the work.
The dashboard is the intended operational counterpart to the customer-facing experience. Its implementation scope brings leads, conversations, meetings and proposal review into one staff interface.
This is implemented software scope described in the handoff. Production access and each integration still require verification.
Customer context
Lead lists, lead details, transcripts and activity timelines.
Follow-up & proposals
Meeting management, proposal preparation, review and approval actions.
Operational oversight
Overview, analytics, equipment management and employee administration.
Governance
Audit logs, agent controls and permission-aware operations.
05 / CONTROL IS PART OF THE DESIGN
AI assistance. Business oversight.
Approved inputs
Proposal drafts are intended to use approved pricing, equipment information and commercial content. The agent should not invent commitments.
Bounded permissions
Staff roles, agent-specific capabilities and per-lead action budgets define who or what can perform an operation.
Operator control
Database-backed kill switches provide a way to disable agents. Audit records help staff inspect actions and investigate failures.
These are described controls and design intentions. They are not security certification, regulatory assurance or proof that every possible failure has been prevented.
06 / BEHIND THE BUILD
Two applications.
Clear responsibilities.
Website & frontend
The project brief identifies Next.js, React, TypeScript and Tailwind CSS for the frontend, with animation supporting the interface. This is separate from the Highline portfolio’s own React/Vite implementation.
AI services & business data
The supplied backend architecture uses Python, FastAPI, LangGraph, SQLAlchemy and migration tooling. Application workflows coordinate agents, structured records and authorised operations. The recorded production target is Cloud Run with Cloud SQL for PostgreSQL; this is a deployment target, not a confirmed live environment.
Authentication & integrations
The brief describes Clerk-related authentication and Google Calendar integration work, alongside file, email, audit and governance components. Production authentication configuration and backend-dependent integrations require deployment verification. No credentials or internal customer data are included here.
07 / IMPLEMENTATION STATUS
What is live. What comes next.
Corporate websiteLive
Publicly accessible at gridnova.in; independently inspected for this portfolio.
Custom AI backendBuilt & locally tested*
Production deployment deliberately paused in the supplied handoff. A completed production API deployment is not established.
Agents & staff dashboardImplementation scope*
Part of the built platform. Complete production deployment and end-to-end operation remain unverified.
Calculator & booking integrationsProduction unverified
Interfaces and integration work are described. Backend-dependent estimates, calendar availability and live booking success need verification.
*Status is reported in Highline’s supplied project brief. Grid Nova’s application repositories and local test results were not supplied for independent verification in this portfolio task.
Additional scope: Associate Network
The engagement has expanded into a separate Associate Network implementation covering registration, approval, onboarding, site information, documents and project administration. Its completion status has not been established here; it is not included among the completed AI deliverables above.
08 / VALUE THROUGH THE WORK
A clear public presence.
A structured operational foundation.
The verified public deliverable is Grid Nova’s corporate website. The supplied handoff describes a built, locally tested AI platform intended to centralise enquiry information, assist staff and support controlled proposal workflows.
No conversion uplift, revenue increase, response-time reduction or hours saved are claimed. After deployment, useful measures would include lead completeness, reviewed proposal turnaround, staff correction rates and successful human handoffs.
Explore Highline’s automation approach ↗YOUR BUSINESS / YOUR WORKFLOW
What should your website
connect to next?
Bring the customer journey and the work behind it. We’ll help define a useful scope.
Discuss a connected buildNEXT IN THE ARCHIVE
Leak Master ↗