How does a software project with ayonto work?

You don't need a finished specification

It helps if you can briefly describe four points:

• Goal: Which problem should the software solve, and how will you know it's solved?
• Users: Who works with it – customers, employees, both? In the browser, on the phone or both?
• Existing setup: Which systems, spreadsheets or processes exist today that need to be connected?
• Constraints: Is there a deadline, a budget or requirements (e.g. data protection, accessibility)?

Then write to us via the contact form or request a callback. Tassilo and Ricardo will get back to you personally and arrange a no-obligation initial call. In it, we listen and ask questions before telling you openly how we can help. If we're not the right people, we tell you that, too.

Five steps from the initial call to running operations

1. 1
   Initial call

   A no-obligation first meeting. We listen, ask questions and tell you openly whether and how we can help.

2. 2
   Quote

   With a fixed scope: what's included and what isn't. You review it at your own pace and decide.

3. 3
   Project start

   With your go-ahead, you get a list of the input we need and your project space in the Ayonto Drive.

4. 4
   Implementation

   In sprints with regular demos on the running system. You give feedback and approvals.

5. 5
   Launch and operations

   We take the software live and into the stores and run it afterwards.

How long the implementation takes depends on the scope. An MVP of a single platform can be ready in 4–8 weeks; a complete product with a web app, iOS and Android usually takes 4–9 months. We count from the go-ahead: pauses before that, for decisions or legal questions, for example, are part of it and don't count as project time.

We collect input in one list and in the Ayonto Drive

Some things only the client can provide: access, content, images, company details, approvals. So that this doesn't get scattered across individual messages, every project gets a list at the start. In a shop project this fall, it was 38 items in 7 areas, from brand and design through product and legal to shipping and domain.

Not everything has to be there at once. Upload what already exists right away, and both sides see what's still missing. You don't need finished texts; bullet points are enough. Statements that need legal review are only used in the version you have approved.

Everything goes into the Ayonto Drive, our own project space for clients, in use since October 2026. You sign in with a link from an email, without a password, and invite colleagues yourself. Every delivery lands in its own dated folder, including large files up to 50 GB, and an interrupted upload resumes. We get notified as soon as something has arrived.

Instead of a black box, you see the running system

In the concept phase, we clarify the platform, apps, interfaces and milestones with you, for example whether a web app will do or native apps are needed.

Development happens in sprints with regular demos instead of a black box. Tassilo and Marc do the development, and your point of contact stays the same. What this looks like is shown by our own products, such as BKF Manager or Tactio. After the launch, we handle hosting, backups, updates and monitoring; Marc is responsible. More on this under Operations & hosting.

What we take away

Effective time is what counts. Counting the schedule from the go-ahead and naming the input needed from the start gives both sides numbers they can rely on.

One list replaces many messages. When we ask for everything at once at the start and collect it in one place, both sides see what's missing, and nothing gets lost in a chat history.

No break between the steps. Whoever helped write the concept also develops, and whoever develops runs the software afterwards. How we run software is described in the guide SaaS hosting in Germany: data protection, backups, monitoring.