How we work
Know what happens after your enquiry
The principle is the same for mobile apps and websites: first we understand the task, then we record the solution we can commit to. Development does not begin with a vague feature list.
1. We understand your goal
We review who the solution is for, what happens today and what should work more simply. The project planner or short enquiry provides a starting point for discussion, not a finished specification.
2. We define the first version
We select the pages, screens and actions required. We separate essential launch requirements from ideas for later. We assess the state of the content and system connections.
3. We put the proposal in writing
We assign a price, schedule, client responsibilities and acceptance criteria to the development scope. We do not leave exclusions, third-party service costs or handover contents until the end.
4. We build and demonstrate the solution
The approved plan becomes working components. We ask for feedback at agreed points and distinguish change requests from the original commitment. When a new requirement arises, we clarify its impact too.
5. We check the whole process
We do more than check whether a button can be clicked. We assess data entry, permissions, system connections, feedback and error situations against the acceptance criteria. For websites, mobile use, content and indexing settings are also part of the handover.
6. We hand over and clarify operation
At handover, we provide the code, access and documentation specified in the proposal. We assign responsibilities for launch, app store publication, third-party licences and maintenance separately. Completion of development does not replace approval by an external platform.
How can you help?
Have a contact person authorised to make decisions, relevant professional material available and an appropriate way to access the necessary systems. We do not ask for actual login credentials through the public form.