How it works

At a glance

• You keep a single prioritized queue of requests.
• We work on the top “ready” item(s) up to your plan’s WIP limit.
• Most admin-sized tasks complete in 2–3 business days once started.
• If something is project work, we pause and provide fixed-price options.

1) Onboarding

• Access: dedicated user, MFA/SSO rules, and required permissions.
• Environments: confirm sandbox strategy (preferred) and how releases happen.
• Working agreement: WIP limits, approvals/UAT expectations, and a point of contact.

2) Submit requests

Requests must be specific enough to implement safely. We require:

• Goal (what changes for users)
• Current behaviour
• Desired behaviour
• Acceptance criteria (how we know it’s done)
• Examples/screenshots/record IDs when relevant

3) Triage

Every request is classified quickly so work stays predictable:

• Admin scope: queued and delivered under your subscription.
• Needs info: paused until the required details are provided (doesn’t consume WIP).
• Project work: we pause and send a fixed-price Small / Medium / Large quote.
• Needs dev: we recommend dev time blocks or a fixed-price project.

4) Delivery and release

• We pull from the top of your prioritized queue.
• We test in sandbox when available; higher-risk changes require UAT sign-off.
• We document what changed and the basic test steps.

5) When it’s bigger than subscription scope

• We outline scope, options, and assumptions.
• We provide a fixed price (Small / Medium / Large) or dev time blocks.
• Work only starts after you explicitly approve the cost.