The Situation
The Technical Requirements
The platform required deep Microsoft 365 integration — not a surface-level connection, but per-user account wiring so that outbound emails originated from the correct sender's address, replied threads landed in their Outlook inbox naturally, and a copy of every sent message appeared in their personal Sent folder. That level of integration required Microsoft Graph with per-user OAuth, careful token management, and precise control over email composition and routing.
Beyond email, the platform needed a reusable template engine with dynamic field injection, a one-to-many submission workflow that triggered automated status tracking on each send, bidirectional thread synchronization between Outlook and the application, and a scoring engine capable of ranking records against structured, configurable criteria. Each module had to work independently and compose cleanly with the others.
"The email integration had to feel native — not like a third-party tool sending on someone's behalf, but like the message actually came from them. That distinction drove the entire architecture."
Meeting those requirements meant building the platform in layers — shared infrastructure and authentication first, workflow and communication engine second, intelligent matching last.
The Challenge
Four Engineering Challenges
Each module introduced its own technical constraints. Together, they required a cohesive architecture that kept the user experience seamless while handling significant complexity underneath.
Per-User Microsoft Graph Authentication
Each user's outbound email had to originate from their own account — not a shared service account. That required per-user OAuth flows, token storage and refresh handling, and routing logic that correctly resolved the sending identity for every request.
Bidirectional Email Thread Sync
Reply threads needed to be visible inside the platform without disrupting the user's existing Outlook workflow. The solution required polling Graph for thread updates and surfacing them in the application — keeping both views consistent without duplicating state.
Reusable Template Engine with Dynamic Injection
Templates needed to support saved, reusable content pre-populated with dynamic fields — contact names, email addresses, phone numbers, and other entity-specific data — resolved at send time from the linked record. Field resolution had to be reliable across template variations and entity types.
Configurable Scoring & Ranking Engine
The match engine needed to score and rank records against a set of structured criteria — and those criteria had to be configurable per role, not hardcoded. The scoring logic had to be consistent, explainable, and fast enough to run against the full record database without perceptible latency.
The Approach
Infrastructure First. Features on Top.
The build started with shared infrastructure: the data model, the Microsoft Graph authentication layer, and the core application shell. Establishing these correctly upfront meant every module that followed inherited consistent auth, a clean data foundation, and a predictable API surface.
The email integration was built next — per-user OAuth flows, token lifecycle management, and the Graph API calls for sending, reading, and threading messages. The goal was a seamless experience: emails originate from the user's account, Sent items appear in Outlook automatically, and reply threads surface in the platform without any manual sync.
The template engine and one-to-many submission workflow were layered on top of the email integration. Templates store reusable content with named field placeholders resolved at send time from linked records. A single submission action fans out to multiple targets, sends each email through Graph, and opens a tracked workflow record per recipient — each with its own status lifecycle.
The match engine was the final module. Criteria are defined per role as weighted attributes. At query time, the engine scores every record in the database against those criteria and returns a ranked list — giving users a prioritized shortlist without any manual filtering.
Phase 1
Data Model & Core Application
Designed the entity model and relationships, stood up the core application, and established the API layer that every subsequent module would build on. Data integrity and a clean service boundary at this stage reduced rework across all later phases.
Phase 2
Microsoft Graph Integration & Email Engine
Implemented per-user OAuth authentication with Microsoft 365, built the token management layer, and wired the Graph API for send, read, and thread operations. Outbound emails route through the user's own account; replies and sent copies are natively available in Outlook.
Phase 3
Template Engine & Submission Workflow
Built the reusable template engine with dynamic field injection and the one-to-many submission workflow. Each submission fans out to selected targets via Graph, creates a tracked workflow record per recipient, and initializes a status lifecycle — all in a single user action.
Phase 4
Match Engine & Role-Based Scoring
Designed and implemented a configurable scoring engine. Criteria are defined per role with weighted attributes. At query time the engine scores all records in the database and returns a ranked shortlist — replacing manual search with an automatic prioritized result set.
Disciplines & Capabilities Applied
The Results
What the Platform Delivers
The Microsoft Graph integration delivers a genuinely native email experience — messages originate from the user's own account, appear in their Outlook Sent folder automatically, and reply threads are accessible inside the platform without any manual synchronization.
The submission workflow turns a multi-step manual process into a single action — one submission fans out to any number of targets, routes each email through Graph, and opens an individual tracked record per recipient. Status updates flow through the lifecycle automatically as replies arrive.
The match engine eliminates manual search. When a new role is entered, the scoring engine evaluates every record in the database against the role's weighted criteria and returns a ranked shortlist — giving users a prioritized starting point rather than a blank search field.
Native
Outlook experience — sent items, replies, and threads fully integrated
1 action
Fans out to multiple targets with individual tracked workflows per send
Ranked
Shortlists auto-generated by the scoring engine for every new role
Modular
Four independent modules composing into a single cohesive platform