Landscaping roll-ups: consolidating Aspire, LMN and crew data

Why job costing comes before software#

Job costing comes before software because it decides whether margins can be compared across add-ons at all. One company estimates maintenance from man-hours at a loaded rate, another uses unit prices per visit, and a third recovers overhead through material markup. Moving all three onto Aspire or LMN without agreeing the model puts three incompatible sets of numbers into one database.

The costing decisions below should be written down and signed off by the platform CFO and the operations lead before any add-on's estimates or contracts are loaded.

A useful test is to re-cost a handful of the add-on's completed jobs under the platform model before migrating anything. If gross margin moves sharply, the difference usually comes from burden or overhead treatment, and it is far easier to explain to the add-on's founder before the numbers appear on a platform dashboard.

Standardizing maintenance, enhancement and snow contracts#

Standardizing contracts means giving every maintenance, enhancement, irrigation and snow agreement the same type, scope fields, renewal date and site record, whichever add-on signed it. Commercial property managers often hold contracts with more than one add-on, under different site names and different service calendars, and the platform cannot see the full relationship until those records match.

Scope exhibits and site maps are the parts most often lost. They usually sit as PDFs or images outside the management system, yet they define what a crew is paid to do. Attach them to the site record during migration, and flag contracts with assignment or change-of-control clauses, which are common in agreements with large property management companies and homeowner associations.

Snow work needs its own fields. Add-ons price it per push, per event, per season or by time and materials, and each structure records different evidence: storm logs, trigger depths, salt usage and site photos. Decide which structures the platform will offer, map old contracts to them, and keep the event logs, since they are the proof behind every snow invoice.

Crew data: what to move and what to protect#

Crew data covers far more than schedules: rosters, route sheets, timecards allocated to jobs and cost codes, production per crew, equipment assignments, applicator licenses, safety records and personnel files. Only the operational fields need to move into the platform's field management system. Pay rates, tax forms and employment eligibility documents belong in payroll or HR with restricted access.

Crew production history is valuable for estimating, but it is tied to named people. Report it at crew or division level in platform dashboards, and keep individual detail visible only to the managers who need it.

Integration sequence for each add-on#

The integration sequence for each add-on moves from definitions to data to decommissioning, so nothing is loaded before it can be compared. Running the same order for every acquisition also lets the platform reuse mapping tables instead of rebuilding them.

• 1Secure admin access to the add-on's management system, accounting system, payroll and shared drives before closing user accounts.
• 2Map the add-on's cost codes, labor burden and overhead method to the platform model.
• 3Build the contract register with type, scope, renewal date, site and assignment terms.
• 4Load sites, contracts and open work into the platform system, attaching scope exhibits and site maps.
• 5Move crew rosters, timecard allocations and equipment assignments; route personnel records to HR.
• 6Run estimates against actuals for a sample of recent jobs to test the costing mapping.
• 7Export full history, then cancel or close the old system only after the export is verified.

Retiring small-company systems such as Jobber#

Retiring a small add-on's system starts with knowing what cancelling actually does. Jobber's help center, for example, says cancelling an account preserves it and lets you re-subscribe later to retrieve reports, while permanently closing an account is final. That difference decides whether a missed export can be recovered.

Jobber also says CSV-format reports can be exported by picking a report, setting the date range and exporting, and that client export is available on select plans. Set date ranges back to the add-on's first year on the system, check the plan before relying on any export, and keep the files with the platform's archive index. Spreadsheet-run add-ons need the same discipline: collect every version, not only the latest workbook.

Illustrative: a commercial landscape platform's third add-on#

Illustrative: a fictional commercial landscape platform runs its founding company on Aspire. Its third add-on is a design-build and maintenance company on LMN with a strong snow business tracked in spreadsheets. The add-on burdens labor inside its hourly rate, while the platform shows burden as a separate line.

The operating partner holds migration until the cost code mapping is agreed and tested against a sample of last season's jobs. The contract register reveals that several property managers already buy maintenance from both companies under different site names, so sites are merged before contracts load. Crew timecards move into the platform system, personnel files go to HR, and the snow spreadsheets are archived with every version. Branch margins become comparable from the next season onward.

How SourceX approaches landscape operating records#

Consolidated landscape records, such as estimates against actuals, crew production by task, maintenance visit logs, irrigation repairs and snow event histories, are linked operating records of the kind AI developers use for estimating and scheduling tools. Under the SourceX Enterprise Data Value Framework, domain expertise, human-generated signal, recency, data cleanliness and rights add value, while the privacy burden of crew personal data and preparation cost reduce net value.

SourceX runs any license through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Crew names, pay details and customer contacts are removed during Preparation, and the supplier approves every step.