Bantuva

How it works

Bantuva delivers Salesforce work end to end: you describe the problem, we agree what done means, agents build it in a sandbox, and nothing reaches your production org without your acceptance. Here is the engagement stage by stage.

1

Enquiry

What happens. You describe the work in the contact form. Bantuva reads it, replies, and records your company and you as its contact — every enquiry is answered or closed, never silently dropped.

What you see. A reply, and your enquiry kept on record.

2

Demonstration

What happens. While you are still deciding, a real story taken from your own problem is agreed, built in a sandbox, tested and reviewed — through the same delivery flow a paying client gets.

What you see. The demonstration story — working software to try, not a slide deck — and you say whether it is right.

3

Onboarding

What happens. When the engagement is accepted, you are invited with single sign-on, your project is created, and your development, UAT and production orgs are connected and health-checked.

What you see. The project invitation, and a setup checklist that turns green when every credential is in place.

4

Definition

What happens. Your incoming work — emails or tracker issues — becomes draft stories, and each one is walked through with you and agreed before anything is built.

What you see. The agreed story with its criteria — the problem, the outcome, what is out of scope, the acceptance criteria, the route and the priority.

5

Build and review

What happens. An agent builds the story in one sandboxed job using only your project's own credentials, tests it on your development org, and a Delivery Architect reviews the change before it merges.

What you see. The test evidence and the review findings — measured coverage, and a review that approves the change or names what to change.

6

Acceptance

What happens. The reviewed change is deployed to your UAT org, where you exercise it and accept or reject it; a rejection sends the story back to build.

What you see. The change on your own UAT org, with your acceptance recorded against it — a recorded human decision.

7

Release

What happens. Accepted stories are merged and the release is tagged; production is deployed only after a validate pass, and a failed deploy redeploys the previous release.

What you see. The release notes and the evidence pack — what shipped, with the story, the review and the test evidence behind it.

8

Knowledge

What happens. What the work taught is proposed as knowledge for a person to decide, delivery performance is reviewed, the method is published, and the platform is run from its runbook.

What you see. The audit trail — every write, gate decision and status change is recorded with who made it, person or agent.

The page's source names the journey steps behind each stage — because how we work should be checkable the same way our work is.