We have no specification yet. Is that a problem?

No. A specification is the output of the first piece of work, not a precondition for it. What we need is read access to what runs today and a person who knows the exceptions. The rest we write down and hand back to you to correct.

Can we start with something small?

That is the rule rather than the exception. The first paid step is bounded: fixed scope, fixed outcome, quoted in writing before anyone starts. Where that cut falls is itself a question, and it is precisely the question the free call answers.

What happens to the system if the engagement ends?

It keeps running, on your side. We build on technologies you can hire for. That is exactly what the list above is for. What your team needs for that is produced during the work rather than as an appendix to it: the code sits in your repositories, along with the operations guide and the architecture decisions.

Aarau · an answer within 48 hours

Custom software development in Switzerland

Business applications, internal platforms, integrations and the reporting that hangs off them. What happens from your first message onwards is set out below step by step, and so is what you keep at the end, even if you do not continue with us.

Describe your project

What we build

Four kinds of work, and they rarely arrive one at a time.

Business web applications and internal platforms

The tool that exists only at your company, because it is shaped like your process. Today it is often a spreadsheet with macros and one person who knows how it works. We build it as an application: with roles, with an audit trail, and with an operational footprint your IT already recognises.

API design, system integration and workflow automation

Two systems hold the same information, and between them sits somebody re-keying it. We build the interface and the flow around it: who approves what and when, what happens on a failure, what is traceable afterwards.

Modernising Java, TypeScript, React and Next.js systems

A system runs, but nobody enjoys changing it. We read it before we say anything about it, and cut the modernisation into steps that can each go live on their own. We do not recommend a full rebuild while the existing system can still be moved in steps.

Data analysis, dashboards and reporting automation

The report somebody assembles by hand from four sources before the meeting. We automate the preparation and put the result where the decision is made. It is part of a build, not a product of its own.

What happens after your first message

1. You send us the process or the system
A few sentences will do: what runs how today, where it jams, which systems have a say. We do not need a requirements document. If you have one, send it along.
2. We answer within 48 hours
With a practical first step, and with the questions we cannot answer before asking them.
3. The call takes 30 minutes and costs nothing
We go through the questions about your project together during it. You do not get a questionnaire as homework.
4. By the end of those 30 minutes your path is named
You hear it in the call, not in an email two weeks later: what the first bounded step would be, and why that one and not another. If the right first step is not one we would carry out, we say that too.

What you keep if you do not continue with us

The path we name at the end of the call is yours. You can implement it internally, put it out to tender, or leave it. We do not invoice for it, and no condition hangs off it.

That is not a courtesy. It is the only way 30 minutes are worth anything to you: afterwards you know more about your own project than before, even if you never hear from us again.

What the engagement includes, and what it explicitly does not

The code	In your repository, under your organisation. We work in it.
The test suite	Automated tests along your business cases, not along the screens. They run in your pipeline and tell you whether the estate is intact long after our last working day.
The operations guide	How the system is deployed, configured and monitored, and how to get back on a failure. Written for somebody who was not there.
The architecture decisions	Short, dated, with the reasoning for why the alternatives lost. This is the document that is missing in two years if nobody wrote it.
Not included: operations and hosting	Both run on your side, unless we agree otherwise.
Not included: a fixed quote before the first look	Before anyone has looked at the process and the estate there is no honest number. Afterwards there is.

The test is simple. Could another firm take over next Monday without calling us? If not, something is missing from the delivery.

How the work runs afterwards

The first engagement is small and bounded in writing. Scope and outcome are settled before anyone starts. We cut it so that it is worth something on its own, even if nothing follows it.
We name no number before we have seen the system. Quoting on the phone means guessing at your estate. That costs us engagements, and we take the loss.
There is nothing here to tie you in. We sell no platform of our own and no licence model. It is built on what your IT already runs: Java and Spring Boot, TypeScript, React and Next.js, a relational database.

When not to ask us

Five cases in which this call gets you nothing. We would rather say them here than in the second meeting.

•You need a binding number before anyone has looked at the estate. Nobody who has not read it can give you one.
•A standard product covers your case, possibly one you already licence. Then building your own is the more expensive answer, and we will say so before you order it.
•Nobody in the business has time to show us the real cases, or an existing system that has to take part stays closed to us. Without both there is no plan we could hold to.
•The decision about what gets built has already been taken internally and wants confirming from outside. We will examine it, and sometimes the examination comes out the other way.
•Somebody has to start next week. If we have no slot we say so in the first call, rather than promising you a date we cannot keep.

If it is about Camunda 7 or about approval workflows

Two cases have their own pages, because they need their own answer. If the process in question runs on Camunda 7 today, start with the Camunda 7 migration. If it is about approvals, deadlines and tasks across several departments, that is BPMN process automation.

Questions that come before the call

We have no specification yet. Is that a problem?: No. A specification is the output of the first piece of work, not a precondition for it.; What we need is read access to what runs today and a person who knows the exceptions. The rest we write down and hand back to you to correct.
Can we start with something small?: That is the rule rather than the exception. The first paid step is bounded: fixed scope, fixed outcome, quoted in writing before anyone starts.; Where that cut falls is itself a question, and it is precisely the question the free call answers.
What happens to the system if the engagement ends?: It keeps running, on your side. We build on technologies you can hire for. That is exactly what the list above is for.; What your team needs for that is produced during the work rather than as an appendix to it: the code sits in your repositories, along with the operations guide and the architecture decisions.

Send us the process that slows you down

A few sentences will do: what runs how today, which systems are involved, what about it is expensive. We answer within 48 hours with a practical first step and propose a time for the 30 minutes. No sales pitch, no obligation, no questionnaire as homework.

Request the free 30-minute call