Altus Intelligence Platform

As Altus Group moved toward a unified platform vision, I led and contributed to several platform-wide initiatives that power the Altus Intelligence Platform, including org onboarding, user management, collaborations (guest users), navigation, data and model management. My role was to create a foundation that aimed to modernize legacy workflows, grounded in constraints like legacy system dependencies and limited technical flexibility.
This case study will focus on lease file uploads into ARGUS Enterprise*.

Category
Product
Platform
Desktop application
Deliverables
Research
Figma screens
Team
2 Engineers
3 Product manager
3 Designers
Platform team
Role
Lead Designer
Overview | Altus Intelligence Platform
Key contributions to the platform:

Org creation and collaborations

  • Org creation, org admin invitation
  • Admin settings
  • Whitelisting domains for Collaborations
  • Role-based permissions and data controls

User management

  • User onboarding, Role and permission assignment
  • SSO migration and compliance
  • Clear activation and deactivation flows
  • Partnered with PMs and other designers to audit legacy tools, gather internal feedback, and align with SOC/regulatory needs

Design system contributions

  • Reviewed with the platform design system team before implementation
  • Created hand-off assets like annotation cards
  • Created custom UI elements like onboarding components, date pickers, and icons when system didn’t have the desired component
Overview | Lease Ingestion

Context

Many of Altus' users clients relied on outdated tools, manual processes, and disconnected systems. Lease data was copied over by copying and pasting, or reviewed cell by cell.  

The challenge wasn’t just to design a better experience, it was to bridge old workflows with a modern interface, ensuring users could adopt improvements without breaking their processes or systems.

Business need:

  • Reduce manual time spent by appraisers doing manual tasks (time savings - aprox $)
  • Jump start the appraisal process for ARGUS Enterprise users and Aquasition users
Discovery

We conducted in-depth research, interviewing appraisers and analyst to understand their workflow around lease ingestion, sending our surveys, and gathering examples of the type of documentation they receive and what how it is used on ARGUS Enterprise.

Key insights:

  • Appraisers rarely start with a brand new AE model, 98% of the time they received a previous model without key assumptions, which meant we didn't just need to build a lease ingestion tool, but a comparisson tool
  • Comparing lease changes cell-by-cell was tedious and often delegated to junior analysts
  • Lease documentation came in various formats but mainly PDF and Excel)
  • Acquisition teams needed speed over depth, a quick pulse on value, not full AE model fidelity

Gathering examples of leases, we reviewed layouts, common data points and file types, setting up a Figjam with a birds eye view of all the documentation examples, noting commonalities and anomalies. This helped us articulate to the development team what we should prioritize, and what the system should look out for.

Definition

The goal of the lease ingestion project was to streamline how users uploaded and mapped lease data into the Altus Intelligence Platform, reducing the need for manual entry, improving data accuracy, and enabling faster modelling into ARGUS Enterprise.

We identified three core user needs:

1
Ease of upload
Users needed a simple, predictable way to upload lease tables without manually copying and pasting or reviewing each column/row.
“Once I receive the files, I just need to review the data is correct...row by row.”
– Consultant
2
Flexible field mapping
Lease tables varied widely in structure. Users needed the ability to review, edit, and confirm how each column was mapped to Altus-standard fields, especially when auto-matching failed or misinterpreted headers.
“Sometimes different clients have a different name for this”
– Analyst
3
Confidence before submission
Because lease data would be pushed into ARGUS Enterprise models , users needed clear validation and control before committing, with the ability to catch errors early and reduce downstream rework.
“I want to make sure the data I'm uploading is reviewed before I override all my model data.”
– Analyst

We also had to work within a few constraints:

  • The system only supported table-based formats (like Excel), not PDF parsing or data integrations
  • Header matching relied on a keyword dictionary, not AI/OCR
  • Models were stored and updated in ARGUS Enterprise, so the workflow needed to fit legacy tech and data flow requirements
Ideation

Given the constraints set by the engineering and product team, we explored a wizard-style flow that supported guided upload, semi-automated field mapping and data validation prior to submitting data to a new, or existing AE model.

1
A progressive, guided flow
I designed the process to be a clear, step-by-step wizard to reduce cognitive load and prevent overwhelm. Each step focused on a specific task: uploading the file, confirming headers, adjusting field mappings, and submitting to ARGUS.

Design goals:
  • Break a complex process into manageable, linear steps
  • Provide clear orientation at each stage (e.g., where the user is in the process and what comes next)
  • Minimize user errors by guiding them through a structured, predictable flow
2
Mapping confidence
Since the dictionary-based matching wasn’t always accurate 100% of the time, I designed a visual interface that allowed users to review and edit each field. Where users could correct mismatched fields and fill in any unmapped fields, ensuring they maintained control over what data entered the model.

Design goals:
  • Build trust in automation by showing how the system made its matches
  • Empower user control so they can easily fix incorrect mappings
3
Data validation
Instead of waiting until the end of the flow to surface issues, I built in contextual error messages and visual cues throughout the steps, so users could spot and resolve problems early.

Design goals:
  • Surface issues early so users don’t waste time progressing with broken inputs
  • Help users self-correct with clear, contextual messaging (unmapped fields, formatting issues)
  • Prevent data quality issues before lease information is submitted to AE

The goal was not to reinvent the ingestion process, but to optimize clarity and trust within a technically constrained system, helping users confidently prepare data for downstream use in ARGUS Enterprise.

Design
1
Step by step wizard
I broke the ingestion process into a clear, linear wizard with distinct stages:
2
Field mapping and row selection interface
After auto-matching rows and columns, users could review, override, or fill select missing mappings. I designed this to resemble a familiar spreadsheet structure with editable field selectors.
3
Inline error-handling and data review
To prevent users from progressing with incorrect or incomplete data, I incorporated inline validations throughout the flow. These included warnings for unmapped fields, unsupported formats, or missing data.
Hand-off

Given the technical complexity of integrating with ARGUS Enterprise and handling structured data files, close collaboration with engineers was critical.

  • Provided alternatives for edge cases not covered in early specs
  • Annotating each step of the Figma flow with interaction notes and edge case guidance (e.g., duplicate fields, unsupported formats)
  • Meeting with the lead front-end developer to ensure component logic matched user expectations
  • Testing early staging builds and flagging visual inconsistancies and bugs
Evaluation

We conducted early walkthroughs of the ingestion flow with internal subject matter experts and a few trusted client advisors. While the ingestion flow improved accuracy and efficiency for valuation workflows, acquisition analysts, especially those underwriting new deals, needed a faster way to assess viability without having to prep detailed lease tables.

To address this, I created a quick prototype using Claude AI to demostrate this:

  • Quick property-level IRR calculations
  • The option to upload lease tables for refined estimates
  • A simplified UX flow geared toward speed and directionality, not completeness or legacy tool reliance

This prototype explores how we might serve acquisition teams earlier in their funnel, while still offering a path to upload detailed lease documentation.

See next project👉