BuildCycle
// REFERENCE PROJECT: LANDSCAPE CARE · WEB APP WITH OFFLINE MODE

LPV Admin

Landscape-care projects with their tasks, contracts, materials and hours in one place, even without a connection.

At LPV Gießen, every landscape-care project comes with a municipality, contacts, contracts with deadlines, tasks, materials and the hours the team puts in. LPV Admin brings this together in one browser application with logins and role-based access. It runs on a server in Germany and keeps a local copy in the browser, so work can continue when the connection drops. Invoices and contracts stay on the LPV’s own NAS or in the cloud storage it chooses.

LPV Admin
Offline · 2 changes waiting
ProjectStatus
Orchard meadow, south slopeConservationRunning
Wet meadow, valley floorEco accountRunning
Hedgerow by the farm trackConservationPlanning
Next work step
Remove the cuttings
Team Nord · this week
Queue
Withdrawal 12 × fence posts
First mowing: done

Product illustration with made-up sample data, no real projects or people.

Industry
Landscape care and nature conservation
Type
Browser application with offline mode
Cycle
Ongoing development
Stack
React 19 · Vite · IndexedDB · Fastify 5 · Prisma 6 · PostgreSQL
// THE STARTING POINT

The LPV needed one application for everything that hangs off a project, without handing its documents to someone else. Invoices and contracts were to stay on its own NAS in the office or in its chosen OneDrive or Google Drive storage, never permanently on the application server. On top of that came clear roles and permissions and the requirement to keep working without a connection. Changes made offline must not get lost. They have to reach the server automatically once the device is back online.

// WHAT WE BUILT
✓Projects with municipality, categories, project supervision and linked contacts
✓Contracts with a status workflow, deadlines, offers and exports
✓Tasks with reminders, plus a material store with deliveries, withdrawals and reservations
✓Working time, leave and overtime with evaluations and a cost overview
✓Offline storage in the browser: changes wait in a queue and sync automatically after reconnecting, with a sync history
✓A file manager that works directly on the LPV’s NAS instead of storing documents on the server
// HOW THE PROJECT RAN
Step 1
Picking up what was already there
LPV Admin already existed when we joined. Instead of starting over, we first got the existing application running as it was and checked it from end to end. That showed what already works for the LPV and where updates are still due, and the work continues from there.
Step 2
Requirements from everyday work
Conversations and feedback from the LPV team turned into a change plan. We work through it point by point and compare it against the original requirements.
Step 3
Try it in the preview first
New features arrive in small steps and land in a preview with sample data first. There, every change can be clicked through and checked before it touches real project data. Two things from everyday work matter here: anyone without a signal can still record what has been done, and the app syncs it once the connection is back. And invoices or contracts stay where the LPV keeps them anyway, on its own NAS or in the cloud storage it chose.
Today
A preview, not a promise
The current version can be used in a preview and is checked there. It is not live and not signed off yet.
Outcome
Offline
work continues without a connection, changes sync after reconnecting
NAS
invoices and contracts stay with the LPV, not on the server
Status and limits

LPV Admin is in active development. The current version runs in a preview and is neither live nor signed off (as of 17 October 2026). We do not link to the application here, because its login is reserved for the LPV team.

NEXT PROJECT
Agentic Coder →

Are your projects, deadlines and hours still spread across spreadsheets and folders? Describe your plan and get a first assessment of scope and timeline.