Custom projects · assessment and pilot

Connect solar sales, installation and after-sales records

Carry survey requirements and approved quotations into equipment allocation, installation milestones and warranty support.

Discuss solar EPC software →

Solar projects move between salespeople, surveyors, procurement, installers and support staff. ALGONLP can assess solar EPC software that carries the approved requirements and quotation through each handoff. Connect survey records, equipment serials, installation milestones and warranty requests, while leaving engineering calculations and current policy assumptions with the responsible specialists.

Keep survey and quote versions connected.
Know which equipment belongs to each project.
Give support the accepted installation history.

AI-generated illustration of a solar engineer and technician reviewing a rooftop installation in safety equipment. — Illustrative workflow.

Workflow comparison

Before and after: how the workflow could change

Illustrative comparisons for a scoped implementation. The proposed workflow depends on agreed processes, supported integrations and staff use.

AI-generated illustration of the solar engineer and colleague comparing separate paper job folders beside completed rooftop panels. — **Today**Illustrative workflow view.

AI-generated illustration of the same solar team handing over a coordinated job folder beside organized parts cases. — **Proposed workflow**Illustrative workflow view.

Keeps the quote’s assumptions and approvals available for later review.

Today: A survey note and the latest supplier price are absent from the quotation the customer receives.
Proposed workflow: A proposed quotation record links reviewed survey inputs, equipment and price versions.
How it works: Technical staff approve design inputs and authorised sales staff approve the commercial version before it is issued.

Gives installers a traceable scope and a clear owner for unresolved substitutions.

Today: The installation crew receives equipment and instructions that do not match the accepted quote.
Proposed workflow: The project links the approved scope to serial allocation and installation tasks.
How it works: Record equipment changes as exceptions, obtain the required review and update the crew’s project record.

Gives support the relevant project context without reconstructing the installation.

Today: Support asks the customer again for equipment details and commissioning documents.
Proposed workflow: The warranty ticket opens against the project’s equipment and handover history.
How it works: Staff retrieve the correct serial, accepted documents and recorded warranty terms, then assign the service request.

Illustrative example

A practical end-to-end example

Illustrative example: a site survey reveals a constraint that changes the equipment list. Technical staff review it, sales issues an approved quotation revision and the customer accepts it. Procurement reserves the agreed equipment and records serials. The crew closes reviewed commissioning tasks, and a later warranty enquiry opens against the correct project record.

Where solar project information gets separated

Sales enquiries and site-survey findings are captured in different places, so requirements are repeated or missed.
Supplier prices and quotation revisions change without a clear record of the version the customer approved.
Equipment reservations, serial numbers and crew plans are difficult to trace to the correct project.
Support staff cannot quickly find commissioning documents, installation details or the relevant warranty terms.

Keep the approved project record moving

Qualify the enquiry
Record the site, intended use, project owner and required survey information. Request only documents needed for the next step.
Complete the survey
Capture approved site notes, photographs and constraints. Assign technical questions to the qualified reviewer.
Prepare a versioned quote
Link the reviewed design inputs, equipment list, vendor prices and commercial terms. Retain the customer-approved version.
Allocate equipment and teams
Reserve items against the project, record serials and schedule crews using confirmed availability.
Track installation milestones
Record delivery, installation checks, commissioning and open issues, with staff sign-off at agreed stages.
Hand over to support
Retain accepted handover documents, equipment references and warranty or maintenance tickets in the same project history.

A project scope that follows the handoffs

A scoped build can include lead and survey CRM, quotation/BOM versions, approval queues, serial allocation, installation milestones and after-sales tickets. Existing accounts and specialist solar-design tools can be assessed for supported connections.

A CRM records the workflow; specialist tools and qualified staff provide engineering design. Capacity, equipment suitability, commercial assumptions and policy-sensitive calculations need traceable review.

AI assistance with technical and commercial sign-off

AI may extract bill fields or vendor price-sheet lines into drafts, summarise surveys and prepare explanations from approved calculations. Staff verify every extracted value. Engineers approve design and commissioning; authorised sales staff approve price and commitments. Regulation and tariff assumptions must be dated and checked before customer proposals are issued.

Is this a useful fit for your business?

A good fit is an installer or EPC team coordinating several salespeople, surveys and crews, particularly where project handover or maintenance is difficult.

A small equipment dealer may need a standard CRM or stock package. Complex design requirements need an appropriate engineering tool alongside operational software.

Start with one enquiry-to-handover project

Map the records
Review a redacted survey, quote, equipment list and handover pack, identifying the authoritative source for each field.
Pilot real exceptions
Test a quotation revision, substituted equipment, rescheduled crew and unresolved commissioning item.
Extend into support
Train the teams and connect warranty or maintenance workflows after the installation record is reliable.

Agree the first release

Scope, migration and ongoing operation

What the agreed scope can include

Enquiry, survey and quotation history
Equipment allocation and installation stages
Handover, warranty and maintenance tasks

What needs separate scoping

Engineering design, policy advice and guaranteed customer savings are outside the CRM’s administrative role.

Data migration

Review open project stages, accepted quote versions, equipment serials and existing warranty or handover records.

Training and ongoing support

Train survey, sales, procurement, installation and support staff on approvals and project exceptions. Agree support hours, issue ownership, backups, recovery checks and change-request terms before rollout.

Useful answers

Questions and answers

Can this calculate system sizing and customer savings?

Only through an explicitly scoped, reviewed calculation or specialist-tool connection. Engineering inputs and current tariff or policy assumptions must remain visible and accountable.

Can we track serial numbers and warranty claims?

That can be included where your staff capture reliable serials and warranty terms. Claims should link to the relevant equipment and approved handover record.

How do quotation changes reach installation teams?

Retain versions and mark the approved scope. Material changes require review, then update procurement and installation tasks with a traceable handoff.

Can we keep our current solar-design software?

Yes, where a supported interface or export makes the connection practical. Discovery checks technical access, licences and what information should be exchanged.

What determines the project cost?

Project stages, quotation rules, stock/serial tracking, design-tool access, data migration and after-sales requirements shape the estimate. Tool licences, hosting and support are identified separately.

When could we go live?

We set a phased schedule after discovery and access checks, rather than promise a date before scope is known. A rollout date depends on verified project records, quotation controls and installation-team acceptance of the pilot handover. Start with the agreed pilot and expand after sign-off.

Discuss a focused first step

Bring one project handoff that needs fixing

Tell us how enquiries become surveys, quotations and installation jobs. A redacted project pack can help identify the smallest useful pilot.