AIonicOS + TAC Engineering. As a scoped entry point.

One process. One result. One approval.

We take one task somebody still does by hand today: from Microsoft 365, the ERP, DATEV, or the ticket system. We build it with TAC Engineering on AIonicOS — with the models that suit the task, your existing systems, and one clear human approval. Up to three source systems, one approval step, implementation at a fixed price.

Running costs are the environment, AI consumption, and the agreed maintenance. Prices and billing rules are fixed before you commission the work; AI consumption is reported on actual usage.

Owner-run, Hamburg. You speak with Gerald Fehringer, Managing Director of NC AGENTIC GmbH, the company behind AiLoft and startvisor.AI. He has founded several ventures himself and is personally accountable for the quote, the implementation, and the acceptance.

AiLoft / entry offer Limits agreed up front

What the entry offer covers

  1. 01 1 result, described and accepted in advance
  2. 02 up to 3 source systems through existing interfaces
  3. 03 1 approval step, where the decision is made today
  4. 04 €0 platform license for the AIonicOS core

Why this works

Why a tailored process does not start from zero.

  1. The base already runs

    AIonicOS orchestrates models, company knowledge, tools and approvals. What gets built is your process logic — not the platform underneath it.

  2. Built with TAC

    Scoped development tasks worked on by development agents under defined tool permissions and automated checks. Integration and sign-off stay with us.

  3. Models matched to the task

    Which model handles a given work step follows from the task, its data requirements, and the agreed quality and cost targets.

The time advantage comes from the reused base and the procedure, not from fewer tests.

Examples

Three sub-processes that make a good starting point.

We do not start with your process landscape, but with one task somebody still does by hand. It gets prepared; the decision still sits with you.

Pre-sorting incoming requests

What goes in
Everything that lands in the shared mailbox, usually Outlook: enquiries, complaints, questions about orders.
What comes out
Every message is matched to a topic and a person, with an urgency and a draft reply.
Who approves
Nothing is sent before the responsible person has read and approved it.

Assembling documents

What goes in
Your template, the versions last sent out, and the master data from SharePoint, the ERP, or DATEV.
What comes out
A draft in which every figure points back to its source. Anything that departs from the template is flagged.
Who approves
Signed off by the person who puts their name to it, not by the system.

Preparing an approval

What goes in
A document, a contract, or an application, plus the rule it is checked against.
What comes out
The check points are worked through, deviations are named, and the decision is prepared and reasoned.
Who approves
Decided by the person who is accountable for the approval.
All six processes in the catalog

These examples start the conversation. Sources, interfaces, permissions, and acceptance criteria are engineered for your environment.

Also possible

You do not need automation but an application of your own?

AIonicOS is our base for automation. Where an application of its own does more, we build it as standalone software — by the same method: bounded tasks, agent-supported implementation with automated checks, technical acceptance before it goes live.

Free, no sign-up

Before you commission us: four tools to check for yourself.

Everything runs in your browser and no data reaches us. You can use them without ever talking to us.

  1. Set up an AI pilot

    Ten steps from an idea to a decision-ready proposal. The result is a charter with a source behind every statement.

  2. Assess an AI provider

    Data processing agreement, training exclusion, place of processing. Pre-filled with the published terms of thirteen providers.

  3. Take stock

    Where AI has landed in your company, how mature the governance is, and what to do across three phases.

  4. Set up a SOC

    Classification under the new German BSIG, the BSI attack-detection guide, an operating-model recommendation and a roadmap with a timeline.

Open the AI Toolkit

Entry offer

Your first workflow in production.

One bounded process, from the current-state review to handover. Scope, target criteria, and the fixed price are set before implementation begins.

Included in the offer

One defined result
A process that produces a described result: a draft reply, a checked list, or a finished document. The result is defined and accepted up front.
Sources and connections
Up to three source systems through their existing interfaces: Microsoft 365, SAP or another ERP, DATEV, CRM and ticket systems.
One approval step
A named control point: a responsible person approves before anything leaves the company or a system is changed.
Testing and acceptance
Test cases from your real transactions, documented deviations, and sign-off by the business owner.
Support after go-live
Handover with a runbook, a named owner, and an agreed route for corrections during the first weeks.

How it works

Four steps from the first call into operation.

Four steps following our own procedure, AI Tactical Engineering. Each step ends in a result you can check. The process only goes live when the person accountable for it decides so.

  1. 01

    Clarify the goal

    You bring the process and the person who runs it today. We record the result, the sources, and where approval happens. After that, the fixed price is set.

  2. 02

    Implement

    We connect the agreed sources and build the process with its rules, its exceptions, and the one approval step at the point where somebody decides today.

  3. 03

    Test and approve

    Testing runs against your real transactions. Anything that deviates is documented and corrected. Sign-off comes from the person accountable for the process, not from us.

  4. 04

    Operate

    Runs, exceptions, and AI consumption stay visible. Whatever surfaces in the first weeks goes through the agreed correction route.

If access, accountable owners, and test transactions are in place, we are talking days to a few weeks. If one of them is missing, we tell you which one before you commission the work, and how the start shifts.

Ongoing costs

What runs on after go-live.

Implementation is covered by the fixed price. After that, three categories remain: they recur monthly and are itemised on the invoice.

After go-live

  1. Environment operation

    Infrastructure, runtime environment, monitoring, and technical operation of the agreed deployment.

  2. AI consumption

    Models, retrieval, and tools are billed on actual usage and reported per category. The billing rule is fixed up front; the amount follows throughput.

  3. Maintenance and support

    Care of the environment, required updates, and support at the agreed level.

Prices and billing rules are fixed before you commission the work. AI consumption is reported on actual usage; a budget ceiling can be agreed separately. This overview does not replace a quote.

Less talk — build with AI.

Bring us a task somebody still does by hand.

Half an hour is enough to settle three things: what goes in, what should come out, and who approves. If that fits into one result, three sources, and one approval step, you get a fixed price after step 1. If it does not, we tell you in the same call.