Built on mindBrain

Your business.
An application that acts.

Web Igniter adapts mindBrain to your processes to design and deploy your business application.

Concept illustration: a shared mindBrain foundation connects accounting documents and messaging conversations.
One shared software core.Concept illustration

The starting pointmindBrain already exists.

Your applicationWeb Igniter adapts it to your business.

Applications that
speak your business.

Two examples of what we can build with mindBrain.

Your accounting application

Your documents arrive.
The accounting moves forward.

Gather documents, prepare operations and highlight what needs your approval.

You ask

“Prepare this month’s accounting.”

Your request sets the starting point.

The application prepares

Documents, operations and points to check.

Work follows the agreed process.

You decide

The approvals that move work forward.

You step in at the agreed stages.

Your business operating system

One conversation.
Your business in context.

Review ongoing work, find commitments and prepare the next actions from Telegram.

Agency · Studio · IT services

One shared project.
An answer for every role.

Client, team, production and delivery belong to the same graph. Hermès highlights the relationships relevant to your question.

Marc · Project managerQuestion on Telegram

« Can we deliver the Acme project on Friday? »

The same question, for your role

Hermès connects commitments, work in progress and blockers affecting delivery.

The Acme project, in contextView: project manager

Scroll to explore the graph

One project ontology, several business perspectivesThe Acme project connects the client, team, tasks, production and delivery. Objects stay in place; each view highlights relationships relevant to a question. Statuses illustrate a fictional scenario. All relationships are listed after the graph. PersonA question TelegramThe conversation Hermès agentBusiness context Business questionThe relevant path ClientAcme ContactsClient contacts OpportunityWebsite redesign Offer / ProposalAgreed scope ContractClient commitment SalesThe client relationship ProjectACME · Website MilestonesNext delivery TasksAPI-42 · in progress DeadlinesFriday Risks / BlockersDelivery at risk Project managerMarc TeamProject team DesignerHomepage design DeveloperPaul DesignHomepage approved SpecificationsApproved scope CodeAPI unfinished Versionsv1.8 · candidate EnvironmentsStaging TestsBlocked by API-42 DeliverablesHomepage · v1.8 DeploymentAwaiting tests DeliveryFriday · at risk Client approvalAwaiting delivery
HermèsBusiness answer
Friday delivery is at risk.

API-42 is unfinished and blocks testing of homepage v1.8. Paul owns the task. This blocker must be resolved before confirming delivery.

API-42 · in progressPaul · ownerTests v1.8 · blocked
Explore the project relationships

All 39 relationships from the model are preserved. Three additional links support the API-42 scenario: the task is assigned to Paul, it blocks testing and the deliverable is scheduled for delivery. Dotted links connect the question to its context.

  • Person asks a question Telegram
  • Telegram forwards Hermès agent
  • Hermès agent interprets Business question
  • Client has Contacts
  • Contacts generates Opportunity
  • Sales manages Opportunity
  • Opportunity leads to Offer / Proposal
  • Offer / Proposal becomes Contract
  • Contract triggers Project
  • Client commissions Project
  • Project manager leads Project
  • Project has Milestones
  • Project contains Tasks
  • Project has deadline Deadlines
  • Project exposed to Risks / Blockers
  • Team works on Project
  • Team includes Project manager
  • Team includes Designer
  • Team includes Developer
  • Designer produces Design
  • Design feeds Specifications
  • Specifications guide Code
  • Developer produces Code
  • Code generates Versions
  • Versions deployed to Environments
  • Versions subject to Tests
  • Tasks produces Design
  • Tasks produces Code
  • Project produces Deliverables
  • Versions forms Deliverables
  • Tests allows Deployment
  • Deployment enables Delivery
  • Delivery subject to Client approval
  • Client approves Client approval
  • Business question selects a subgraph Project
  • Business question accesses context Client
  • Business question accesses context Tasks
  • Business question accesses context Deliverables
  • Business question accesses context Risks / Blockers
  • Tasks assigned to Developer (API-42 scenario)
  • Tasks blocks Tests (API-42 scenario)
  • Deliverables scheduled for Delivery (API-42 scenario)

Inside your application

Everything is connected.
Your application understands it.

A building, its residents, a maintenance visit, an invoice… With mindBrain, these records make sense through the relationships between them.

Business exampleProperty management

Places, people and equipment.

12 objects · 12 relationships

Scroll the graph to explore the connections

Places, people and equipment.A building brings together spaces, equipment and people. Relationships identify who manages, owns and occupies it. Each arrow shows the direction of a relationship. The full list follows the graphs. manages concerns contains includes includes includes own occupy live in belong to has include Property manager Joint ownership Building Owners Tenants Households / Residents Apartments Shared spaces Cellars Technical rooms Equipment Lift

From an incident to its financial impact.

13 objects · 17 relationships

Scroll the graph to explore the connections

From an incident to its financial impact.An incident can trigger maintenance or repairs. Contractors, contracts, invoices and the budget belong to the same context. Each arrow shows the direction of a relationship. The full list follows the graphs. monitor can detect affect trigger can trigger applies to modify perform perform bound by generate affect pay fund administers funds funds Inspections Incidents Building Equipment Maintenance Repairs Contractors Contracts Invoices Service charges Owners Budget Property manager

Your business is more than a record.
Your application connects objects, actions and their consequences.

Connect my business data
Explore the 29 relationships Illustrative example

The property

  • Property manager manages Joint ownership
  • Joint ownership concerns Building
  • Building contains Apartments
  • Building includes Shared spaces
  • Building includes Cellars
  • Building includes Technical rooms
  • Owners own Apartments
  • Tenants occupy Apartments
  • Households / Residents live in Apartments
  • Tenants belong to Households / Residents
  • Building has Equipment
  • Equipment include Lift

Maintenance and repairs

  • Inspections monitor Equipment
  • Inspections can detect Incidents
  • Incidents affect Building
  • Incidents trigger Maintenance
  • Incidents can trigger Repairs
  • Maintenance applies to Equipment
  • Repairs modify Building
  • Contractors perform Maintenance
  • Contractors perform Repairs
  • Contractors bound by Contracts
  • Contracts generate Invoices
  • Invoices affect Service charges
  • Owners pay Service charges
  • Service charges fund Budget
  • Property manager administers Budget
  • Budget funds Maintenance
  • Budget funds Repairs
The shared foundationmindBrain

Knowledge, processes and continuity of work.

Your business shapes
the application.

Web Igniter provides the consulting and implementation to turn this foundation into an application that fits your company.

  1. UnderstandYour processes and priorities.
  2. AdaptRules, data and tools.
  3. DeployThe application in your environment.

Which application
for your business?

Let’s start with a concrete process and the outcome you want to achieve.

Get started