Warranty, scope, and care-plan policies, published in one place
Warranty
Every fixed-price build includes a 30-day warranty, starting at production launch, covering any bug where the delivered application does not match the accepted requirements. New feature requests made after launch are not covered by this warranty and are quoted separately.
Scope Policy
Requirement Phase
While requirements and wireframes are still being defined, scope changes are free. Nothing is locked in, and nothing is billed as a change, until development starts on a given feature.
Unbuilt Features
A feature that is planned but not yet built can still be changed, reordered, or dropped at no extra cost, as long as development has not started on it yet.
Built and Accepted Features
Once a feature is built and accepted, a request to change how it behaves is treated as new scope. It is estimated and scheduled like any other new piece of work, not folded into the original budget.
New Feature Requests
A request for a feature outside the originally agreed scope is quoted separately as a mini-sprint, with its own timeline, its own deliverables, and its own sign-off, so the original engagement is never quietly stretched.
Care Plans
| Option | Commitment | Best For | What's Included |
|---|---|---|---|
| Essential Care | 3-month plan, 2 hours per month | For a stable application that mainly needs monitoring and occasional updates. |
|
| Standard Care | 6-month plan, 5 hours per month | For an active application that ships small improvements on a regular cadence. |
|
| Premium Care | 12-month plan, 10 hours per month | For a business-critical application that needs priority attention and fast turnaround. |
|
Operational Rules
Inactivity Pause
If a project goes 30 days or more without client input or a response, the engagement is paused. Resuming work after a pause requires a written re-boarding notice of 5 business days, so the project can be properly rescheduled.
Intellectual Property Transfer Gate
Source code, repository access, and production deployment credentials remain the property of the developer until the final payment milestone clears. On receipt of that final payment, full ownership transfers to the client.
Communication Standard
All project communication runs through a single channel agreed at kickoff, whether that is email, a messaging app, or a project management tool, so nothing gets lost across scattered threads.
Working Hours and Out-of-Hours Rate
Standard support runs Sunday-Thursday, 9:00 AM-6:00 PM Egypt Standard Time (UTC+2). Work requested outside those hours is billed at 1.5x the standard rate.
AI Privacy Isolation Guarantee
AI coding assistants operate under local context rules that restrict them to the current workspace. Client source code and client data are never sent to an external provider for model training.
Source code ownership, repository transfer, and production deployment access all transfer to the client on receipt of the final payment. Before that milestone, the developer retains ownership of all deliverables.
These policies took effect on January 1, 2025.