mindBrain Bootcamp · 4 weeks

Build your
business application.

Four weeks to design with mindBrain, test your rules, and plan the next phase of your project.

A collaborative workspace for designing and testing a business application
Learn by building. AI-generated atmosphere image.

Start with your business expertise.

No programming experience required.

A first proof of concept with sample data.

Natural language changes the interface.
Questions change the design.

Chat tools powered by large language models (LLMs) have made natural language a way to interact with software: type or speak a question to get an answer instead of searching for a screen.

Connected to company data, this interface lets you ask questions such as, “Why is this deal stuck? Who needs to step in?” The answer may draw on contacts, opportunities, activities, and business rules.

How you frame questions becomes a strategic design choice: it defines what each role needs to understand, decide, and do. Transactional interfaces, built for entering and editing data, cannot cover all these conversational uses.

The design approach needs to evolve. You need to design the knowledge, relationships, and conditions that make answers possible, alongside operations and views.

Transactional approach

What does the user
need to do?

Create a contact. Update an opportunity. Log an activity.

OperationsDataViews

Answer-oriented design

What does each role need to know
to decide and act?

Which deal is stuck? Why? Who needs to step in? What consequences should we expect?

QuestionsBusiness modelAnswers

Both approaches work together. Operations supply the facts; the business model organizes the knowledge needed to answer questions.

One case, several perspectives

Same opportunity.
Different questions.

Prospecting, sales, finance, leadership: each role has a specific job to move forward. Choose a role.

The example on this page is a CRM model that makes a use case easier to understand. The bootcamp is open to all kinds of agentic applications.

Atelier Nord opportunity€18,000 offerOwner: Camille, SDRBudget not yet confirmed

The SDR’s perspective

Prepare a useful next step.

When I qualify an opportunity, I want to identify what is missing so I can plan the next step.

“What information or approvals are missing before we can hand off this deal?”

The answer in this example

Two items still need attention.

No follow-up is scheduled and the budget is not confirmed. Camille needs to prepare a conversation and check the budget before the handoff.

Facts used: owner, next activity, budget confirmation.

Read all five business questions
Prospector
Is there an active opportunity, who are the contacts, and who owns it?
SDR
What information or approvals are missing before we can hand off this deal?
Sales manager
Which opportunities are stuck, and which ones need my intervention?
CFO
Which amounts still depend on a signature, delivery, or invoicing? The corresponding financial facts still need to be added.
CEO
Which roadblocks could affect our goals? We also need the pipeline and the goals.

Fictional data, scripted answers. Explore the reasoning; no agent is connected to this page.

Explore needs at a larger scale

You have just seen five perspectives on one opportunity. How many answer needs does that represent across your business?

Several roles.
How many answer needs?

The same business activity involves different responsibilities. Adjust the two sliders.

For example, 5 roles with 8 questions each represent 40 answer needs.

5 roles × 8 questions

40

answer needs
to organize

Illustrative calculation: some questions are shared across roles. This total does not count screens or estimate development costs.

With mindBrain, start with these questions.

Organize facts, relationships, and rules in a shared business model. People and agents can then use answers whose conditions are explicit.

Do you need to anticipate every possible wording?

A reference question can support different phrasings and parameters. “Where should I step in?” and “Which deals need my help?” draw on the same knowledge. A new question may also require another source or rule: that gap needs to stay visible.

See how answers change

One fact changes.
Which answers change?

Schedule a follow-up for Atelier Nord. Observe what changes and what still needs to be checked.

Change the situation.

Demo rule: a scheduled follow-up and a confirmed budget are required before proposing a handoff to the manager.

Is there a next activity?No activity scheduled.
Is the budget confirmed?This information is still unknown.
Can we propose a handoff?Not yet: two conditions still need to be met.

Scheduling a conversation resolves the missing follow-up. It does not confirm the budget.

The selected role’s answer in the roles module uses these same facts. An unknown budget does not mean a rejected budget.

What makes an answer possible?
The factsAn owner, a follow-up, a budget.The ruleBoth conditions before the handoff.The answerWhat is missing and what becomes possible.
Discover the next action

A useful answer.
A next step with clear conditions.

An agent can prepare an action using the available answers. Conditions and approvals remain explicit.

SituationNo follow-up, budget not yet confirmed.
ProposalPrepare a qualification conversation.
ResponsibilityCamille clarifies the need before acting.

Based on your situation

Preparing the next step.

The follow-up still needs to be scheduled. Preparing a conversation does not yet allow the opportunity to be handed off.

The proposal has not been prepared yet.

Local simulation: no activity is created and no message is sent. Changing the facts cancels the prepared proposal.

Explore agent automation

Answers that change.
Agents that adapt.

