Who Owns Your Claude Skill Files? Moving a Lender's Underwriting Build Into Its Own Account

If the person who built your AI underwriting tool disappeared tomorrow, would your team still be able to run it? For this private lender the answer was no, because every underwriting skill file sat inside the builder's own Claude account.

The client is an executive at a private real estate lender. The underwriting build was working well enough to test, which is exactly the moment ownership becomes a problem. If you lead lending for investors, our page for mortgage loan officers and private lenders shows the wider work we do.

The situation

On a monthly strategy call, three separate issues came up. They looked unrelated, and they turned out to share a theme: who controls the pieces that keep a loan moving.

The first was ownership of the build itself. The second was a gap in the lender's pipeline once rehab work finishes. The third was an automation that the lender already depended on.

What was broken

Each issue was a quiet risk, not a loud failure.

• The underwriting skill files lived in the builder's Claude account, not the lender's. The lender did not hold the logic its underwriting depended on.
• Borrowers finishing a rehab could shop competitors instead of staying with the lender. Nothing in the process pulled them into the lender's DSCR refinance pipeline early.
• The lender relied on an existing robotic process automation bot, which we flagged as a possible weak point in the workflow.

What we built

We handled the three issues in the order of how much they could hurt.

• Ownership transfer. We worked through moving the underwriting skill files from our Claude account into the executive's, and started live testing on the lender's own deals. The last files were still being loaded and verified, with a follow-up planned once everything was confirmed working in the lender's account.
• A sandbox test of a replacement. We began evaluating Claude's browser-based agent as a possible replacement for the current automation bot. It is to be tried in a sandbox first, so the live workflow is not touched while we learn how it behaves.
• Early refinance outreach. The next step was outreach to highlighted borrowers about DSCR term sheets, with the goal of getting them into the refinance pipeline early instead of letting them shop competitors once the rehab is done.

What changed

No outcome had been recorded at the time of this call, so we have no conversion or time-saved figure to quote. The change was in control. Before the call, the lender depended on a build that lived in someone else's account. After it, the skill files were in the lender's account, with the last few still being verified, and were being exercised on the lender's real deals.

The other two threads were set up as controlled experiments. The sandbox test keeps the replacement idea away from live loans, and the term sheet outreach goes to a targeted group of borrowers. Neither was reported as a win. Both can be reversed if they do not work.

Questions to ask before you hand over an AI build

If you are paying someone to build AI tools for your business, ask these before the work goes live. Whose account holds the skill files and prompts? Can your own team log in and run the tool without the builder present? Can they open the files and see why a result came out the way it did? Is there a plan for testing changes in a sandbox before they touch production?

On the pipeline side, ask a plain question of your own process: what happens to a borrower the day the rehab finishes? If the answer is that they are on their own, you have a gap a competitor can use.

Frequently asked questions

Why should my company own its Claude skill files?

Because the skill files hold your underwriting logic. If they live in a vendor's or builder's account, you cannot edit them, test them or keep them if the relationship ends. Moving them into your own account gives your team direct control over how the tool behaves.

How do you move skill files between Claude accounts?

In this build we worked through transferring the underwriting skill files from the builder's account into the client's account, then began live testing on the client's deals. The remaining files were still to be loaded and verified, with a follow-up planned once everything was confirmed working in the new account.

Why test a browser agent in a sandbox before replacing an automation bot?

A sandbox lets you see how the new tool behaves without risking live loans or live data. This lender's automation bot was flagged as a possible weak point, but replacing it blindly could create a bigger problem than the one it solves.

What is the point of contacting rehab borrowers about term sheets early?

It keeps a borrower inside your pipeline while the rehab is still running. The goal on this project was to start the DSCR refinance conversation before the work finished, so borrowers are not shopping competitors once the project is complete.

If you are not sure who holds the logic behind your AI tools, book a 30-minute AI follow-up and reporting audit. We map where your accounts, files and automations live and what to bring in-house first.