Operating policy

What the subscription is

• Regular admin-sized tasks delivered continuously.
• A single prioritized queue (you control the order).
• Work-in-progress limits to protect speed (1 active task on most tiers; higher tiers may allow 2).

What it is not

• Not an unlimited backlog burn-down.
• Not a replacement for a full-time Salesforce admin.
• Not a vehicle for large redesigns, migrations, or multi-team programs.

Admin scope

Subscription tasks should be small, specific, and bounded.

Typical fits

• Fields, layouts, record types, and small configuration updates.
• Reports and dashboards (new or tweaks).
• Small validation-rule changes.
• Minor changes to existing automation (simple Flow tweaks).
• Permission updates limited to ≤ 2 profiles and/or permission sets.
• Small Experience Cloud / portal configuration tweaks (when applicable).

Guardrails

• ~3 hours or less of hands-on admin work.
• One outcome / one area per request (no bundling).
• Must be testable with clear acceptance criteria.

Intake requirements

To avoid back-and-forth, each request must include:

• Goal (what changes for users)
• Current behavior
• Desired behavior
• Acceptance criteria
• Helpful context (optional): impacted users, deadline, sample records/screenshots

If required details are missing, the request is marked Needs info and does not consume WIP.

When a request is bigger than subscription

If something is not admin-scope, we won't guess. We'll classify it and give you a clear next step:

• Needs discovery: unclear requirements → fixed-price discovery.
• Fixed-price project: larger build → Small / Medium / Large quote.
• Dev time blocks: code/integration required → time blocks with defined deliverables.

Projects are billed separately and only start after your explicit approval.

Delivery, testing, and release

• We prefer sandbox-first when available.
• We document what changed and how to verify it.
• Higher-risk changes require UAT sign-off before production.
• You own business decisions and prioritization; we own implementation quality.

Service levels

• Time to first response: next business day for most tiers (faster on higher tiers).
• Most admin-sized tasks complete within 2–3 business days, depending on complexity and dependencies.
• If a task is blocked waiting on customer input, it leaves WIP until unblocked.

Security & privacy

• Access is limited to what's required to deliver work.
• Credentials are handled via secure methods (never over email).
• We minimize data handling and avoid exports unless required.
• We keep a change log (what changed, when, and why).