Defining rules lets you design automated processes. When a fact changes, the answer to a business question changes too: the agent can then determine what it may or must do.

A fact changesAn opportunity passes its deadline.
The answer changes“Which opportunities are at risk?”
A rule guides the agentPrepare an alert for the owner.

At a larger scale, answers and actions can form a sequence that moves an entire process forward. You define the conditions for execution and the points where a person steps in.

Read both processes in full

A fully agentic process

From detecting risk
to informing the right people.

The agent follows business answers and carries out actions authorized by the rules.

  1. IdentifyIdentify opportunities at risk using the available facts.
  2. SummarizeSummarize the risks, their causes, and useful interventions.
  3. AlertSend an alert to the sales rep involved.
  4. ReportSend a summary to the sales director.

The rules specify triggers, recipients, and the conditions that authorize these messages.

A combined agent and human process

From a prepared report
to a quote ready for signature.

The agent prepares the work. A person approves the proposal that authorizes the next step.

  1. PresentThe agent submits a report and a proposal to the person responsible.
  2. ApproveThe person reviews, adjusts if needed, and approves the proposal.
  3. PrepareThe agent uses the approved proposal to prepare the quote.
  4. SendThe agent sends the quote to the prospect for signature, subject to the defined conditions.

Human approval authorizes the next steps. The prospect’s signature remains a separate step.

In both cases, you design the connection between facts, answers, rules, and actions. These examples describe processes to build and test.

Test the important situations

A good rule
also holds up at the edges.

If a follow-up is scheduled but the budget is missing, the handoff must remain on hold. Test three situations from the same example.

These test cases are independent of your earlier choices.

The case to check

Follow-up scheduled, budget unknown.

Expected result
The handoff remains on hold: the budget is missing.
Observed result
In this example, a follow-up alone does not allow us to propose a handoff.

Keep this distinction in your own rule.

What this small test checks

It compares a local demo rule with the expected result for a specific case. In the bootcamp, your model’s scenarios help you observe results, identify gaps, and gather feedback from people who know the business.

  • Follow-up only: handoff on hold.
  • Budget only: handoff on hold.
  • Both conditions met: a proposal is possible, but human approval is still required.
Understand mindBrain’s place in your application

The role of mindBrain

With your CRM.
Or at the heart of your application.

mindBrain connects business information, concepts, and rules to answer questions. It can complement existing software or support the model of an application you build.

The CRM example makes the explanation concrete. mindBrain adapts to any business model, whatever kind of agentic application you build.

You already have a CRM with an API

Keep your tool.
Add business context.

Your CRM continues to manage prospects, opportunities, quotes, and activities. A connector syncs the relevant data with mindBrain, which connects it to your company’s questions and rules.

CRMConnectormindBrainAgent

For example: identify opportunities at risk, explain why qualification is stuck, or prepare a pipeline review. The agent can then create a task in the CRM through its API, if its tools and permissions allow it.

The CRM remains the source of truth for its records. Requested operations use its API; the connector keeps synchronized data consistent.

You are building a custom application

A business model.
Your own application.

mindBrain can also provide the foundation for a fully custom CRM or another business application, without relying on a third-party CRM.

Transactional tables
Prospects, quotes, notes, tasks, and their state changes.
mindBrain model tables
The concepts, relationships, questions, and rules that give this data meaning.

For example: create a prospect, understand what is missing from their record, prepare a quote, and trigger the follow-up in the same application.

The application still needs access controls, storage, and operations. Its model defines the conditions that authorize the agent’s actions.

Connecting data: mindBrain Pro and Personal

In production, mindBrain Pro provides connectors to manage data synchronization. The scope depends on the software and available access.

For mindBrain Personal, connectors need to be adapted. Existing MCP servers can speed up this work by providing access to tools and data. Field mappings, data flow directions, and update frequency still need to be defined. MCP access alone does not provide continuous synchronization.

Another way to use the application

A request in the chat.
An answer, an action, or an interface.

An agent such as Hermes or OpenClaw can connect your application to Telegram, WhatsApp, Discord, or Slack, depending on the integrations you set up.

You no longer need to design a fixed screen for every use case. The agent can handle transactions, answer questions, and trigger workflows. When a view or form helps move the work forward, it can also generate an interface on demand and send its URL in the chat.

An example use case to build

“Which opportunities are at risk, and what should I do?”
  1. UnderstandThe agent queries the mindBrain model and gathers the causes of the risk.
  2. PresentIt answers in the chat and can send a link to a review view created for this request.
  3. ActYou choose the next step. The agent creates a task or starts the authorized workflow.
