Skip to content

From Request to Finished Tool: How DivineMind Builds New Features

You tell AIRIS what is missing. That becomes a development order that is built, tested and documented with a video. This is how we have worked since October.

D
DivineMind Team
November 18, 20262 min read
From Request to Finished Tool: How DivineMind Builds New Features

Every company knows the moment: the software can do almost everything, just not that one thing. Until now, that meant writing a request to the vendor and hoping it would eventually appear in an update. We built this process differently.

The journey of a request

  1. Say what is missing. You write or tell AIRIS what you need. AIRIS first checks whether it can be solved without programming, for example with a setting, an additional field or a template. If so, it does it immediately.
  2. Answer follow-up questions until it is clear. If something truly new is needed, AIRIS asks: what exactly, who uses it, a concrete example, what result is expected. This becomes a development request with a number.
  3. Build and test. The request is programmed and run through in a demo account with invented data, never with real customer data.
  4. Document with video. Every finished request gets a short video showing how the new feature is used.
  5. Release. Only after approval by a person does the feature go live. It then appears in the help section, and the video serves as the guide.

What this means in numbers

Our own team has been working this way since October 20. Since then, 19 feature requests have been logged as development requests. 17 of them are live, 16 with video, most of them on the same day. Two were not built.

Examples from recent weeks: sent emails now clearly show who they were sent to. The travel expense report tracks daily allowance and overnight allowance per day and calculates mileage allowance according to Austrian rates. Notes now support lists in the editing toolbar.

And when a customer needs something?

Customers tell AIRIS in exactly the same way. Their request reaches us as a report with a number, and AIRIS gives you that number. We review every report: if it fits the product and also helps other businesses, it becomes a development request and follows the same path, all the way to the video. Not every request gets built. If it does not, we will tell you honestly.

Why we do it this way

Software for small and medium-sized businesses must adapt to their everyday work, not the other way round. The route via AIRIS turns a request into a traceable task with a number, a review and proof. In the end, a person decides what gets built.

Free potential analysis or book an initial consultation.

Tags

airis
programmierauftrag
produkt
ki

Frequently Asked Questions

Want to learn more?

Discover how DivineMind.AI can help your business work more efficiently and stay compliant.

D

DivineMind Team

The DivineMind.AI team shares insights on business automation, compliance, and AI.