Delivery
Team Guide
When you purchase MX products, they are not ready to implement right off the truck. There is quite a bit of technical configuration that needs to happen based on your unique environment, set up, and vision for what you would like to achieve with our products.
Get started
Delivery Team: Table of contents
Lesson 1 4ish mins
Readiness assessment
Start here
Meet your team
Lesson 2 1ish mins
By the numbers
Lesson 3 5ish mins
What to expect
Lesson 4 5ish mins
Your deliverables
Lesson 5 10ish mins
Implementation
Timelines
Lesson 6 3ish mins
Before we begin
Lesson 7 7ish mins
Best practices
Delivery Team: Meet your team
Intro
Dedicated Delivery Team
You will have a hands-on team of technical problem solvers that have decades of experience supporting all types of financial platforms. They will set you up for the most speedy and successful “time-to-live”. How you lay the foundation and set up your product will be critical for your success. Our team will work hands-on with your team to make your integration as seamless as possible, make the customer experience as impactful as possible, and set up your system in such a way that you will see the greatest lift in engagement, adoption and improving trust with your customers.
Bottom line
Solutions Architect
The Delivery Team’s primary goal is to help your team get up and running with your new digital banking tools.
Solution Architect
Integration Engineer
Project Manager
MX Academy
Technical team that partners with you to create integration designs that ensure the technical and business objective success of your users.
There is nothing worse than buying something and having it not be what you’d hoped for, right? Solution Architects make sure that doesn’t happen to you. They are your technical advocate that ensures we can execute on your vision and what you are hoping to accomplish with your purchase. They collaborate with your technology teams so you can be confident with the timelines and resources required for your integration with MX. They are there every step of the way as you work with sales to tailor the technical side of your solution to your unique environment while also ensuring your integration with MX is set up for your long term success. When you are ready to jump on board, the Solution Architects are there to make sure you experience a seamless transition from working with your sales representative to working with your implementation team. They follow through to the end by communicating important integration details and not letting anything slip through the cracks.
MX system experts that will guide you through the integration process and set you up for success.
Integration engineers are critical to making sure that your integration will work, be a success, and open doors for future opportunities. They are MX system experts and bring decades of experience supporting all types of financial platforms. The integration engineers will make sure that your integration is being designed correctly and that the right tools and technology are in place to accomplish the goals you have set for your MX tools. They will be your technical expert, and work hands-on with your team of engineers to guide them through the integration process. They will also be your troubleshooting resource for diagnosing technical problems and assisting with MX APIs.
A dedicated resource who coordinates all the moving pieces to ensure a timely and successful go-live with your MX products.
Your project manager will be right by your side and be your trusted guide and “go-to” person through implementation. They are your advocate and will ensure that what you purchase is up and running by your service start date. They take your project from a concept to reality by making things easy to understand, connecting the right people, and ensuring things are done on time and correctly. They are expert listeners who understand what it takes to make your goals happen. They will be prescriptive consultants that recommend steps you need to take to make the project come together.
An engaging, impactful suite of learning content designed to help you understand, adopt, market, and advocate for your MX product.
Getting a new digital banking tool is a huge deal! And getting your team members up to speed so they can best help your customers/members is no small task. Employees throughout your entire organization will need to be trained on how to use the MX products, support it, sell it, market it, and so much more. All team members will be impacted by the new tool in some way, and training and enabling all of them in their specific roles might seem a little daunting. MX Academy is here to help. We will empower you with everything you need to be successful from training and enabling your team to marketing to customers. We’ve crafted a premium suite of content, including eLearning courses, tutorial videos, walkthrough articles, and marketing templates and assets. All of MX Academy’s content has been designed, tested, and improved to best help your team master your new tool quickly and effectively.
2 of 8
Lesson 2
4ish mins
Lesson 3
1ish min
Lesson 4
5ish mins
Lesson 5
Implementation timelines
Lesson 6
10ish mins
Lesson 7
3ish mins
Lesson 8
7ish mins
Delivery Team: By the numbers
Fact 1
Over the past five years, the Delivery Team has successfully completed more than…
You’re in good hands. Your implementation team has over three decades of experience at MX and will use that to make your implementation as seamless as possible.
Fact 2
In other words, we’ve done this a time or two. Better yet…
Fact 3
Our project management team is fluent in over…
1,500
Method- ologies
7
Agile, PMI, Six sigma, Waterfall, Kanban, Critical Path, Capability Maturity
92%
of customers go live on time
3 of 8
Delivery Team: What to expect
Your partners throughout the entire process
Starting with your conversations with sales, the Delivery Team will be there to make sure that they understand your vision and provide the context for what it will take to get there. This team will facilitate your entire onboarding process from start to finish. They will be “all-hands-on-deck” until your integration has been configured In a way that not only meets your needs and expectations, but also can be built upon and deepened in the future. They will lay the foundation for growth and success both technically and by enabling and empowering your employees and customers.
More insights
Here’s where the Delivery Team fits in
Standard Delivery Team timeline
Start meeting with sales
Close deal
Go live
Grow
Even before you meet them, your dedicated Solution Architect advocates for your success from the very beginning. They partner with your sales representative, and once they have nailed down the vision for what you are wanting to accomplish, they help transform it into a solid, viable solution for your organization. You can expect their presence on calls where you outline technical documentation and review architectural diagrams. They will also be there to answer questions over email or Slack. Once you purchase MX tools, they will assist in your transition to implementation and will be on your kickoff call and act as a resource to your project manager throughout setting up your integration.
As soon as you wrap up with the sales team, your project manager will be right by your side and be your trusted guide and “go-to” person through implementation. You will likely have met them prior to closing, as the will often assist your sales rep during the sales process in understanding dependencies, milestones, schedules and more. You can expect to work with them anywhere from 60 days to 6 months depending on depth of integration and resources available. If the right resources are not allocated, including a project manager from your team and a technical contact who knows the details of your product and has access to influence resources on your side, the timeline could potentially be prolonged. It is also important to have an executive sponsor to ensure that key resources from your team are in place to complete the project in the proposed timeframe.
You can expect dedicated support from the integration engineers when you wrap up with the sales team and are ready to get your engineering team involved with coding. They will be your guide from setting up the technical back end of your integration through going live with your tools and a little bit beyond. They will get you set up for success and stay involved to make sure everything works properly. In fact, although you may not work with them directly, they will be there to assist your Client Strategy Consultant with deeper technical questions about your integration.
Integrations Engineer
When you are ready to put a training and marketing plan into place, MX Academy will be there to provide you with best practices, and quality, engaging learning content. If you need more hands -on help or custom solutions, our team of experienced designers and marketing experts will be there to consult with you on how to achieve your vision.
4 of 8
Delivery Team: Your deliverables
You should have a general idea what this team will be partnering with you on. It’s helpful to know the exact deliverables you can expect in the process. Let’s take a closer look at the team, and each team member. When you are done with the onboarding, the Delivery Team will make sure the following is complete:
Each member of the Delivery Team will provide specific deliverables that will be vital to your implementation.
Technical architecture diagram built for your unique environment Technical details of your solution documented and communicated to relevant stakeholders Access to the MX Developer Portal Access to the MX integration test environment Business objectives consult to ensure your success
When you purchase MX tools, they aren’t just “ready to turn on.” There is a lot of work that goes into making sure both our engineers and yours are setting everything up for success. There are technology, resource, and integration requirements. That is where integration engineering comes into play. These folks are technical experts who will be the ones to understand what you want to accomplish with MX tools, and will ensure everything is set up correctly for your specific requirements. They will also guide your engineers through the implementation process. They are able to look at your code and make sure things are ready on your end for a successful partnership, identifying mistakes that may be made on your engineering team’s end that could cause problems down the line.
Successful integration: properly integrate and support all platform configurations Successful launch of the services purchased (including MX Academy) Troubleshooting QA processes Program management
Ensure that your architecture is integrating as expected with our platform Share best practices, leveraging decades of experience integrating with banking platforms Help your technical teams build an integration that doesn’t just solve a problem today, but also creates a foundation for success and further growth Provide an analysis on all calls being made to and from our platform with your systems. We’ll ensure that we are seeing the correct calls, order of calls, and success we want to see Ensure the data models your team selects for creating data on our platform will work the way it’s expected to
Deliverables
Setting up your MX experience involves many players including yourself, MX, and third party vendors. Sometimes there can be as many as 7-15 vendors! Making sure that every single one of those teams comes to the table together, at the right time, with their deliverables in hand is essential for your success and timing. That is where project managers will be your best friend. They will manage all of the teams to orchestrate a seamless experience where partners come together, ready with what they need at the right time.
Defined project plan: understanding your deliverables within your time frame Advocate behind the scenes: Driving and pushing the right people to get the job done Set proper expectations, timelines, manage requests and tasks Communicate your priorities and expectations to MX teams, and requirements back to you resolve technical issues: Ensure there is a speedy resolution for you to hit your deadlines
Conduct a kick-off call Facilitate a weekly status update meeting Other meetings as deemed necessary
Meetings
Your entire MX Academy package comes ready to use out of the box. Our specialized team of designers has worked hard to make sure your package delivers a premium, engaging learning experience. We take pride in the highly visual and delightful content we produce.
eLearning guides Tutorial videos Walk-through articles Marketing templates and assets A searchable help center
Take a closer look at what’s inside MX Academy
5 of 8
Delivery Team: Implementation timelines
Here’s what a standard timeline looks line
Not sure what to expect from a timeline perspective? No sweat! Our solution architects have put together a few example timelines to help you get the picture. They were built based on what most of our clients do, giving you a good idea about how to build your own timelines. Keep in mind that your timeline has a lot to do with your team’s capabilities and the resources you’ve allocated to the project.
No matter how complex your project timeline is, the Delivery Team is there make sure it runs smoothly and efficiently, taking a load of stress off your back.
Widget or MoneyMap integration
Nexus integration
MXmobile integration
2-3 months
6-9 months
9-12 months
Click to view milestone details
Project Kickoff
Platform Connectivity
Authentication
Bill Pay
Remote Deposit
Branch Locator
UX/UI Development
Data Connection to MX Platform
Internal Transfers
External Transfers
P2P Payments
QA and Integration Testing
Launch
Data connection to MX Platform Process Breakdown
SSO Coding 1. MX to set up integration environment 2. MX to establish API key 3. Obtain a widget URL with a SSO API 4. Create users with the Real Time API 5. Embed widgets Develop Data Connection 1. MX to establish API key 2. Code to the MDX On Demand / MDX Real Time API 3. Create users with the On Demand / MDX Real Time API
Close
Internal Transfers Process Breakdown
Middleware Layer Design 1. Agreed upon foundation 2. Design and document middleware 3. Feedback follow up (redesign if needed) 4. Functional documentation provided to MX (pre-meeting) 5. Kickoff call with vendor Development 1. Additional adjustments 2. Build Middleware to connect MX API’s to vendor’s API’s 3. Connect vendor API to Middleware layer 4. MD UI Functional Testing 1. Error messaging 2. Fields testing Performance Testing 1. Concurrency testing 2. Load testing
External Transfers Process Breakdown
P2P Payments Process Breakdown
Branch Locator Process Breakdown
Remote Deposit Process Breakdown
Bill Pay Process Breakdown
Authentication Process Breakdown
Platform Connectivity Process Breakdown
1. Send IP address ranges to MX 2. MX whitelists IP Range 3. Client whitelists MX IP ranges
UX/UI Development Process Breakdown
1. Accounts UI design work 2. Accounts UI implementation 3. Transactions UI design work 4. Transactions UI implementation 5. MX product sync-up
Product Testing
Go Live / Handoff
MX Academy Process Breakdown
Action Determine Budget Determine Strategy Set up call with Marketing and Training
QA and Integration Testing Process Breakdown
1. Functional UI testing 2. Compliance review 3. Load systems testing 4. Establishing QA standards 5. QA testings 6. Functional data testing
Product Testing Process Breakdown
1. Ongoing integration work 2. QA test corrections 3. Employee testing
Go Live / Handoff Process Breakdown
MX will set up a call with a CSC and your team for hand-off.
Responsible You / MX You / MX MX
Project Kickoff and Firewall/ Server Setup
QA Testing
Go Live / Hand Off
Project Kickoff and Firewall/ Server Setup Process Breakdown
UX/UI Built in OLB/Mobile
Data Retrieval From Nexus and Reporting API
Action Whitelist MX IP Whitelist your IP Issue API Key & Client ID
Responsible You MX MX
Data Retrieval From Nexus and Reporting API Process Breakdown
Action Review data Code to Nexus
Responsible You / MX You
Go Live / Hand Off Process Breakdown
MX will a call with CSC and you for hand off
Action Determine escalation path Set up call with MX Support Zendesk
Responsible You / MX MX MX
Data Connection to MX Platform Process Breakdown
Action Code to the MX Batch specs or MDX Real Time API Verify Pending/Posted Transaction Reconciliation Verify when users, members, accounts, and transactions are passed Error Handling/Retry mechanisms Create users Create members Functional data testing Loading testing QA/Pilot testing Go live
Responsible You You / MX You / MX You / MX You You You You You You
Access and create a Gantt chart template with your project milestones
6 of 8
Delivery Team: Before we begin
Stay in the loop
The delivery team will be doing a lot of heavy lifting for you, but there are resources you will want to plan on allocating for your implementation to be as smooth as possible. Here are some of the people you’ll want to plan on including on your project team:
Getting in touch with the right people and gathering the right information before we get started will go a long way during your implementation.
3
Questions
you’ll want to know the answers to before we begin
1.
Who knows where your data is and how it moves?
2.
Who knows your firewalls and infrastructures?
3.
Have you done a third-party integration before? Who ran that initiative?
Project Manager (individual or team) Client Marketing / Client Training (individual or team focused on these initiatives) Product Lead (individual or team) Backend Architect (individual or team) 2-4 Backend Engineers 2-4 Frontend Engineers QA Team (2-4 individuals or more)
7 of 8
Delivery Team: Best practices
Mistakes we’ve seen and how to avoid them
Don’t be blindsided by things that could slow down your implementation timeline. Check out the following best practices to keep your project moving as quickly as possible.
Following our Best Practices Guide is a sure way to avoid unnecessary headaches and roadblocks throughout your implementation process.
Working with online banking providers and third-parties
Internal alignment and planning
Not having the appropriate resources allocated for your project
Even more insights
Challenge
Being the only person driving the MX initiative at your company
Not having a clear understanding of what you are hoping to achieve in implementing MX products
Not defining critical details upfront
Changing how you want things implemented partway through
Security teams not being thorough in their initial due diligence
Not having the appropriate resources allocated for your project.
Solution
Every project will be a little different and require different resources. Check out the “Before We Begin” section for what we recommend.
Being the only person driving the MX initiative at your company.
Make sure to involve multiple stakeholders at your company. Best practice is to have upper executives involved from various parts of the company. For example: not just the CIO or Chief Digital Officer, but also, CMO and potentially CTO to also make sure there is buy in from the technology side of the FI.
Not having a clear understanding of what you are hoping to achieve in implementing MX products.
Have clearly outlined business objectives and how you are going to measure their success:
What specific desired business outcomes are you set out to achieve (monthly, quarterly, annually)? How will achieving those desired business outcomes affect your overall business (increase revenue, reduce risk, improve experience)? What are the key activities, events and results that will indicate that you are on track or have achieved your desired outcomes (Aggregation success metrics, user growth/retention rates, product innovation, product speed/stability, user experience etc). How does the MX solution enable you to achieve your desired business outcomes and defined business objectives? What does success and failure look like for your product and user experience?
Not defining critical details upfront.
Determine a unique identifier for users, or which users will be loaded into MX.
Changing how you want things implemented partway through.
For example, if you originally wanted widgets but decide mid-project to build parts of the UX yourself.
Security teams not being thorough in their initial due diligence.
Ensure that your security team is digging deep enough during pre-sales to check off your security standards before signing. If you require another layer of information once implementation begins, make sure your team is ready to dedicate time to the project.
Relying on online banking providers to code up
Ensuring that the party responsible has access to all needed data including that data housed outside of the core (CC, mortgage, etc.)up
Relying on online banking providers to code up.
Coordinating with your online banking provider and any third-parties on how you plan to integrate with MX a big key to success. Things like how the data will be passed to MX and identifying the user experience are key elements that in many cases will need to be scoped and implemented by your partner and could effect your go live timelines.
Ensuring that the party responsible has access to all needed data including that data housed outside of the core (CC, mortgage, etc.)
Data can live in a variety of areas with your tech stack. Knowing where this data resides and which data elements you plan to send to MX will help avoid roadblocks during delivery. For example, your online banking provider may have access to all DDA account data (checking, savings, moneymarket, etc.). Still, credit card processing may be handled by a third party and may not be stored within the core or within your online banking provider’s systems. This could require some additional work for your online banking provider to bring in this data or an additional integration with the third-party to MX. These details can take time and delay your project, so it’s best to determine what data is available as early as possible and agree on the data to be sent to MX.
8 of 8
Delivery Team
Now you know The Delivery Team. They’re your go-to for getting off on the right foot and seeing your implementation through to the end. If you need a refresher on all things delivery, feel free to jump back into this guide!
Catalyst
Meet more MX teams
Close this guide
TechOps
Help improve MX Academy!
