# Who to hire for Apromore Apromore is process mining, so the person you hire is part data engineer, part analyst and part change lead. Here is what to test for before you sign. **Published:** 2026-07-03 **Canonical:** https://synconai.com/hire-apromore-salesforce-partner **Author:** SynconAI Architecture Team ## In short Hire an Apromore partner for event-log engineering and process analysis first, and Salesforce configuration second. Salesforce completed the acquisition on 3 November 2025. Look for someone who can extract a clean case, activity and timestamp log from your org, read the result with your operations team, and recommend a change before anything is rebuilt. ## Sources - **Salesforce Signs Definitive Agreement to Acquire Apromore** (retrieved 2025-11-03) https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-apromore/ > Salesforce completed its acquisition of Apromore on November 3, 2025. - **Salesforce Signs Definitive Agreement to Acquire Apromore** (retrieved 2025-11-03) https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-apromore/ > Apromore provides a comprehensive view of business processes across all systems and applications, including Salesforce and other critical enterprise business systems, reducing operational blind spots. - **Process Intelligence - Business Process Optimization | Apromore** (retrieved 2026-10-13) https://apromore.com/product/ > Our Integration Center provides integration capabilities to connect with a variety of client systems in order to extract, transform it into event logs and load these into Apromore. ## What to take away - The core skill is turning Salesforce history and other system data into an event log with a case, an activity and a timestamp. Configuration experience alone does not cover it. - Ask for a Business Analyst or Platform Data Architect certified person next to the process analyst, and check who actually runs the extraction. - A sound first engagement is one process, one question and one decision. Mining every process at once produces maps nobody acts on. - If your process lives in one org and the question is simple, a capable admin with Salesforce reports may answer it without a partner. ## The guide Most buyers meet Apromore as a diagram: boxes and arrows showing how work really moves, with thick lines where cases pile up. It is a persuasive picture, and it hides the part that decides whether the project works. Someone has to build the table underneath it. Salesforce completed the acquisition on 3 November 2025, and the announcement describes the capability as process intelligence that gives a view of how processes run across systems. This guide is about hiring the people who build that table, and the people who can tell you what it means once it exists. ## What the work really is Process mining starts from an event log. Each row records that something happened to a case at a point in time: this Case was opened, then reassigned, then escalated, then closed. Three columns carry the weight, namely a case identifier, an activity name and a timestamp, and everything else is context such as the person, the queue or the product. Apromore describes its own route to that table plainly: "Our Integration Center provides integration capabilities to connect with a variety of client systems in order to extract, transform it into event logs and load these into Apromore." That sentence is the job description. A partner is extracting, transforming and loading. Calling that a Salesforce implementation undersells it, and hiring for it as if it were a Salesforce implementation is how projects stall. Salesforce adds its own wrinkle. The history you need is scattered. Standard history objects hold some status changes, field history tracking holds others only if someone switched it on for those fields, and a good deal of real work, such as emails, calls and Slack messages, leaves no change record at all. An experienced partner will tell you in the first conversation which of your steps are visible and which are not. If every step looks visible to them, they have not looked at your org yet. The announcement frames the wider ambition: "Apromore provides a comprehensive view of business processes across all systems and applications, including Salesforce and other critical enterprise business systems, reducing operational blind spots." Read it as a statement about breadth. Your process probably crosses an ERP, a ticketing tool or a spreadsheet, and the case identifier that links those systems rarely exists on its own. Building it is the hardest single task on most projects, and it should be priced and staffed as a task, not assumed. ## Skills and certifications that matter You are assembling a small team rather than finding one hero, so name the roles and ask who fills each. The data engineer is the person who builds the log. Look for SOQL fluency, experience with the Bulk API and the history objects, and some history of joining Salesforce data to a second system on a shared key. There is no Apromore-specific Salesforce certification, so do not accept a logo wall as a proxy. Ask for the Salesforce Certified Platform Data Architect if the work involves large volumes or messy keys, and ask what the person has built that was not a Salesforce report. The process analyst is the person who reads the map. The relevant Salesforce credential is the Salesforce Certified Business Analyst, which tests requirements and process thinking inside the Salesforce context. More telling than the badge is whether they can explain the difference between a variant that is wrong and a variant that is merely rare, because mining tools surface both and only your operations team can tell them apart. The Salesforce builder is the person who changes the org once a decision is made. Salesforce Certified Platform Administrator and Platform App Builder cover the configuration side, and Platform Developer is relevant if the fix is an Apex trigger or a Lightning component rather than a Flow. If the outcome you want is an agent that handles a stage automatically, add Salesforce Certified Agentforce Specialist to the list, and treat it as a later hire, not a first one. The Trailhead pages for each of these list exactly what the exam covers, and your own technical lead can read them in an afternoon. The point is not to demand every credential. It is to know which role each credential stands for, so that a proposal can be checked against the roles. ## A first engagement worth buying Scope one process and one question. For example: why do some Cases bounce between queues three or more times before anyone resolves them? That is a question with a measurable symptom, a clear owner and a natural case identifier. A question such as "where are our inefficiencies?" has none of those, and it produces a map where everything looks slightly inefficient. A sensible shape has four stages. First, an extraction workshop in which the partner and your Salesforce owner agree which objects hold the case, which fields hold the activities, and what history is missing. Second, a first log and a data-quality read-out: how many cases, what date range, what share of cases have a recognisable start and end, and which timestamps look wrong. Third, an analysis session with the people who do the work, who will correct the partner's assumptions in the first ten minutes. Fourth, a decision memo that recommends a change, names the metric it should move, and says how you will know within a quarter whether it did. Notice what is absent: a migration, a rebuild, and a new automation. The announcement says the technology is meant to accelerate Agentforce and automation strategy by mapping processes. That is the order of events. You map, then you decide, then you change. A partner who proposes the change in the first proposal has skipped the evidence. ## Red flags specific to Apromore Watch for a partner who treats the project as a dashboard build. A process map that nobody can trace to rows in a log is a drawing. Ask to see a case on the map traced back to its source records, and ask how long that trace takes. If it cannot be done live, the lineage was never built. Watch for scope that starts with every process. Mining thrives on a narrow question and suffers from breadth, because each new process brings its own case identifier, its own data quality problems and its own set of people who must validate the result. Watch for a plan that migrates records to make the discovered path the official path. A discovered path is a finding. It might show a workaround that is actually safer than the documented route. Moving records to match a picture is a separate decision with its own risks, and the picture should not make it. Watch for silence about privacy. An event log often carries the names of employees and customers. In Australia, personal information in that log is covered by the Privacy Act 1988, and task-level data about staff raises workplace questions as well. A partner should raise this before you do. Watch for vague answers about time. Salesforce field history is retained for a limited period, and if a field was never tracked there is no past to mine. A partner who promises two years of history for a field that was only recently tracked is guessing. ## Ten questions to ask 1. Which three columns will define our event log, and what in our org fills each one? 2. Which of our process steps leave no record in Salesforce, and how will we see them? 3. How will you build a case identifier that links Salesforce to the second system? 4. What share of cases do you expect to have a clean start and end, and how will you report the rest? 5. Who runs the extraction, what is their experience with the history objects and the Bulk API, and are they on the project every week? 6. Show a case on a map and trace it to the underlying rows. 7. How do you separate a rare but legitimate variant from an error? 8. Which employees will see task-level data, and what do you recommend we tell them beforehand? 9. What decision will the first engagement end with, and what would make you recommend doing nothing? 10. What will you refuse to do in this engagement, for example migrating records or building automations? ## Checking references and evidence Ask for a reference that describes the log, not the logo. The useful conversation with a previous client covers how long the extraction took against what was planned, what data turned out to be missing, whether the operations team accepted the findings, and whether a change was made because of them. A reference that can only say the dashboards looked good has told you nothing about outcomes. Ask for a redacted sample of the data-quality read-out from a previous project. A partner who has done this work has one. It will show row counts, date ranges, a share of incomplete cases and a list of fixes, and its existence tells you the habit is real. Ask for the decision memo from a past engagement with the client name removed. The memo shows whether the partner ends with a recommendation or with a gallery of charts. ## Commercial models and the statement of work Three models are common. A fixed-scope discovery works well for the first engagement because the deliverable is a log, a read-out and a memo. A time-and-materials arrangement suits the extraction work if you cap it and review at a set point, since data problems are the main source of overrun. A subscription for the platform itself is separate and belongs with the vendor. Keep the licence conversation apart from the services quote, and see [what a licence conversation involves](/apromore-salesforce-licence-cost) when you reach it. Whatever the model, put these items in the statement of work: the named process and question, the systems in scope, the date range of history, the definition of a case, the data-quality measures to be reported, who owns the extracted data and where it is stored, the people who may see employee-level detail, the deliverables, and an explicit statement of what is out of scope. Add an acceptance test: the partner traces three cases from the map to source rows in front of your team. On cost, [the implementation cost page](/apromore-salesforce-implementation-cost) explains what drives a quote and does not invent a figure, and you should insist your own quotes show the extraction effort as a separate line from analysis. ## When you can skip a partner If the question concerns one object in one org, such as how long Opportunities sit in each stage, you may not need process mining at all. A good administrator can answer it with Opportunity history and a report, and in some cases with a Tableau or CRM Analytics view. The same is true if you do not yet know the question. Spend a week with the people who do the work and write the question down. If you cannot, a partner will fill the gap with a favourite, and you will pay for their preference. A partner earns their place when the process crosses systems, the history is incomplete, or the findings will challenge people who are not inclined to believe a map. For related questions see [what happened to Apromore](/what-happened-to-apromore), [integrating Apromore with Salesforce](/integrating-apromore-with-salesforce), [should I migrate from Apromore](/should-i-migrate-from-apromore) and [process intelligence for Salesforce](/apromore-process-intelligence-salesforce). The acquisition itself is described in the [Salesforce announcement](https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-apromore/), and the exam outlines are on [Trailhead](https://trailhead.salesforce.com/credentials/businessanalyst). | Role | What to check | Evidence to ask for | | --- | --- | --- | | Data engineer | Builds the event log from history objects and a second system | A past log specification and a data-quality read-out | | Process analyst | Reads variants with your operations team | A decision memo with a named metric | | Salesforce builder | Makes the change once a decision exists | Platform Administrator, App Builder or Developer certification as relevant | | Engagement lead | Keeps one question and says no to scope growth | A written out-of-scope list from a previous statement of work | ## Questions ### What should I look for when hiring an Apromore partner? Look for event-log engineering first: someone who can build a case, activity and timestamp table from Salesforce history and a second system. Then look for an analyst who can read variants with your operations team, and a builder who can change the org afterwards. Ask each role who fills it and what they have built before. ### Which Salesforce certifications are relevant to an Apromore project? There is no Apromore-specific Salesforce certification. Salesforce Certified Business Analyst suits the analyst, Platform Data Architect suits large or messy data, and Platform Administrator, App Builder or Developer suit the person who changes the org. Treat each as a pointer to a role, then ask for evidence of actual work. ### What is a good first Apromore engagement? One process, one measurable question and one decision. Examples include why Cases bounce between queues several times before resolution. The partner builds a log, reports its data quality, runs a session with the people who do the work, and ends with a decision memo that names the metric the change should move. ### Should an Apromore partner migrate records to match the discovered process? Not as part of discovery. A discovered path is a finding, and it can reveal a safer workaround as easily as a flaw. Moving records to match a map is a separate decision with its own risks. A partner who bundles it into the first proposal has skipped the evidence stage. ### Can I skip a partner for an Apromore project? Sometimes. If the question concerns one object in one org, a capable administrator can often answer it with history and reports. If the process crosses systems, the history is incomplete, or the findings will meet resistance, a partner who builds a trustworthy log is worth having. --- SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Salesforce consultancy (https://synconai.com/salesforce-consultancy).