LAND ACQUISITION SOFTWARE / LAND CRM EVALUATION WORKSHEET
Prepared October 14, 2026 by Pillar.
Updated October 19, 2026 with a plan-and-cost record.
Method template; no vendor has been tested in this worksheet.
Guide: https://www.pillar.codes/blog/land-acquisition-software-mapping-vs-crm

Use one copy per product, plan and user role. Compare the same permitted
candidate and required outcome in each tool, including your current setup.
Keep sensitive customer records in an appropriately controlled location.

SETUP
Product / version:
Plan, trial or subscription:
Tester / user role:
Date and market:
Candidate reference:
Jurisdiction and parcel identifiers (retain as text):
Number of parcels in this opportunity:
Required outcome for the land team:
Non-negotiable requirements:
Accepted manual steps:

PLAN AND COST RECORD
Quote or public plan URL / document:
Quote / source date and expiry, if stated:
Currency:
Number of users and required roles:
Billing period and minimum commitment:
Amount actually due in the initial term:
Monthly equivalent, if advertised (retain its billing conditions):
Renewal price / terms, if known:
Geographic scope and required datasets:
Included searches / results / exports and their allowance periods:
Contact lookup and outreach credits; cost per required action:
Required add-ons and their billing periods:
Setup, import or integration work and its owner:
Recurring manual steps / separate tools:
Record access and export on cancellation:
Unpriced or unverified requirement, owner and next action:
Keep unanswered costs unknown; do not enter zero for a missing quote.
Compare the same users and required work. Do not add amounts in different
currencies or periods. Separate the initial term from renewal assumptions.

EVIDENCE STATES
Observed: task completed on the recorded plan; retain result evidence and
state whether it meets the requirement.
Documented only: source or written answer describes the capability;
no completed task yet.
Not tested: unanswered; record an owner and next action.
Unsupported: recorded failed test or explicit confirmation establishes
that this plan cannot meet the required outcome.
Missing demonstration alone is not evidence of unsupported capability.

REPEAT THIS RECORD FOR EACH TEST BELOW
Task / required outcome:
Evidence state: Not tested
Observed result and whether it meets the requirement:
Evidence file, public source URL or written vendor answer:
Source / test date:
Manual steps or separate tools required:
Unresolved question:
Responsible person / next action / due date:

TEST 1 — PARCEL IDENTITY AND SOURCES
Can a colleague identify every included parcel and jurisdiction, retrace
the source and date, and find the unanswered site question?

TEST 2 — OPPORTUNITY AND OWNER RELATIONSHIPS
Can the team relate multiple parcels to one opportunity without losing
which recorded owner belongs to which parcel? Record entity/contact
verification questions separately.

TEST 3 — INCLUDED / EXPORTED ROWS AND ALLOWANCES
Expected records:
Records included in the tested plan:
Records actually exported:
Selection or per-export limit:
Unique-row / frequency allowance and period:
How own uploads differ from platform-sourced records, if applicable:
Plan / credits / outreach assumptions and dated source:

TEST 4 — FILE AND SPREADSHEET HANDOFF
Retain the original export and inspect a working copy.
Parcel identifiers imported as Text; original values retained:
Notes with commas or quotation marks remain in their intended fields:
Candidate/parcel/owner relationships can be reconstructed:
Unresolved question and next action remain accessible:
Record the step where any information changed before attributing it to
the source product. CSV syntax does not guarantee required field coverage.

TEST 5 — COLLEAGUE REPLAY
Colleague can reopen the destination and explain the candidate,
research question, responsible person and next action without the tester:

OPTIONAL GEOMETRY TEST
Required by this workflow: Yes / No
If No, leave this outside the purchase criteria.
Format actually provided:
Geometry type / coordinate reference and axis order:
Geometry reopens and matches the source:
Point location versus parcel-boundary output kept separate:

DECISION
Suitable now / conditional on resolution / unsuitable for this workflow:
Evidence supporting the decision:
Workaround tested and accepted by:
Remaining question, owner and next action:
Review trigger or date:

A worksheet score is not a vendor benchmark, engineering opinion,
property determination or assurance that the site can be developed.