Projects, buildings, floors, units
The full physical hierarchy modelled explicitly, with amenities, floor plans and unit types — so inventory is a fact rather than a spreadsheet tab.
Groundwork
Build it. Sell it. Manage it. One system for all three.
Groundwork is a 21-module ERP for property developers. Projects, buildings, floors and units are modelled once, then everything else hangs off them: construction milestones, procurement and suppliers, sales and bookings, buyer payment plans, contracts, rent, maintenance, shareholders, HR and finance.
- 21 modules
- Unit-level inventory
- Buyer payment plans
- Rent & leases
- Customer portal
- Shareholder register
Built, pre-launch 21 production modules across construction, sales, rental and finance.
21modules
covering build, sell and manage in one system
63migrations
of modelled development, sales and finance domain
5role types
admin, finance, sales, project management and customer
1source of truth
from floor plan to final payment
01 / The problem
The unit is the atom. Almost no system treats it that way.
A developer’s entire business is a set of units. A unit is under construction, then available, then reserved, then sold on a payment plan, then handed over, then rented, then maintained. It generates cost, then revenue, then service charges.
Most developers track that journey across a construction spreadsheet, a sales spreadsheet, an accounting package and a WhatsApp group. Nobody can answer “what has this unit actually cost us and earned us” without an afternoon of reconciliation.
Groundwork models the unit once and lets every module — construction, sales, contracts, rent, maintenance, finance — attach to it. The question becomes a page, not an afternoon.
02 / In operation
What the team actually looks at.
The shape below is true to the real product. The numbers are not — these are illustrative values, never customer data.
Groundwork project / tower B live
Units sold 128/180 71%
Collected $4.2M +$310k
Arrears $186k
Build progress 74%
- Unit B-1204 · 3 bed Instalment 6 of 12 received on plan $28,000
- Unit B-0907 · 2 bed Reserved · contract pending signature reserved
- Unit B-0312 · retail Leased · rent run posted let $3,400/mo
- Unit B-1508 · 3 bed Instalment 4 overdue by 21 days arrears $22,000
Illustrative interface with sample data.
03 / Capabilities
What it does, in detail.
12 capability areas, each built because the operation breaks without it.
Construction and milestones
Construction phases and milestones tracked per project, with progress visible to management and, where you choose, to buyers.
Sales and bookings
Availability, reservation, booking and sale against a specific unit, with the sales team working from live inventory instead of a printed list.
Buyer payment plans
Instalment schedules per buyer with due dates, receipts, arrears visibility and statements the customer can see themselves.
Contracts and documents
Contract generation and a document store attached to the unit, the buyer and the project, so evidence lives where it is needed.
Procurement and suppliers
Suppliers, purchase orders and expense capture tied to projects, giving a real cost position per development.
Rent and leases
For retained stock: tenancies, rent runs, arrears and renewals, in the same system that sold the unit next door.
Maintenance
Work orders against units and common areas, assigned, tracked and costed back to the project or the service charge.
Shareholders
A shareholder register with entitlement tracking — the module most developers keep in a lawyer’s filing cabinet.
HR and payroll
Staff records, structure and payroll inputs for the site and office teams that the projects depend on.
Customer portal
Buyers sign in to see their unit, their payment plan, their receipts and their construction progress — which removes most of the calls to the office.
Reporting and dashboards
Sales velocity, collection performance, project cost position and occupancy — read from the same records the modules write, so no figure is re-keyed. The reporting surface is still being widened.
04 / Surface area
21 modules, one system.
Breadth is only an asset when the parts share a data model. Every module here reads and writes the same records — there is no export step between them.
- Project
- Unit
- Construction
- Sales
- Lead
- Customer
- CustomerPortal
- Contract
- Finance
- Expense
- Supplier
- Rental
- Maintenance
- Document
- ShareOwner
- HR
- Communication
- Notification
- Reporting
- Dashboard
- UserManagement
05 / Architecture
Genuinely modular, so a developer can switch on only the business they are in.
A Laravel application built on a first-class module system — each of the 21 modules is independently enabled, with its own routes, models, migrations and views. A developer doing build-and-sell only can run without Rental and Maintenance until the day they need them.
- L1 Staff interface Role-scoped web application for admin, finance, sales and project management.
- L2 Customer portal Buyer-facing access to unit, plan, receipts and construction progress.
- L3 Module layer 21 independently toggleable modules over a shared core.
- L4 Core Identity, permissions, audit logging, documents and notifications.
- L5 Async Queued jobs for statements, rent runs, notifications and reporting.
06 / Integrations
Built to connect, not to be a silo.
Third parties are first-class parts of the architecture, isolated behind stable internal contracts so any one of them can be replaced without touching the core.
Payments
Collection of instalments and rent with receipting straight onto the buyer ledger.
Messaging
Email, SMS and push for payment reminders, milestones and maintenance updates.
Document storage
Cloud or local object storage for contracts, plans and evidence.
Accounting export
Structured export of financial movements for the finance team’s ledger of record.
Construction & property
Want Groundwork for your operation?
We can walk you through the live platform, talk about how it maps onto how you work today, and be honest about where it does not fit.