Service levels, revisions, and future incentives
After an automation is accepted and in production, the contractor is responsible for maintenance and edit requests.
If SLA drops below 90% in any calendar month, all per-automation bonuses for that month are reduced by 20%.
Example: 4 standard + 2 lite automations ($1,400 in bonuses) at 85% SLA → $1,400 × 0.80 = $1,120. Total comp: $2,120 instead of $2,400.
Important: The base retainer is never affected by SLA performance. Only per-build and incentive bonuses are reduced.
By timestamp of submission and resolution
Communicated via agreed channel (Slack, email, PM tool)
Fix deployed and contractor confirms completion
(Requests resolved within 24h / total requests) × 100
On the 1st of each month
Clear briefs produce clean builds.
One revision round included per build at no additional cost
If the revision addresses a gap in the original brief (something Leo failed to specify), it does not count as a revision
Additional revision rounds count as maintenance requests — governed by SLA (must resolve within 24h)
Fixes required to pass the acceptance checklist are completion, not revisions — they don't count
Additional incentive tiers may be introduced after the initial engagement period, based on operational data and mutual agreement. Potential future incentives include efficiency bonuses, reliability bonuses for uptime streaks, and expanded scope bonuses.