Build together
QA and complete the existing OrkastraRX pilot on Dynamics 365 Sales; validate its proposed OneScan integration.
Agilidy / LSPedia · Proposed partnership POV
Build together. Co-sell together.OneScan + OrkastraRX. A joint Microsoft go-to-market opportunity.
I already have a working OrkastraRX pilot on Dynamics 365 Sales, built with guidance from a pharmaceutical executive with 30+ years of experience. I propose partnering with LSPedia to QA and validate it, build OneScan and Dynamics 365 Supply Chain Management integrations, publish through Microsoft Marketplace, and pursue a joint Microsoft co-sell motion—led fractionally as LSPedia expands its sales team.
Prepared by Jason Wickman · Founder, Agilidy · October 2026 · Independent strategic perspective
Why now · Competitive market opportunity
A Microsoft alternative as Veeva CRM customers transition.
Veeva is transitioning customers from its legacy Salesforce-based CRM to Vault CRM, with legacy support scheduled to end December 31, 2029. Salesforce Life Sciences Cloud is another competitor. This creates a window to propose a Microsoft-based specialty pharma option—not a guaranteed migration opportunity.
Differentiate together
Connect commercial orchestration and traceability; explore Dynamics 365 Supply Chain Management opportunities.
Co-sell together
Pursue joint Microsoft sales plays for OneScan, OrkastraRX and applicable Dynamics 365 solutions, subject to eligibility.
Fractional build-and-sell leadership
As LSPedia hires account executives, Jason proposes to help fractionally complete the solution, develop the Microsoft alliance and create shared pipeline. This is a partnership proposal, not a full-time job application.
Proposed competitive positioning; no claim of a completed Veeva replacement or approved Microsoft co-sell arrangement.
The partnership proposal · Build together. Co-sell together.
Two complementary solutions. One joint Microsoft go-to-market motion.
This is not a request for LSPedia to become an OrkastraRX customer or a referral partner. It is a proposal for LSPedia and Agilidy to jointly develop an integrated offering, then pursue qualified opportunities for both OneScan and OrkastraRX alongside Microsoft sellers and the Microsoft partner ecosystem.
01 · Build
Combine domain expertise and commercial intelligence
LSPedia contributes OneScan and pharmaceutical traceability expertise. Agilidy contributes OrkastraRX, Dynamics 365 architecture and implementation experience. Jointly validate an integration and package the customer value proposition.
02 · Position
Leverage 25+ years in the Microsoft CRM ecosystem
Jason Wickman brings experience helping launch Microsoft CRM, serving as a Microsoft Dynamics Sales Director, and working at the intersection of sales, marketing, service and technology. Use that background to shape a credible joint Dynamics 365 and specialty pharma proposition.
03 · Co-sell
Take both offerings to market with Microsoft
Develop joint sales plays, customer targeting and Microsoft-facing solution collateral; evaluate Microsoft Marketplace listings and Partner Center co-sell pathways for each eligible offer. Share opportunities through a mutually agreed partner-led sales motion.
The intended outcome: a repeatable joint solution and shared pipeline for both partners.
This is a proposed partnership, not an existing LSPedia–Agilidy–Microsoft arrangement. LSPedia's current Microsoft co-sell participation has not been confirmed. Marketplace and co-sell status require offer-specific qualification and Microsoft review; neither Microsoft participation nor seller support is guaranteed.
Microsoft's current co-sell eligibility requirements ↗The thesis
OneScan and OrkastraRX: complementary capabilities, a shared path to market.
LSPedia OneScan already handles the hardest back-office problems in pharma: serialization, traceability, supply chain integrity and regulatory compliance. Those capabilities are not in question.
The open question is commercial: how do specialty pharma teams plan launches, manage contract pharmacy and HCP accounts, and coordinate field activity on top of that compliant foundation? Today that work often lives in spreadsheets, point tools or a generic CRM that was not built for specialty pharma workflows.
OrkastraRX already has a working pilot on Dynamics 365 Sales, built with guidance from a pharmaceutical executive with over 30 years of experience. The proposal is to partner with LSPedia to QA, validate, integrate, publish and co-sell it.
Inside OrkastraRX · Platform concepts
From fragmented signals to coordinated commercial execution.
Adapted from the OrkastraRX strategic presentation. These are conceptual product visuals, not live customer dashboards, measured results, or evidence of a completed OneScan integration.
Platform architecture · OrkastraRX deck, slide 5
A commercial intelligence layer above existing systems
Prioritized accounts
Physician access
Launch missions
Prior auth visibility
Territory intelligence
Executive forecasting
ORKASTRARX CORE ENGINE
Unified intelligence · prediction · orchestration
CRM
Field activity
Market access
Data vendors
Launch signals
Field notes
Proposed LSPedia opportunity: assess which OneScan events can safely and usefully enrich this intelligence layer.
Revenue Leakage Funnel™ · deck slide 3
See where launch revenue disappears.
Target accounts
Engaged accounts
High intent
Script written
Prior auth approval
Patient start
Persistence
Illustrative funnel shape adapted from the deck; not LSPedia or customer performance data.
Launch Mission Engine™ · deck slide 8
Not tasks. Missions.
Activate Tampa Nephrology
WHY NOW
High patient potential + payer policy change
HIDDEN BLOCKER
Prior auth burden on office staff
BEST ANGLE
Workflow simplification + onboarding kit
SUCCESS CRITERIA
2 patient candidates + scheduled next meeting
Illustrative mission example from the OrkastraRX presentation.
Source: OrkastraRX strategic deck supplied for this discussion, slides 3, 5 and 8. The original deck also illustrates the Physician Access Graph™ (slide 7) and Launch Command Center (slide 10).
Proposed architecture
Two platforms, one commercial-to-compliance flow.
The diagram below is a proposed reference architecture. No integration between OrkastraRX and OneScan has been built or certified. It is a starting point for a joint validation, not a deployed system.
Front office · proposed
OrkastraRX on Dynamics 365
Sales, account management and specialty pharma launch workflows.
- Launch account targeting and sequencing
- Contract pharmacy and HCP account management
- Specialty launch milestones and field coordination
- Commercial reporting and next-best-action prompts
Back office · verified platform
LSPedia OneScan
Serialization, supply chain and compliance (per lspedia.com).
- Product serialization and GTIN management
- Supply chain traceability and shipment events
- Regulatory compliance and aggregation
- Exception handling and recall support
Integration layer · proposed, not built
OrkastraRX ↔ OneScan connector
A proposed, bounded data flow that surfaces OneScan serialization, shipment and exception events into Dynamics 365 account and launch records, and routes commercial decisions back as context. Everything in this band is a hypothesis to validate, not a shipped connector.
Launch readiness signals
OneScan serialization status → D365 launch milestone
Account compliance view
Read-only shipment and exception status per account
Exception routing
OneScan exceptions → responsible account owner in D365
Commercial value
What a front office adds on top of a compliant back office.
Faster, coordinated launches
Launch account targeting, field coordination and milestone tracking in one commercial system, with OneScan serialization readiness visible alongside.
Account-level commercial visibility
A single account record across contract pharmacies, HCP networks and health systems, with proposed read-only compliance context from OneScan.
Faster exception response
Serialization exceptions and recalls routed to the responsible account owner, so commercial outreach and substitution decisions happen sooner.
Value statements are hypotheses to validate during the pilot-to-market roadmap, not measured customer outcomes or guaranteed benefits.
Three practical use cases
Where the front office and back office meet.
01
Specialty pharma launch orchestration
A specialty product launch touches contract pharmacies, limited distribution networks, REMS programs and payer access. A proposed OrkastraRX layer on Dynamics 365 would let commercial teams plan account targeting, track launch milestones and coordinate field engagement, while OneScan manages the serialization, GTIN allocation and compliant distribution underneath.
Proposed capabilities to validate
- Launch account targeting and sequencing in D365
- Field activity coordination and next-best-action prompts
- OneScan serialization events surfaced to commercial owners as launch-readiness signals
02
Account management across contract pharmacies and HCP networks
Specialty distribution relationships span multiple contract pharmacy partners, health systems and HCP practices. A proposed front-office account model would consolidate contract terms, service-level commitments and interaction history, while OneScan continues to own the verified product movement and compliance records behind each account.
Proposed capabilities to validate
- Unified account record across contract pharmacy and HCP relationships
- Contract renewal and service-level visibility for account managers
- Proposed read-only view of OneScan shipment and compliance status per account
03
Supply-chain and commercial alignment for recalls and exceptions
When a serialization exception, supply disruption or recall occurs, commercial teams need to know which accounts and patients are affected. A proposed integration would surface OneScan traceability data to sales and account leadership so outreach, substitution and continuity decisions happen faster.
Proposed capabilities to validate
- Exception alerts routed to the responsible account owner in D365
- Affected-account lists generated from OneScan traceability data
- Coordinated customer communication and substitution guidance
Proposed pilot-to-market roadmap
The pilot exists. Complete, validate, publish and co-sell.
Five jointly governed stages from an existing pilot to a validated commercial offer. Timeline, responsibilities, quality gates and ownership would be agreed with LSPedia.
1
01 · Existing pilot
A working OrkastraRX foundation
- Pilot already built on Dynamics 365 Sales
- Product direction informed by a pharmaceutical executive with 30+ years of experience
- Jointly review the pilot and agree the production feature backlog
2
02 · QA and pharma validation
Validate the solution
- Complete functional, integration, security and performance QA
- Assess applicable pharmaceutical workflows, regulatory expectations, privacy and audit requirements
- Document gaps, acceptance criteria and remediation priorities
3
03 · Integrate
Connect OneScan and Dynamics 365
- Design, build and test the OneScan integration
- Validate Dynamics 365 Supply Chain Management integration points and licensing
- Demonstrate traceability and commercial workflows end to end
4
04 · Marketplace
Package and publish
- Define joint product ownership, licensing, support and commercial terms
- Complete production readiness, documentation and deployment packaging
- Submit eligible offer to Microsoft Marketplace and complete required reviews
5
05 · Co-sell
Launch with Microsoft
- Pursue Microsoft co-sell eligibility and seller enablement
- Create joint sales plays against Veeva and Salesforce alternatives
- Enable LSPedia account executives and build shared qualified pipeline
Timeline is a proposed plan for discussion, not a committed schedule or guaranteed outcome. Actual durations depend on scope, data access, security review and joint resourcing.
What is verified vs. what is proposed
Honest about what exists and what we are testing.
Verified current capabilities
- LSPedia OneScan is a serialization, supply chain and compliance platform (per lspedia.com)
- OrkastraRX is referenced as a Dynamics 365 commercial offering (per orkastrarx.com)
- Microsoft Dynamics 365 Sales is a generally available CRM platform
Proposed, to be validated
- Any data flow between OneScan and Dynamics 365 via OrkastraRX is proposed, not yet built or certified
- Specific fields, APIs, security models and compliance handling require joint validation
- No LSPedia or OrkastraRX endorsement, partnership or commercial relationship is implied by this page
Partnership discussion
Let's bring the existing pilot to market together.
If the architecture and use cases here are worth validating, the next step is a short working session to review the existing pilot, agree QA and pharmaceutical validation gates, scope OneScan and Supply Chain integrations, and align on Marketplace and co-sell responsibilities.
No LSPedia, OrkastraRX or Microsoft endorsement, partnership or commercial relationship is implied by this page. All integrations are proposed and require joint validation.