Euthyna pricing How Euthyna
pricing works.

What Euthyna does, in one paragraph

Big projects pay money out in stages. A builder is paid when a stage of work is finished. A borrower draws money from a loan when a condition is met. Each of those payments is called a release. Before a release goes out, someone is supposed to check that the work is done, the paperwork is in, and the right people have approved it.

Euthyna does that checking. You tell it what proof each release needs and who has to approve it. When a release is due, Euthyna checks it against those rules. If everything is in order, it clears the release. If something is missing, it holds the release and says exactly what is missing. Either way, it writes down what happened and why, in a record that cannot be changed later. Euthyna never holds or moves the money itself. Your bank does that, as it always did.

Why this stage exists

You cannot judge software like this from a website. Whether Euthyna helps you depends on details we cannot guess. How often is money released on your project? Who has to sign off on each release? What proof do those people ask for? Where does that proof sit today?

So we ask before we sell. Discovery costs you a meeting and costs us a meeting. If Euthyna is a poor fit for your project, we would rather say so now than sell you a pilot that disappoints you.

How it works, step by step

You bring one real project. In the meeting, we walk through how money reaches the people doing the work today. Where are the payment points? Who approves each one? What documents does each approver rely on? Where do those documents live now?

Then we show that same payment schedule inside Euthyna, while you watch. You see what a checked release would look like for your project, not for an invented one.

If you want to try it yourself, we give you a practice copy of Euthyna. It is a sandbox. Anything you enter there is practice, and none of it becomes your real record.

Within a few days you get a written pilot proposal. It says what we would set up, how many weeks it would take, what the fixed price would be, and roughly what a yearly subscription would cost afterwards. Reading it and doing nothing is a perfectly normal outcome.

What you are agreeing to

Nothing. There is no fee, no contract, and no obligation. We do not bill Discovery later, and we do not deduct it from a later price, because there is nothing to deduct.

What a pilot means here

A pilot is a trial, but it is not a demonstration. We set Euthyna up around your real project: the actual points where money is paid out, the actual people who approve each payment, and the actual proof each payment needs. Then your people use it for real. When a payment is due, Euthyna checks it, clears it or holds it, and records why. Those decisions count.

It is fixed in three ways on purpose: fixed scope, fixed price, fixed end date. Before you start, you know exactly what will be set up, what it costs, and when it stops. It does not renew on its own, so it cannot quietly turn into a subscription you never chose.

Why the pilot is paid

Setting Euthyna up around your project is real work on both sides, and your people are making decisions that matter. So the pilot is priced as work rather than given away. Paying for it also means you take it seriously, which is what makes the result trustworthy.

How it works, step by step

First we agree one project and write the pilot down. The document names the payment points inside the project, the proof each payment needs, and who approves what. It also says roughly how many payments to expect, how much storage the proof will need, and how many weeks the pilot runs. Nothing starts until that document is agreed.

Then we set it up with you. Arranging what Euthyna already does around your rules is part of the fixed price, not a separate invoice.

From the first day, the decisions are real. Each payment is checked against your own rules and is either cleared or held. Every outcome is recorded with the proof behind it. A hold is as useful as a clearance here, because it shows you the product doing its job.

At the end, we write a proposal for a yearly subscription. We size it to what you actually used, not to what anyone guessed at the start. Your setup and your recorded decisions carry into the subscription exactly as they are.

What you are agreeing to

One fixed fee, paid by invoice, for a fixed number of weeks. That is the whole commitment. When the pilot ends, it either becomes a yearly subscription because you decided so, or it simply stops. Nothing renews automatically, and there is no penalty for stopping.

Why this is the stage most customers stay in

Discovery is where you decide whether to try. The pilot is where you find out whether it works. Production is what you actually buy, and it is the stage the product is built around.

It is sold by the year rather than by the month for a simple reason. A record of decisions is only worth something if it is unbroken. If you have to defend a payment decision in year three, you can only do that if year one is still on file, with the proof attached to it.

