Built with you

Tell us what you need. We build it.

Q: If it helps everyone, will Rutba build it?

We build it into the product. No extra charge. Most of what customers ask for is something other customers also want and we had not thought of. That is not a bespoke job — it is the product being finished, and you are the reason it got finished.

Q: If it is specific to your business, will Rutba build it?

We build it for you, as an extension. Quoted as a project. Every business has something nobody else does — a pricing rule, a compliance form, a device on the shop floor, a way of working that predates the software. That is real work and it is priced as real work.

Not a slogan — a commercial arrangement with terms. Most of what customers ask for goes into the product at no extra charge, because it turns out other customers wanted it too. What is specific to your business gets built for you, quoted as the work it is. And when the answer is no, you get the reason.

Tell us what is missing What we will not do

An aluminium plate clamped on a CNC bed with freshly cut channels and holes

It is a button, not a promise

The request starts in the app, from the screen where the problem is.

Every Rutba app carries the control in its toolbar. What you send travels with the page you were on, the app and engine version and any recent errors — so nobody has to ask you to reproduce it — and none of that appears in public.

A board shared across customers

You can see what other Rutba customers have asked for and add your weight to it — with no company or email attached to any request, only a display name. A shared queue tells you whether you are one voice or twenty, which a private ticket system structurally cannot.

Reporting a bug shows the matches first

The dialog opens on the board rather than a blank form. Finding that somebody already reported it, with eleven votes and a status of In progress, is the best outcome a bug report can have for everyone involved.

The answer comes back where you will read it

Status changes on your own requests land in the updates strip on the app dashboard you already open, beside what shipped and what maintenance is planned. A reply nobody sees is not a reply.

How the loop is built, including where it stops →

What actually happens next

One request, four answers, three different prices.

Vendors say “we will build it” without ever saying which of these they mean, which is exactly why nobody believes the sentence. Here are all four, including the one that is a refusal.

If it helps everyone

We build it into the product.

No extra charge

Most of what customers ask for is something other customers also want and we had not thought of. That is not a bespoke job — it is the product being finished, and you are the reason it got finished.

Post it on the feedback board, where every customer can see it and vote. Nothing is filed into a queue nobody reads.
A person answers, by name, and says whether we are going to do it — including when the answer is no, and why.
When it ships you get it on your existing plan. You are not upsold your own idea.
It appears in the changelog with the release, publicly.

If you need it sooner than our queue

Sponsor it and it moves up.

Quoted, and cheaper than bespoke

Sometimes the thing is on the list and the list is long. You can pay to move it, and what you are buying is position rather than ownership — it stays part of the product, everyone gets it, and it costs less for exactly that reason.

We quote the work and a window before you commit to anything.
It ships as part of the product, on the normal release path, maintained by us forever.
Because other customers benefit, the price reflects that. You are subsidising the roadmap, not funding a private build.
If we would have built it in the same quarter anyway, we say so and do not take the money.

If it is specific to your business

We build it for you, as an extension.

Quoted as a project

Every business has something nobody else does — a pricing rule, a compliance form, a device on the shop floor, a way of working that predates the software. That is real work and it is priced as real work.

Built on the same extension seams the products themselves use, so it survives upgrades rather than breaking on the next release.
Scoped and quoted in writing, with the parts we are unsure about named as unsure rather than padded.
You own the specification and the data. We will not resell what you paid for as a feature without asking you.
If we think you would be better served by a configuration change, or by a different product entirely, we will say that instead of quoting.

The limits

What we will not do, so the rest of this page means something.

Any vendor can promise to build whatever you ask. The ones worth believing are the ones who will tell you where that stops.

We will not make the product worse for everyone else

A request that would complicate the software for the other customers gets built as an extension for you rather than into the core — or gets declined with the reason.

We will not promise a date we cannot hold

You get a window and the things that would move it, not a date chosen to close a deal. If it slips you hear it from us before you notice.

We will not charge for something we were building anyway

If your request is already scheduled, we say so and you wait for the release like everyone else — at no cost.

We will tell you when we are the wrong answer

Including when the honest recommendation is a competitor. There are comparison pages on this site that say exactly that, by name.

Flexibility

A vendor that will change the software but not the contract has not made you an offer.

Every one of these is checkable — against the product, or against the terms of service. That was the test each had to pass to be on this list.

Start with one product

Nothing forces you to take the family. Most people start with the one thing that hurts, and adding another later is a subscription change rather than a migration.

Change or cancel any product on its own

Cancelling one leaves the rest running untouched, and standard plans have no minimum term.

Your data leaves whenever you want it to

Export at any time while you are a customer, and for 30 days after you stop. We do not charge you to leave and we do not hold data hostage to a renewal.

Run it on your own hardware where the product supports it

Rutba Vision runs entirely on your own infrastructure and only checks its licence with us. Dedicated single-tenant infrastructure is available for the hosted products on Enterprise plans.

Your domain, your branding, your identity provider

Business email at your own domain, customer-facing surfaces under your brand, and federation to your own identity provider where you have one.

A quote, not an estimate

What you are charged is confirmed in writing before anything bills. Where we cannot price something we name it rather than guessing at it.

After you buy

The half of “flexible” that most vendors quietly drop.

Being easy to buy from is not the same as being easy to live with. This is the second half.

A person answers

Support is people who can read the code. There is no deflection wall in front of them and no tier you have to buy to reach one.

Your request is public, and voted on

The feedback board is shared across customers. You can see what others asked for, add your weight to it, and watch it move — rather than posting into a form and hearing nothing.

We answer with a decision, including no

A request gets a real answer with a reason. Silence is the failure mode we built the board to prevent.

You hear about changes before they happen

Thirty days before anything you depend on is removed, and thirty days before a price change reaches your subscription. Both are in the terms of service rather than in a blog post.

Early customers get more of us, not less

While we are small, the people building the product are the people you talk to. That will not scale forever and it is genuinely true now.

Why we can offer this and they cannot

It is a fact about our size, not about our character.

An incumbent with a hundred thousand customers cannot build what you ask for, and it is not because they do not care. A change that suits you has to be evaluated against every other customer it touches, scheduled behind a roadmap set a year out, and shipped through a release process built for that scale. Your request is a rounding error in their planning, and honestly so.

We are small, and the people building the product are the people you talk to. That is worth something specific right now — and it is worth saying plainly that it will not scale forever. If it matters to you, being an early customer is when it is true.

One thing this page cannot show you yet: A list of the things we built because customers asked. We are new enough that it would be a short list and we are not going to pad it. What we ship publicly appears in the changelog, dated, and the requests themselves are on the feedback board where you can watch them move.

So — what is missing?

Tell us what your business does that the software will not let you do. You will get a real answer with a reason, and a price only if there needs to be one.

Tell us what you need Start from your situation