▸case-01 Our RevOps team is introducing new engagement scoring dimensions to our revenue platform. Could you prepare a complete schema specification and validation framework for these new fields? The deliverable should include field definitions, required flags, allowed value lists, numerical bounds, and a structured migration checklist to roll out this version update. | fail→pass | 26,379 | 21,435 | -19% | 1 | 1 | 0% | 4,624 | 3,955 | -14% | 0 | 0 | — |
▸case-02 We have duplicate account records between Salesforce and HubSpot with conflicting phone numbers and domains. What deterministic matching rules should we configure in our CRM to merge these accounts automatically? | pass→pass | 19,607 | 18,266 | -7% | 1 | 1 | 0% | 2,791 | 2,935 | +5% | 0 | 0 | — |
▸case-03 Our enterprise sales team needs round-robin lead distribution across North American SDRs based on geographic territory and company size tier. How should we configure our routing workflow logic? | pass→pass | 17,978 | 18,167 | +1% | 1 | 1 | 0% | 2,774 | 3,057 | +10% | 0 | 0 | — |
▸case-04 We want to update our B2B sales pipeline stages from Discovery to Closed Won and set mandatory exit criteria for SDR opportunity handoffs. What exit criteria and stage definitions should we implement? | pass→pass | 16,387 | 17,967 | +10% | 1 | 1 | 0% | 2,505 | 2,874 | +15% | 0 | 0 | — |
▸case-05 We ingest intent signals from Bombora and 6sense into our Snowflake data warehouse. Engineers want to map provider topic names directly to raw string IDs. How should we structure the canonical intent signal schema? | fail→fail | 21,648 | 16,747 | -23% | 1 | 1 | 0% | 3,442 | 2,967 | -14% | 0 | 0 | — |
▸case-06 Our marketing ops team is building a raw data dictionary sheet for third-party enrichment fields from ZoomInfo. They plan to list only field name, data type, and description. What standard metadata columns must be added to ensure governance? | pass→pass | 14,045 | 12,291 | -12% | 1 | 1 | 0% | 2,155 | 2,053 | -5% | 0 | 0 | — |
▸case-07 We are deprecating old intent category codes and introducing v2 signal schemas next month. Developers suggest overwriting existing database column definitions in production without effective dates. How should schema version changes be managed? | fail→fail | 17,682 | 13,471 | -24% | 1 | 1 | 0% | 2,480 | 2,179 | -12% | 0 | 0 | — |
▸case-08 We are ingesting buying stage propensity scores from an external vendor scaled 0 to 100. Should we store these as unbounded integers without validation logic? | pass→pass | 11,251 | 10,699 | -5% | 1 | 1 | 0% | 1,686 | 1,827 | +8% | 0 | 0 | — |
▸case-09 Our data team documented intent signal fields in a static spreadsheet table. Security and compliance auditors require proof of data flow from vendor APIs to downstream CRM objects. What documentation artifact is needed? | pass→pass | 12,348 | 9,632 | -22% | 1 | 1 | 0% | 1,805 | 1,576 | -13% | 0 | 0 | — |
▸case-10 When standardizing contact intent signals across multiple vendors, our team wants to keep signal taxonomy completely separate from entity matching systems. How should signal taxonomy interface with entity identifiers? | pass→pass | 20,560 | 13,516 | -34% | 1 | 1 | 0% | 2,791 | 2,137 | -23% | 0 | 0 | — |
▸case-11 An engineer proposed naming canonical signal fields using obscure internal system codes like attr_px_992_q. How should signal field names be formatted for GTM revenue teams? | pass→pass | 15,473 | 11,782 | -24% | 1 | 1 | 0% | 2,360 | 1,987 | -16% | 0 | 0 | — |
▸case-12 We are designing a unified signal schema for web event tracking. The developer marked all 40 attributes as mandatory nullable strings. What structural classification framework should be applied? | pass→pass | 17,062 | 14,091 | -17% | 1 | 1 | 0% | 2,548 | 2,372 | -7% | 0 | 0 | — |
▸case-13 We receive job seniority attributes from Clearbit (sub_role), ZoomInfo (mgmt_level), and Clay (seniority_tier). Should we store these in separate provider-specific tables without alignment? | pass→pass | 15,296 | 33,939 | +122% | 1 | 1 | 0% | 2,188 | 2,470 | +13% | 0 | 0 | — |
▸case-14 In our signal taxonomy, a lead can have an intent strength score, but intent topic is sometimes missing. How do we enforce data integrity when dependent attributes rely on primary fields? | pass→pass | 15,632 | 12,980 | -17% | 1 | 1 | 0% | 2,193 | 2,184 | -0% | 0 | 0 | — |
▸case-15 For SOC2 compliance, auditors want to know who owns each intent data feed and how fresh the data is when used in lead scoring. What fields must be present in the signal dictionary? | pass→pass | 14,547 | 11,649 | -20% | 1 | 1 | 0% | 2,379 | 2,228 | -6% | 0 | 0 | — |
▸case-16 We are adding a new technographic technology stack attribute to our account signals. What framework steps are required to launch this new dimension into our platform? | fail→pass | 17,550 | 9,003 | -49% | 1 | 1 | 0% | 2,525 | 1,645 | -35% | 0 | 0 | — |
▸case-17 Our intent vendor sends buying stage values like 'Awareness', 'Evaluation', 'Decision', and occasional typos like 'Eval_Stage_1'. How should the validation layer handle stage values? | pass→pass | 15,003 | 12,340 | -18% | 1 | 1 | 0% | 2,221 | 2,033 | -8% | 0 | 0 | — |
▸case-18 A team lead proposes leaving the source column blank in our signal dictionary since all data comes from our main IP enrichment vendor. Is omitting source attribution acceptable? | pass→pass | 12,490 | 7,635 | -39% | 1 | 1 | 0% | 1,761 | 1,253 | -29% | 0 | 0 | — |
▸case-19 We are changing the data type of intent_score from string to float across our production pipelines. What document should be prepared to guide downstream team transition? | fail→pass | 15,257 | 12,955 | -15% | 1 | 1 | 0% | 2,238 | 2,287 | +2% | 0 | 0 | — |
▸case-20 Our RevOps team frequently modifies taxonomy definitions without recording when changes happened or why. What versioning element must be instituted? | pass→pass | 8,666 | 8,459 | -2% | 1 | 1 | 0% | 1,196 | 1,415 | +18% | 0 | 0 | — |
▸case-21 The data engineering team uses snake_case in Snowflake, while marketing uses spaces and capital letters in spreadsheets like Buying Intent Level. How should canonical field names reconcile these styles? | pass→pass | 15,079 | 9,888 | -34% | 1 | 1 | 0% | 2,192 | 1,736 | -21% | 0 | 0 | — |
▸case-22 We are introducing a composite account engagement score ranging from 0.0 to 1.0. How do we prevent invalid out-of-bound scores from entering our downstream analytics? | pass→pass | 14,009 | 12,718 | -9% | 1 | 1 | 0% | 2,220 | 2,192 | -1% | 0 | 0 | — |