Run Salesforce with a small team.

Agents that answer questions about your org, make changes, and keep it healthy. Every change is approved by a person and recorded.For companies without a big Salesforce team.

Talk to us about OrgSmith

Salesforce needs more care than most teams can give it

Every request becomes a ticket for an admin who's already busy. Questions about the org go unanswered because nobody remembers how it was built. OrgSmith gives a small team an agent team of its own, under the rules you set.

How it works

1Ask
2Plan
3Build in a sandbox
4Approve
5Deploy
6Record

What it does

Ask about your org

Plain-language answers about your objects, fields, flows, reports and data, with the sources they came from.

Change it safely

Describe the change. Agents plan it, build it in a sandbox, test it, and wait for an approver before production.

Keep it healthy

Routine admin, data hygiene and monitoring, with problems explained in plain words.

Approvals and audit

Second-person approval for anything that matters, and a full record of who asked, who approved and what changed.

The agent team

7 agents, one job each

Each agent has a clear role, the way a good delivery team does. They hand work to each other, and to you for review.

Orchestrator

Takes the request, plans the work and coordinates the other agents.

Business analyst

Works out what's being asked and what it affects in the business.

Product owner

Shapes the request into stories with acceptance criteria.

UI/UX

Designs the screens, layouts and fields people will use.

Architect

Decides how the change fits your org: objects, automation, sharing and limits.

Developer

Builds the change in a sandbox.

QA

Tests the change against the acceptance criteria before anyone is asked to approve it.

People stay in charge

Everyone has a role on each org. Each role includes everything the one before it can do.

Role	Can
Contributor	Ask questions about the org, request changes and have them built in sandboxes.
Approver	Everything a Contributor can, plus approve other people’s requests on that org.
Admin	Everything an Approver can, plus manage the org’s connection and members’ roles on it.
Owner	Admin on every org in the account, invites and removes people, and can approve when no one else can, after confirming identity.

Built to be safe

Sandboxes first

Agents build and test in sandboxes. Production is never the first place a change appears.

Second-person approval

Changes are approved by someone other than the person who asked, with the right role on that org.

Roles per org

Someone can be an Admin on one org and a Contributor on another. Raising someone's role needs approval.

A full record

Who asked, what the agents planned and built, who approved it, and what changed.

Changes are planned and built by StoryWright, the delivery engine inside OrgSmith. About StoryWright

Is it a fit?

A good fit for

Companies with a small Salesforce team, or none in-house
Teams with a long backlog of small changes
Orgs that have grown for years and are hard to understand
Companies that need approvals and an audit trail

Not the right fit for

Teams who want agents to change production without review
Large programmes that need a full delivery team; that's our Delivery service

Questions

Can OrgSmith manage more than one org?

Yes. An account can connect several orgs, and each person's role is set per org.

What if the person who asked is the only one who can approve?

The account owner can approve when no one else can, after confirming their identity, and that approval is recorded.

How does it connect to our org, and what data leaves it?

Talk to us. We'll take your admin and security teams through how the connection works before you connect anything.

Interested in OrgSmith?

Tell us about your org and team. We'll show you what it can do and how to get it.

Ask for a demo