From Personal Solar System to a Public Engineering Tool

"Most software tools are born from requirements documents. Global Sun Hub started with something much less elegant: a roof, a calculator, and a lot of wrong assumptions."

Before this project became a public platform, it was just me trying to answer a simple question: How many solar panels can I actually install on my roof — and what will that system really look like?

That question turned out to be far more complex than most online tools are willing to admit.

From a personal solar system to lines of code

I didn’t start Global Sun Hub as a product idea. I started it as a homeowner building a solar system.

Like many others, I began with online calculators. They were fast, clean, and confident. Too confident.

On paper, it looked fine. On my roof, it didn’t.

Real panels have dimensions. Roofs have edges, obstacles, and orientations. And suddenly, the “perfect” system didn’t fit anymore. That mismatch — between theory and reality — became the seed for the first algorithm.

When solar theory breaks on a real roof

The first thing that broke was the idea of average panels.

Mixing formats breaks layout assumptions completely. Most calculators ignore this because it complicates the math. I couldn’t — because my roof forced me not to.

That’s when the concept of panel formats appeared in the code: discrete size groups, real dimensions, and efficiency as a variable, not a constant. Suddenly, the system size was no longer a single formula — it was a constraint problem.

Turning a roof into a constraint system

Once you stop pretending roofs are rectangles, everything changes. A roof becomes a finite surface with unusable margins, orientation constraints, and panel spacing requirements.

This meant the calculator had to reject impossible layouts, prefer fewer, larger panels in some cases, and prefer smaller formats in others. Some outputs became less impressive — and more honest.

"Accuracy over optimism. That was the most important design decision we made."

The biggest surprise: energy ≠ system size

Another thing that broke quickly was the obsession with kilowatts. Two systems with the same kW can have different panel counts, different layouts, and different production profiles.

Real-world experience forced the logic to separate:

That separation now exists everywhere in Global Sun Hub. It’s also why the tool tries to explain why a result looks the way it does — not just show a number.

Engineering decisions driven by reality, not conversions

Building this as a public tool raised a different question: Should this behave like a lead generator — or like an engineering instrument?

Most platforms choose conversion. Global Sun Hub chose clarity.

That meant no forced assumptions, no hidden defaults, and no “contact an installer” as the main outcome. It also meant extra engineering work — more edge cases, more validation, more explanations. But that’s the cost of respecting the user.

What changed after real users arrived

Once other people started using the tool, the pattern repeated itself: unusual roofs, mixed panel expectations, and country-specific constraints. Each one fed back into the system. Algorithms evolved, defaults became configurable, and explanations became more explicit.

Global Sun Hub stopped being my calculator. It became a shared engineering surface.

The goal is simple

Give people tools that help them understand their system — not just buy one. If this sounds slower, messier, and harder than typical SaaS development — it is.

And that’s exactly the point.