The rules we work by

We tell you when you do not need us.

The first conversation is about what you want to achieve, who is going to use the software, and what those people do today without it. Sometimes that conversation shows that a product you can already buy does the job, or that a simple website is enough where you had an app in mind. When that happens we tell you, even though it means that there is no project for us.

We start with a small first version.

We first build a small version of the product. It is small, but it works and people can use it. Your users try this version, and what they do with it shows what should be built next. You also spend less money before you know whether the idea works.

You know what you get and what it costs before we start.

You receive a written proposal before we start. It states what we will build, what the schedule is, what it costs and what is not included. It also estimates what you will pay to other companies each month to keep the software online. A later extension, or a change during the project, is agreed with you in writing in the same way before we start on it. If the work is going to cost more or take longer than planned, we tell you as soon as we know, and you decide what happens next.

You see the product while we are making it.

You do not have to wait until the end of a project to see what you are paying for. Each time a part of the product is finished, you receive a version that you can open and use yourself, on your own phone or computer. You can ask for changes while they are still easy to make, and the finished product does not come as a surprise.

You deal with the person who does the work.

The person you talk to in the first conversation is the same person who designs your product, builds it and launches it. Your questions go straight to someone who knows the answer, and you do not have to explain the same thing to a second person.

We keep the software simple.

We choose the simplest way that solves a problem properly, and we build with tools that many developers know. Simple software has fewer faults and costs less to maintain. It also means that you are not tied to us, because another developer can take over the work if you ever want that.

Working with us

  • What we need from youA project runs well when there is one person on your side who is able to make decisions, and when you respond within a few days to the versions that we send you. If the software has to connect to something that you already use, we need access to it. We also need you to explain how your business works, because you know that better than we do.
  • What happens after the launchA fault that you report after a delivery, within the period that our general terms set, is repaired without charge. Software also needs attention later, because phones and browsers change and because the people who use the software ask for improvements. That later work is support. The proposal states which support you receive from us after the launch. Support can cover repairing faults, keeping the software working after such changes, and adding new features.

We send you our general terms together with the proposal.

Do you want to have something built?

Send an email to hello@aytebit.com and describe what you need. We reply within one working day.

Contact