Right of Way Acquisition Software: Custom Build Versus Trimble Landfolio
Buy, unless you carry a relocation caseload or federal funding participation. For a single corridor under about 60 tracts, Trimble Landfolio or Quorum Land System plus a disciplined file structure will cost less than the delay a build prevents.
On this page
Buy, unless you carry a relocation caseload or federal funding participation. For a single corridor under about 60 tracts, Trimble Landfolio or Quorum Land System plus a disciplined file structure will cost less than the delay a build prevents. Building wins when several corridors run at once, when reimbursement depends on proving sequence, and when alignment revisions force a manual reassessment every few months.
What Trimble Landfolio and Quorum Land System do well
You have a corridor, twelve agents and a Friday status meeting that runs on a spreadsheet typed up on Thursday. Before anyone proposes building something, two products are worth taking seriously.
Trimble Landfolio is a genuine land and property administration platform for infrastructure and resource projects, with real strength in tenure, obligations and spatial linkage. Quorum Land System comes out of energy land management and is strong on lease and tract administration, payments and obligation tracking for pipeline and transmission owners. Neither is a toy, and if your programme fits their model you should use it rather than pay to rediscover what they already encode. Esri sits underneath both worlds, and if your agency already runs an enterprise geodatabase with a parcel fabric, a great deal of the mapping problem is solved before any acquisition tool arrives. Some agencies also stretch Oracle Primavera Unifier into this work, which is workable when acquisition is a small part of a larger programme controls estate.
Buy if most of this is true. One corridor. Fewer than about 60 tracts. A single acquiring jurisdiction. One funding source without federal participation. No relocation caseload. Acquisition agents on your own payroll, whose files you can see. Under those conditions a packaged product and a firm document structure will carry the programme, and a build would consume the schedule it was meant to protect.
The floor is lower still. A utility acquiring twenty easements on one line does not need software. It needs a numbered tract list, a checklist and one person who owns it.
Where they stop: your stage model, relocation and segment clearance
Three edges recur, and every one of them is where agencies and utilities reach us.
The acquisition stage model is written in your manual, not in a configuration screen. Your approval sequence, delegation thresholds, offer package composition and file checklist come from statute, agency policy and funding conditions. Under the Uniform Relocation Assistance and Real Property Acquisition Policies Act of 1970, implemented at 49 CFR Part 24, order matters: an agent who makes a written offer before the review appraisal is complete has created a file that may not reimburse. Products model a pipeline. They rarely enforce a sequence that a Federal Highway Administration reimbursement audit will test line by line, or produce a per tract completeness view against your own checklist.
Relocation assistance is case management, not property administration. Displaced residential and business occupants bring comparable dwelling analysis, moving cost claims, payment schedules, entitlement calculations and appeals. That is a different discipline with a different clock, and packaged land systems either omit it or reduce it to attachments on a parcel. If you have a caseload, the attachments approach will fail an audit and will fail the occupant first.
Segment clearance is the report nobody can produce. Construction mobilises on a segment only when every tract in it is acquired, condemned with possession granted, or excluded by design change. One unresolved half acre owned by an estate in probate idles a crew costing tens of thousands a day. That report needs your corridor structure, your segment boundaries and your schedule, which are client specific by definition. It also needs condemnation modelled as a parallel pipeline against the same tract record, because the tracts most likely to delay the job are exactly the ones a voluntary acquisition model pushes into a comment field.
The arithmetic: named user licensing against building in house
Land administration platforms in this category are licensed per named user per year, with implementation quoted separately and usually running to a meaningful multiple of year one licence cost. The figures we see modelled land between roughly $2,500 and $6,000 per named user annually once the spatial module and document management are included.
Run five years on both sides, because implementation is capital on the buy side too and comparing year one flatters nobody honestly.
At $4,000 a user, 25 named users cost $100,000 a year and $500,000 over five years, before implementation. A build landing at $300,000, plus $50,000 to migrate live tract files, plus about $52,000 a year to run and extend it, totals near $560,000 across the same period. Crossover sits at about 28 named users. At $2,500 a user it moves out to roughly 45.
Express it in tracts if that is how your programme thinks. One agent typically carries 40 to 80 active tracts, so 28 users is somewhere near 1,500 tracts under management at once. Below that, buy. Above it, the licence maths stops arguing for a subscription, though the four conditions below should still be what decides it.
What a custom right of way build actually costs
A first release covering the tract register with parcel and take geometry, the acquisition stage pipeline with approval gates, appraisal and review appraisal records, approved just compensation, offer generation and service records, agent contact diaries and corridor status reporting runs $65,000 to $140,000 and ships in 12 to 16 weeks. Programmes normally start on one corridor. A full platform adding relocation assistance case management, condemnation tracking, instrument generation, payment integration, reimbursement file packaging and a landowner facing portal runs $180,000 to $450,000 across 6 to 14 months.
Two lines nobody quotes. Migrating live tract files runs 10 to 25 percent of the build and reaches the top of that range when the same tract exists in a shared drive, a spreadsheet and an outside agent's own system with three different numbers. Year two onward runs 15 to 20 percent of build cost annually, and for a public agency that figure should be in the capital request from the start rather than discovered in the second budget cycle.
What pushes it up: the number of acquiring jurisdictions and funding sources, since each brings its own procedure and checklist. Spatial depth, because reading a county assessor parcel feed is different work from consuming your enterprise geodatabase and writing take geometry back into it. Instrument templates, which are real drafting time with counsel rather than a formatting exercise. External access for outside agents and law firms, which introduces identity and permission scoping. What holds it down: one corridor, one funding source, the acquisition pipeline first.
The four conditions that move a programme to building
Regulatory fit. Federal funding participation changes the character of the file. Right of way certification under 23 CFR Part 710 has to be defensible before construction is authorised, the Uniform Act sets the order of appraisal, review, written offer and negotiation, and an interstate gas pipeline operating under a Natural Gas Act certificate carries its own conditions. When reimbursement turns on demonstrating sequence, the sequence has to be enforced by the system and exportable per tract, not reconstructed from folders.
Scale economics. Above the crossover in the arithmetic above, and rising, especially where several corridors run at once and clearance currently requires a manual roll up across programmes.
A workflow that is your competitive advantage. Alignment revision handling. When engineering shifts the centreline, a system holding parcel and take geometry can identify in an afternoon which tracts gain a take, which lose one, which acquired easements now sit partly outside the corridor and which owners must be reapproached. Programmes that do this by hand spend three weeks and still miss two tracts.
Integration sprawl across three or more systems. Enterprise geographic information systems, the financial system that issues warrants, document management, the project schedule, and outside agents working in their own tools. Every manual join between those is a place where the status on the Friday report stops matching the status in the field.
How to decide in a week
Run the blocking tract test. It costs almost nothing and it is the question your programme actually exists to answer.
Monday morning: ask for a list of every tract blocking your next construction segment, with the earliest defensible clearance date for each and the reason it is blocked. Start a timer.
Tuesday and Wednesday: watch how the answer is assembled. Note every source touched, every person interrupted and every fact that turns out to be a recollection rather than a record. Mark each blocked tract as a negotiation issue, a title or ownership issue, a condemnation issue or a relocation issue.
Thursday: check three of the tracts against the actual files. Compare the reported stage with what the folder shows. In most programmes at least one will differ, and that difference is the real finding.
Friday: if the list arrived within a day and survived the check, buy a packaged product and spend the money on agents instead. If it took three days, or the condemnation and relocation tracts had to be chased separately, or the stage in the report did not match the file, you have a build case with a scope already written by the exercise.
Then pay for discovery. At Digital Heroes that produces a signed product requirements document before any code is written: the ownership model including undivided interests, life estates and compensable tenant interests, the stage pipeline with your delegation thresholds, the geometry and clearance rules, the reimbursement checklist and the acceptance criteria. A public agency owns that document whether it proceeds with us, runs a competitive procurement against it, or takes it to Trimble.
Who we are wrong for: a single corridor of thirty easements, and any programme wanting to start development while the alignment is still moving weekly. We fit multi corridor programmes with relocation caseloads and audit history. More than fifty specialists, over 2,000 projects delivered, and a named team you meet before signing. Our India LLP, US LLC and UK LTD entities mean the intellectual property assigns under your own law, which matters when acquisition records outlive vendors. Checkable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The 2024 DORA report found AI adoption significantly increases individual productivity, flow, and job satisfaction, but negatively impacts software delivery throughput and stability - a paradox leaders must manage with fundamentals like smaller batch sizes and robust testing. Source: DORA / Google Cloud (2024) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- Salesforce's field-service research (State of Service / field service trends, survey of 5,500+ service professionals) found that 74% of mobile workers report increasing workloads and 47% say appointments don't go as planned due to customer miscommunication, unaccounted-for parts, or insufficient appointment lengths and travel times. (The separate claim that admin tasks consume ~30% of a technician's hours is NOT supported by the report - the seventh-edition data instead states technicians spend about 18% of working hours, ~7 hours/week, on admin, and only ~32% of time interacting with customers.). Source: Salesforce (2024) →
- 88% of organizations are concerned about employee retention, and providing learning opportunities is respondents' #1 retention strategy; career progress is cited as people's top motivation to learn, yet only 36% of organizations qualify as 'career development champions.'. Source: LinkedIn Learning (2025) →
Frequently asked questions
How do we model an owner who dies in the middle of negotiation?
As a change in the ownership interests attached to the tract, with the prior interest closed and the estate or heirs recorded as new interests, not as an edit to a single owner field. Probate can add months, and the tract has to keep its negotiation history intact across the change. Ask any developer to whiteboard this before signing, because it separates domain experience from confidence.
Why do agent contact diaries need special handling?
Contemporaneous negotiation records become evidence in condemnation proceedings, so they need immutable timestamps, clear attribution and append only history. A free text field anyone can edit later is worth less than a paper diary in a hearing, because opposing counsel will say so. Agents work from cars, so capture has to be mobile and quick, with corrections recorded as new entries rather than overwrites.
Who owns the acquisition records if a firm builds this for an agency?
The agency should own the repository, the cloud accounts and every tract record, in writing before kickoff. Acquisition files outlive vendors and often outlive the staff who created them, and they must stay producible for many years after the corridor is built. At Digital Heroes the client owns the code and the data from the first commit, which for public bodies should be a procurement requirement rather than a negotiation.
Can outside acquisition agents work in the same system?
Yes, and it is usually the strongest argument for building. External identity with scoped permissions lets a contracted firm work their tracts while your programme manager sees status in real time rather than at handover. Agree data standards and diary requirements in the contract, not after go live. Programme risk carried inside an outside agent's own files is invisible until it becomes a schedule impact.
How long does a first release take?
Twelve to sixteen weeks for the tract register with geometry, the stage pipeline with approvals, appraisal and offer records, agent diaries and corridor reporting, usually scoped to one corridor. Relocation case management and condemnation tracking add four to seven months. The most common cause of a slipped date is instrument template wording still under review with counsel while development runs, so settle templates before kickoff.
What is the difference between a land management system and a right of way system?
A land management system administers tenure, leases, obligations and payments over the life of an asset you already hold. A right of way system runs the acquisition itself: appraisal, offer, negotiation, condemnation and possession, against a construction schedule that needs segments cleared in order. Many programmes need both, and the mistake is assuming one product covers the acquisition phase because it covers the ownership phase.
Should relocation assistance live in the same system as acquisition?
Yes, because an occupant entitlement is triggered by an acquisition and the two share the tract. Model it as its own case type with occupant records, comparable dwelling analysis, claim submission, payment tracking and appeals rather than as documents hung off a parcel. Keeping it separate guarantees the two views disagree at exactly the moment a reimbursement audit asks about a displaced tenant.
Can the system push acquisition status back into our geographic information system?
It can, and you should ask any developer which platform they have written to and what the write path looked like. Reading a county parcel layer, computing takes and remainders against an alignment, and publishing status back to an enterprise geodatabase are three separate pieces of work with three different failure modes. Vague claims of spatial experience usually mean the first one only.
What happens if the alignment changes after acquisition has started?
Some tracts gain a take, some lose one, some acquired easements end up partly outside the corridor and some owners must be reapproached with a revised offer. Hold parcel and take geometry as data and the reassessment is an afternoon with a reviewed exception list. Hold it in drawings and folders and it is three weeks of manual comparison that still misses tracts.
Should we build while the corridor is still in environmental review?
Usually no. Wait until the alignment is stable enough that takes are not being redrawn monthly, because every revision during development turns into rework you pay for twice. Use the review period to settle your file checklist, your delegation thresholds and your instrument templates with counsel. That preparation shortens the build far more than starting three months early ever would.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
What security features does custom project management software need?
The non-negotiables are single sign-on, role-based permissions, encryption in transit and at rest, and an audit log of who changed what. If client work under NDA lives in the tool, custom actually improves your position, because you can run single-tenant on your own cloud account instead of shared SaaS infrastructure. You only need SOC 2 certification if you plan to sell the tool to others; for internal use, an annual penetration test is the sensible spend.
Should I customize Jira with plugins or just build our own tool?
If two or three Marketplace apps close the gap, stay on Jira, since it starts around $8 per user per month and the apps ride on top. The trap is that cloud apps are licensed for every user on the instance, so in Digital Heroes audits a 200-seat Jira with three or four paid apps plus a ScriptRunner consultant often lands at $30,000 to $50,000 a year. At that run rate a custom tool scoped to your actual workflow pays for itself in two to three years and ends the plugin upgrade treadmill.
How big a team does it take to build a project management platform?
A typical Digital Heroes pod is 4 to 5 people: a product designer, two or three engineers, and a shared project manager and QA. Smaller than that and timelines stretch because one person is context-switching across design, backend, and testing; bigger only helps after the MVP, when work splits into parallel streams. Headcount matters less than whether the same pod stays on your project from discovery to launch.
We're paying for 250 Monday seats. Would building our own tool be cheaper?
Cheaper only if you hold the tool for three years or more. 250 seats on Monday's Pro tier at about $19 per user per month is roughly $57,000 a year, while a custom platform costs $120,000 to $200,000 to build plus 15 to 20 percent annually to run, so cash break-even sits around year three. Building wins if you also gain workflow fit and unlimited seats; if Monday fits fine and you only dislike the invoice, negotiate an enterprise contract instead.
Who can build a custom project management software system?
Digital Heroes builds custom project management software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other project management software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .