SurgePV × Heaven Designs · Video plan

Built by designers, for designers

Two videos that put a real design team using SurgePV on camera: what features they use, and a real design shown next to the real install.

27 Oct 2026Owner: SiddharthStatus: draft, HGE site approvals in hand

WhyProve a real team uses this every day

Aurora, OpenSolar and Arka are 100x our size. Prospects doubt that a smaller tool is stable and that it was designed by people who know the work. Heaven Designs answers both doubts: we run a real design team that uses SurgePV every day on real projects. These videos put that team on camera.

The two videosOne shoot day, one site, a full feature library

Video 1

Designers' favourite feature

One Heaven engineer per clip names one SurgePV feature they use, says what it saves them, and stops. 1–4 sentences, 10–25 seconds, in their own language with English subtitles. Aim for 12–20 clips across nationalities, genders and languages.

Video 2

Designer walkthrough on an installed HGE site

A Heaven designer screen-records a real HGE site in SurgePV and narrates each feature as they use it. Each step cuts to drone and ground footage of the same roof, already installed. 6–10 min master; every chapter also exports as its own feature demo.

Video 1: the three prompts (no script)

  1. Which feature do you open first on a hard project?
  2. What did you do before it existed, or in the tool you used before?
  3. What does it save you: minutes, a redraw, a site revisit, an argument with the client?

Video 1 shoot spec

  • 4K landscape, face centred with headroom, so 9:16 and 1:1 crops work from the same file.
  • Same background and lighting for everyone, so the clips read as one team.
  • Lav mic, clean room audio, 10 s of room tone per person.
  • At each person's desk with SurgePV behind them. Record a 30 s screen capture of their feature for B-roll.
  • Lower third: first name, role, city/country, years designing.
  • Written release from each person before the shoot. Ask the team; don't assign people.

Video 1 cut map

CutLengthUse
Master2–3 minHomepage, About, sales deck, YouTube
Feature singles10–25 sFeature pages, social posts, in-app tooltips
Language cuts60–90 sCountry pages and regional ads
Montage30 sPaid social (9:16, 1:1)
Supercut by feature45–60 sThree designers on one feature; battle cards
Onboarding inserts15 s"<name>'s tip: …" first-run tips

Section 1Which features go on camera

The ruleFilm only what a real user gets on the live app today, and only what the Heaven team actually uses.

Heaven designers rated SurgePV 6–7/10 against SketchUp on 13 Oct. If a designer praises a feature they don't use, it will show on camera, and an Arka user will point it out in the comments. So this list is a menu for the engineers to choose from, not a script.

Feature status comes from the ClickUp mirror (last synced 12 Oct) and the requirements register (20 Oct, addendum 25 Oct).

Tier 1

Live on the app, safe to film

Listed in the order a design is built, which is also the order Video 2 follows.

#FeatureLive sinceLikely angle (in the engineer's own words)
1Google 3D imagery + Fit to 3D for roof heightsR1/R2Building heights come from the 3D mesh, not site photos or a tape-measure visit
2Composite roof / pitch tool, flat roof with parapet and setbacksR1–R3Complex roofs drawn in minutes; setbacks start at the parapet
3Obstructions and trees, azimuth-aligned snapping when repeated10 AugWater tanks, staircases and trees placed fast and casting real shade
4Walkways, handrails, safety linesR1–R3Things that get forgotten in SketchUp but a real rooftop needs
5Snap system plus mirror / repeat / copyR2–R4Repeating blocks across a building without redrawing them
6Fill face and add table / lasso add tableR1–R3A full roof filled in one action, with spacing rules applied
7Right-click orientation (landscape/portrait) while placing21 SepA layout change that used to mean redrawing the whole table
8Remove single panels without breaking the structureR1Clearing panels around a vent without rebuilding the table
9Structure types with editing (TSL: fixed tilt, shed, flush)6 OctThe structure HGE actually installs, shown in 3D and editable
10Semi-automatic stringing12 OctStrings done in minutes, with inverter limits checked as you go
11SLD generated from the design, PDF and DXF exportR2The single-line diagram comes from the design, not drawn in AutoCAD
12Conduit and cable tray12 OctCable routing on the roof, for C&I jobs
13Sun simulation, heatmap, solar accessR1–R2You see the shade before you commit to a layout
14Bill upload (PDF) into the energy pageAugConsumption entered from the bill instead of typed in
15Module/inverter search by size and AI datasheet upload17 SepFinding the right Waaree module without scrolling 50 pages
16Customizable proposal + 3D link (mobile)R2The customer opens their roof in 3D on their phone
17Design sharing in the org and duplicate designAugTwo designers on one project, or a v2 option for the client
18SketchUp and AutoCAD exportAugThe design goes into the tools the rest of the job still uses
Tier 2

Confirm on the live app before filming

These were on dev at the last sync. Someone has to open the live app and check each one before it's filmed.

