Submit the work request
Customers raise changes, fixes or feature ideas through the portal with files, context, priority and target environment attached.
A faster, clearer way to get Salesforce work done: raised in one place, delivered against the right environment, and ready for your approval with the testing already done.
You ask for the work and approve the release. We handle the delivery in between, and you can see exactly where it is the whole way through.

Portal request
Customer describes the work and target environment.
Delivery route
Kitsune turns the request into the right delivery path.
Sandbox delivery
Work starts where it can be tested safely.
Evidence and approval
Release decisions stay controlled and auditable.
Work starts sooner
Requests turn into action quickly, so simple Salesforce changes do not sit waiting for a slot.
Lands with confidence
Every change is tested and evidenced before it is put in front of you to approve.
Spend stays predictable
Progress is tracked against your retainer or delivery budget, with no surprise effort.
A clean delivery interface: requests, progress, evidence, approvals and budget position.
Behind the clean interface, the orchestra does the heavy lifting so Salesforce work moves faster and lands with more confidence.
The orchestra shortens the gap between a customer asking for work and Kitsune starting the right delivery work, while keeping sandbox boundaries and approval gates clear.
Customers raise changes, fixes or feature ideas through the portal with files, context, priority and target environment attached.
The request is linked to the customer project, Salesforce org details, sandbox lane and any existing delivery rules.
Kitsune turns the request into a clear path: triage, build, checks, review and handover.
Work begins in the right branch or sandbox context, with scope checks and a clear rollback plan from the start.
Automated checks, review notes, screenshots, logs and acceptance evidence are gathered before anything is promoted.
Humans keep control of production decisions while the orchestra handles the repeatable delivery work around them.
The aim is not automation for its own sake. It is dependable Salesforce delivery, kept inside safe environments, with the decisions that matter staying firmly with people.
Work is prepared and tested in sandboxes, never directly in production.
Commercial judgement, client approval and production release decisions stay with people.
Requests, changes, tests and evidence are tied back to the project record.
Org access, portal permissions and environment links are kept narrow and auditable.
Clients should know what they can request, how quickly work can start, how it is tested and where they approve it. The point is less admin around delivery, not another process to manage.
Send the sandbox, portal and approval context you already have. We will map the intake route, test evidence and human sign-off points before any automated delivery lane is switched on.