Once the build is running, our progress depends on a small number of things arriving from your side on time. Here is the complete list.
Timely responses
Most questions we ask are blocking, meaning work stops until you answer. We keep them short and specific for that reason. A same day or next working day reply keeps the project on its schedule.
Content on the agreed dates
The content checklist from kickoff has dates against each item. If an item is going to be late, tell us in advance so we can reorder the work rather than sit idle. Late content is the most common cause of a missed launch date.
Consolidated feedback
One reply per review round, agreed internally before it is sent. Conflicting feedback from different people forces us to stop and ask who decides.
Access and credentials
- Domain registrar access or a contact who can update DNS records.
- Existing hosting or cPanel details when we are working on a live site.
- Accounts for any third party service we need to connect.
Share credentials through the portal at crm.zylax.com.my rather than plain email or chat, and change any shared password after the project ends.
Testing on your side
When staging is handed over, someone from your team needs to actually use it. Fill in the forms, click through the checkout, read the pages on a phone. You know your business processes better than we do and you will catch things a developer would not think to try.
Payments on schedule
Milestone invoices are tied to stages of work. An unpaid milestone invoice pauses the next stage, which pushes every date after it.
Decisions
Some questions have no perfect answer and simply need a choice made. Where we have a recommendation we will give it, so you can approve rather than deliberate.
If you are going to be away or unreachable, nominate a stand in and tell us. Reply to your email thread or write to [email protected].
