By Unmesh Sheth, Founder and CEO, Sopact. All fund, company and numerical examples are fictional.
A portfolio record needs to retain what the company is, what the fund agreed with it, what has happened since and which evidence may support the next decision. Connecting files by company name is a beginning. Keeping their relationships, dates and meaning usable is the larger task.
Nina opens the latest update from RouteWorks. An older spreadsheet says Route Works Ltd. A transcript uses the founder's name. Two investments support the same company. Unless those sources are connected deliberately, the fund can create three companies in its analysis or count one result twice.
Give each kind of record its own identity
Use the CRM's stable organization ID internally when it is the agreed company master. Display the investee's name in the team's everyday views and reports. Maintain a reviewed alias list for legacy names. AI can suggest that two names refer to the same company, but an uncertain match stays unresolved until someone checks it.
Keep company, investment and observation separate. RouteWorks is the investee. Cedar's initial investment and follow-on investment are separate funding records. RouteWorks' Q2 return holds that quarter's reported results. The company's Q2 result is one observation even if both investments helped support its work.
| Record | What it holds | Important distinction |
|---|---|---|
| Company | Stable identity, aliases, description and relationship owner | A renamed company is not automatically a new company. |
| Investment or award | Fund, instrument, approved amount, agreement dates and obligations | Two investments do not create two copies of a company outcome. |
| Contact and role | Reporting contact, relationship owner and effective dates | A new contact does not create a new organization. |
| Reporting return | Company, period, requested dictionary version and submission status | A corrected Q2 return is not Q3. |
| Evidence | File or response, source location, coverage and access | Upload date is not the period the evidence describes. |
| Decision | Reviewer, finding, rationale and effective date | An AI suggestion is not an approval. |
Agree ownership field by field. If the CRM owns company name and fund assignment, a read-only connection should preserve that authority. A company may nominate a reporting contact who is not yet in the CRM; hold that nomination separately until the relevant owner reconciles it.
Specify the integration's selected fields, update frequency, failure handling and last successful refresh. Test a changed name and a failed update. A blank imported field should not silently erase a valid observation. Do not promise a refresh interval until the actual connection demonstrates it.
Bring scattered sources into an onboarding packet
Begin with the CRM export and a source register. Group fields by their job rather than copying every field into a survey. A structure with donor slots, geographic targets, reporting dates and document references can seed the workflow, but it does not contain all the evidence needed for a report.
| Existing information | Reuse during onboarding | Check before relying on it |
|---|---|---|
| CRM row ID, organization ID, name and website | Match the continuing company record | Preserve the source row ID when the organization ID is absent; review the match before merging. |
| Fund, product type, funding amount, agreement date and maturity date | Draft investment context and reporting obligations | Distinguish commitments, disbursements and totals. Confirm which amount and date the report requires. |
| Repeated donor and funding-allocation fields | Create separate donor-to-investment allocation records | An empty slot is not an unidentified donor; reconcile populated allocations without assuming they are exhaustive. |
| Target community, geographic target and thematic pillar | Draft intended population, place and outcomes | Donor address, headquarters and intended service area are different concepts. |
| Owners, contacts and first reporting date | Propose the onboarding owner and collection schedule | Confirm the reporting contact, cadence, due date and any final reporting obligation. |
| Model and metric-definition document references | Locate existing definitions before drafting new ones | A filename in a CSV is a reference, not the PDF's contents or proof of approval. |
| Performance, notes and employee statistics | Supply dated context and questions for review | A CRM status or commercial headcount is not a verified beneficiary outcome. |
Ask each relationship owner to nominate the latest permitted investment memo, logic model, dictionary, financial statement and relevant meeting notes. Register the company, document type, version, coverage period, owner, location, access and retrieval status. Import or link the nominated files through an approved upload or scoped connection. Files on a colleague's computer do not become accessible merely because the CRM is connected.
Treat a dash or blank in an export as an unresolved source value until its meaning is known. Preserve it separately from confirmed zero, not applicable and not yet due. Normalize equivalent category labels through a reviewed mapping while retaining their original spelling. Do not infer reporting readiness from the number of populated CRM fields.
For Cedar, RouteWorks's CRM row points to a dictionary PDF held by the relationship owner. The intake record initially says Referenced, not retrieved. Once the authorized file is supplied, extraction can begin. If two versions disagree, Nina receives a focused version question instead of a new request for every field.
Apply the five context categories
The Foundations course describes five categories. For a portfolio, they become the following practical brief.
| Category | RouteWorks example |
|---|---|
| Who or what we follow | Company RouteWorks, its two investments, reporting contacts and service locations |
| Situation and history | Earlier returns, investment memo, onboarding call, prior corrections and open actions |
| Meaning and criteria | What counts as service reach, the placement definition, financial basis and approved review thresholds |
| Rules governing use | Company-only access, permitted AI inputs, impact and finance reviewers, retention and release rules |
| Decision and audience | Nina's quarterly review, the relationship owner's follow-up and an authorized donor summary |
Context has scope. Fund strategy applies across the fund. A company's dictionary applies to its measures. A donor request applies to that report. A document's observation dates apply to its evidence. Supplying everything to every AI question is neither necessary nor an access policy.
Keep history without exposing everything
The investment memo may explain why the fund expected RouteWorks's model to work. Company-facing reporting should not automatically expose internal deliberation. A donor may need an approved result without access to commercially sensitive financial statements.
Design the required views before collection and test them as the relevant user. Check the record, underlying file, export and any connected assistant. An access rule written in a workbook still needs implementation.
Bring legacy impact data and historical financial statements into the same record structure, retaining original names, periods, source files and known correction history. Reconcile uncertain matches before merging them with new observations.
Start with manually approved uploads if that gives the team a clear source boundary. Add a file-store connection only after folder scope, permissions, provenance and refresh behavior are tested. More connected files do not automatically mean better answers.
Build this part of your plan
Draw how RouteWorks connects to its initial and follow-on investments, approved dictionary and Q2 return. Add the old company name as an alias. Write the five context rows and the person who owns each. Then change the reporting contact and identify which permissions need review.
Check your reasoning: the two investments link to one company and one Q2 outcome observation. The old name resolves through a reviewed alias; the contact change retains history. The donor's report can cite an approved result without exposing the original restricted file.
Test a tool: import the same company under its current and historical names. Require a proposed match with a review step. Add a second investment and confirm the company result is not doubled. Ask an unauthorized company user for another company's financial statement; the request must be denied.
Next: Agree the company measures.