HSHS RenewablesYours / No back doors
Sample data. Not connected to your Xero.
Yours

No back doors

You wrote “is it are package with no back doors”. You own the system, all of it, from day one: the code, the data, the hosting account and the documentation.

If we were not around: nothing changes. The system keeps running on your own hosting account, your data exports in full any day, and any competent web developer can maintain or extend it using the documentation we hand over at launch.

What is yours

At handover
The codeYours from day one, every change kept, so another developer can pick it up.
The dataYour database. Export everything to a spreadsheet any day, no asking.
The hosting accountIn your name. We have a login you can switch off.
The domain and integrationsYour domain and your Xero account. Connections are authorised by you and stay with you.
The documentationWritten instructions for the office and for the next developer.
The trainingRecorded walkthroughs for the office and the install staff, and a handover session at launch. Nobody needs us on the phone to do their job.

Who can get in

WhoNamed accounts only
What they seeOwner, Management or Install staff. You decide who is which.
The accountsRegistered to your business, not to ours. We work inside them.
UsA login you can switch off

Who sees what →

Every action, with who did it

Every step on a job is recorded with the name of the person who did it: who booked the survey, who moved the stock onto the van, who signed it off. It is on the job record, for you to read.

See it on Follow one job →

Export everything, any day

Everything exports to a spreadsheet from the admin screens, and the database itself can be copied out whole. Nothing is held in a format only we can read. You can take a full copy at any time without asking us.

Exit paths, written down

  1. Keep running it yourself. Nothing expires. There is no licence key.
  2. Bring in your own developer. Give them the code and the written instructions. We will do a recorded handover call with them.
  3. Move to another agency. Same as above. It is built with tools most developers already know.
  4. Move hosting. The whole system can be moved to another provider or another team, or the data lifted out into a different database if you outgrow this one.
  5. Move to a packaged system later. Because your data is clean and exportable, it starts from real records, not a spreadsheet archaeology project.