MissionWorks System Analysis

MissionWorks System Analysis

An interactive breakdown of the current system landscape, feature requirements, and integration challenges to prepare for the Site Stacker onsite consultation.

Dashboard: The Fragmentation Problem

This dashboard summarizes the MissionWorks system analysis, focusing on the core challenge: a fragmented network of disconnected applications. Use this view to understand the high-level landscape, the key systems in play, and the urgent need for consolidation and automation.

9+
Core Systems & Apps
2
Primary CRMs

(NEON & HubSpot)

100%
Manual Data Transfer

(Between core systems)

High-Level System View

The current network relies on manual processes to share data, creating silos, duplicate work, and a poor experience for partners and users who require multiple logins.

MissionGuide
(Short-term)
❌
NEON CRM
(Donations)
➤
MANUAL DATA ENTRY
➤
MissionNext
(Long-term)
❌
HubSpot CRM
(Historical Data)

Primary Goal: Consolidation

The most desired "Nice to Have" feature across all systems is a unified MissionWorks Consolidation Site. This site would provide a single login for users, connect directly to a central CRM, and handle all activities, events, and memberships in one self-contained system.

System Deep-Dive

Explore the current portfolio of MissionWorks applications. Each system serves a specific purpose, but as the report shows, they operate in isolation. Click on a system from the list below to see its primary function and its associated non-negotiable features that must be preserved in any new solution.

⬅

Select a system from the list to view details.

Feature Requirement Analysis

This section details the functional requirements for any future system, broken down by priority. These are the critical features that must be preserved and the high-priority improvements desired. Use the filter to toggle between categories and see the associated feature list.

Feature Priority Breakdown

Integration Gaps & Data Flow

The most significant challenge facing the MissionWorks network is the profound lack of system connectivity. This section visually breaks down the specific data-sharing failures and the manual processes they create, underscoring the high priority of the "Nice to Have" consolidation features.

1. MissionNext ➤ HubSpot / NEON

MissionNext explicitly states that none of its systems are connected. Data transfer between its subsites and the various CRMs is performed entirely by hand.

MissionNext Sites
(Journey, QuickStart)
MANUAL UPLOAD
➤
HubSpot / NEON
(CRMs)

2. MissionGuide ➤ NEON CRM

There is no integration between the MissionGuide platform and the NEON payment processor. This creates a significant manual workload for staff and a confusing "Two Login" problem for partners.

Partner Signs Up on NEON
(Login 1: Payment)
STAFF MANUALLY ENTERS
➤
Partner Configures on MG
(Login 2: Profile)

3. MissionLinked ➤ Admin

The MissionLinked fundraising platform is completely isolated. There is no ability to import any data, and reporting relies on a monthly spreadsheet sent from the India office.

MissionLinked
(Fundraising)
MONTHLY SPREADSHEET
➤
Admin/Finance
(Reporting)
Interactive Report generated from "Analysis of Site Stacker Information Sheet Requirements".