Solva Systems › Landscaping
Software for landscaping and grounds maintenance.
Recurring maintenance that schedules itself and project work that does not, in one system that understands they are different.
Book a conversationWhat usually goes wrong
Grounds maintenance is a cycle and landscaping is a project, and most companies do both out of the same yard. Software that understands one of them makes the other into admin.
- Maintenance schedules live in somebody’s head. Which sites are due, at what frequency, and which got skipped when it rained.
- Seasonality wrecks the plan. Grass in summer, leaves in autumn, and a schedule built for one that does not describe the other.
- Project work eats maintenance days. A landscaping job overruns and the round quietly slips, usually without anybody deciding to let it.
- Kit goes missing. Mowers, blowers and trailers spread across crews with no clear record of what is where.
- Contract billing is done by hand. Monthly maintenance invoices rebuilt every month from a spreadsheet.
What we build instead
Kestrel on our home page is a cyclical round, and Bramall is crews across sites. Grounds maintenance is genuinely both at once, and the engine underneath both already exists.
Rounds that schedule themselves
Every site, its frequency and when it is next due, generated rather than remembered.
Seasons built in
Frequencies that change across the year without rebuilding the schedule each time.
Projects and maintenance side by side
One view of what the crews are actually committed to, so an overrun is a decision.
Extras that reach the invoice
Additional work agreed on site added there, with a photo, and billed.
Kit tracked to a crew
What went out with whom, what came back, and what is due a service.
Contract invoices raised for you
Monthly maintenance billing generated from the schedule instead of rebuilt by hand.
Why not one of the off-the-shelf ones
Round based apps do the maintenance side well and job apps do the project side well. Most companies we speak to are running both and reconciling them by hand, which is the actual problem worth solving.
| Team size | Typical per-seat tool | Over three years |
|---|---|---|
| 5 people | around £38 a seat | about £7,000 |
| 15 people | around £38 a seat | about £21,000 |
| 30 people | around £38 a seat | about £41,000 |
The question is not whether the licence is cheap. It is what you are working around every day, and what that costs you in evenings. Work out your own three year figure.
How it works
We learn how you actually run. Usually a couple of calls. If it suits you we will come and spend a day watching the work move through the company.
You see it before you pay anything. We build the opening screens in your branding, with your words for things and demo data in them. Not a finished system, enough to see the shape of yours and tell us where it is wrong.
Then we build the real one. The monthly starts and takes three to six months depending on how much system there is. Every fortnight you are told where it is up to. One fee covers building it, running it, hosting it and improving it.
Worth a conversation about how the round and the projects fit together?
Book a conversation