Apliko
Together we build a better Internet
New collaboration standards that will make your project faster, smoother, and of the highest quality.
Why do we introduce standards?
A great website is the result of synergy between your vision and my technical skills. To avoid delays and misunderstandings, I have prepared this short guide. These are simple rules that protect your time and budget.
1. Communication in one place
We eliminate the chaos (Messenger, WhatsApp, SMS). Arrangements communicated through multiple channels often get lost.
New rule:
We conduct all project communication exclusively via Email or the Ilaro platform. This way, nothing escapes us.
2. Working hours and availability
Programming requires focus, and high quality requires a rested mind. That's why I work within fixed time frames.
New rule:
I am available from Monday to Friday. The guaranteed response time to messages is 2 business days. Weekends are a time to recharge, so that on Monday I can return to your project with full energy.
3. Complete set of materials to start
Working in "installments" (sending photos and texts while coding is in progress) extends the website creation process up to twice as long and generates layout errors.
New rule:
I start programming work only after receiving a complete set of materials (texts, logo, photos). If something is missing, we use "placeholders", and you can fill in the content yourself in the CMS after the website is delivered.
4. Respecting deadlines
I reserve time in my calendar specifically for your project. Delays in providing information block this time.
New rule:
Lack of response or materials for more than 3 business days will result in the project being "frozen". Work will resume on the first available date, which may mean postponing the website delivery by a few weeks.
5. Estimating stages and budget control
IT projects often live and evolve for years. To maintain financial transparency over such a long period, we avoid open budgets.
New rule:
Every stage of work (e.g., a new module, another month of development, a sprint) is estimated and approved separately before starting. Thanks to this, even with long-term cooperation, you have full control over costs and consciously decide to initiate the next tranche of work.
6. Pre-deployment testing
Verifying changes directly on the live website (production) is risky for your brand image and the stability of the service.
New rule:
You will receive a link to the test version (staging) from me. That's where you can check the website's functionality and provide feedback. We only move to the official version (target domain) when everything has been checked and approved by you in the test environment.
7. Full transparency on work status
No more constantly asking "is it done yet?". I respect your time and peace of mind, which is why I prioritize complete transparency in the process.
New rule:
You receive an automatic notification (email/messenger) the moment a new version lands on the test or production server. Additionally, you have constant insight into the status of individual tasks, so you always know what is ready to be checked and what I am still working on.
8. Scope stability (Scope Freeze)
Throwing in new ideas while work is in progress ("since we're already here, let's add this too") is the most common cause of project delays.
New rule:
During an ongoing stage, we do not introduce new changes or functionalities. The only exceptions are bug fixes. All new ideas that come to your mind are added to a "to-do" list and implemented in the next, separate stage.
9. Professional QA testing (as standard)
I believe that high quality should be the standard, not a luxury add-on. That's why professional QA tests are included in every estimate by default.
Budget-friendly option:
The cost of testing usually accounts for about 10-20% of the stage value. If your budget is very tight, you can opt out of them before work begins. This will lower the invoice, but remember – the responsibility of thoroughly "clicking through" the website and catching any minor bugs will then rest more heavily on you.
What do you gain from these rules?
Faster execution
The website is built on time, without unnecessary downtime.
Higher quality
I can focus on coding and design, rather than managing chaos in emails.
Peace of mind
A clear process ensures you know exactly what stage we are at.