Yes, you probably can
Open a general-purpose AI model, drop in a rent roll, and you’ll get a clean table back in seconds. Ask for a market overview, and you’ll get a paragraph that reads well. String a few of those steps together, and you have something that looks like appraisal AI.
This is today’s reality, but, it’s not the hard part.
The demo runs on one file, on a quiet afternoon, with the builder sitting next to you. Production runs on hundreds of files a year. Rent rolls from twenty different property managers. Scanned T-12s. Deadlines stacked three deep. Model updates you didn’t schedule. The more complex the file, the more likely the AI gets something wrong, and it won’t tell you.
So before you build it, or hire someone to build it, know what you’re signing up for. These are the questions we’d ask of any option on the table. Including us.
1. Who picks up when it breaks at deadline?
It will break. The question is who’s on the hook in the next hour, with a report due and a client waiting.
In most homegrown setups, one person knows how it works. If that’s you, every fix comes out of billable time. If it’s a consultant, you’re on their calendar. And appraisers catch up on nights and weekends, exactly when a one-person shop is least likely to answer.
The quiet failure is worse. An AI model can return a number that’s wrong and still looks right, with no error message. A misread unit count, or a free-rent concession dropped from a rent roll, flows straight into your income approach. Someone has to own catching that, and tracing why it happened.
Ask:
- It fails at 4pm on delivery day. Who do you call, and how fast do they respond?
- Is that support in a contract, or is it a favor?
- Does it cover nights, weekends, and holidays?
- How do you know the AI is producing accurate numbers?
- When the AI produces a wrong number, who finds the cause and fixes it so it doesn’t repeat?
2. Where does your client data go?
Appraisal files carry exactly what clients expect you to protect: rent rolls, operating statements, lease terms, borrower details. The moment that data hits an AI step, it travels.
Where it’s stored, how long it’s kept, and whether it trains a model depends on the tool, the plan, and the settings someone picked. Those terms change. Most people pasting files into a chatbot have never read them.
Two problems show up later. If the work happens in someone’s personal AI account, your client data sits in an account your firm doesn’t control, and it walks out the door when they do. And USPAP’s Ethics Rule puts confidentiality obligations on the appraiser. “I pasted it into a chatbot” is a hard answer when a lender’s security questionnaire lands on your desk.
Ask:
- Can you name every place client files travel once they enter the AI step?
- Is any of that data used to train a model, yours or anyone else’s? Get the answer in writing.
- Does the work happen in accounts your firm owns, or in someone’s personal login?
- Can you show an independent security audit, like SOC 2 or ISO 27001, when a client asks?
- Can you cut off a former employee’s access in one step?
3. Who keeps it running after the builder moves on?
AI models get updated and retired on the provider’s schedule. When that happens, prompts that worked last month can return different results. Sometimes the change is obvious. Often, it isn’t.
Someone has to notice, retest, and fix it. In a homegrown setup, that’s usually the person who built it. The prompts, the workarounds, the “don’t touch that” knowledge, all of it lives in their head. When they leave, take on more clients, or retire, it goes with them.
The first invoice is the cheap part. Year two, counting your own hours, is the real number.
Ask:
- If the builder leaves or gets busy, who maintains it?
- Is it documented well enough for someone new to fix it without starting over?
- When the underlying model changes or is retired, who retests your workflow, and who pays for it?
- What does year two cost, with your own hours on the bill?
4. Does it work for the whole firm?
Most homegrown AI starts as one appraiser’s shortcut. That’s a fine start. Trouble starts when the firm depends on it.
A shortcut built around one person’s habits doesn’t know your templates, your comp database, or how a job moves from engagement to delivery. If the output lives in a chat window, someone copies it into the workbook, then into the report. Every copy is a chance for an error. Every manual step eats the time you were trying to save.
Then there’s consistency. Five appraisers writing their own prompts get five versions of the same analysis. Now your reviewer checks the work, and the prompts behind it.
Ask:
- Was it built around one person’s habits, or your firm’s workflow from engagement to delivery?
- Does the output land in your comps, workbooks, and reports, or does someone paste it in?
- Does every appraiser get the same result from the same file?
- Grow from 3 appraisers to 15. Does it still work? Does the cost still make sense?
5. Can you defend the work two years from now?
Whatever touched the report, the appraiser who signs it owns it. AI speeds up the work. The judgment and the signature stay with you.
That makes the record everything. USPAP’s Record Keeping Rule requires a workfile that supports your conclusions, kept for at least five years. If a value gets challenged by a client, a reviewer, or in court, you need to show where every number came from and what the AI touched. A chat history on someone’s laptop won’t hold up.
Ask:
- If a value is challenged, can you show exactly what the AI touched, where the data came from, and how it reached its conclusion?
- Is there a record of every automated change: what changed, when, and by what?
- Does an appraiser review and approve everything the AI produces before it reaches a report?
- Could you rebuild that record if the tool, or the builder, disappeared tomorrow?
How to weigh your answers
Every option will have gaps. Each one is a risk you’re choosing to own. Choose them on purpose.
The worksheet gives extra weight to the questions that matter most. A tool that saves an hour but leaves you alone at deadline, or unable to explain a value, costs more than it saves. And if any option, vendor included, can’t answer in plain language, that’s your answer.
Put every option side by side
We built Valcre’s AI features to support appraiser judgment. Hold us to these same questions. Valcre is SOC 2 and ISO 27001 certified (see our security page).
To make that easier, we turned this list into a worksheet. Score building it yourself, hiring a consultant, and buying software side by side, with a guide to reading the results. It adds questions on cost, exit, and control, where building often wins. Score those honestly too.


