Property Preservation Software: Build Custom or Buy Aspen Grove and Pruvan
Buy. If you run under roughly 1,500 orders a month for one or two national clients, Aspen Grove Solutions plus Pruvan covers you and a build is wasted capital.
On this page
Buy. If you run under roughly 1,500 orders a month for one or two national clients, Aspen Grove Solutions plus Pruvan covers you and a build is wasted capital. Build only when you hold the servicer relationship directly, price work against two or more investor allowable schedules, and cannot attribute a denial to a cause, a client or a crew.
What Aspen Grove, Pruvan and the servicer portals actually do well
Aspen Grove Solutions has real depth on the order and vendor network side, and its people know the difference between a HUD conveyance file and a Fannie Mae loan without being told. Property Preservation Wizard is a competent work order system for a regional vendor. Pruvan is a well built capture tool, and its photo workflow is better than anything you would ship in the first six months of a build. The servicer portals you log into every morning are, for the job they were designed to do, fine.
So here is the position, and writing it costs us work. Most mortgage field services companies should buy. If your orders arrive inside a national's system, your crews complete them, you invoice through that portal and somebody else files the reimbursement claim, you have a mobile app problem rather than a platform problem. Pruvan plus disciplined bookkeeping is the right answer, and a custom build would recreate your client's software without moving your margin at all.
Buy if most of these are true:
- You complete under roughly 1,500 orders a month for one or two national clients.
- You are a subcontractor, so the reimbursement claim is not yours to file.
- You work one investor's rule set in practice, whatever your contracts say.
- Your denial rate is low and you can name the cause of every denial.
- You have no in-house engineering and no appetite to own a system for ten years.
Nothing that follows applies to that operator. The rest of this page is written for the company that holds the servicer relationship and carries the claim.
Where they stop: the allowable matrix and the evidence window
HUD publishes maximum property preservation allowables that vary by line item and by state. Fannie Mae maintains its own property preservation matrix. Freddie Mac and the VA maintain theirs. A national field services company works several of them at once, so the same debris removal at the same address carries a different maximum, a different documentation standard and sometimes a different definition depending on whose loan it is. Your servicer client then layers its own rules on top, and those change by bulletin.
What packaged products hold is a rate table per client. What they do not hold is the investor rule set as a versioned, effective dated object that drives pricing and validation together. So a coordinator has to know that this order is a Fannie file, that this line sits over the matrix, and that a bid is required before the crew leaves the driveway. That knowledge lives in three experienced people and walks out of the building at five o'clock.
The second gap is worse because it is invisible. Your deliverable is not a grass cut, it is a defensible evidence package: before, during and after from consistent angles, an address verification shot, a measurement reference for volumetric work. The evidence window closes the moment the crew drives away. Six weeks later the servicer denies the debris line because the before photo does not establish the volume claimed, and you have already paid the crew. No product tells the crew what shot list this specific line item under this specific investor requires, and none of them runs duplicate detection across visits, which is the single most valuable quality control feature in this category because photo reuse is the most common contractor fraud and it is invisible to manual review at volume.
Third gap: your clock started before your order arrived. Inspection and preservation deadlines run from days since vacancy determination or days since the previous inspection, not from the moment the order hit your queue. Systems that start counting at receipt show green dashboards while you miss dates.
The arithmetic: per-order software cost versus the cost to build
Take twelve months of invoices from your work order platform, your capture app and any per-seat portal licences, add them up and divide by orders completed. Do not trust a range from a blog, including this one, but most regional operators land between one and three dollars an order. At 1,500 orders a month and two dollars an order, software costs you $36,000 a year. At 6,000 orders a month it is $144,000. At 15,000 it is $360,000.
Now set a build beside it. A focused first release runs $70,000 to $150,000 in our delivery experience. Amortise the midpoint over five years, add year two support, and you are carrying roughly $30,000 to $55,000 a year. On subscription cost alone the two lines cross somewhere near 2,000 orders a month.
That crossover is the wrong number to act on, because licence fees are the smaller half of this business. The number that decides it is denial. Take ninety days of denied and reduced lines, total the dollars, and divide by orders in the same period to get your denial cost per order. Compare that with your software cost per order. In every field services engagement we have run, denial cost per order was several times the software cost per order, and it was the figure nobody had ever calculated.
So the honest crossover is this: around 4,000 orders a month across two or more investor rule sets, with a denial rate you cannot attribute by cause, client or crew. Below that, buy. Above it, the denials pay for the build inside the first year and the licence savings are a rounding error you should ignore in the business case.
What a custom build actually costs, migration included
Two honest bands, both from delivery rather than a price sheet. A focused first release covering order intake from client portals and files, allowable aware pricing and validation, a contractor mobile app with offline guided capture, routing against the tighter of the two deadlines and completion validation runs $70,000 to $150,000 over 14 to 20 weeks. A full platform adding bid workflow with automated follow up cadence, three way reconciliation between contractor pay, client billing and the reimbursement claim, sampled quality control with duplicate photo detection, vendor compliance tracking and per client document packaging runs $180,000 to $420,000 phased across 8 to 14 months.
Then the two lines nobody quotes in the pitch.
- Data migration: 10 to 25 percent of the build. Open orders are the expensive part, because each one has to be entered and then verified against the existing deadline by a second person. Closed orders with their photo archives are bulk loaded, and the photo archive is usually larger than everyone expects, because it is the evidence behind every claim you have ever filed.
- Year two: 15 to 20 percent of build cost annually. That covers support reachable during a Friday completion run, investor matrix updates when HUD or Fannie publishes a revision, and the new client servicer you win, each of which brings its own order format, photo standard and invoice specification.
What pushes the number up here specifically: the count of client servicers, since each is real weeks of work; investor coverage, because HUD, Fannie, Freddie and the VA are four separate models; offline mobile depth, which is a genuine engineering requirement when your properties are rural; and volume, because dispatching 30,000 orders a month needs queue engineering that 3,000 does not. What holds it down: start with your largest client and one investor. The second client costs a fraction of the first if the model was built correctly.
The four situations where building wins
Custom versus off the shelf turns on four conditions. One is not enough. Two make it arguable. Three and you are already losing money by waiting.
- Regulatory fit. You work two or more investor allowable schedules, so pricing and validation are a rule engine with effective dates rather than a price list. When Fannie revises its matrix you need every open order to revalidate, and you need to answer the question nobody can answer today: how much of last quarter's denied work would have passed under the rule that actually applied.
- Scale economics. Past roughly 4,000 orders a month, a single percentage point of denial is a salary. Sampled quality control with duplicate photo detection stops being a nice report and starts being the control that funds the project.
- A workflow that is your competitive advantage. Servicer contracts are increasingly won on compliance and reporting quality rather than price. If your evidence packaging is a person assembling PDFs, you are competing with your slowest coordinator. If it is generated from the completion record, you can put a client-facing quality dashboard in a pitch and win work on it.
- Integration sprawl across three or more systems. Order platform, capture app, one portal per servicer, an accounting ledger and the spreadsheet where somebody reconciles what was ordered, done, paid to the vendor, billed to the client and reimbursed. Five records in four systems that meet once a month, six weeks late. One completion record producing vendor pay, client billing and the reimbursement claim is the whole point of the build.
How to decide in a week
Run this test. Monday, export every denied or reduced line from the last ninety days. Tuesday, code each one by cause: non-compliant photos, work over allowable without an approved bid, completion documented after the due date, inconsistent quantity measurement, other. Wednesday, attribute each to a client, an investor, a vendor and the coordinator who approved it. Thursday, total the dollars and divide by orders. Friday, ask your operations lead which of those causes a rule enforced at the point of work would have prevented.
If the coding takes a day and the causes are concentrated, buy and fix your process. If nobody can complete the coding because the data lives in four systems, that inability is your answer, and the exercise has just cost you a week and taught you more than a vendor demo would.
Then buy a paid discovery phase rather than a build. At Digital Heroes that produces a signed product requirements document before any code is written, covering the data model, the investor rule objects, permissions and acceptance criteria. It keeps a fixed price fixed, and you own it whether we build or not. Take it to three firms and the quotes will finally be comparable.
We are the wrong firm for you if you want a body shop billing by the hour, if you need someone on site in your regional office, or if you are a subcontractor who should be buying Pruvan. We are more than fifty specialists across India LLP, US LLC and UK LTD entities, so your intellectual property assigns under your own law, and you meet the named team before signing. We run our own products, including ShopScore, HeroCheckout and Section Vault, so the people choosing your architecture live with those decisions on their own revenue. Check us on Clutch, Trustpilot, Fiverr Vetted Pro and our D-U-N-S record before you take any of that on trust.
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.
- PTC identifies the leading causes of failed first visits as parts unavailability (the single most-cited complaint, named by 51% of field service executives), technicians lacking the required equipment or skills, and insufficient time allocated to the job - making parts logistics and skills-based dispatch the highest-leverage fixes. Source: PTC (2023) →
- Timefold reports field service operations moving to automated route optimization typically see 10-25% fuel savings and 15-30% drive-time reductions, and documents a case where a global services firm cut drive time 33% and distance 43% while eliminating overtime. Source: Timefold (2025) →
- The average number of formal learning hours used per employee fell to 13.7 in 2024, down from 17.4 in 2023, a decline the report attributes partly to a shift toward informal and on-the-job learning not captured in the formal-hours metric. Source: Association for Talent Development (ATD) (2025) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
Frequently asked questions
How much does it cost to build custom property preservation software?
A focused first release covering order intake, allowable aware pricing, an offline contractor app with guided photo capture and completion validation runs $70,000 to $150,000 over 14 to 20 weeks. A full platform with bids, three way reconciliation, sampled quality control and per client document packaging runs $180,000 to $420,000 across 8 to 14 months. Add 10 to 25 percent for data migration and 15 to 20 percent annually from year two.
How long does a property preservation build take before crews are using it?
Crews are usually on the mobile app in week eight to ten, well before the back office pieces are finished, because guided capture is the part that pays first and the part field staff adopt fastest. The full first release lands at 14 to 20 weeks. What slips schedules is not engineering, it is waiting for a client servicer to supply a current order specification or photo standard, so request those in week one.
Who owns the photo archive if we build with an outside developer?
You should, in writing, before kickoff. Your photographic record is the evidence behind every claim you have ever filed, and a servicer can question a completion years after the fact. Insist on owning the repository, the cloud accounts and the storage bucket outright, with an export that produces original files and capture metadata rather than a compressed report. At Digital Heroes the client owns all of it from the first commit.
What happens if HUD or Fannie Mae revises its allowable matrix mid-build?
In a correctly built system nothing dramatic happens. Allowable schedules are data with an investor, a jurisdiction, a line item, a maximum and an effective date, so a revision is a new version loaded by an operations manager rather than a developer release. Every open order revalidates against the rule in force on its own date. If a developer proposes hard coding the matrix, that is a red flag worth ending the conversation over.
Can we keep Pruvan for capture and build only the back office?
Yes, and for many operators that is the sensible first move. Pruvan handles capture competently, and a build that ingests its output, applies investor allowable validation, produces vendor pay, client billing and the reimbursement claim from one completion record, and tracks bids with follow up, delivers most of the value. The limitation is that guided shot lists per investor per line item cannot be enforced inside a tool you do not control.
What is the difference between a work order platform and a reimbursement claim system?
A work order platform moves the job: intake, assignment, completion, invoice. A reimbursement claim system decides whether the work will actually be paid, by testing each line against the investor allowable, checking that the required evidence exists before completion is accepted, and packaging the documentation the servicer needs. Most vendors sell the first and let you assume it does the second, which is why denials surface at invoice reconciliation rather than in the driveway.
Should we build if we are a regional vendor working for a national?
Almost certainly not. If your orders arrive in the national's system and they file the claim, you would be duplicating their platform without changing your economics. Buy a capture tool, keep clean books, and put the money into crew retention and insurance certificates instead. Revisit the question the day you win a direct servicer contract, because that is when the reimbursement claim and its denial risk become yours.
Can a custom system detect contractor photo reuse across visits?
Yes, and this is one of the strongest arguments for a build. Photos captured in the app rather than selected from a camera roll carry device location, timestamp and a hash recorded at capture. Comparing hashes and perceptual similarity against previous visits to the same property flags reuse automatically before a human reviews anything. At any real volume no manual review process catches this, which is precisely why the practice persists.
What happens if our largest servicer client leaves after we build?
The build survives it better than the buy does, which is counterintuitive. Client specific portals, order formats and photo standards should sit in configuration rather than code, so losing a client removes a configuration and its integration maintenance. Onboarding the replacement costs a fraction of the first because the investor rule sets, the evidence model and the reconciliation logic are already there. Ask any developer to show you that separation before you sign.
How do we compare quotes from firms that priced different things?
You cannot, and you will get four quotes that are not comparable because each firm scoped its own idea of the job. Fix it by paying for discovery first and taking the resulting written specification, with the data model, investor rule objects, permissions and acceptance criteria, to every firm on your list. Then the quotes describe the same system. Any firm that refuses to quote against someone else's specification has told you something useful.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
Who owns the code when an agency builds our field service software?
You should own it outright, and the contract must say so: source code, designs, documentation, and every account (hosting, app stores, domains) registered to your company rather than the agency's. Work-for-hire terms with ownership transferring on payment are standard at reputable agencies, and it is how Digital Heroes contracts every build. Walk away from any proposal where you license the platform instead of owning it, because that recreates the vendor lock-in you were leaving ServiceTitan to escape.
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.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
What security and compliance does custom field service software need?
The baseline is encryption in transit and at rest, role-based access so a technician sees only their own jobs, remote wipe for lost phones, and audit logs on anything that touches money. Run payments through a processor like Stripe or Square so card data never touches your servers and the heaviest PCI burden stays with them. If your crews serve regulated sites such as healthcare or government facilities, say so in scoping, because access and documentation requirements shape the data model.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
What features should the first version of a custom field service app include?
Version one needs the daily loop and nothing else: job creation, a drag-and-drop dispatch board, a technician mobile app that works offline, photo and signature capture, and invoicing that reaches your accounting system. Customer portals, route optimization, inventory, and reporting dashboards belong in phase two. The test for every feature is whether a dispatcher or technician touches it every day; if not, cut it.
Can a custom field service app sync with QuickBooks and the payment processor we already use?
Yes, and it should be scoped as a named workstream rather than a finishing task. QuickBooks Online, Xero, Stripe, and Square all offer mature APIs, and a two-way invoice and payment sync typically adds $8,000 to $20,000 to a build depending on how items, taxes, and customers map. The decision that matters most is source of truth: agree which system owns customer records and pricing before development starts, or you will reconcile duplicates forever.
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.
Who can build a custom field service management software system?
Digital Heroes builds custom field service 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 field service 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
More from Priyanka.
Senior UX Designer · UK · London · 2 posts on the site
Published · Last updated .
