Engagement model

This page describes how we structure scoped project engagements and advisory sessions for database performance and migration programming — the same model referenced in our supplier disclosure on the home page.

Intake and confidentiality

You share workload context, compliance constraints, and access boundaries. We respond with clarifying questions within two business days (Malaysia time). Mutual NDA language is available in our terms if your policies require it before log access.

Statement of work

Accepted engagements receive a statement of work listing:

Objectives tied to measurable outcomes (for example p95 latency on named endpoints, or successful rehearsal of a cutover script).
Environments we may access and the read-only period before any write.
Deliverable format (memos, pull requests, migration files).
Fees in MYR, payment milestones, and estimated calendar duration.

Nothing starts until the statement of work is signed and any deposit invoice is settled per the payment section in terms.

Execution rhythm

Weekly written checkpoints summarise findings, risks, and next experiments. Pairing sessions use screen share; we do not exfiltrate production data to personal devices. Code lands in your repositories unless otherwise agreed.

Advisory-only path

Some clients purchase a pack of advisory hours without implementation. Hours expire six months after purchase unless extended in writing. Unused hours are non-refundable once the pack is opened, as described in our refund policy.

Closing an engagement

Handover includes open questions, monitoring suggestions, and ownership map for each script. Optional follow-up office hours can be quoted separately.