Battery in the studioP90 / P75 / P99Hourly/monthly data exportShift multi-select & drag-selectManual table editsBill AI for ToU & tiered ratesMulti-inverter SLDSize-based incentives3D model importPanel textureBOM revampRecommender revamp3D link button on proposal pageFeet-inch input
Check before booking any screen recordingsThe UI revamp was already on dev on 3 Sep. If it ships soon after we record, every recording will show the old interface. Ask engineering for its release date. If it's within a month, record after it ships.
Do not film yet
FeatureWhy
Smart FillPrototype and spec only (27 Oct)
Pitched roof / SmartroofDev in progress; 41 open Smartroof bugs
3D editing, push/pull, erase part of a polygonHGE's own requirements, not built yet
Editable/welded structures, carport, truss, ground mountPlanning or backlog; editable structures are HGE's top complaint
Fill to a kW capacity limitBacklog
AI roof / obstruction detection, ClaraRoof geometry still has bugs and there's no PRD. Prospects already ask "where is the AI"
DXF import, PVsyst export, CRM, BESS, Structure BOMNot shipped
Solar access on large projectsSlow. On camera, use a residential or small C&I roof only

Video 1How to hand out features

  1. Ten-minute poll with the Heaven team. Show the Tier 1 list. Each person picks two: the one they use most, and the one that saved them the most time on a real job.
  2. Assign from the poll so the 18 features are covered. Each person gets one of their two picks. Cover every stage (site, panels, structure, electrical, energy, proposal) so the master runs in design order.
  3. Two people on the same feature is fine for the big ones (fill face, stringing, structure, 3D link). That gives the "three designers, one feature" supercut.
  4. Before the shoot, each engineer opens their feature on the live app and records the 30 s screen clip on a real Heaven project. If it misbehaves, they swap to their second pick.
  5. Ask who has used Arka, Aurora, OpenSolar, PVsyst or SketchUp professionally. Their "what I did before" line becomes the clip for that "Switching from" page.

Section 2Video 2: designer walkthrough on an installed HGE site

2.1 Pick the site (one day)

Choose from the approved sites using these criteria, in this order. Keep one backup in case the first fails the as-built check.

  1. The as-built matches a design we can show. Panel count, table layout, structure type, inverter and string count all match the install photos.
  2. Flat RCC roof or shed. Pitched roof isn't live yet.
  3. Shows several Tier 1 features: more than one roof level, a parapet, an obstruction (water tank, staircase, tree), walkways, a TSL-type structure, a string inverter, and cable tray or conduit if possible.
  4. Residential or small C&I (under about 100 kWp), so solar access and heatmaps compute quickly on camera.
  5. Has generation data from the inverter portal covering a few months. This is optional, but very strong if we have it (see 2.4).
  6. Good drone access: no airspace restriction, roof visible from above, safe for a ground crew.

2.2 Pre-production (about 4 days)

StepWhatWho
As-built checkCompare the design with install photos: panel count, rows, structure legs, inverter location, strings. Write down any differences.Presenting designer + HGE site engineer
Redraw on the live appRebuild the site in SurgePV on the app build, not dev, using only Tier 1 features. Save a copy at the end of each chapter (VIDEO-01-site, VIDEO-02-roof, …) so any chapter can be re-recorded from a clean start.Presenting designer
Clean demo orgCustomer name and street hidden or replaced (keep the city). No other customers visible in project lists, no test data in the inventory.Presenting designer
Chapter outlineOne line per chapter: what's on screen, the one point to make, the matching real-world shot. Bullet points, not a script.Presenting designer + producer
Real-shot listEach feature visible on the real roof (parapet, walkway, structure legs, inverter, ACDB/DCDB, cable tray), so the crew films the match for every chapter.Producer
Shadow timeIn the sun simulation, pick a date and time when a clear obstruction shadow falls on the array. Film the real roof at the same time of day for the match cut.Presenting designer

2.3 Chapters (6–10 min master; each chapter also exports alone)

#ChapterOn screenReal-world matchLength
0Cold open3D view, slow orbitDrone orbit of the installed array, same angle; match cut5–8 s
1The siteProject page: location, roof type, customer goal, sanctioned loadDesigner on the roof or at the gate, one line to camera20 s
2Imagery and heightsMap, Google 3D, Fit to 3DDrone top-down, north-up, same framing as the 2D view30–45 s
3Roof, parapet, setbacksComposite / flat roof with parapet; setbacks appliedGround shot along the parapet30–45 s
4Obstructions and treesWater tank, staircase, tree, azimuth snappingThe same water tank and tree in real life30–45 s
5Walkways and handrailsWalkway placementThe walkway on the real roof20–30 s
6Panel layoutFill face or add table, orientation change, removing single panelsDrone pass over the rows45–60 s
7StructureTSL structure in 3D, one editClose-up of the real legs and purlins30–45 s
8StringingSemi-automatic stringing, inverter limitsThe installed inverter, its label, string wiring45–60 s
9SLD and cablingSLD generated, conduit / cable trayACDB/DCDB and cable tray on site30–45 s
10ShadeSun simulation at the chosen time, heatmap, solar accessReal shadow at the same time of day, side by side30–45 s
11EnergyBill upload, tariff, expected generationInverter portal: actual generation (only if 2.4 passes)30–45 s
12ProposalProposal pages and the 3D link on a phoneCustomer or HGE rep holding the phone on the roof (optional)30–45 s
13CloseProposal page next to a photo of the installed systemDesigner's one closing line10–15 s

