Skip to content
All resources

Blog

How to roll out a new tool at a CRE firm: start with the people doing the work

by Daniel Leong, GTM

Rolling out a new tool at a CRE firm? Get a sponsor's mandate, map the people doing the work, then involve IT, the budget owner and procurement.

Guide cover reading “Rollout”: roll out a new tool by starting with the people doing the work

Short answers

How do teams overcome change management problems when rolling out a new tool?

Get a sponsor's mandate to look at a problem, then start with the people who do the work today, and map their problem before anyone talks about a product. Then bring in IT, the budget owner and procurement with that map in hand. Pilot on one workflow, check the result against a baseline you wrote down first, and widen from there.

Who should you talk to first?

Once a sponsor has given you a mandate to look: the analysts, asset managers and operations staff who do the task now. They know where time goes, which workarounds exist and what a good result looks like. If the budget owner hears about a tool before they do, the tool becomes something that happens to the team.

Why not go to the budget owner first?

Do tell them early that you are looking at a problem, so the work is legitimate and the cost can be planned. Do not ask them to buy a product until you have the map. A budget owner who buys without one gets vague answers to the first hard questions from IT and procurement, and a team that was never asked. The rollout then starts behind.

I work on go-to-market at Fifth Dimension. This guide is the order I would use, and the reasons for it.

Why do rollouts of new tools stall at CRE firms?

Most stalled rollouts show the same signs:

  • Someone senior picked a tool before anyone mapped the problem.
  • No sponsor gave the work a mandate, so interviews and pilots had to fight for time.
  • The people doing the work were not asked what was slow or painful.
  • IT heard about it late and raised access and data questions that nobody could answer.
  • Procurement and risk reviews started after the pilot, so the pilot had to stop and wait.
  • No one owned the result, so the pilot ended with a vague "interesting".
  • The old process kept running next to the new one, and everyone did the work twice.
  • A few enthusiasts used the tool, and the rest quietly went back to spreadsheets and email.
  • The team was already absorbing other system changes, so the new tool landed at the wrong time.

Each of these is a sequencing problem. The fix is to involve the right people in the right order, and to define success before the pilot starts.

Step 1: map the affected user and their problem first

The affected user is the person who does the task today. Spend time with them before you look at any tool.

  • Name the workflow you want to improve, for example the quarterly asset report, offering memorandum review or lease abstraction.
  • List the people who touch it, including those who only hand over a file.
  • Ask each person to walk you through the last time they did it. Watch them do it if you can.
  • Write down the steps, the files, the systems, the waits and the workarounds, including any outside party whose files feed the work, such as property managers or the fund administrator.
  • Note which documents arrive under an NDA or data room terms, and which teams or funds sit behind an information barrier.
  • Ask what a good result looks like, and who checks it.
  • Write down how long it takes now, using their own estimate and a timed sample. This is your baseline.

Template: affected user map

Copy this table and fill in one row per role. The example row shows the level of detail to aim for.

  • Example: asset management analyst

    Task they do
    Builds the quarterly report from property manager packages
    Inputs and systems used today
    Property manager files, Yardi, a SharePoint folder, a house template
    How long it takes now
    [your timed sample]
    Handoffs in and out
    Receives packages from property managers; hands the draft to the asset manager
    What goes wrong
    Late files, different layouts, rework after review
    Who checks the result
    Asset manager
    What better would look like
    Less rework after review; the reviewer can trace each figure

Questions to ask the people doing the work

  • Walk me through the last time you did this. What did you open first?
  • Where do you wait on someone else?
  • Which step do you dislike most, and why?
  • Which step would worry you if a tool did it?
  • What do you check before you send it on?
  • Who relies on the result, and what do they do with it?
  • What workarounds or personal spreadsheets do you keep?
  • If a new tool worked, what would you do with the time?
  • What would make you stop using it?

The questions about what would worry them and what would make them stop matter most. They tell you what the rollout has to prove.

Step 2: write a before and after that someone can check

