Cap Orbit vs Microsoft 365 Copilot: The CRE Deal Workflow

The short answer

Office apps and the shared deal record.

Microsoft 365 Copilot is built to help whoever is inside the document: rewrite this paragraph in Word, summarize this thread in Outlook, add a chart to this sheet in Excel. It is a horizontal product for every role at every firm that runs Microsoft 365.

Upload the broker’s files or link their folder. Extract the rent roll unit by unit and normalize the operating statement. Fill your model and edit it in the same tab. Draft the memo in the voice your committee knows. Keep the work together on the deal.

Credit where due

Where Copilot wins.

Copilot lives where your firm already works: it sits in Word, Excel, PowerPoint, Outlook, and Teams, grounded in the mail, files, and calendars each person can already reach, under the permissions the firm already set. For everyday drafting, meeting summaries, and inbox triage, that placement is the point.

The pricing is published: a per-seat add-on to the Microsoft 365 plan the firm already licenses, thirty dollars a seat each month at the enterprise tier, with a free chat tier on eligible plans. Microsoft states that prompts and organizational data are not used to train its models, and ISO 27001 and GDPR certifications are in place.

• Embedded in Word, Excel, Outlook, and Teams, with nothing new to roll out
• Grounded in the firm’s own mail, files, and calendars, respecting existing permissions
• Published per-seat pricing on top of the existing Microsoft 365 plan

Where it stops

The gaps a deal team hits in the first week.

Nothing in Microsoft’s materials describes reading a rent roll or a T-12. Copilot can act on data already laid out in a workbook, but broker materials arrive as PDFs, scans, and buried exhibit tabs, and turning those into a clean, traced extract and then a model is not a job the product claims. The closest thing Microsoft offers a finance team, Finance Agent, is built for corporate finance operations, matching transactions, writing variance commentary, and chasing receivables, and it connects to Dynamics 365 Finance and SAP, systems a real estate investment firm does not typically keep its deals in.

Reliability inside Excel is a fair question to put to it. A widely reported September 2025 incident showed Copilot in Excel returning incorrect arithmetic, and in an underwrite, where one wrong cell survives into the committee deck, that class of error carries real consequences.

And the deal does not accumulate as a team record. Each Copilot conversation starts from the document in front of you, so last week’s analysis does not inform this week’s thread, and nothing in Microsoft’s materials we reviewed describes a per-deal memory that builds over the months a transaction actually takes. Add the practical condition that Copilot in Excel only works on files saved to OneDrive or SharePoint, and the shape is clear: a tool for the document in front of you, not a system that holds a deal.

Where Cap Orbit wins

Build the model. Draft from it. Edit both.

Read the offering memo, rent roll, T-12, and loan agreement together. Extract unit-level data even from scans, trace figures to file, sheet, and row, and reconcile source totals. Normalize the statement, fill the model, and prepare the memo in one instruction.

Open the files and edit directly. Change a rent and see returns recalculate while two analysts and the terminal work in the same sheet. Review memo changes in Cap Orbit or Word. Edit the deck in place. Formulas and charts survive, and the workbook opens in Excel without repair.

The deal keeps its own record. Deal memory carries the facts, parties, and decisions into the next session and to the next teammate. At each phase the model and memo lock together into a frozen, timestamped snapshot while the working model stays live. The same record runs forward: closing reconciles the settlement statement and trues up the going-in basis, and asset management closes each period against the original underwrite in the house trackers.

Isolation

Review where your firm’s data lives.

Copilot runs inside the firm’s one Microsoft 365 environment, drawing on whatever each person already has permission to open. That is the right design for office work: the permissions are already set, and the product inherits them.

Each Cap Orbit firm has its own database and document storage. Files, prompts, and outputs never train models. Enterprise puts the platform in your AWS account with your SSO, network controls, and keys. Your security team audits it with its own tools.