A software development process with every step on the record.

Each step ends with something you keep.

1. Call

   Thirty minutes online with the engineer who would build it. We go through how the business runs today, where time or money leaks, and your picture of finished. If the work is not worth doing yet, you hear that before we hang up.

   You get A proposal on its way, a reasoned 'not yet', or a short list of what we still need to price it.

2. Proposal

   The scope lists inclusions and exclusions, and what you provide by which date. Milestones and one total follow from it. You sign in your browser, and each side holds the same signed file.

   You get One fixed total, in a free proposal that binds you only once you sign it.

3. Build

   We deliver milestone by milestone and announce each one in writing. You then have 14 days to test it against the agreed scope, and your client portal shows the project as it moves.

   You get A login to the whole project record from the first day.

4. Launch

   Live on our hosting in Germany, or on your own servers. The new release runs next to the old one and takes traffic once it answers correctly, so a bad release is undone with one command.

   You get A system in production and a proven way back.

5. Warranty

   12 months from acceptance while we host the system, extended by each month the Premium Subscription runs, to a ceiling of 24, and 90 days if you host it yourself. Any defect in our work that surfaces in that time is repaired at no charge. Afterwards you choose Base Platform Care, the Premium Subscription or a clean handover.

   You get The source code for all paid work, whichever you choose.

The schedule assumes three things from you.

A person who can make decisions, access to the systems we connect to, and the content or data we asked for, each by the date in the schedule.

When one of them arrives late, the dates it touches move by the length of the delay, and the contract states it. Either side must report a delay in writing within five business days, so a slip is on record while it is still small.

How is a milestone tested and accepted?

You test it for 14 days against the agreed scope, counted from the day we announce the delivery in writing. It is accepted when you approve it, when the 14 days pass with no material defect reported, or the moment it goes into live use.

A material defect reported in time stops the clock until we fix it and deliver again, and you then have seven business days to re-test. Minor defects do not hold up acceptance. The warranty covers them. Final delivery follows the same rule, and the warranty runs from that acceptance.

A change of scope is priced before it is built.

Each one arrives as a numbered change order that states what changes, what it adds to the fee and how it moves the dates. Work on it waits for your approval, given in writing or in your client portal, and once approved it becomes part of the agreement. Invoices follow the signed schedule and the change orders you approve.

Our own tests run before you test anything.

Each new behaviour arrives with its own test, first shown to fail against the real defect. A money check that cannot run stops the work. Every record is authorised on the route that serves it, and anything that spends, deletes or contacts a customer for the first time waits for a person.

Engineering sets out the rules in full, and the release gate shows what every change has to pass.

Do you charge for a discovery phase?

No. The call and the written proposal are both free. Many studios run a discovery phase or workshop before they quote, and it can last anywhere from a couple of hours to three days. When one call is not enough to write the scope, we name what is missing and ask you for it.