Skip to content

DaylightProduct design & engineering

Solar takes
a team.

Daylight brings solar and batteries to homes. I designed and built the portal that brings the people behind each installation together.

A home with solar panels across its roofA home at the end
of every handoff.
Daylight · 2024 to present

Conceived, designed, engineered.
From the first workflow to production.

Mike Battaglia
Senior PM & Product Engineer

01The shared project

The whole picture.
And the next step.

From sales to operations to builders, the work changes hands. The project should not lose its context along the way.

Daylight

Dashboard / Alex Morgan

Alex Morgan

142 Orchard Lane · DL-1042

Ask Ray
ApplicantAlex Morgan
Sales organizationOrchard Solar
InstallerNorthline Energy
OriginationStage 1 of 6

Credit & Underwriting

Completed

Soft Credit Inquiry Completed

System Details

System Size (kW-DC)
8.40
Year-1 Production (kWh-DC)
11,250

Upload Utility Bill

Uploaded

utility-bill.pdf

Title Verification

Pending Approval

Acceptable documents for title verification

Title verification document uploaded. Awaiting reviewer approval.

Energy Subscription Agreement & Underwriting

Send the PPA to the customer.

Not sentTitle verification is pending.
Source-faithful reconstruction · Fictional project data · Selected origination cards

Progress is more than a status.

The stages show where a project is. The requirement cards explain what moves it forward. Completed work stays visible; an outstanding review stays outstanding.

Designing around the real project rules

I built the project pages, stage navigation, and requirement flows around the work itself. The six phases have different conditions and owners. Credit, equipment, system design, pricing, utility bills, title checks, and the agreement belong to origination, not one generic form.

The illustration selects five cards for readability. Later stages remain visible but unreached. Actual availability depends on the project, its completed requirements, and the viewer’s permissions.

02Each person’s work

One portal.
Your kind of work.

A salesperson follows their projects. A reviewer works a queue. I designed the navigation around those roles, and saved views around the work people return to.

Dashboard 3 Jobs

View and manage your jobs

Filters
ViewsAll jobsNeeds attention Ready to install + Save view
Fictional jobs in the Needs attention dashboard view
Customer NameStageNext StepSales Rep
Alex Morgan142 Orchard Lane · DL-1042OriginationAwaiting reviewJamie Park
Jordan Lee26 Maple Drive · DL-1086Document VerificationUpload missing documentsJamie Park
Sam Rivera8 Cedar Court · DL-1103InstallationSubmit installation photosTaylor Brooks
Showing 3 sample jobsNeeds attention · Saved view
Reconstructed dashboard · Named views preserve personal filters and sorts, not separate copies of the project.

Start where you left off.

Name a useful set of filters once. Return to the same slice of work tomorrow. The destination changes; the shared project record does not.

Roles, saved views, and permission boundaries

I built persistent, personal filter-and-sort sets across the dashboards. The sidebar shows destinations the user is entitled to access. A Sales/Reviewer switch appears only for users entitled to both roles, not as a universal mode switch.

This is a static, selected-column reconstruction. In the product, saved views can be created, updated, and deleted. These views keep frequently used filters close without duplicating the underlying project record.

03Project Notes

The conversation
belongs here.

A status cannot tell the whole story. I built Project Notes to keep questions, evidence, and the people answering them beside the work.

One project, one conversation.Context stays together as the project moves through its stages.

A handoff to a person.Mentions and replies bring the right teammate back to the right note.

Evidence within reach.Files stay attached to the question they help explain.

Project Notes

Alex Morgan · DL-1042

Jamie ParkPartner

@Taylor Brooks The bill is uploaded. What still needs to happen before we can send the agreement?

utility-bill.pdfPDF attachment
Taylor BrooksDaylight

Title verification is awaiting reviewer approval. I’ll check on the timing.

ReplyAsk RayClose Note
Alex MorganPartner

Confirmed the system details with the homeowner.

ReplyAsk Ray
Create Note8 notes in this project
Source-faithful Notes reconstruction · Fictional people and thread
The small decisions behind a useful conversation

