Our Approach | DITAP Capital

A decision-making framework

First, the question.
After, the capital.

What project should we fund? What risk should we accept? How much should we allocate, and when should we stop? DITAP’s operational model frames these questions as the core of its Capital function.

To understand

Identify the need, the context, and how it fits within the overall ecosystem strategy.

Purpose and scope of the project

To evaluate

Compare assumptions, demand, team capacity, and financing needs.

Comparable information and scenarios.

To structure

Relate the project’s horizon with its liquidity, exposure, and capital commitments.

Defined responsibilities and milestones

To accompany

To examine a review of the decisions and the underlying assumptions that led to them.

Tracking and review criteria

The analysis behind the decision.

Looking at the potential.
Understand the exhibition.

The proposed framework combines strategic reading with financial tools. No single indicator tells the whole story: assumptions, context, and the quality of the information are all part of the evaluation.

Return and use of capital: ROIC, present value, and recovery period, to relate resources and expected results.
Liquidity and horizon: Cash flow needs and time commitments, including periods of reduced activity.
Risk and sensitivity: Alternative scenarios, focus, and exposure to critical variables.
Government and monitoring: Responsible parties, information, and criteria for reviewing, continuing, or stopping an initiative.

A firm decision also feels…
In what conditions should it change?

The principle before inertia.

Let's build perspective.

Good decisions start…
with a conversation.

Let's talk.

Support before, during and after implementation.

A clear initial contact. A written proposal. Agreed-upon next steps.

Before: to understand and define

We discussed your needs and established goals, deliverables, deadlines, and costs within the proposal.

During: to coordinate the work

We agreed on responsibilities, stages, and the necessary information to move forward. The launch and training are defined according to the project.

After: knowing how to proceed.

We’ve agreed on the channels, times, and scope of the follow-up support, so you’ll know who to contact.

Answers before deciding.

What am I going to receive before signing a contract?

A written proposal outlining the scope, deliverables, stages, price, and terms. It also identifies any additional services you would like to include.

How is support organized?

We’ve defined the contact channel, the hours of operation, and the scope of support within the proposal. This allows you to understand what kind of assistance your service offers and how to request help.

What’s happening with the information related to my organization?

When defining the project, we reviewed what information is needed, who can access it, and how it will be shared. In software systems, we also agreed on the conditions for backup, preservation, and export.

A protected technology foundation.

HTTPS / TLS

Encrypted connections

Your browsing on this website uses HTTPS/TLS to protect information during transmission.

AES-256

Encoded within the infrastructure.

Vercel, the provider of hosting for this website, documents the use of AES-256 encryption for data stored within its infrastructure.

DITAP

Information for a serious conversation.

We define what documentation is required for each evaluation and how to share it throughout the process.

Learn about the supplier’s specifications.

Strategic conviction. Financial discipline.

First, the question. After, the capital.