Software for solar and energy engineering
Engineering teams lose most of their time to steps that are mechanical: redrawing the same layout, recalculating the same table, producing the same document set for every project.
Typical problems
- Layouts drawn by hand for every site, then redrawn when a constraint changes.
- Calculations spread across spreadsheets with no shared version of the truth.
- Documentation assembled manually for each project and each authority.
- Component and price data updated in several places, or not at all.
What we build
- Layout and design tools that generate options from site geometry and constraints.
- Calculation engines with versioned inputs, so a result can always be reproduced.
- Automated document sets: technical reports, bills of material, offers.
- Component and pricing catalogues kept in one place and used everywhere.
- Project systems that carry a site from first enquiry through to handover.
Constraints we design around
Correctness
Calculations validated against your existing spreadsheets before anything replaces them.
Traceability
Every generated document tied to the exact inputs and version that produced it.
Standards
Output shaped to the norms and templates the authorities and clients expect.
Engineer control
Generated results stay editable. The tool proposes, the engineer decides.
How the work runs
We start from one real project and its files. Reproducing an existing result exactly is the fastest way to prove the model is right.
The calculation core is built and validated first, separately from any interface, because that is the part the team has to trust.
Automation is added where it saves the most hours, one step at a time, so the team keeps working throughout.
Questions we get
Can it work with our CAD or design tools?
Usually yes, through file exchange or an API. We check the formats early and tell you what is realistic before you plan around it.
Our calculations are in spreadsheets nobody wants to touch.
That is a normal starting point. We rebuild the logic, then run both versions in parallel until the numbers match on real projects.
Do we have to change how we work?
The tool follows your method rather than replacing it. If we think a step should change, we say why, and it stays your call.