Advice first. Then the build — if you want it.
An old system nobody dares to touch. Two systems that should talk and do not. A process that lives in Excel. Before anyone writes code, we look at it with you, write down what we recommend, and hand you a document you own. Whether we build it afterwards is your decision.
A development shop asks you for a specification you cannot write yet. A large consultancy hands you slides and leaves. Either way, the hard questions — what to build, what to keep, what it will cost, in which order — are answered by whoever is loudest in the room, not by anyone who has to live with the result.
We have sat on both sides. Our CTO built the IT of two universities from the inside and wrote the requirements for an SAP rollout as the client. Our CEO spent a decade in regulated manufacturing before founding exbisoft. We advise the way we would want to be advised.
Each one has a fixed duration, a written deliverable, and a clear next step. You own everything we produce and may take it to any supplier, including into a tender. If you build with us afterwards, the fee is credited as stated.
You have a proposal, an estimate, an architecture or a codebase from someone else and want an independent view before you sign or continue.
Leads to: A Requirements Workshop, a Discovery Workshop, a Modernisation Assessment — or nothing. That is fine.
One well-defined initiative — a portal, an integration, a single process — and no written requirements yet.
Leads to: A fixed-price proposal for the initiative, or an upgrade to the Discovery Workshop with the full fee credited.
If you build with us: Full fee credited against a development contract signed within 3 months
A whole system or product. You know the problem, not the solution: no specification, no budget number, no idea whether it is a week or a year.
Leads to: A concrete proposal. The Discovery Workshop is the first phase of our full-lifecycle process, priced and packaged on its own.
If you build with us: Full fee credited against a development contract signed within 3 months
You run a system nobody dares to touch and need to know: keep, wrap or replace — and in which order.
Leads to: An app modernisation engagement, or a tender with our report as the specification.
If you build with us: 50 % of the fee credited against a development contract signed within 3 months
On request, not packaged: tender support (we write the specification and evaluate vendors, and then do not bid) and an outside-architect retainer for companies that want a standing technical counterpart.
Sixty minutes, free, on video. Its only purpose is to say which package fits — or that none does. The second meeting is paid.
Every recommendation we write, we would be willing to implement ourselves. That keeps the advice honest: no architecture we could not deliver, no estimate we would not sign.
Our CTO specified and lived with university systems for over a decade, including writing the requirements for an SAP rollout delivered by someone else. We know what a good specification has to do for you after we leave.
A Discovery Workshop ends with a clickable prototype, not a slide deck. Your management can click through what you are about to commission.
Vendor-neutral, tender-ready, owned by you. Most clients stay with us for the build. None of them has to.
Tell us the problem in a sentence. We will tell you in an hour which package fits — and whether you need one at all.
Book a first conversation
