Skip to content
DEEN
Contact

Your systems work together. Your team decides.

TEQMINDS connects the software you already use into one shared platform, takes over recurring steps and prepares decisions so that your team can review and make them.

Arrange a conversation See an example
Foundation
Modular platform, operated by us and configured to your processes
Principle
Collaborative intelligence
Location
Hanover, Lower Saxony, Germany
01 · Approach

What we mean by collaborative intelligence

Software handles what repeats and can be clearly defined. People decide where experience, responsibility and context matter. Our platform makes the two work hand in hand.

  1. 01

    Connect, don’t replace

    Your specialist software, mailboxes and portals stay in place. We connect them so information reaches the right place without copy and paste.

  2. 02

    Prepare, don’t pre-empt

    Incoming items are classified and suggestions come with reasoning and sources. The decision stays with your team.

  3. 03

    Configure, don’t code

    Rules, responsibilities and approvals are set up – and can be adjusted when your processes change.

02 · Platform

One shared core, modules as needed

Every solution runs on the same platform core. On top of it we activate the modules that fit your processes. The scope follows from the analysis, not from a fixed package – and can be extended later.

Platform core surrounded by six modulesPlatformcore01Integrations02Intake &documents03Workflows04Assistance05Knowledgesources06Reporting

  • Platform core

    Users and roles, permissions and approvals, audit logging, interface management, operation and updates. Included in every configuration.

  • 01Integrations

    Connect specialist software, mailboxes, portals, data sources, and machine and sensor data.

  • 02Intake & documents

    Capture and structure emails, forms and receipts.

  • 03Workflows

    Rules, responsibilities, escalations, approvals and notifications.

  • 04Assistance

    Classify, prioritise and summarise – with reasoning, in controls that fit the task.

  • 05Knowledge sources

    Make policies, contracts and manuals findable; add external sources via interfaces.

  • 06Reporting

    Make workload, processing status and history visible.

03 · Example

A damage report in property management

How system and team work together on a typical case.

  1. System

    Intake

    The report from the tenant portal or mailbox is captured and assigned to the right property.

  2. System

    Classification

    Trade and urgency are suggested – with reasoning and a reference to matching framework agreements.

  3. Team

    Decision

    The case handler reviews the suggestion, adjusts it if needed and approves it.

  4. System

    Execution

    The job goes to the contractor, the tenant is informed and the case is logged.

Illustrative process; the actual set-up depends on your configuration. The principle carries over to fields with the same starting point, such as trades, tax advice or logistics: there, too, several unconnected systems run side by side, requests and documents arrive through many channels, and similar decisions recur every day.

More on property managementSix areas of use in detail

The starting point: a property management company works with management software, a tenant portal, several mailboxes, phone and a document archive – usually without any connection between them. Reports, requests and invoices arrive through all of these channels every day, and many decisions are alike: who is responsible? How urgent is it? Who takes on the job?

  • Damage & defects

    Intake

    Reports from the tenant portal, email and phone notes, often with photos.

    System prepares

    Merges reports about the same damage, assigns property, unit, trade and urgency, and suggests contractors from existing framework agreements.

    Team decides

    Placing the order, approving costs and following up on unclear cases.

  • Tenant requests

    Intake

    Questions about service charges, certificates, keys or house rules.

    System prepares

    Recognises the request, pulls in contract and property data and drafts a reply.

    Team decides

    Reviews, edits and sends the reply.

  • Invoices & receipts

    Intake

    Invoices from contractors and utilities by email or as scans.

    System prepares

    Reads invoices, assigns property and cost type, matches them against the order and flags discrepancies and duplicates.

    Team decides

    Approval and booking; the basis for the service charge statement.

  • Contracts & deadlines

    Intake

    Tenancy, maintenance, utility and insurance contracts.

    System prepares

    Makes contracts searchable, extracts deadlines such as notice periods, index adjustments or maintenance intervals and sends timely reminders.

    Team decides

    Terminate, renew or adjust.

  • Owners & associations

    Intake

    Resolutions, minutes, correspondence and owner enquiries.

    System prepares

    Bundles documents per property and unit, finds the resolutions relevant to a question and compiles documents for the owners’ meeting.

    Team decides

    Answering owners and chairing the meeting.

  • Master data

    Intake

    Tenant changes, new contact details, changed bank details.

    System prepares

    Detects changes, reconciles them between management software, portal and document archive and highlights discrepancies.

    Team decides

    Confirms changes, especially to bank details.

Which systems are connected and which steps run automatically is decided together in the analysis. These areas are examples, not a fixed scope of services.

Managing properties? Let’s talk
04 · Interface

The interface takes shape with the task

Rigid input masks always show the same fields; a chat window shows only text. Our platform builds the user interface dynamically for each case: with the fields, suggestions and buttons that this step needs. Your team sees what it is about and works directly on the case – without phrasing instructions and without searching through menus.

Chat window only
You

“Please look at the new damage report and do something sensible with it.”

Assistant

Sure. I have looked at the report. It is probably water damage, which …

  • Every detail has to be written as a sentence
  • Result hard to check, basis unclear
  • The next step remains manual work
Generated interface
CaseWater damage · Property 14, Unit 3
Urgent
TradePlumbing
ContractorSuggestion 1 of 3

Basis: Tenant portal report with 2 photos · Plumbing framework agreement

Place orderAdjustAsk tenant
  • Input in the right control instead of free text
  • Basis of the suggestion visible at a glance
  • Approval and next step in one click

Illustration of the interaction concept; contents are fictitious. Which elements appear depends on the case and the configuration.

05 · Process

From the first conversation to ongoing operation

  1. 01

    Analysis

    We look at your systems and processes and identify media breaks and duplicated work.

  2. 02

    Connection

    Your existing tools are connected to the platform.

  3. 03

    Automation

    Recurring steps run as workflows; approvals sit where your team should decide.

  4. 04

    Operation

    We run the platform as a service and adapt it when requirements change.

Also by TEQMINDSShelfwire

Shelfwire makes specialist literature usable for assistance systems: cited down to the paragraph number, without training on the works, with pricing set by the publisher. Within the TEQMINDS platform, Shelfwire can be connected as a knowledge source.

Visit shelfwire.de
06 · Contact

Let’s talk about your processes.

In a first conversation we work out where connection and automation could pay off for you – and what is possible with the tools you already have.

Pilot customers wanted. We are looking for companies that would like to introduce the platform into their processes together with us.

* Required