Turn the map into a one-page scope. It should hold the workflow, the people, the baseline, and what you will measure in the pilot.

Baseline
Hours per cycle, number of handoffs, rework loops, errors or exceptions found in review, and time to answer an investor or board question. Use your own numbers from the map.
Success measure
The same measures after the pilot, on the same kind of work, measured once people have learned the tool rather than in the first cycle, plus usage: the share of cycles run through the new tool. Count the internal time it took (IT, reviewer, champion) in the cost.
Review rule
Who checks the output, and how they can see where each figure came from.
Stop rule
What would make you pause or change course.

Do not borrow results from a vendor page or a case study to set your target. Set it from your own baseline.

Measure the workflow, not the person, and tell the team what is timed and logged, and why. If the workflow runs quarterly, test on last quarter's files alongside the live cycle, and plan around close, valuation and audit periods, or the pilot gives you one data point at the worst time. Check the firm's change calendar too, so the pilot does not land on top of another system change.

Step 3: bring in IT with the map in hand

IT needs to know what data the tool will touch and who will use it. With the user map, you can answer both. Agree one rule before anything else: no firm or counterparty data goes to a vendor, including in a demo or trial, until IT and risk have agreed what can be shared. Bring the workflow and the systems and file locations it touches (for example a SharePoint library or a property management system such as Yardi), the roles who will use it and what each should see, and the vendor's security and deployment documentation.

TopicQuestions to ask every vendor
ConfidentialityWhich documents arrive under an NDA or data room terms, and do those terms allow a third-party processor? Do any teams or funds sit behind an information barrier that access must reflect?
AccessDoes it support single sign-on and role-based access? How are permissions mapped from our systems, and how are users added and removed?
IntegrationsWhat can the integration's service account reach in SharePoint, Yardi or other systems?
NetworkCan access be limited to approved networks?
DataWhere is data held? Is customer data used to train models? Is each customer separated? Which AI model providers and other subprocessors receive data?
AssuranceCan we see a SOC 2 Type II report (and a bridge letter covering the time since its period ended) or ISO 27001 certificate, and recent penetration test results?
Exit and incidentsHow are data, outputs and configured workflows exported, returned or deleted at the end, and how fast are we told about an incident?
Support and contractWhat support hours cover our time zones, and what liability and indemnity does the contract give?
DeploymentCan it be deployed the way our policies require?
LoggingCan we see who did what, and export the logs?
RetentionHow long are prompts, outputs and logs kept, and can we set that to meet our record-keeping obligations?
DocumentsWhich policy documents can the vendor share for our review?

Shortlist two or three tools, take references, and follow your procurement policy on competing quotes. Compare them on public or synthetic documents until IT and risk approve sharing real ones.

Step 4: bring in the budget owner with a problem, not a product

By now you can show the budget owner a user-led case:

The problem in the users' words
Quote the map, not a brochure.
The baseline
What the workflow costs today in hours and delay.
The scope
One workflow, a named group, a defined period.
The cost structure
How the price scales, so the first purchase does not look like the final one.
The stop rule
What happens if the pilot does not work.

On cost structure, ask each vendor how price scales with users, documents or assets, integrations and usage, and what a sensible first scope costs. Before the conversation, check whether the cost sits with the management company or the fund, under the fund agreement, and if several funds share it, how it is split under your expense allocation policy. And say what the freed time is for, consistently with what the team will be told.

A budget owner who sees a clear problem, a baseline and a small scope can say yes or no quickly. A budget owner who sees only a product has to guess.

Step 6: run the pilot

Pick the group
A small group from the team that does the work, including sceptics, not only enthusiasts, with a champion among them.
Give them the time
Relieve pilot users of some other work, or the pilot competes with their day job and loses.
Set the length
At least one full cycle of the workflow, longer if the first cycle is spent learning the tool.
Run old and new side by side, for a fixed period only
The reviewer compares the two. The approver's sign-off on the results is the condition for retiring the old step; parallel running with no end date is how rollouts stall.
Decide go, extend or stop
Against the success measure and stop rule from step 2. The sponsor chairs the decision and the budget owner decides on the spend, with IT and risk able to stop it on data grounds.

