We successfully launched with 14 alpha users and confirmed that users not only wanted an in-app “Schedule of Investment” experience but also full control over their data. This feature has been critical to the business, addressing longstanding customer requests. Many users had threatened to leave or already churned due to its absence. By implementing this feature, we’ve saved existing contracts and secured new ones. The research Trevor and I conducted for Portfolio View played a key role in achieving this success.

1. Information and Solutions – They shared key details we hadn’t thought of, important info to remember, and solutions for addressing pain points.

• Differentiate visual treatment: Highlighting what is user data vs. Aumni data.
• Important Data Points: Key data points like fair market value, currency, board seats, and costs often change and aren’t always backed by legal documents, so customers need the ability to update their own “Schedule of Investments” (SOI).
• Cross pollination and overriding data: If we override data, we can’t cross pollinate with the latest data that others have uploaded, so there is a risk the users data will become stale and out of date.
• Various solutions brought up: Some ideas from CS on what we could do to potentially fix or look out for as we are thinking through solution.
• What customer’s care about: They want flexibility and to be able to override and not have to double check their work. They want to know that the number they see is the number they trust.
• Outliers: Extra feedback, mostly around limitations in the app.

2. Problems Identified

• Aumni Errors & Processes: The Unaccommodated Investee model is the closest fit for our data summarization form but still falls short in capturing transactions linked to investments. Reconciling data and documents to get investments to 100% accuracy is time-consuming and often incomplete.
• Missing Documents: Some deals are over 10 years old, and finding legal docs is unrealistic. We shouldn’t require them.
• Time-Intensive Setup: Getting Aumni fully operational takes significant hands-on effort.
• Gatekeeping: Customers hesitate to share Aumni with peers due to unresolved data issues they can’t override.
• Messy Audit Logs: Audit logs intended to guide reconciliation often overwhelm customers.
• Contacting CS is a Hassle: Customers prefer to self-edit data in the app rather than relying on CS for updates.
• Rigid Model: Our data model lacks flexibility, misaligning with some customers’ expectations.

Pain Points:

• Customers juggle multiple platforms for data tracking, leading to outdated or incomplete portfolio data.
• Difficulty in viewing a holistic portfolio picture; users prefer consolidating to one or two tools.
• Users want all their data centralized for easy access.

Opportunities:

• Combined SOI and valuation tracker.
• In-app Statement of Investment (SOI).
• Integrated valuation tracker.

Pain Points:

• Aumni’s rigid data model prevents customers from inputting or overriding data.
• Users want a hybrid experience: Aumni handles most data entry, while they supplement missing or more accurate data.
• Users need flexibility for:
  • Adding transactions without documents.
  • Overriding calculations they disagree with.
  • Writing off investments they deem inactive.
  • Rolling up or splitting transactions across funds.

Opportunities:

• Allow customers to:
  • Add custom investments and transactions.
  • Edit data points, showing their version alongside Aumni’s.
  • Resolve audit log items using custom data.
  • Create placeholders for future workflows.
  • Link documents to custom entities.

Pain Points:

• Users struggle to trust Aumni’s data due to inaccuracies they can’t fix.
• Back Office gatekeeps Aumni due to these issues, limiting Front Office use.
• Users want transparency between Aumni-reviewed and customer-inputted data without overlap.

Opportunities:

• Clear UX distinction between Aumni-reviewed and customer-inputted data.
• Interface to compare both data sets and choose which to display.
• Features for confirming data accuracy without requiring documents.
• Hyperlinking to data sources for transparency.

Pain Points:

• Custom Fields are limited to Reports, leaving other areas unable to track additional data points.
• Users need flexibility to track unique data across the app.

Opportunities:

• Add Custom Fields to:
  • Portfolio View.
  • Portfolio Company Overview pages.
  • Data points for additional context.

Pain Points:

• Data inconsistencies hinder reporting and team sharing.
• Users need reliable data for investment tracking, internal reporting, and LP updates.

Opportunities:

• Data fidelity integrated across the app, ensuring customer-inputted data cascades throughout.
• In-app report builder with presentation-ready outputs tailored for different audiences (e.g., LPs, internal teams, pitch decks).