Solutions
Salesforce data management, one job at a time
Between the first lead and the renewal, a record gets created, changed or copied in bulk at about seven moments. Each page below takes one of them: what goes wrong, which apps help, and where a person from our side can step in.
Which job is giving you trouble this week?
Salesforce data management usually lands on one person as a single, shapeless task. Split by the moment the data changes, it becomes seven smaller jobs, and teams usually feel only one or two of them at a time.
| Stage | The job | Apps and where they stand |
|---|---|---|
| Capture | Get data and documents in safely | Portage and Stow, both early access |
| Clean | Make the data true | Sluice and Sextant, early access; Lazarette, pre-release |
| Convert | Get every lead to the right owner and account | Slipway, early access; Bosun, pre-release |
| Engage | Know the account before you call | Muster, Rigging and Pennant, all early access |
| Close and renew | Repeat what works and produce the paper | Sistership and Purser, early access; Purser Sign, a planned Purser feature in design |
| Prove | Know who changed what, and who can | Wake and Telltale, early access; Watchbill, pre-release |
| Ready for agents | Find out if your data can take an AI agent | Sounding, pre-release; Tiller, in design |
How do you decide where to start?
Start where it hurts, not at the top of the table. If the Friday spreadsheet is the problem, open Capture. If the problem is a leadership question about AI, open Ready for agents. Each page has the same shape: the job, the apps, how they hand off, and a person to call when an app isn’t the answer.
If you can’t say which job hurts, start with a number. A Data Health Check takes two weeks and ends with a scorecard, a fix list in priority order and a 90-day plan.
Every app installs by itself, and none needs another. Pick one, run it on your own data, and add a neighbor later if it earns its place.
See it first. Take it back. Keep the receipt.
Every app previews a change before it happens, can undo it where undoing makes sense, and keeps a record of what happened. Where there’s nothing to undo, the page says so. How the promise works.
Where things stand. Twelve apps are in early access with design partners. Bosun, Sounding, Watchbill and Lazarette are pre-release: built and install-tested. Tiller and Purser Sign are designs, and nothing in them is built. None is on AppExchange yet, and each page says exactly how far along its apps are.
Questions people ask
What does Salesforce data management cover?
Everything that creates, changes, copies or removes records in bulk, from the first import to the renewal, plus the evidence that it happened correctly. Here we split it into seven jobs, so you can fix the one that hurts without redesigning the rest.
Do I need to work through the stages in order?
No. They follow a record’s life from capture to renewal, but a team can have a duplicate problem and a perfectly good import. Pick the stage that matches this week’s problem. Each app works alone, and none depends on another.
How do I know which stage to fix first?
Measure. Count duplicates, check how complete your key fields are, and see who owns what. The data health scorecard takes about 20 minutes to run yourself, and a Data Health Check does the full job in two weeks. Then fix the finding that does the damage and is quick to repair.
Start with the job that hurts
Book a Data Health Check, or look at the apps and pick the one that matches this week’s problem.