Bodic Atlas
Your procedures, market notes and projects no longer live in a tool on the side. Bodic Atlas hosts them inside your CRM, attached to the accounts, funds and deals they concern — and turns documentation into a project, then a meeting decision into an assigned task.
What your team knows, written once
Each page is built from blocks — rich text, images, tables — inside sections you define. A closing procedure, a note on a jurisdiction, a step-by-step guide: everything that used to be passed on verbally or as an attachment finally has a home.
- Every change creates a version: you see what changed, when and by whom.
- A page's contributors are identified, not just its author.
- A page can be featured, tagged, and filed in the section of your choice.
A wrong note is worse than a missing one
The problem with internal documentation is not writing it, it is knowing whether you can still rely on it. Atlas sets a review frequency per page and flags the ones that have passed it.
- Four explicit states: draft, current, needs review, archived.
- You set the frequency — every six months, every year — and Atlas calls for the review when the time comes.
- A page can be flagged for an update request addressed to its owner.
A written procedure becomes a launched project
This is what sets Atlas apart from a wiki: the page describing how to do it becomes the project that does it, with no re-entry and without losing the link to its origin.
You document
The page describes the process, the steps, the points to watch.
You convert
In one move, the page becomes a project. The project keeps the link back to the page it came from.
You execute
Phases, milestones, team and budget sit on that foundation, and the documentation remains the reference.
Projects you can read at a glance
An Atlas project carries its phases, milestones, team and budget. Read it as a Gantt chart for the timeline, as a calendar for deadlines, and as indicators for progress.
- Gantt view: colour-coded phases, progress in percent, milestones placed on the timeline.
- Milestones, dated and checkable, for the deadlines that are not up for negotiation.
- Team made up of internal users as well as external contacts, each with their role.
- Budget tracked by category: licences, external providers, internal time.
Nothing floats beside the CRM
This is the difference from a generic project management tool: a page, like a project, attaches to the objects in your CRM, and their tasks are full-fledged activities.
Attachments
A page or a project links to an account, a contact, a fund, an LP opportunity, a deal or a commitment. The link can also target a whole type — "applies to every fund".
Tasks, not a silo
A project task is a CRM activity: it appears in the timeline, turns up in searches and attaches to the same history as everything else.
Inherited permissions
Access follows CRM permissions. What a user cannot see in the CRM, they cannot see in Atlas either.
A decision made is a task assigned
A project keeps a log of its meetings and their minutes. Each decision can be turned into a task, which keeps the link to the meeting it came from.
- Minutes are published on the project, dated and attributed.
- A decision becomes an assigned task, with its due date.
- The task keeps its originating meeting: you always know where an action came from.
Connected to the whole Bodic platform
Atlas builds on your existing data and enriches it with what your team knows.
Bodic CRM 360°
Accounts, contacts, timeline
Bodic LP Pipeline
Projects linked to LP opportunities
Bodic Deal Flow
Documentation anchored to deals
Bodic Meeting
Meeting minutes
Bodic Atlas
New
Bodic Data Room
Reference documents
What our clients ask us
How is this different from Notion or Confluence?
A general-purpose wiki knows nothing about your data. In Atlas, a page attaches to a fund or an account, a project links to the opportunities it concerns, and a task is an activity in your CRM. Documentation stops being a folder on the side and becomes a layer of your information system.
How do we know whether a procedure is still valid?
Every page carries a status — draft, current, needs review, archived — and a review frequency that you set. Atlas flags pages whose deadline has passed, and anyone can request an update from their owner.
Who can see what?
Atlas permissions are CRM permissions. A user only sees in Atlas what their permissions grant them elsewhere: there is no second set of access rights to maintain.
Can we follow a project without opening every task?
Yes. A project reads as a Gantt chart — phases, progress, milestones — as a calendar for deadlines, and as headline indicators. The detail stays available, but the overall state is visible at a glance.
Where is this data hosted?
In France, like the rest of the Bodic platform, on Clever Cloud infrastructure.
Let's talk about Bodic Atlas
In 30 minutes, let's look at how your procedures, notes and projects can stop living beside your CRM.