PE Tools Integration

Overview

Deciding.org converts committed investment decisions into governance, execution, and modeling artifacts that can be mapped into the PE systems your firm already uses — without retaining the raw deliberative transcript.

Most private equity firms already have powerful tools for CRM, diligence, modeling, planning, and execution. Those tools often start with incomplete context.

After an IC decision, the logic of the decision fragments. The rationale sits in an IC memo. The risks sit in diligence notes. The assumptions sit in Excel. The owners sit in email.

Deciding.org creates a structured decision artifact at the moment of commitment and packages it for the systems that must act on it.

The problem

The decision is made in one room. The work happens in ten systems.

Analysts, operating partners, legal teams, and portfolio teams manually reconstruct what was decided, why it was decided, which assumptions mattered, and what needs to happen next.

That reconstruction takes time. It introduces drift. And it means downstream tools operate without the actual decision logic.

Deciding.org is the decision-to-execution layer. It does not replace your CRM, diligence room, project management system, financial model, or planning platform. It gives those systems the structured decision context they are usually missing.

Three artifact types

Once a decision is committed, Deciding.org preserves the governed decision record and generates structured JSON outputs in three shapes:

Governance artifact

For IC records, board review, LP confidence, and cleaner governance review.

Fields include: final decision, rationale, alternatives considered, key risks, dissent notes, assumptions, accountability, committed date, review date.

Execution artifact

For project management, diligence checklists, owner assignment, milestones, and value-creation plans.

Fields include: decision title, rationale summary, key assumptions, open risks, owners, workstreams, milestones, diligence gaps, escalation triggers, review date.

Modeling artifact

For financial models, scenario planning, sensitivity analysis, and advanced modeling.

Fields include: investment thesis, variables with base/upside/downside, key assumptions, sensitivities, causal dependencies, unresolved model questions, scenario definitions.

Where the artifact helps

The following categories describe where structured PE decision artifacts typically accelerate downstream work. Examples of systems this artifact can support include those listed — this is not a claim of native integration unless a tested connector exists.

Financial modeling and Excel AI

Deciding.org can export: investment thesis, key assumptions, upside/downside drivers, sensitivities, diligence gaps, scenario definitions, and unresolved model questions.

The artifact can accelerate model setup by giving analysts and AI modeling tools a structured starting point rather than requiring them to reconstruct assumptions from meeting notes.

Examples of systems this artifact can support include: Excel, Shortcut, Endex, and internal LBO/DCF/operating model templates.

Scenario planning and enterprise modeling

Deciding.org can export: variables, assumptions, uncertainty ranges, causal relationships, dependencies, and scenario definitions.

For planning platforms that support plain-text or structured input specifications, the modeling artifact can reduce manual setup by mapping directly from the decision record to model parameters.

Examples of systems this artifact can support include: Anaplan CoModeler, Workday Adaptive Planning, Analytica, and internal planning systems.

Deal execution and diligence

Deciding.org can export: diligence checklist items, open risks, legal questions, integration priorities, responsible owners, escalation triggers, and deadlines.

The artifact gives downstream diligence and execution tools a structured map — what the firm decided to prioritize, which risks remain unresolved, and who owns what next.

Examples of systems this artifact can support include: DealRoom, Midaxo, Asana, Jira, Notion, and internal PMO tools.

CRM and relationship intelligence

Deciding.org can export: final decision status, rationale summary, follow-up owners, pipeline stage context, and next steps.

Where firms use Affinity, DealCloud, or similar systems with API or MCP access, the final decision logic can be mapped into CRM notes, pipeline status, follow-up reminders, and relationship context. Affinity's MCP for private capital explicitly supports pipeline stage updates, notes, and reminders — making the decision-to-CRM handoff a well-supported pattern.

Examples of systems this artifact can support include: Affinity, DealCloud, Salesforce, and proprietary CRM or data warehouse workflows.

How it flows

flowchart TD
    A[Deliberation] --> B[Committed Decision]
    B --> C[Deciding.org Final Artifact]
    C --> D[Governance Record]
    C --> E[Execution JSON]
    C --> F[Modeling JSON]
    D --> G[CRM]
    D --> H[Diligence Room]
    E --> I[PMO / Deal Execution]
    E --> G
    F --> J[Excel AI / Shortcut / Endex]
    F --> K[Anaplan / Analytica]
    F --> L[Data Warehouse]

API endpoint

The PE export endpoint is available to all authenticated users with Admin or Owner role on the decision:

POST /v1/decisions/:decisionId/export-pe?format=execution
POST /v1/decisions/:decisionId/export-pe?format=modeling
POST /v1/decisions/:decisionId/export-pe?format=governance

The format parameter selects which artifact shape is returned. The decision must be in FINALIZED status. All three formats share a common envelope:

{
  "schema": "deciding-pe-execution/v1",
  "commitment_id": "<decision-uuid>",
  "org_id": "<org-uuid>",
  "committed_at": "<ISO-8601>",
  "execution": { ... }
}

The raw deliberative transcript is not retained and does not appear in any export format.

Affinity write-back (optional)

Add ?write_affinity=true to the execution format request to push the decision to an Affinity deal record via Affinity MCP. Requires AFFINITY_MCP_TOKEN to be configured. Gracefully skipped if the token is absent.

Claim discipline

This page uses cautious, defensible language throughout:

"examples of systems this artifact can support include…" — not "native integration with"
"can be mapped into" — not "drops directly into"
"structured handoff", "integration-ready artifact", "connector-ready JSON" — not "one-click compatible"

Tested connectors will be documented explicitly as each is validated. Story 4 candidates (Anaplan CSV spec generator, Midaxo REST import, Shortcut prompt package, generic webhook) are in the backlog.

On this page