Optional chapter 14: SketchUp/AutoCAD export, for the "works with your tools" message.

2.4 Predicted vs actual generation (decide before the edit)

Putting SurgePV's predicted monthly generation next to the inverter's real figures is the strongest proof we could show, and also the riskiest. Pull the real data first and compare it privately:

Within about ±10% on annual energy

After allowing for real downtime and soiling: put it in chapter 11.

Further off

Leave it out and don't publish it. Raise it with engineering as a calibration case: it relates to the known "global irradiance too high" issue.

2.5 Recording spec

Screen

  • 2560×1440 (or 1080p) at 60 fps in OBS. Browser at 110–125% zoom so the UI is readable on a phone.
  • Clean Chrome profile: no bookmarks bar, no extensions, notifications off.
  • Highlight the cursor and show keystrokes. Shortcuts are part of the story.
  • One take per chapter, each starting from that chapter's saved copy. Cut out waiting time in the edit, but don't make the app look faster than it is.

Face-cam & audio

  • Face-cam on its own track (same 4K spec as Video 1), for a corner overlay or a full-screen cut.
  • Lav mic, the same one as Video 1. 10 s of room tone per session.

Site

  • Drone: a top-down shot matching the 2D view, an orbit matching the 3D camera, a low pass along the rows, and a 2–3 min shadow time-lapse.
  • DGCA-registered pilot; check the Digital Sky zone the day before.
  • Ground: every item on the real-shot list, plus 30 s of the designer walking the roof.
  • Morning or late afternoon, with one session timed to the shadow match.

ScheduleFour weeks, both videos in parallel

WeekVideo 2Video 1 (same weeks, shares crew and kit)
1Pick the site, as-built check. Confirm the UI revamp date. Redraw on the app. Chapter outline.Team poll; assign features; collect release forms
2Screen recordings: two half-day sessions, chapters 1–13.
Site day: drone, ground shots, shadow time-lapse, designer on the roof.
Shoot day at the Heaven office, 15 min slot each; screen clips the same day
3Edit the master; check every match cut lines up; English subtitlesEdit the 2–3 min master; subtitles per language
4Export each chapter as its own feature video; thumbnailsSingles, language cuts, 30 s montage, onboarding inserts

Roles

RoleDoes
ProducerOwns the schedule, shot lists, releases, final check
Presenting designerAs-built check, redraw, recordings, narration, closing line
HGE site contactSite access, install photos, inverter portal data, roof safety
Drone operatorDGCA-registered; flies the shot list
EditorMasters, chapter exports, cutdowns, subtitles
Engineering contactConfirms Tier 2 features and the UI revamp date; on call during recordings

RisksWhat could go wrong

RiskWhat to do
The UI revamp ships right after recordingGet the date in week 1. If it's close, record after it ships.
The app breaks or is slow on cameraRecord on the app build from per-chapter saved copies; retake. Small residential or C&I site only.
Design and install don't matchThe as-built check catches this. If a difference remains, the designer says on camera what changed on site and why. Being upfront about it keeps the video credible.
Actual generation embarrasses the predictionCheck privately first (2.4). Leave it out if it's off.
Customer is identifiableBlur house number and gate signage; city only in the lower third.
A feature on camera changes soonChapters are standalone, so re-record only that chapter.

Website add-on"Switching from" footer

Like Attio's "Import from" footer, which names the tools customers leave: Switching from: Arka · Aurora · OpenSolar · HelioScope · PVsyst, with each name linking to its own migration page.

One honest constraintSurgePV has no project import from these tools, so the footer must not say "Import from". The better offer: Heaven Designs redraws your existing projects in SurgePV. That answers the most common Arka objection ("I'll have to redraw my previous projects") with a service no software-only competitor can match.

Each "Switching from X" page carries:

NextDecisions still open

  1. Which approved site, plus a backup: chosen with the 2.1 criteria and the as-built check.
  2. Who presents Video 2: someone who uses SurgePV daily and is comfortable on camera, ideally also in Video 1.
  3. The UI revamp release date: from engineering, before any screen recording is booked.
  4. Who produces and who edits: in-house or external.
  5. Which languages and markets come first: this decides which language cuts get made first.
  6. The redraw offer: how many past projects it covers, and whether it's free or paid.