Why starting with the problem works better than starting with a product

  • First conversation

    Product first
    Product and price
    Problem first
    Problem and workflow
  • What the team hears

    Product first
    A tool is coming
    Problem first
    We want to fix a task you know well
  • IT questions

    Product first
    Raised late, answered vaguely
    Problem first
    Raised with a data and access map
  • Procurement

    Product first
    Starts after approval
    Problem first
    Starts in parallel
  • Pilot

    Product first
    Broad, loosely defined
    Problem first
    One workflow with a baseline
  • Adoption

    Product first
    Depends on persuasion or a mandate from the top
    Problem first
    Built on the users' own pain points, backed by the sponsor
  • If it fails

    Product first
    Hard to tell why
    Problem first
    The map shows which assumption was wrong

The sponsor comes first in both. Neither order guarantees success, but problem first gives you evidence at every step, and it gives the team a part in the decision.

A rollout plan you can copy

Each phase ends with a decision. As a rough guide, mapping takes two to four weeks, vendor security and legal review often takes one to three months, and a pilot should cover at least one full cycle of the workflow; adjust to your firm.

  • 1. Map

    What happens
    Sponsor's mandate, user map, interviews, baseline, one-page scope (steps 1 and 2)
    Owner
    Business owner, with an analyst
    Decides
    Sponsor
    Exit decision
    Is the problem worth solving?
  • 2. Align

    What happens
    IT review, vendor shortlist, budget owner conversation, procurement, legal and risk review (steps 3 to 5)
    Owner
    Business owner, IT lead
    Decides
    Budget owner, with IT and risk sign-off
    Exit decision
    Can we run a pilot?
  • 3. Pilot

    What happens
    A small group runs one workflow, old and new side by side for a fixed period (step 6)
    Owner
    Business owner, a champion in the team
    Decides
    Sponsor and budget owner
    Exit decision
    Did the measures move against the baseline?
  • 4. Widen

    What happens
    Add the next workflow, team or region, using what the pilot taught; a new region means fresh data residency, transfer and consultation checks
    Owner
    Business owner, IT
    Decides
    Sponsor and budget owner
    Exit decision
    Does it hold up with more users?
  • 5. Embed

    What happens
    Retire the old process once the approver signs off the parallel run, update documented procedures, set a review routine
    Owner
    Business owner, reviewer
    Decides
    Sponsor, on the approver's sign-off
    Exit decision
    Is the old way gone?

Roles checklist

  • A sponsor who gave the work its mandate and chairs each gate, with the budget owner deciding wherever spend is committed.
  • A named business owner who cares about the outcome.
  • A champion inside each team, who is a user, not a manager.
  • An IT contact for access, data and logging.
  • A budget owner who has seen the map and the scope.
  • A procurement and risk contact who has the vendor documents.
  • A reviewer for outputs, with a rule for how they check them, and the approver who signs the numbers, whose sign-off on the parallel run retires the old process.

Also involve

  • HR, legal, the data protection lead and compliance, as step 5 describes.
  • The owner of financial controls, if the output feeds financial statements or investor reports.
  • Outside parties whose files feed the workflow, such as property managers or the fund administrator, as inputs to the map.

And set a date to review the pilot against the baseline.

What objections will the team raise, and how do you answer them?

"I do not trust the output."
Agree. Build in a review step where the reviewer can see the source for each figure, and keep a log of changes. Treat review as a standing part of the work.
"This is extra work."
Run the pilot on one real task, relieve pilot users of other work, and run old and new side by side only for the fixed period. If it still adds steps, change the plan.
"Will this replace me?"
Be honest about what is decided and what is not, agree the message with HR first, and do not promise what the firm has not committed to. Describe what the tool is meant to take on (the assembling and reconciling) and what stays with the person (judgement and sign-off).
"My spreadsheet already does this."
Ask them to show it. Put its logic into the map. If the spreadsheet holds knowledge, capture it.
"I do not have time to learn another system."
Start in the files, systems and inbox they already use, and ask each vendor how its tool fits there.
"I sign these numbers; I am accountable."
Often the real blocker is the reviewer or approver, not the analyst. Let them set the review rule; their sign-off is the condition for retiring the old process.