What you are agreeing to

You agree to a one-year term and we invoice you for it. At the end of the year, the subscription renews only by agreement: we ask, you decide. It does not roll over silently, and there is no automatic price increase hidden in it.

If you choose not to renew, you can download your account record, signed order documents and proof files during the agreed period after the term ends. Decisions and approvals can be read there but cannot be downloaded. There is no exit fee, and once undisputed invoices are paid, nothing you are entitled to download is held back.

How capacity works, in plain terms

Capacity is the amount of work your subscription covers. It is written into your agreement as five figures. How many projects Euthyna checks. How many payments a year. How much proof you store. How many years that proof has to be kept. And how many environments you need. An environment is one running copy of Euthyna. Everyone has a live one. Some customers want a second copy for testing or training.

Two customers on the same plan can have very different figures, so there is no standard allowance and no number printed on this page. Yours is whatever your agreement says it is.

Capacity never changes on its own. If an action would take you past it, Euthyna refuses that one action and explains itself: what you agreed, what you have used, what this would make it, and what to ask for. Nothing already recorded is deleted, everything on file stays readable, and your downloads keep working.

What to expect day to day

Most days are unremarkable, which is the point. Someone submits a payment with its proof. Euthyna checks it against your rules, clears it or holds it, and records the outcome with the reason. The people who need to see that record, inside your company and outside it, log in and read it. Nobody pays extra to look.

What Scale means here

Your subscription covers an agreed amount of work: a number of projects, a number of payments a year, an amount of stored proof, and so on. When your business grows past that, you need more room. Scale is the name for getting that room without starting a new contract or a new setup.

Why it is a change to your contract rather than a fresh start

Growth should not cost you your history. Imagine that adding a second project meant a second contract and a second setup. Your record would end up split across two systems. The rules you spent months getting right would be written again from scratch.

So Scale raises the figures inside the agreement you already hold. Your year keeps its original start and end dates, your tenant stays the same, and every decision already recorded stays exactly where it is.

What actually changes

Three things. First, you can run more projects, and more of the separate companies that own them. Lenders often require each project to sit in its own company, sometimes called a special purpose vehicle. One of those counts like any other company.

Second, reporting widens. You can see every project at once instead of opening them one at a time, which is usually what a bank's credit committee or an investor update actually needs.

Third, you can reuse what worked. The rules and payment templates written for your first project become the starting point for the next, so each project takes less setting up than the last one did.

What does not change

The checking. A larger plan raises how much you are allowed to run. It does not loosen a single rule, skip a single approval, or leave a single decision unrecorded.

What you are agreeing to

A written change to your existing agreement, priced on the same basis as your original subscription. Your renewal date does not move. At the next renewal, the higher capacity is simply what you renew.

What enterprise requirements means

Most companies above a certain size have rules that every piece of software must follow before it can be used. Staff must sign in through the company's own login system. Data must be stored in a certain country. Records must be kept for a set number of years. The security team must review the software first. The purchasing team must use its own contract. Those are enterprise requirements. Euthyna can meet them, but meeting them changes how and where we run it for you, so it is agreed and priced separately.

Why this one is negotiated

Everything up to Scale is the same product with different figures written into it. Enterprise is different in kind. It changes how and where we run Euthyna for you, and what we promise in the contract. Those things cannot sit on a price list, because they are specific to your company.

Two examples make it concrete. A rule that your data stays inside a named country is a decision about where the software runs, and it costs something to meet. A rule that we answer your security questionnaire and accept a review before go-live is a commitment of our people's time. Both get agreed, written down and priced with you.

What companies usually need here

Single sign-on, which means your staff reach Euthyna through the company login they already have, so nobody keeps a separate password. A dedicated environment, which is a copy of Euthyna that runs only for you. Or your data stored in a country or region you name. Records kept for more years than a standard setup keeps them, because lenders or regulators require it.

