How a project runs

Everything about a project, without having to ask.

Most of a buying decision happens without the seller in the room. This page is written for that part: the sequence, the people, the money and the data. If it answers your questions, we have done our job even if you never call.

The five phases

00
From the call to the offer
We work out where the money actually sits, agree the target picture and turn it into a project plan with a fixed price. Nothing is billed up to this point.
From youOne or two working sessions

ResultA project plan, a fixed price and a decision you can take or leave
01
Systems and data
We look at what already exists: shop, ERP, CRM, spreadsheets, inboxes. We map where the numbers live and how reliable they are.
From youRead access to the relevant systems

ResultA written map of your data and an honest note on what is missing
02
Context and rules
Your margins, your exceptions, your approval thresholds, and the cases where your company decides differently from the textbook.
From youTwo or three sessions with the people who actually decide

ResultThe rule set your system will follow, in plain language, signed off by you
03
Setup under your name
HELYOS is configured on your data, connected to your systems, and dressed in your brand on your own domain.
From youAccess, a domain or subdomain, one owner on your side

ResultA running system your team can log into
04
Approvals and pilot
A limited group works with it. The routine runs through, the exceptions go to a person. We adjust the rules against what really happens.
From youThree to five people using it daily

ResultA tuned rule set and a decision on going wider
05
Operation
The system stays in work. We record what it suggested and what happened next, and that record improves the next suggestion.
From youHalf an hour of review a month

ResultA system in daily use, plus a short monthly report

What we need from you

One owner

A single person on your side who can decide. Not a committee. This is the strongest predictor of whether a project lands.

Access, not exports

Read access to the live systems. Working from exported spreadsheets doubles the effort and halves the accuracy.

Your real rules

Including the uncomfortable ones. Every company has decisions that appear in no process document. Those are the ones that matter.

Two hours a week

During phases one and two. After that, considerably less.

What it costs

Time to live: It depends on the complexity, mainly on how many systems have to be connected and how fast we get access. After phase one we name a date and hold it.
Model: Fixed price for the setup, agreed after the first call. A monthly fee for operation and further development. No hourly billing and no open-ended budgets. Most of what we earn comes from a system that is being used, which means we lose money when it goes quiet. That is deliberate.
Operation: From 499 € a month. No VAT is added, see below.
Setup: A fixed price, quoted after the working sessions. It depends on how many systems have to be connected, and you see the figure before anything is billed.
Up to the offer: Free. The call, the sessions and the project plan cost nothing.
Notice: Monthly, to the end of the month. No minimum term.
VAT: Currently not charged under section 19 of the German VAT Act.

Where your data sits

Access: Named people only, on your side and ours. Nobody works in your system who is not on that list.
Export: Your data and your configuration are exportable in a readable format while the system runs.
Paperwork: Processing agreement, list of subprocessors and a record of processing activities, ready before the system goes live rather than after.
Everything else: Hosting location, retention periods, logging and what happens at the end of a contract are settled in writing before you sign, not afterwards. We name them in the offer. If a point matters to you, ask on the call and you get a straight answer.

When we stop

We end a project ourselves if the data turns out to be too thin to decide on, if the rules cannot be pinned down because nobody owns the process, or if what you need is a person rather than a system. In that case you pay for what has been done and nothing beyond it. Saying this in month one is cheaper for both of us than discovering it in month five.

Nobody takes responsibility for a system they cannot explain.

That is why our systems prepare the work and carry out what has been approved. Approvals, exceptions and manual overrides stay with your people, and the path to every decision stays readable.