How do you keep a new tool in use after launch?

Review on a schedule
Look at the pilot measures against the baseline at a set date, and again after the next phase.
Keep a champion in each team
They collect questions and raise problems early.
Train by role, on real tasks
Train on the team's own tasks, with a named person to ask. Before the pilot, tell the wider team what is changing, what is not, and what is logged.
Retire the old process
Once the approver signs off the parallel run. If both run side by side forever, the new one loses.
Write down what you learned
Update the map. It becomes your template for the next workflow.
Share examples inside the firm
One analyst showing a real task works better than a slide deck.
Ask what is still slow
Each answer is the next workflow.
Name a day-to-day owner
Someone handles joiners, leavers and access, and reviews cost against usage before each renewal.
Ask for outputs in the new format
When leaders ask for the report or memo from the new tool, the team follows.

Where Fifth Dimension fits

Fifth Dimension is AI for commercial real estate, from underwriting to lease abstraction. Do your own map first; any vendor's workflow sessions should start from it. Here is what Fifth Dimension publishes:

Access and integrations
Through email or the web app. It is built to sit across the systems you already run, not replace them, connecting Excel, SharePoint, Argus and more, and for asset teams unifying Yardi, Argus, CoStar, Excel and email.
Review trail
Evidence & Controls keeps sources, assumptions, review steps and changes visible so your team can understand how an output was produced.
Custom workflows
The ability to build custom skills around your processes and outputs, and Tasks that schedule recurring automations and repeatable workflows, with review and control built in.

For IT and procurement, see Fifth Dimension security and the Trust Center.

Together, we identify the manual processes that are slowing you down across the full lifecycle of how you invest in and manage your assets. Start with the people and work that matter most, then expand as Fifth Dimension connects more of your organisation. Fifth Dimension includes high-quality service to help your team identify valuable workflows, configure the platform around how your firm works and keep improving what you have built. Request a demo, and bring the workflow, not the files, until IT and risk have agreed what can be shared.

FREQUENTLY ASKED QUESTIONS.

How do you manage change when rolling out a new tool at a real estate firm?
Get a sponsor's mandate, map the people who do the work, write a baseline, and pilot one workflow. Bring in IT, the budget owner, procurement, legal and risk with that map, and review the result against the baseline before you widen the rollout.
Who should be involved first in a tool rollout?
A sponsor, to give the work a mandate, with the budget owner told it is happening; then the users who do the task today. They know the steps, the workarounds and what good looks like. Then bring in IT, the budget owner, procurement and risk with the map.
What does IT need to know before a new tool is approved?
Which systems and files the tool will touch, which roles will use it, how access and permissions will work, whether confidentiality terms allow a third-party processor, where data is held, which subprocessors and model providers receive it, whether activity is logged, how long data and logs are retained, and how data is returned or deleted at the end.
How do you get a team to use a new tool?
Start on a real task they already do, give pilot users time, name a champion in each team, and keep a review routine against your baseline. Run old and new side by side for a fixed period, then retire the old step once the approver signs off.
How do you measure whether a rollout worked?
Against the baseline you wrote before the pilot: hours per cycle, handoffs, rework loops, errors found in review, response times and usage, on the same kind of work, once people have learned the tool. Do not set targets from a vendor's or another firm's results.
How does Fifth Dimension support a rollout?
Fifth Dimension works through email or the web app, includes high-quality service to help teams identify valuable workflows and configure the platform around how the firm works, and keeps sources and review steps visible through Evidence & Controls. Its security page and Trust Center list its security controls and policy documents.

Tools & libraries.