A formal security review, and your security questionnaire answered, before you go live. Promised response times, so support is a commitment written into the contract rather than a courtesy. A named person on our side, and regular reviews of how well your rules and approvals are working. And a contract on your purchasing team's own terms, negotiated rather than accepted as written.

What it does not buy you

Looser checking. An enterprise agreement changes what we run for you and what we promise. It never changes what Euthyna lets through.

What you are agreeing to

A yearly agreement on negotiated terms, paid by invoice. Payment terms, renewal terms and notice periods are part of what we negotiate. After signing, every change to scope or capacity is a written amendment: a signed change to the contract, priced on the same basis as the original.

The five kinds, in plain English

Custom development means building something into Euthyna that exists only for you: a new decision rule, a workflow only your company uses, or a report that is not in the standard set.

Integrations means connecting Euthyna to software you already use, such as the system where your documents live, your project management tool, or your accounting system. The point is that documents and approvals arrive in Euthyna on their own instead of being uploaded by hand.

Migration means loading your past projects, decisions and proof into Euthyna, so your record starts complete rather than empty.

Training means sessions for each group of people who will use Euthyna: the people who run it day to day, the people who approve payments, investors and lenders, auditors, and your administrators.

Advisory means help designing the rules themselves, before anything is set up: what proof each payment should need, who approves what, and what should happen when something is missing.

The line between setup and professional services

Setup means arranging what Euthyna already does around your project. That covers your decision rules, your payment templates, the proof each payment needs, who approves what, who can see what, and the standard report layouts. You can do that yourself, or we do it with you during the pilot. Either way, it is part of what you are already paying for.

Professional services begin where setup ends. They are work that exists only because of your other software, your history, or a request that is specific to you. If Euthyna can already do it and it only needs arranging, that is setup, and it is included.

Why we keep it separate

If this were folded into the subscription, every customer would be paying for the integrations, migrations and custom reports that only some customers need. Quoting it separately means you buy the pieces you need, you can see what each one costs, and the subscription price stays honest.

It also lets us answer the obvious question plainly: no, none of this is required. Euthyna runs without a single piece of it.

What you are agreeing to

Each piece is written up as a fixed scope with its own price before any work starts. You take the ones you want and leave the rest. Buying professional services does not change your subscription price, your capacity or your renewal date. Not buying them does not limit what Euthyna does.

Why a price list would mislead you

Think of one project with a handful of payments a year. Now think of a portfolio of dozens of buildings, running on a copy of Euthyna set up just for one company. The software is the same, but they are very different things to run. A single published number would be wrong for almost everyone who read it.

So we write you a proposal instead of publishing a number you would have to adjust in your head. The proposal is specific, it is in writing, and it is based on your project rather than an average one.

The first thing it depends on: how much work

This is what we call capacity. It is measured in five figures. How many projects Euthyna checks. How many payments a year, counting both stage payments to builders and drawdowns. A drawdown is an amount taken from a loan in stages. How much proof you store. How many years that proof has to be kept. And how many environments you need. An environment is one running copy of Euthyna: your live one, plus any test or training copy.

The second thing it depends on: your company's own rules

Some companies have rules that every piece of software must meet. Staff sign in with the company login. Data stays in a certain country. Records are kept for a set number of years. The security team reviews the software first. Support response times are promised in writing. The purchasing team uses its own contract. Meeting those rules changes what we run for you and what we promise, so it changes the price. That is the Enterprise plan.

We size both things from your own project: the payment schedule, who approves each payment, and what proof they rely on today. That is why the first step is a conversation rather than a checkout page.

The one thing it never depends on

How many people use it. There is no charge per person, and no list of paid-for users to keep up to date. Euthyna exists to make every payment decision visible to everyone with a stake in it: investors, lenders, operators, approvers and auditors. Charging per person would put a price on that visibility, so we do not do it.