Maintenance & Support

Clear policies and procedures for ongoing support after your project launches.

Availability

I'm a high‑school student working part‑time. I reply fast Sun–Thu, 09:00–18:00 (North America/Toronto).

Exam weeks may slow me down; I'll be upfront about any delays.

30-Day Warranty (Included)

30 days from project acceptance. I'll fix defects caused by my code that deviate from the approved scope.

Remedy: Fix the issue or provide a reasonable workaround.

What's Covered

Fix defects caused by my code that deviate from approved scope
Security & dependency updates (on request)
Minor fixes/tweaks and small content edits (<15 min)
Light monitoring if I have access; backups if hosting allows
Version upgrades (framework/CMS) when safe

Not Included

New features or redesigns
Content writing, SEO/ads, analytics accuracy
Hosting/third-party outages
Breaking platform changes or end-of-life
Legal/regulatory compliance

How On-Demand Support Works

After the warranty period: on‑demand support only, hourly rate, business hours.

You send a request

Submit your support request with details

I triage quickly

I assess priority and provide initial response

I share an estimate

You receive time/cost estimate for approval

You approve

Confirm you want to proceed with the work

I do the work

Complete the requested changes or fixes

Summary & invoice

Receive work summary and invoice for payment

Billing: Hourly rate set in proposal; 15‑minute minimum; rush work may add a surcharge.

Response Time Targets

Best‑effort targets, not guaranteed SLAs. Actual availability depends on my schedule.

P1

—Critical (Site Down)

Complete outages or critical functionality broken

Acknowledge: ≤1 business dayStart: 1–2 business days

P2

—High (Degraded/Bugs)

Significant issues affecting user experience

Acknowledge: ≤1 business dayStart: 2–3 business days

P3

—Normal (Minor/Edits)

Small fixes, content updates, minor improvements

Acknowledge: Schedule within a weekStart: As scheduled

Client Responsibilities

Provide timely access (repo, hosting, CI/CD, third‑party accounts)
One point of contact and quick approvals
Keep domains/hosting/licenses current; keep backups if you self‑edit

Additional Terms

Third-Party & Upgrades

Third‑party costs are pass‑through
Breaking changes/EOL usually require a paid mini‑project

Billing & Pause

On‑demand work invoiced on completion (or weekly for bigger tasks)
Payment due on receipt; more than 4 days late → work pauses until paid

Project Handover

You own the code after full payment.

On request: brief runbook and one 30‑minute handoff call to help you understand the project structure.

Questions about maintenance?

I'm happy to clarify any part of the support process before we start working together.

Ask me anything