Credit & Underwriting
CompletedSoft Credit Inquiry Completed
Case studyThis collection is private for now. Enter the password to view.
← Return to mikebatts.netProduct design & engineering
Daylight brings solar and batteries to homes. I designed and built the portal that brings the people behind each installation together.
A home at the endConceived, designed, engineered.
From the first workflow to production.
01The shared project
From sales to operations to builders, the work changes hands. The project should not lose its context along the way.
142 Orchard Lane · DL-1042
Soft Credit Inquiry Completed
utility-bill.pdf
Acceptable documents for title verification
Send the PPA to the customer.
The stages show where a project is. The requirement cards explain what moves it forward. Completed work stays visible; an outstanding review stays outstanding.
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
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.
View and manage your jobs
| Customer Name | Stage | Next Step | Sales Rep |
|---|---|---|---|
| Alex Morgan142 Orchard Lane · DL-1042 | Origination | Awaiting review | Jamie Park |
| Jordan Lee26 Maple Drive · DL-1086 | Document Verification | Upload missing documents | Jamie Park |
| Sam Rivera8 Cedar Court · DL-1103 | Installation | Submit installation photos | Taylor Brooks |
Name a useful set of filters once. Return to the same slice of work tomorrow. The destination changes; the shared project record does not.
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
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.
Alex Morgan · DL-1042
@Taylor Brooks The bill is uploaded. What still needs to happen before we can send the agreement?
Title verification is awaiting reviewer approval. I’ll check on the timing.
Confirmed the system details with the homeowner.
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
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.
Notes first. See the latest handoff before the paperwork.
The stages, on demand. A compact current stage opens into the full journey.
Room to reply. Notes opens into a near-full-height sheet.
Title verification document uploaded. Awaiting reviewer approval.
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
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.
06After power-on
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.



Original screenshots from the Daylight homeowner app.
07Conception to production
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.
Project pages, stage rules, role-aware navigation, and saved views.
Project Notes, attachments, individual mentions, notifications, and a mobile-first hierarchy.
Ray’s shared engine, portal surfaces, and homeowner lane.
The homeowner app’s energy and payments experience, with native implementation by our iOS engineer.
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.