White-label Rescue Sprint
Statement of work
One workflow, two weeks, one fixed fee. Bracketed fields are filled in per engagement.
Parties
[Agency] (the Agency) engages Abanoub Rodolf Boctor, who operates ThynkQ, to deliver the work below for the Agency's client, [End client].
Standing terms
- Two weeks, fixed scope.
- The Agency invoices its client.
- NDA signed before scoping.
- No ThynkQ credit unless the Agency wants it.
- Delivery dates are targets, not guarantees. A slip is flagged to the Agency the day it is known, with a new date in writing.
The Agency owns the client relationship, scoping and project management. ThynkQ does not contact the end client.
We accept no more than two concurrent engagements.
Scope
One workflow: [the blocked workflow, in one sentence]. Scope locks within the first 1 to 2 days. Acceptance criteria, access boundaries and the decision owner are written down before work starts: [acceptance criteria].
Deliverables
- Scoped outcome and acceptance criteria
- Implemented workflow or integration
- QA proof and responsive checks where UI is involved
- Deployment or launch-readiness notes
- A written scope the Agency can put in front of its client.
- One weekly status note the Agency can forward as is.
- Code in the end client's repo, not ThynkQ's.
- A handover doc the Agency's team can run from.
Timeline
Start [start date], 2 weeks. 2-week sprint with a mid-point check-in and a final deployment review. The Agency gets one weekly status note it can forward as is.
Out of scope
- A new platform, rebuild, or multi-surface launch
- Open-ended discovery on scope too unclear to fit two weeks
- Ongoing leadership after the workflow ships
Fee and payment
$12,000, one time, for the standard two-week scope. The Agency invoices its client directly. Payment to ThynkQ follows the published terms: 50/50 on everything up to $59,999. The deposit is fully refundable if the Agency cancels before kickoff begins. Once kickoff begins, the deposit is non-refundable. No work starts before the deposit clears.
Ownership
Code goes in the end client's repository, not ThynkQ's. Under the published IP terms, custom code and deliverables transfer on receipt of full payment. The final statement names who receives them: [Agency or End client].