Threaded replies, individual mentions, removable pending attachments, drafts, unread counts, and notification preferences all shape the handoff. Notification deep links open the project’s Notes and focus the relevant thread.

Attaching a file to a note keeps evidence with the conversation. It does not file it as a project document or approve a requirement. In this example, the bill was uploaded to the project separately. Posting a reply does not complete a requirement.

Ask Ray carries the note’s context into an editable draft before it is sent. Nothing sends automatically. The Notes modal closes so the Ray drawer opens in view; a person can then review a reply before posting it.

04Designed for the job site

A phone needs
a different order.

Shrinking the desktop page buried Notes below a long block of applicant details. I moved the conversation up, made stages collapsible, and kept the next step in reach.

01

Notes first. See the latest handoff before the paperwork.

02

The stages, on demand. A compact current stage opens into the full journey.

03

Room to reply. Notes opens into a near-full-height sheet.

9:41
Daylight

Dashboard / Alex Morgan

Alex Morgan

Project Notes8 Total

Tag collaborators and create internal notes for this project.

View 2 New Notes
Applicant DetailsAlex Morgan
142 Orchard Lane
OriginationStage 1 of 6
  1. OriginationCurrent
  2. Document Verification
  3. CAD Design & True Up
  4. Permitting & Interconnection
  5. Installation
  6. Permission to Operate

Title Verification

Pending Approval

Title verification document uploaded. Awaiting reviewer approval.

Reconstructed mobile hierarchy · Open the stages
Making the same project work on two layouts

The desktop Notes card and mobile Notes card both exist on the page. I fixed their duplicate IDs and refresh behavior so an update reaches both. I also refined mobile navigation, touch targets, and deep links.

In the real portal, Notes opens in a centered desktop modal and a 92dvh mobile sheet. This inline illustration demonstrates the stage disclosure; its Notes link takes you to the thread above. It does not connect to the live portal.

05What came next

The next product
was in the questions.

What is blocking this project? Which document is missing? What happens next?

The same questions kept surfacing in Notes. I turned that pattern into Ray: cited help inside the work, with a path to a person.

Meet Ray

06After power-on

Now it’s about
living with energy.

For a homeowner, the questions are different. What did my panels produce? What is the battery doing? What am I paying for?

I designed the energy and payments experience with Daylight’s iOS engineer, who implemented the native app.

01

Understand the moment.

Daylight Energy overview: a home photograph, current battery and solar totals, and a plain-language explanation of the home’s energy
What the home is doing, in a sentence a person would say.
02

See where it goes.

Daylight energy breakdown: battery charge and solar energy generated against consumed
Production, storage, and use in one readable picture.
03

Know what you owe.

Daylight Payments: current balance, energy rate, bank on file, and bill history
A clear balance, the rate behind it, and payment history.

Original screenshots from the Daylight homeowner app.

07Conception to production

I built it.
Then kept going.

Senior PM and Product Engineer at Daylight since 2024. I owned the portal from conception through design, production code, and release, with Daylight’s operations and engineering teams.

Foundation

Make the project legible.

Project pages, stage rules, role-aware navigation, and saved views.

Collaboration

Keep the context together.

Project Notes, attachments, individual mentions, notifications, and a mobile-first hierarchy.

Intelligence

Turn questions into a next step.

Ray’s shared engine, portal surfaces, and homeowner lane.

Beyond installation

Make energy understandable.

The homeowner app’s energy and payments experience, with native implementation by our iOS engineer.

Build progression and engineering receipts

June–July 2026: stage-link clarity and unreached states; note attachments; mention and reply notifications; individual mentions; mobile Notes hierarchy and refresh fixes; role-aware navigation; persistent saved dashboard views.

August–September 2026: the Ray portal beta, reviewed replies, document workflows, live sheets, retrieval improvements, and the shared homeowner support backend. The work evolved through implementation, review, and feedback from the people using it.

I work with operations on the process rules, use AI tools throughout implementation, and take the result through engineering review. Native iOS implementation belongs to my teammate. My ownership spans the product, design, portal engineering, and the experience across those surfaces.

Different people.
One project moving forward.