CT Demand Management Application ( DMA) Ideas Portal
Hi JP,
Thank you. The flow you indicated below makes sense. We currently don’t flag requests with “EY Private” attribute and keen to enable that in the current BAU workflow.
@Cristian Diaz: could you please schedule some time with JP to understand the use cases (and any other considerations on who can access these requests) and come up with a plan to flag EY private demand (include Anil/Candace as needed).
Hi Sree
Doing well thanks – hope you are too! I see three main flows for EY Private demand:
Anything that a SL needs for Private, e.g. Private Tax or Assurance - through the SL TO
Private-specific global products, e.g. Ecosystem hub - through the GM TO
Anything that a Region needs for Private, e.g. localization, pursuit / engagement support, deployment, etc. - through the RTH (if an RTH does not exist, then via the SL TO)
These are all standard flows in DM already, so I don’t foresee that we need to do anything in particular to integrate demand for Private – seems to me it should be BAU, but let me know if you think differently.
What I would like is visibility of what demand is in the DM pipeline for Private. Do you have a way to flag this in the tool today?
Happy to discuss to make sure we are aligned.
Kind regards
Jean-Pierre Coetzee |
Hi JP,
Hope you are doing well. Just wondering about the process and timing for integrating the demand intake for EY Private, and thought of reaching out to you to get your thoughts. Could you please let us know.
Thanks in advance,
Sreenivasa Sunku
PFB the summary of the discussion with JP. Red ones were added by JP.
There are 3 main demand flows – global Private; global Private via a Service Line, and Regional Private via a RTH
Below types of intake will go to the Global Markets OTO team. Requester is expected to select ‘Global Markets’ option from the Service Line field.
Private Global intakes from Global team.
Eco system hub related intakes. This is just an example of a global Private product, see below
There are five/six global private products. Demand for these products are examples of global demand that are channelled through the GM TO, e.g Velocity, 7 Drivers of Growth, Ecosystems hub, GBB
Additionally, global intakes can also come from any Service Line that provides products used by Private, e.g. Private Tax, Private Assurance, SaT, Consulting
accounts. Requester is expected to select appropriate option from the Service Line field. Private also consumes SL assets, such as VIA, Assess, GTP, Canvas, Capital Edge, etc.Intakes coming from above mentioned service lines will follow the existing routing and governance placed in CT DMA.
I would distinguish regional demand as a third flow. Regional demand examples incl. supporting a pursuit, or engagement team, deploying a product in the local market, GTM activities, etc. If RTH is identified, RTH will take care of them as usual.
There is no exceptional governance for Private accounts as of now. Not sure what this means? Can you find out if there is a flag in our account databases (ARD / Mercury) that is used or can be used to flag an account as Private?
Possible Requirement
A user must identify the ‘Account Segment’ to inform from which segment the customer is from and to advise the significance. It can have three options as below: We need to identify and track demand by account segment. This should be consistent with segments that are used in our account structure
G360
Focus Core
Core
A user must identify if it is a Private or Non-private Account/customer since private accounts can be available in all these segments. We need to identify, tack and report on demand for Private accounts across all SL / functions. A Private account can exist in all three account segments, but the majority of them will be in Core. What if the demand is not for an account, i.e. it’s a product? Do we need to track if this is Private demand?
A requester can enter above mentioned data points during intake submission. However, OTO/PdM/TSM should be able to update these info as well. These data points should be available in the Master report. Should be able to filter on account segment and by Private accounts
All existing notifications should have this as an additional info in the email body.
When an intake is marked as Private Jean-Pierre and other required members should receive a notification so that they can triage with OTO/PdM/TSM if required. Also just for visibility of cross-Service Line demand for Private
Next Actions:
JP to help us with the definitions/overview of Account Segments mentioned in 4a. Even any WIKI or internal sites would help. Also definition of what a Private account is
Core team to work on the solution.
Team to share G360 requirements so we can look for consistency
EY Private strategy
EY Private equips us to respond fast to address the challenges of the Now and support our clients as they begin to focus on the Next and Beyond. It is a collaborative community of professionals in Assurance and Tax, focused on providing comprehensive services to private businesses, their owners, entrepreneurs, C-suite executives and the sources of private capital that fund their ambitions.
Private clients are already an important part of EY’s account landscape, contributing approximately 40% of global revenue with double digit growth. Across all EY account segments, over 90% of accounts are private.
As a NextWave initiative within the client centricity pillar, EY Private is also a strategic priority in the Tax and Assurance strategy refreshes.
EY Private recognizes the enormous opportunity presented by the private market. It connects our service lines with a unified goal: to unlock the ambitions of private clients and, by supporting them, to extend EY’s market leadership in the dynamic and fast-growing private market.