Where does each role’s responsibility end?
The connector supplies the facts.
It respects the source software’s access permissions and synchronization scope. Missing or outdated data limits the answer.
mindBrain holds the context and rules.
It structures answers using the available facts. Unknown information still needs to be clarified; required rules and approvals still apply.
The agent communicates and executes.
Creating a quote, sending a message, or publishing an interface requires the corresponding tools, permissions, and connections. Generated interfaces must also control access. Conventional screens remain useful when the work calls for them.

The bootcamp starts with a model and scenarios using synthetic data. Live connections and production deployment come later, based on the scope you have tested.

Prepare my project

Your turn

What about
your project?

Start with a simple scenario to understand the question-centered approach. Choose a starting point, then adapt it to your project.

Your first model outline

A brief to discuss.
A project to test.

Process
Qualifying an opportunity through to handoff
Roles
SDR and sales manager
Question
What information or approvals are missing before we can hand off this deal?
Event
A qualification conversation is scheduled
Next step to prepare
Check the conditions before proposing a handoff
Rule / approval
The budget and follow-up are confirmed; the manager approves the handoff.
First test
A scheduled follow-up without a confirmed budget must not authorize the handoff.

This brief is a starting point. Scope and feasibility still need to be reviewed.

Your text stays on this page. It is not sent with your email address.

Your first project

Qualifying an opportunity through to handoff

During the bootcamp, you will define this scope, build the model with the Architect, and check how it works with the Operator and people.

Build and test this project

From your first brief
to your first tested proof of concept.

Four weeks of practice with mindBrain on a focused process. You bring the business knowledge; the program gives you the method.

To build

The Architect.

You define the questions, facts, and rules. The Architect handles the technical build. You review it and request changes.

To use

The Operator.

You use your model through messaging, ask business questions, and observe the possible next steps in the scenarios you prepared.

  1. Define.

    Set the scope of a process, its roles, priority questions, and expected outcome.

  2. Build.

    Organize information, relationships, and rules with the Architect.

  3. Test.

    Prepare synthetic data and try the expected cases, unknowns, and exceptions.

  4. Refine.

    Review results, gather human feedback, and decide on corrections and next steps.

What you will be able
to bring to the table.

A first working model
A business scope, its information, questions, and rules.
Usage scenarios
How people and agents use this model.
Test scenarios and results
Expected behavior, gaps, and missing facts.
Human feedback
How well the answers are understood and how useful they are to the relevant roles.
A decision on what comes next
Make corrections, prepare a pilot, or consider expanding the scope.
What does “tested” mean?

Business consistency: the people involved recognize the concepts and rules. Functionality: the model behaves as expected in the tested scenarios. Usage: the answers help people move forward.

A proof of concept with sample data provides observations within a stated scope. A pilot with users and real sources can then assess adoption, integrations, and operating costs.

A clear framework for progress.

Weekly sessions over 4 weeks. No programming experience required, with definition work and practice between sessions.

Live connections to third-party software come later. The schedule, support, mindBrain access, and price will be specified before you enroll in the bootcamp.

Get the program and dates

Before you get started.

Scope, commitment, and the next step.

Do I need to know how to code?

No. You describe the expected behavior in natural language. The Architect handles the technical build. You still need to define your needs, review proposals, and practice with the Operator.

What will I build in four weeks?

The goal is a first working business model in mindBrain, within a focused scope, tested with synthetic data. Your scenarios and observations will help you decide what comes next. A larger project will require additional work.

Are the modules on this page connected to mindBrain?

No. They are local illustrations using a fictional case. They make the principles interactive. The bootcamp teaches you to build and use your own model with the Architect and Operator.

Will I connect my company’s real data?

The announced program uses synthetic data to test situations and rules. Live connections to third-party software and a pilot with real sources come later.

What tools, access, and costs should I plan for?

The program will specify pricing, the schedule, support, the duration of mindBrain access, and any exercise-related costs. It will also specify the supported messaging channel among Telegram, WhatsApp, or Discord.

Can I bring an internal need or an idea for a future service?

Yes. Start with a team process or a service you want to offer clients. The first goal is a demonstrable, tested scope. A pilot, client deployment, and commercial preparation are next steps to consider.

Will my brief be sent with my email address?

No. The brief fields stay in your browser and can be downloaded as text. The form sends only your email address to the existing mailing list service. If you do not download it, your brief is lost when you reload or close the page.

Does joining the mailing list commit me to a purchase?

No. You are requesting the program, dates, pricing, and details so you can decide. This signup does not reserve a paid seat or commit you to a purchase.

Your business.
Your first model.
The next step.

Get the program, upcoming dates, pricing, and details to choose your session.

Weekly sessions over 4 weeks to build and test a useful scope.

Upcoming sessions,
in your inbox.

No purchase commitment. Decide after reviewing the details.

This form is sent to Listmonk. The receiving service confirms whether it was accepted.