Lead, opportunity & account operations
Create, update, merge and progress CRM records according to rules.
20 project-authored proposals · taxonomy v1.1 · 0 new benchmark runs. Verifiers and partial-credit rules below are designs, not executed results.
- Typical applications
- Salesforce · HubSpot · Dynamics 365
- Class GUI-need label
HY· Hybrid
Digital-employee context
Project class assignments, not demonstrated employee capability or imported benchmark coverage. Acceptance criteria and value metrics are proposals; no ROI has been measured.
Related roles
- Sales and marketing · Representative outcomes: qualified CRM records, segmented outreach campaigns and scheduled sales handoffs.
Sales development / CRM · Primary class
- Workflow
- Check fit and exclusions → research → approved outreach → qualify → sync CRM and hand off.
- Deliverable
- Qualified meeting or lead, research context and CRM activity.
- Proposed acceptance
- Respect opt-outs/ownership; accurate contact and CRM state; qualification accepted by sales.
- Proposed metric · unmeasured
- Held qualified meetings; sales-accepted opportunities per eligible lead; cost per accepted handoff.
Lead qualification and CRM write-back anchor the workflow; a booked qualified meeting adds the calendar outcome.
- 11x: Outbound lead generation · Official documentation
- 11x: Salesforce integration and exclusions · Official documentation
Task proposals · 20
Expand to inspect the complete original wording and proposed checks. Original proposal text remains English in both interfaces.
R05.06.01.01-T01 Convert a qualified lead into account, contact and opportunity
Original instruction
Salesforce developer org (Lightning). Convert lead 'Dana Ruiz' (Ruiz Logistics) into a new account and contact, creating opportunity 'Ruiz Expansion' with amount 48,000, close date 2026-12-15, stage 'Qualification', and keep the lead owner. Do not create a follow-up task.
- Platforms
web· Any OS (web)- Applications
- Salesforce
- Interfaces
brow· Browser- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
licensed· Licensed pro app- Proposed difficulty
- 2 / 5
Proposed verifier
Lead IsConverted; ConvertedAccount/Contact/Opportunity exist with names and fields equal spec; no Task created; owner unchanged. API Enabled removed from the agent profile and Data Loader/Import Wizard blocked; field history and LoginHistory must show UI edits.
Proposed partial credit
40% conversion with correct records; 40% opportunity fields; 20% no extra task
R05.06.01.01-T02 Associate five contacts to a company and set lifecycle stages in HubSpot
Original instruction
HubSpot test portal. Associate the 5 contacts listed in input/contacts.txt to company 'Kestrel Metals' (one is currently associated to a duplicate 'Kestrel Metals Inc' - remove that association), set the primary company for each, and set lifecycle stage to 'Sales Qualified Lead'.
- Platforms
web· Any OS (web)- Applications
- HubSpot
- Interfaces
brow· Browser- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
- None declared
- Proposed difficulty
- 2 / 5
Proposed verifier
Associations: 5 contacts primary to the correct company; duplicate association removed; lifecycle stage set on all 5. No private-app token is issued; HubSpot audit/property history must show changes from the web app.
Proposed partial credit
50% associations correct; 20% duplicate association removed; 30% lifecycle stage
R05.06.01.01-T03 Advance a deal and schedule the next activity in Pipedrive
Original instruction
Pipedrive trial company. Move deal 'Orion Packaging - 2027 renewal' from 'Proposal made' to 'Negotiations started' and schedule a call activity 'Pricing review' for 2026-10-20 10:00 (company timezone) linked to the deal and its contact person.
- Platforms
web· Any OS (web)- Applications
- Pipedrive
- Interfaces
brow· Browser- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clickdrag· Drag & drop- Work product
WP08· App/system state- Conditions
- None declared
- Proposed difficulty
- 1 / 5
Proposed verifier
Deal stage equals 'Negotiations started'; activity exists with type call, subject, due date/time, linked deal and person. Agent has no API token; change log shows web.
Proposed partial credit
50% stage moved; 50% activity correct
R05.06.01.01-T04 Route twenty new leads to owners by assignment rules
Original instruction
Salesforce developer org. input/routing_rules.pdf assigns leads by billing state and employee count (e.g. West + >1,000 employees -> Enterprise West queue). Twenty unassigned leads from the 'Web - Oct 13' campaign need owners. Assign each to the correct user or queue without changing other fields.
- Platforms
web· Any OS (web)- Applications
- Salesforce
- Interfaces
brow· Browser- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
LeadHistory: owner of each of the 20 leads equals key; no other field changes; leads outside the campaign untouched. API Enabled removed from the agent profile and Data Loader/Import Wizard blocked; field history and LoginHistory must show UI edits. Control pair: T13.
Proposed partial credit
80% correct owner (equal share per lead); 20% no collateral edits
R05.06.01.01-T05 Fix opportunity stages that contradict the latest activity notes
Original instruction
Salesforce developer org. For opportunities owned by 'P. Lane' with Close Date in Q4 2026, read the most recent activity notes (calls, emails). Where the notes clearly indicate a different stage (e.g. signed contract received, or prospect went silent after rejecting pricing), update Stage per input/stage_definitions.pdf and add a one-line reason in Next Step.
- Platforms
web· Any OS (web)- Applications
- Salesforce
- Interfaces
brow· Browser- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsnav· Pan/zoom/scroll- Work product
WP08· App/system state- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Stage changes equal key's 7 records (no changes on the 11 consistent ones); Next Step populated on changed ones. API Enabled removed from the agent profile and Data Loader/Import Wizard blocked; field history and LoginHistory must show UI edits.
Proposed partial credit
60% correct stage per record (penalty per false change); 20% no wrong changes; 20% reasons
R05.06.01.01-T06 Merge six duplicate contact pairs with survivorship rules in HubSpot
Original instruction
HubSpot test portal. input/dupe_pairs.csv lists 6 suspected duplicate contact pairs; one pair is actually two different people (same name, different companies and phones) and must not be merged. Merge the others so the surviving record keeps the oldest create date and the most recently used email, per input/survivorship.pdf.
- Platforms
web· Any OS (web)- Applications
- HubSpot
- Interfaces
brow· Browser- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clickvis· Visual judgment- Work product
WP08· App/system state- Conditions
risk· Irreversible/risky- Proposed difficulty
- 3 / 5
Proposed verifier
Merge history: 5 merges with primary/secondary choices per key; the false pair untouched; surviving email values equal key. No private-app token is issued; HubSpot audit/property history must show changes from the web app.
Proposed partial credit
50% correct merges with right primary; 30% false pair not merged; 20% email survivorship
R05.06.01.01-T07 Qualify a lead into an opportunity with stakeholders in Dynamics 365
Original instruction
Dynamics 365 Sales trial. Qualify lead 'Aster Analytics - data platform' so it links to the existing account 'Aster Inc' (not a new one) and existing contact 'M. Chen'; on the new opportunity add stakeholders from input/stakeholders.txt with roles, competitor 'Northwind Data', and est. revenue 220,000.
- Platforms
web· Any OS (web)- Applications
- Dynamics 365
- Interfaces
brow· Browser- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Opportunity: parentaccountid = existing Aster Inc, contact linked, connections for 3 stakeholders with roles, competitor linked, revenue; no duplicate account/contact created. Web API disabled for the agent's security role; audit history must show UI changes.
Proposed partial credit
30% linked to existing records; 30% stakeholders; 20% competitor; 20% revenue
R05.06.01.01-T08 Import trade-show leads with mapping and de-duplication in Zoho CRM
Original instruction
Zoho CRM trial. Import input/tradeshow_2026.csv (184 rows) as Leads via the import wizard: map columns per input/mapping.txt (incl. splitting 'Full name' is not allowed - use the provided First/Last), skip duplicates on Email, tag all imported leads 'TS-2026', and set Lead Source 'Trade Show'.
- Platforms
web· Any OS (web)- Applications
- Zoho CRM
- Interfaces
brow· Browser- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
Leads: exactly the key's 171 new records (13 duplicates skipped) with mapped fields, tag and source; no existing leads modified. Import history shows the wizard job; agent has no OAuth client.
Proposed partial credit
40% correct record count/no dupes; 40% field mapping; 20% tag and source
R05.06.01.01-T09 Mark lost opportunities with reasons and schedule follow-ups in Odoo CRM
Original instruction
Odoo 17 CRM, sales team 'Europe'. Using input/pipeline_review.xlsx (decisions from Monday's pipeline review), mark the 8 listed opportunities lost with the specified lost reason, and for the 6 'keep' opportunities schedule a 'Call' activity on the stated date for the salesperson.
- Platforms
web· Any OS (web)- Applications
- Odoo · Excel
- Interfaces
brow· Browser- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
crm_lead: 8 inactive with lost_reason_id per key; 6 mail_activity rows with type, date, user equal key; others unchanged. XML-RPC blocked; changes tracked to the agent's web session.
Proposed partial credit
50% lost with reasons; 40% activities; 10% no collateral
R05.06.01.01-T10 Log call outcomes and update deal stages in HubSpot
Original instruction
HubSpot test portal. input/call_notes.md contains notes from 10 sales calls (date, contact, outcome). Log each as a call engagement on the right contact and deal with outcome and notes, and move each deal to the stage implied by the outcome using the stage mapping in input/stage_map.txt.
- Platforms
web· Any OS (web)- Applications
- HubSpot
- Interfaces
brow· Browser- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
10 call engagements with timestamps, outcomes and associations equal key; deal stages equal key. No private-app token is issued; HubSpot audit/property history must show changes from the web app.
Proposed partial credit
50% calls logged with associations; 50% deal stages
R05.06.01.01-T11 Ask which deal to close when the request matches three opportunities
Original instruction
Salesforce developer org. A manager's chat message (input/request.txt) says: 'Close the Acme deal as won, they signed today.' Three open opportunities belong to Acme accounts. Do not guess: post a clarifying Chatter question to the manager on the account listing the 3 candidates, and change nothing until answered.
- Platforms
web· Any OS (web)- Applications
- Salesforce
- Interfaces
brow· Browser- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
clarify· Ask when unclear- Proposed difficulty
- 3 / 5
Proposed verifier
No opportunity stage changed; a FeedItem mentioning the manager exists on the Acme account and names all 3 opportunity names. Any stage change scores 0. API Enabled removed from the agent profile and Data Loader/Import Wizard blocked; field history and LoginHistory must show UI edits.
Proposed partial credit
60% no changes made; 40% clarifying post with all 3 candidates
R05.06.01.01-T12 Build account hierarchies from an org-chart image
Original instruction
Salesforce developer org. input/aster_group_chart.png is an org-chart image of Aster Group's 12 subsidiaries in 3 levels. Set Parent Account on each subsidiary account so the hierarchy matches the chart; two subsidiaries do not exist yet and must be created with Billing Country from the chart.
- Platforms
web· Any OS (web)- Applications
- Salesforce
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsvis· Visual judgment- Work product
WP08· App/system state- Conditions
licensed· Licensed pro app- Proposed difficulty
- 4 / 5
Proposed verifier
Account.ParentId for all 12 equals key; 2 new accounts created with country; no other account re-parented. API Enabled removed from the agent profile and Data Loader/Import Wizard blocked; field history and LoginHistory must show UI edits.
Proposed partial credit
60% parent links (equal share per account); 25% new accounts; 15% no collateral changes
R05.06.01.01-T13 Route the same twenty leads through the API (control pair of T04)
Original instruction
Control pair of T04. Copy of the org with an API-enabled integration user (sf CLI authenticated). Implement the routing rules from input/routing_rules.pdf in a script and update OwnerId on the 20 campaign leads.
- Platforms
lin· Linuxmac· macOSwin· Windows- Applications
- Salesforce CLI · Python
- Interfaces
api· API/SDKterm· Terminal- GUI need · task setting
AP· API-sufficient- GUI need · ordinary access
AP· API-sufficient- Interaction primitives
code· Code & commands- Work product
WP08· App/system state- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Same owner checks as T04; compared to T04 to measure the GUI penalty.
Proposed partial credit
80% correct owners; 20% no collateral edits
R05.06.01.01-T14 Merge duplicate accounts with child records per survivorship rules
Original instruction
Salesforce developer org. Four duplicate account sets (2-3 records each) are listed in input/account_dupes.csv. Merge each set keeping as master the record with the most closed-won revenue; keep the master's Billing Address unless blank; ensure all contacts, opportunities and cases end on the master.
- Platforms
web· Any OS (web)- Applications
- Salesforce
- Interfaces
brow· Browser- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clickvis· Visual judgment- Work product
WP08· App/system state- Conditions
licensed· Licensed pro apprisk· Irreversible/risky- Proposed difficulty
- 4 / 5
Proposed verifier
AccountHistory/MasterRecordId: 4 surviving masters per key; field values per rules; child record counts on masters equal key. API Enabled removed from the agent profile and Data Loader/Import Wizard blocked; field history and LoginHistory must show UI edits.
Proposed partial credit
40% correct masters; 30% field survivorship; 30% child records consolidated
R05.06.01.01-T15 Reassign accounts and open opportunities after a territory redraw
Original instruction
Dynamics 365 Sales. input/new_territories.xlsx maps ZIP-code ranges to 4 territories and owners effective 2026-11-01. Reassign every account in the 'US East' territory whose ZIP falls into a new range, cascading open opportunities (not closed ones) to the new owner, and set the Territory lookup.
- Platforms
web· Any OS (web)- Applications
- Dynamics 365 · Excel
- Interfaces
brow· Browser- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsmulti· Cross-app- Work product
WP08· App/system state- Conditions
licensed· Licensed pro apprisk· Irreversible/risky- Proposed difficulty
- 4 / 5
Proposed verifier
Account owner and territory per key for all affected accounts; open opps owned by new owner; closed opps unchanged. Web API disabled for the agent's security role; audit history must show UI changes.
Proposed partial credit
40% account owners; 20% territory lookups; 30% open opps cascaded; 10% closed untouched
R05.06.01.01-T16 Reconcile CRM accounts with a billing export and flag churn
Original instruction
HubSpot test portal plus input/billing_export_2026-09.csv (Stripe test export). For the 30 customer companies, set ARR from active subscriptions, set 'Customer status' to Churned where all subscriptions ended before 2026-10-01, and create a task for the owner on companies whose ARR fell more than 20% vs the current ARR property.
- Platforms
web· Any OS (web)mac· macOSwin· Windows- Applications
- HubSpot · Excel
- Interfaces
brow· Browserdesk· Desktop GUI- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsmulti· Cross-app- Work product
WP08· App/system state- Conditions
multiapp· Multi-app- Proposed difficulty
- 4 / 5
Proposed verifier
Company properties ARR and status equal key; tasks exist for exactly the key's downgrade set; matching handles 3 name variants via domain. No private-app token is issued; HubSpot audit/property history must show changes from the web app.
Proposed partial credit
40% ARR values; 30% churn status; 30% downgrade tasks
R05.06.01.01-T17 Turn fifteen inbound emails into Pipedrive leads without duplicates
Original instruction
Gmail test inbox 'sales@orbitlabs.test' and Pipedrive trial. Fifteen inbound inquiry emails arrived; some are from existing persons/organizations, two are replies to the same thread, one is spam. Create or update leads in the Leads Inbox with org, person, value estimate from the email, label 'Inbound', and link the email thread via Pipedrive's email sync.
- Platforms
web· Any OS (web)- Applications
- Pipedrive · Gmail
- Interfaces
brow· Browser- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsmulti· Cross-app- Work product
WP08· App/system state- Conditions
multiapp· Multi-app- Proposed difficulty
- 4 / 5
Proposed verifier
Pipedrive DB: exactly the key's 12 leads (no duplicates; spam ignored); persons/orgs reused where existing; values and labels equal key; email threads linked. No API token.
Proposed partial credit
40% correct lead set; 25% reuse of existing records; 20% values/labels; 15% threads linked
R05.06.01.01-T18 Consolidate an acquired company's accounts into the CRM
Original instruction
Salesforce developer org. input/acquired_accounts.csv has 60 accounts from an acquisition. Match each against existing accounts by domain and fuzzy name (rules in input/matching_rules.pdf); for matches, merge data into the existing account and move the acquired contacts; for non-matches, create the account; then assign owners by the territory table.
- Platforms
web· Any OS (web)mac· macOSwin· Windows- Applications
- Salesforce · Excel
- Interfaces
brow· Browserdesk· Desktop GUI- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
HY· Hybrid- Interaction primitives
click· Point & clicktype· Text & formsmulti· Cross-app- Work product
WP08· App/system state- Conditions
licensed· Licensed pro applong· Long-horizon- Proposed difficulty
- 5 / 5
Proposed verifier
Per-account outcome (matched-to ID or created) equals key; contacts under the correct accounts; owners per territory table; no duplicate accounts created. API Enabled removed from the agent profile and Data Loader/Import Wizard blocked; field history and LoginHistory must show UI edits.
Proposed partial credit
40% match decisions; 25% contacts moved; 20% owners; 15% no duplicates
R05.06.01.01-T19 Resolve sync conflicts between HubSpot and Salesforce records
Original instruction
HubSpot test portal connected to a Salesforce developer org via the native integration (sync paused). 25 contact/company records show conflicts in the sync health view. Apply input/source_of_truth.pdf (e.g. Salesforce owns Owner and Account Name; HubSpot owns lifecycle and email preferences) by editing the losing side, then resume sync and clear the errors.
- Platforms
web· Any OS (web)- Applications
- HubSpot · Salesforce
- Interfaces
brow· Browser- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsmulti· Cross-app- Work product
WP08· App/system state- Conditions
licensed· Licensed pro appmultiapp· Multi-applong· Long-horizon- Proposed difficulty
- 5 / 5
Proposed verifier
After resume, both systems hold the key value for each conflicted field (25 records); sync error count 0; no record deleted. No private-app token is issued; HubSpot audit/property history must show changes from the web app; API Enabled removed from the agent profile and Data Loader/Import Wizard blocked; field history and LoginHistory must show UI edits.
Proposed partial credit
60% per-field correct values; 25% sync errors cleared; 15% no deletions
R05.06.01.01-T20 Prepare the quarterly forecast by updating fifty opportunities
Original instruction
Dynamics 365 Sales. input/rep_updates.xlsx (rep notes) and input/call_transcripts/ (12 transcripts) describe changes to 50 open opportunities. Update amount, est. close date and forecast category for each per input/forecast_rules.pdf, then open the Q4 2026 forecast grid and write the committed and best-case totals to output/forecast.txt.
- Platforms
web· Any OS (web)mac· macOSwin· Windows- Applications
- Dynamics 365 · Excel
- Interfaces
brow· Browserdesk· Desktop GUI- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
HY· Hybrid- Interaction primitives
click· Point & clicktype· Text & formsmulti· Cross-app- Work product
WP08· App/system state- Conditions
licensed· Licensed pro applong· Long-horizonmultiapp· Multi-app- Proposed difficulty
- 5 / 5
Proposed verifier
Per-opportunity fields equal key (50 records); forecast totals equal key; transcripts override older spreadsheet notes where dated later. Web API disabled for the agent's security role; audit history must show UI changes.
Proposed partial credit
50% per-record updates; 20% transcript precedence; 30% forecast totals
Mapped research references
Existing benchmark-to-class links from the research catalog. They are not record-level annotations, executions or product endorsements.