Its agent spots renewal risk
It connects account value, renewal date, sales activity, and support signals.
Collaborative implementation service for teams
Your team and its agents finally work from the same operational reality.
In 8 weeks, Web Igniter turns one critical process into a shared, governed, measurable system. Each person keeps their view, each agent knows its role, and everyone works from the same current state.
A complete engagement with a Go or No-Go decision at the end of week 2. The standard scope covers one process, one pilot team, and one measurable outcome.
The outcome is not another agent. It is a shared process that keeps working when the session, person, or model changes.
1 processcritical, recurring, and clearly bounded
1 pilot teamwith an available business owner
1 shared realitystructured in mindBrain Pro
1 outcomeverified against jointly defined criteria
Three roles. Three agents. One operational reality.
Sales, delivery, and finance ask different questions. Their agents still use the same clients, commitments, incidents, deadlines, and evidence, with permissions adapted to each role.
Its agent explains delivery risk
It connects milestones, budget, incidents, dependencies, and open commitments.
Its agent qualifies financial exposure
It connects invoices, disputes, delivery delays, and documented ownership.
mindBrain Pro
Shared operational memory
Business objects, relationships, rules, states, decisions, and evidence form a common, governed, inspectable context.
When information changes, the team no longer synchronizes three competing stories. The change becomes visible in each role's authorized context.
Personal proves the mechanism. Pro organizes direct collaboration.
The right starting point depends on how many people and agents must interact directly with operational memory.
mindBrain Personal
One person and one agent test a question, method, and first business model locally on SQLite.
Ideal for a fast, controlled proof.Personal through a central agent
Several people use one intermediary agent. This can be enough for a shared pilot without separate identities in the Brain.
Useful before opening direct access.mindBrain Pro and mindBrain Team
Several people and agents access shared PostgreSQL memory directly, with roles, permissions, and governance.
The level targeted by mindBrain Team Launch.One shared reality does not mean one identical view.
Collaboration becomes reliable when the foundation is shared and access stays proportionate to each role.
Shared objects
Clients, projects, contracts, incidents, and decisions keep one identity across teams.
Role-specific context
Each person and agent receives the facts, indicators, and next actions useful to its responsibility.
Different permissions
Reading, proposing, writing, and approving are configured separately according to operational risk.
Visible changes
An authorized update enriches the shared reality and remains traceable for the other relevant actors.
We start with a question that crosses systems.
A costly operational question reveals the people, data, rules, and decisions that must meet. It also creates a testable project outcome.
01
Sales
Which high-value renewals need action this week?
- Systems
- CRM, support, contracts, and sales activity
- Decision
- Prioritize at-risk accounts and the next useful move
- Expected outcome
- An assigned list supported by evidence
02
Delivery
Which projects could slip before the next report?
- Systems
- Planning, time, budget, incidents, and dependencies
- Decision
- Detect weak signals and choose a corrective action
- Expected outcome
- An exception review before the delay appears
03
Finance
Which overdue invoices hide an operational issue?
- Systems
- Billing, projects, support, contracts, and commitments
- Decision
- Separate simple collection from dispute or delivery failure
- Expected outcome
- The right action assigned to the right owner
04
Tenders
Which requirements still lack evidence or an approver?
- Systems
- Requirements, evidence library, experts, and versions
- Decision
- Close gaps before the final review
- Expected outcome
- A traceable, actionable coverage matrix
Prove. Share. Extend.
One transformation, three decision thresholds to limit risk.
Prove with Personal
Scope the process, establish the starting state, and validate the model on a reduced perimeter.
Share with mindBrain Team
Promote the proof into mindBrain Pro, configure access, agents, integrations, and approvals.
Extend without starting over
Maintain the system with BrainOps Care or connect other teams and domains on the mindBrain Enterprise path.
The week 2 Go or No-Go confirms feasibility and scope before production is built.
Eight weeks from method to a real service.
The engagement covers 8 weeks. The week 2 Go or No-Go avoids building production on an unverified assumption.
Understand, scope, measure
Turn one costly question into a testable scope.
- Map actors, tools, data, rules, and exceptions
- Establish the current operation and observable cost
- Define the business model and acceptance criteria
- Hold the Go or No-Go decision
Produce the Personal proof
Validate context, method, and first action on a controlled scope.
- Build the first business model
- Load useful data and connect the first agent
- Test a fresh session and main exceptions
- Document limits and promotion conditions
Deploy collaboration
Promote the validated case to mindBrain Pro and mindBrain Team.
- Deploy the model and priority sources
- Configure agents, roles, and permissions
- Set up approvals, audit, and human handover
- Test normal cases and exceptions
Put into service and hand over
Run the process in real work and prepare its operation.
- Pass the agreed acceptance tests
- Train the pilot team
- Hand over the runbook, exports, and responsibilities
- Open hypercare and the 90-day roadmap
Standard mindBrain Team Launch scope
Six deliverable groups tied to an operational outcome.
The scope stays legible so price, schedule, and responsibilities can be assessed before commitment.
Process model
One operational question, domain, starting state, actors, rules, exceptions, and acceptance criteria.
Limited proof
A Personal Proof showing that a fresh session retrieves context, follows the method, and produces a useful action.
Collaborative environment
One mindBrain Team on mindBrain Pro for a pilot team, with shared memory, role views, permissions, and audit.
Agents and integrations
Up to 2 configured agents and up to 2 priority integrations in the standard scope.
Adoption
Tests, pilot team training, documentation, runbook, and human handover criteria.
Continuity
Contracted exports, a 90-day roadmap, and 30 days of hypercare after launch.
User count, hosting mode, Pro license, and special requirements are detailed in the proposal after technical qualification.
We define what working means before building.
Ten tests cover continuity, action, collaboration, and control. Their details are adapted to the process during scoping.
- 01Fresh session
Resume the case without a long manual rebrief.
- 02Right context
Retrieve the expected objects and events.
- 03Business method
Respect the agreed steps, rules, and exceptions.
- 04Useful action
Prepare or execute an authorized operation.
- 05Permission
Block or request approval at the right threshold.
- 06Evidence
Link a recommendation to its facts and rules.
- 07Human handover
Give a person the state and next decision.
- 08Role handover
Pass the case between roles without losing context.
- 09Shared consistency
Reflect a change in authorized views.
- 10Audit
Find who viewed, proposed, approved, or changed the case.
From fragmented stories to a collaborative process.
The goal is not to promise an autonomous company. It is to make one shared process faster, more reliable, and more explainable.
Before mindBrain Team Launch
- Each function rebuilds context in its own tools
- Agents receive different briefs
- Rules and exceptions remain in expert memory
- Handovers lose previous decisions
- Pilot value is hard to prove
After mindBrain Team Launch
- Objects and events have one shared reality
- Each agent uses the context authorized for its role
- Rules, approvals, and exceptions are explicit
- Changes and decisions remain traceable
- The outcome is assessed against agreed criteria
Shared memory reduces coordination cost without erasing responsibility.
Governance, security, and exit are scoped as operating decisions.
Exact choices depend on your constraints, systems, and hosting mode. The proposal separates what is included, configurable, quoted separately, or dependent on a third party.
TopicCommitmentStatus
Data and hosting
Location, target environment, and operating responsibilities are documented after technical qualification.
Configurable
Access and roles
Read, propose, write, and approve rights are defined for the pilot scope.
Included
Audit log
Covered operations and required trace level are defined with acceptance criteria.
Included
Backup and restore
Frequency, retention, ownership, and restore tests depend on the selected operating mode.
To define
AI models
The model may change without becoming business memory. Providers and costs are qualified separately.
Configurable
Export and portability
Contracted models, configurations, exports, documents, and procedures are handed over.
Included
Reversibility
Exit, migration, and assistance conditions are described in the final proposal.
Quoted separately
Illustrative demonstration, synthetic data
Renewal risk becomes a shared case, then a coordinated action.
This scenario shows the intended operation. It is not a published client outcome and claims no quantified gain.
Sales, delivery, and finance query the same account with different views. Every step keeps its source and owner.
- 01Sales opens the case
Its agent detects a near renewal, low activity, and several support signals.
- 02Delivery adds context
Its agent links a late milestone and an open commitment without exposing unauthorized financial data.
- 03Finance qualifies the risk
Its agent confirms a disputed invoice and requests approval before any sensitive action.
- 04The team decides from one basis
The action plan, owners, evidence, and next deadline remain available in the shared case.
One shared process. A team to put it to work.
Illustrative atmosphere photography.mindBrain Team Launch engagement
A standard scope starting at EUR 20,000 excl. VAT.
From EUR 20,000 excl. VATThe final amount depends on the process, sources, integrations, hosting, and governance requirements. A proposal defines scope after qualification.
Assess my processIncluded in the standard scope
- Complete 8-week engagement with Go or No-Go at the end of week 2
- 1 process, 1 question, 1 domain, and 1 pilot team
- 1 business model and 1 Personal Proof
- 1 mindBrain Team environment on mindBrain Pro
- Up to 2 configured agents and 2 priority integrations
- Roles, permissions, approvals, audit, training, and documentation
- 30 days of hypercare after launch
Quoted separately
- Additional agents, integrations, processes, or teams
- Third-party model or software licenses and usage
- Hosting, operations, or compliance outside the standard scope
- BrainOps Care after hypercare
Keep the first process useful before turning it into an expansion platform.
A successful launch creates a maintained operational base, not an invitation to multiply scope without evidence.
BrainOps Care
Maintain, monitor, and improve the mindBrain Team process with a clear change path.
Extend the model
Add a new process or source after the first outcome and operating cost are understood.
mindBrain Enterprise path
Connect additional teams and domains with explicit governance and ownership.
Is mindBrain Team Launch the right format?
A good launch needs a recurring problem, a business owner, and criteria the team agrees to verify.
It is not the right format yet if you seek
- A fully managed automation with no team involvement
- A guarantee of revenue, leads, or customer behavior
- A broad platform before proving one process
- A project without an available owner or usable data
- A one-person experiment with no shared workflow
The potential is strong if you have
- One process repeated across several people or systems
- A costly question that crosses sources and roles
- A pilot owner with time for decisions and tests
- Evidence, rules, and exceptions that can be reviewed
- A measurable outcome the team accepts
If the case remains individual or exploratory, Personal or the Bootcamp is often the better first step.
Answers that clarify the service limits.
These answers explain the operating model without turning the page into a technical contract.
Does mindBrain Team replace our existing assistants?
No. It gives compatible assistants shared context, role-specific permissions, and controlled operations around one process.
Is this only a shared document library?
No. mindBrain Team structures objects, relationships, decisions, rules, states, and evidence that agents can use within permissions.
Can we start from Personal?
Yes. Personal is the recommended proof layer. Direct multi-user collaboration targets mindBrain Pro and mindBrain Team.
How many processes are included?
The standard scope covers one clearly bounded process, one operational question, one domain, and one pilot team.
Are integrations guaranteed?
Only integrations agreed during qualification and listed in the proposal are included. Third-party availability remains outside our control.
Where is the system hosted?
Hosting, location, and operating responsibilities are selected and documented during technical qualification.
Can our agents take actions automatically?
Only within configured permissions. Sensitive operations can remain prepared and pending approval.
What happens after the 8 weeks?
The service ends with handover and hypercare. BrainOps Care or a new scoped extension can follow if useful.
What is not included in the price?
Additional scope, third-party usage, hosting, special compliance, and ongoing operations outside the standard are quoted separately.
Can we stop after the pilot?
Yes. The agreed exports, documentation, and operating responsibilities are handed over so the team can decide its next step.
30-minute qualification conversation
Check whether one of your processes is ready for mindBrain Team.
Tick the criteria that are already true today. The check runs in your browser and sends no data.
The conversation confirms a starting point and first recommendation. It does not replace scoping or a technical proposal.