Salesforce software factory

Salesforce changes,verified and ready to merge

Agents take ready work from Backlog to a reviewed pull request, using what Evidentra knows about your org. Open any task to watch the agent work, and read every change in plain words, whether you're an admin or a developer.

Book a demoSee how it works

Illustration of the Evidentra factory board: a Salesforce task moves from Backlog through Implement and Verify to Done, bouncing back once when a test fails. Open the task to see the agent's session and each change explained.

Make agents work
the way your team does

1.0 Intake

Only ready work gets started

Intake checks each task against five readiness criteria and quotes the task for every one. A ready task gets a Start button. One that isn't gets a question on the issue, and waits.

Readiness · #482Ready 5/5
✓Outcome“Close date can't be in the past for open opportunities”
✓Scope“Opportunity only, all record types”
✓Who's affected“Sales users; admins can bypass”
✓How to check“Saving an open opp dated yesterday fails”
✓ContextConflicts with no existing rule on Opportunity

2.0 Implement

A plan you approve, then a build that knows your org

The builder starts in plan mode and works from Evidentra's record of your setup, requirements and past decisions. Nothing is built until a person approves the plan.

Plan · Validation rule: Opportunity close dateWaiting on you
  1. Add Close_Date_Not_Past to Opportunity, skipping closed stages
  2. Bypass for the Sales_Admin permission set, per the decision on record
  3. Add OpportunityCloseDates, a Flow action that moves the 214 open opps already dated in the past to the end of this month
  4. Update OpportunityTestFactory: two tests create past-dated opps
  5. Open a draft pull request against main
Approve planSend back

3.0 Verify

Checked work, not claimed work

CI runs on the commit the agent pushed, then a reviewer reads the change. The reviewer's verdict has to agree with its own test run. A failure goes back to Implement with the failing check attached.

Implementattempt 1
VerifyApex tests: 2 failed
Implementattempt 2 · failure attached
VerifyCI passed · review agrees
DonePR #217 merged

4.0 Review

Readable by admins, not only developers

Every file the agent touches comes explained. A validation rule reads as the error it shows and when. A permission set reads as who gets what. Apex reads as what it queries, what data it changes and whether a Flow can call it. Developers get the source one click away.

Apex classOpportunityCloseDatesExplainedSource

Moves open opportunities dated in the past to the end of this month, so the new rule doesn't block the next person who edits one. It reads 1 query and writes data 1 time.

·Record accessRespects the user's sharing rules
  • rollForward(…)Callable from Flow as an action
  • Reads OpportunityOpen ones with a close date before today
  • Updates OpportunitySets CloseDate to the end of this month

Built on what
Evidentra knows

The factory doesn't start from a blank repository. It works from the same record your team uses to plan: your Salesforce setup, the requirements behind it and the decisions you've already made. That's what lets an agent change your org without breaking what's already there.

How Evidentra reads your org →
Evidentra
Decision
Guardrail
Signal
Insight
Risk
Change
Theme

Questions about the software factory

What is the Salesforce software factory?

A board where routine Salesforce work moves from a ready task to a verified pull request. Each stage has an automation: intake checks the task is ready, the builder plans and builds, verify runs CI and a review, and Done applies your merge rule. A person approves the plan and steps in wherever the line waits on them.

Do I need to be a developer to use it?

No. Admins write the task, approve the plan and review the result. Every file the agent changes is explained in plain words: a validation rule as the error it shows and when, a permission set as who gets what, Apex as what it reads and changes. The source is there for developers who want it.

What work is it suited to?

Scoped changes with a clear outcome: a validation rule, a field and its layout, a permission set, a failing Apex test, a small flow change. Work that needs a design decision stays with your team, and intake says so rather than starting it.

Where does the work come from?

An issue labelled for a factory line becomes a task in Backlog. You can also create tasks on the board. The tracker stays the source for what the work says; the factory reports back with a status comment on each stage change and the pull request link.

What happens when a check fails?

A failed CI run or a review that asks for changes sends the task back to Implement with the failure attached, and the same agent session picks it up with its plan and history intact. Past the line's attempt limit the task stops and waits for a person instead of looping.

Does it deploy to production?

No. The factory ends at a pull request. Your Done rule decides whether that means review requested, approved or merged, and your existing release process takes it from there.

Can I join a task while it runs?

Yes. Open the card and you're in the agent's session: read the plan, answer a question it asked, or steer the build.

Let agents do the routine work.
Keep the decisions.

Book a demoHow it works