Seven objects and 2,300 records across dealflow, fundraising, and commitments

One workspace, four operating jobs

Credo’s requirement crossed the usual CRM boundaries:

1. Dealflow through the investment committee process.
2. LP conversations and Fund IV fundraising.
3. Commitments across investor entities and fund vehicles.
4. Portfolio and executive-network context.

A generic sales pipeline could not carry all four. The model needed connected objects with different stage logic and one shared people/company graph.

What shipped

The completed workspace included:

• seven connected objects,
• approximately 2,300 migrated and verified records,
• 732 deals,
• 976 companies,
• 248 people,
• 214 commitments totaling NOK 1.958 billion,
• 128 LP entities,
• 20 fund vehicles,
• 12 saved views,
• four Phase 1 stage-gate workflows,
• 52 LP meeting notes.

The two populated operating lists were Deal Flow with 732 entries and Fund IV Fundraising with 149 entries.

The model

People ── Companies ── Deals
  │           │          │
  │        LP Entity ─ Commitment ─ Fund Vehicle
  │
  └── Meeting notes / owner / activity

The investor-group hierarchy remained explicit, allowing a parent institution and its sub-vehicles to be represented without duplicate organization records. Commitments connected the LP entity to the relevant fund vehicle with amount, stage, and owner.

Verification

The migration was reconciled column by column. The verification script checked object counts, required links, list membership, and commitment totals. This was not a “the rows imported” sign-off; it checked whether the target model still answered the operating questions in the source files.

The last-mile reality

Two dependencies stayed client-side:

• Microsoft email/calendar sync required the client administrator.
• Workflow tool access had to be transferred from the implementation account to the internal owner.

Those dependencies were documented because a workflow that still sends from the consultant after handover is not complete, even when its logic is correct.

Outcome

Credo accepted the contracted build with one connected operating system for dealflow and fundraising. The team received the verified data, views, workflows, and a path to use Claude for ad-hoc pipeline review and IC preparation without turning conversational access into ungoverned writes.