Site arrangements

Each site has an arrangement — a set of per-site fields that govern budget, response commitments, monitoring intensity, and report cadence. Operators set these directly per site. There is no tier abstraction.

The fields

• • retainer_cents — monthly budget amount in cents. Drives the budget period. (Column name predates the budget terminology lock; rename pending.)
• • included_minutes — minutes of work covered by the budget each month.
• • sla_hours — response commitment, in hours. Null means no SLA.
• • monitoring_enabled — whether uptime checks run for this site.
• • scan_frequency — daily, weekly, or none. Drives both health scans and uptime check cadence.
• • agent_poll_frequency — hourly, daily, weekly, or never. How often Field polls the WordPress agent for plugin/core/theme reports.
• • report_cadence — monthly, weekly, or none. Cadence for client-facing health reports.

Convenience presets

The site editor offers three quick-fill presets so you don't have to enter every field from scratch. Each one populates the arrangement, after which you can adjust any field.

Two rates

Work within the monthly budget is priced at $2.50/min (the budget rate). Work beyond the budget is priced at $3.75/min (the overage rate). See settlement for how this flows into invoicing.

Stripe billing

Each site's subscription is created with inline Stripe pricing tied to a shared “Field — Monthly Retainer” product (the literal Stripe product name, kept as-is for billing continuity). The line-item amount comes directly from the site's retainer_cents. Changing a budget updates the next billing cycle — the current period stays at its locked-in amount.