Client Guidelines
Getting the most out of our collaboration starts with clear expectations. Here's how I work — and how you can help make every project a success.
Last updated: April 2026
I've worked on 20+ projects over 3+ years and these guidelines reflect what I've learned makes collaborations succeed. They're not bureaucratic rules — they're practical principles that protect your budget, timeline, and the quality of the final product.
1Project Kick-Off
Summary: Setting the right foundation before a single line of code is written.
Share a clear brief outlining your goals, target audience, competitors, and any design references or brand assets.
Define your must-have features vs. nice-to-have features upfront — this keeps the scope clean and your budget in control.
Agree on a realistic timeline together. Rushed timelines affect quality; transparent planning benefits everyone.
Provide all required content (text, images, logos, copy) on time. Content delays are one of the most common causes of project delays.
2Communication
Summary: Clear, timely communication leads to better outcomes — for both of us.
Primary communication happens via email (officialshahzil@gmail.com) or the agreed platform (WhatsApp, Slack, etc.).
I aim to respond to all messages within 24 hours on business days. Please extend the same courtesy.
Consolidate your feedback into single, clear messages rather than multiple fragmented messages — this keeps iterations efficient.
3Approvals & Sign-Off
Summary: Moving forward confidently at each stage of the project.
Each major milestone (wireframes, design mockups, development staging) requires your written approval before proceeding to the next phase.
Approved stages that are later reverted incur additional charges as the work must be redone.
Final delivery includes a handover session where I walk you through the project, platform credentials, and documentation.
A 7-day post-launch support window is included for bug fixes related to the delivered scope — not new features.
4Providing Assets
Summary: The quality of assets you provide directly affects the quality of the outcome.
Provide logos in SVG or high-resolution PNG format (at least 2x). Low-quality assets result in blurry visuals.
Share brand guidelines (colour codes, typography, tone of voice) early in the project.
Images should be high-resolution and properly licensed. I can source stock imagery if needed — just let me know.
Written copy must be final before development starts. Copy changes after development can require layout restructuring.
5Scope Changes
Summary: New ideas are welcome — just understand how they're handled.
Any feature or requirement not in the original project agreement is considered out of scope and will be quoted separately.
Small changes (e.g., tweaking a colour, adjusting text) are typically absorbed within revision rounds.
Significant scope additions (new pages, integrations, additional features) are treated as mini-projects with their own quote and timeline.
Scope creep is one of the leading causes of overrun budgets and delayed launches. Let's keep it in check together.
Ready to Start Your Project?
Let's have a quick discovery call or exchange. The more detail you share upfront, the better I can serve you.