SDT PARTNER PROGRAM
99 percent of SDT revenue flows through partners. Sell pre-built EAPs. Build your own product on the SDT Engine. Or embed SDT inside an existing platform you already own.
Secure Digital Transport (SDT) is a new category for moving sensitive data. Every major system roadmap will include SDT inside the next five years as a build concept and an overall business strategy. The partners who define what SDT looks like inside their vertical, their customer base, or their existing product line earn the relationship and the recurring revenue that follows.
Botdoc invented the category and operates the SDT Engine that everything is built on. We are a partner-first company by design. Sales motion through direct enterprise representatives is the exception rather than the rule across our customer base. The program below maps to three distinct partner motions, each tuned to a different partner profile: sell pre-built External Application Projects through your existing customer relationships, build your own vertical product on the SDT Engine, or embed SDT inside a platform you already ship.
THE THREE TRACKS, TRACK 1
Resell Botdoc's family of External Automation Projects (EAPs) into your existing customer base under your standard customer paper. SecureMFP for regulated MFP fleets. SecureMyDealer for automotive retail. New EAPs ship under the Secure My family on a roughly quarterly cadence. Partner margin starts at 35 percent on deployment and recurring revenue, scaling toward 50 percent with volume tiers and white-label arrangements negotiated in the partnership conversation.
Best fit: VARs, resellers, MSPs, MSSPs, MPS dealers, distributors, vertical compliance consultancies. If you already sell into regulated SMB or mid-market accounts, Track 1 attaches to your existing motion without a new go-to-market, without an engineering investment, and without changing how you book revenue. The partner relationship runs through standard reseller mechanics from contract through renewal, with deal-registration protection and per-EAP volume tiers negotiated in the partnership conversation.
THE THREE TRACKS, TRACK 2
Build a product on the SDT Engine. You own the brand, the customer paper, the pricing, and the roadmap. Botdoc supplies the underlying transport, the API, scoping support, and developer enablement. Cloud Maven built Secure File Transport for Salesforce on this track and ships it on the AppExchange. Edward Jones built SDX, an internal financial-advisor document workflow. VedaPointe built VedaPointe.Send for EPIC-integrated healthcare. Each one is a partner product, partner-monetized, Botdoc-powered.
Best fit: Independent Software Vendors (ISVs), system integrators, vertical platform builders, agencies with a buildable customer base. If you have a market you already serve and a technical stack you already own, Track 2 lets you add a new product line without rebuilding the transport layer from scratch, without becoming a transport company, and without inheriting the compliance maintenance work that comes with operating an in-house secure-file-transfer stack.
THE THREE TRACKS, TRACK 3
Integrate the SDT Engine into a platform you already ship. Two outcomes from a Third Party Integration: replace a transport vendor you are already paying for, or open a new monetizable feature inside the product you already sell to your customers. A Third Party Integration (TPI) is invisible to the end customer. They see your product. They get the SDT benefit. You either eliminate a line item from your stack or unlock a pricing tier you could not previously offer.
Best fit: hardware OEMs, platform vendors, established SaaS products with embedded transport needs. If your product already exists and is already in market, Track 3 is the lower-risk way to bring SDT economics into your stack without launching a new product line or training the customer base on a new brand they have to evaluate separately from yours.
PARTNER PROFILE, RESELLERS AND SERVICE PROVIDERS
The first three partner archetypes have an existing customer book and an existing sales motion. They sell what is already built on the SDT Engine into the relationships they already have. Track 1 is the natural entry. Track 2 and Track 3 open up over time as customer demand matures.
Value-added resellers and independent resellers selling into regulated SMB and mid-market accounts. Finance, healthcare, education, automotive, legal. You sell hardware, software, and services into existing relationships. Track 1 fits cleanly. If your customer base wants a Salesforce-integrated workflow, a healthcare-EPIC workflow, or a specific vertical build, Track 2 becomes available too.
Managed service providers and managed security service providers. Recurring-revenue economics align with how you already sell. SecureMFP attaches per device. SecureMyDealer attaches per dealership rooftop. Future EAPs attach to specific compliance triggers in the verticals you serve. Track 1 is the typical entry. Some MSSPs evolve toward Track 3, embedding SDT into their managed security platform.
PARTNER PROFILE, BUILDERS AND PLATFORM VENDORS
The next three archetypes have technical depth, a defined market, and an existing stack. They build their own EAP on the SDT Engine (Track 2) or embed SDT inside a platform they already ship (Track 3).
ISVs with a vertical customer base and an existing product line. Cloud Maven is the textbook example: shipped Secure File Transport for Salesforce on the SDT API as their own AppExchange product. Track 2 is the natural fit. Track 3 is available for ISVs who embed SDT inside an existing product rather than launch a new SKU.
Compliance consultancies, audit firms, and vertical advisors with a referral motion or a customer-facing book. Track 1 fits the referral motion. Track 2 fits firms who want to productize their methodology by building a vertical-specific workflow on the SDT Engine.
OEMs and platform vendors with a customer-facing brand and a product already in market. Track 3 is the typical conversation: SDT becomes a feature inside your product or hardware program. Track 2 is available for partners who want a co-branded product alongside their existing line.
TIER PROGRESSION, ENTRY TIERS
Most partners begin at Referral or Reseller. Both entry tiers carry low commitment, fast path to first dollar, and standard deal-registration protection. The choice between them is whether you want Botdoc to carry the customer relationship and pay a referral fee, or whether you want to carry the customer paper, the recurring revenue, and the 35 to 50 percent gross margin on deployment and renewals yourself.
Margin: referral fee per closed account. Track 1 motion only.
Send us qualified leads. We close, deploy, and own the customer relationship. You earn a referral fee on the first contract and on each renewal. Lowest commitment, fastest path to first dollar.
Best for: compliance consultancies, audit firms, vertical advisors with a referral motion.
Margin: starting at 35 percent on deployment and recurring revenue, scaling toward 50 percent with volume tiers and white-label arrangements. Track 1 motion.
Sell Botdoc EAPs into your customer base under your standard customer paper. We support sales and deployment. You own the relationship and the renewal. Standard 90-day deal-registration protection.
Best for: VARs, MSPs, MSSPs, MPS dealers, distributors with their own quoting and customer paper.
TIER PROGRESSION, GROWTH TIERS
Build Partner and OEM tiers are reserved for partners with the technical capacity to ship a product or the platform reach to embed SDT inside their existing offering. Both tiers carry custom commercial terms in a master agreement.
Margin: partner sets pricing. SDT Engine fees apply per transaction. Track 2 motion.
Build your own EAP on the SDT Engine. You own the brand, the pricing model, and the roadmap. We supply transport, API access, scoping support, and developer enablement. Engine pricing is published on our API page for full transparency. Cloud Maven, VedaPointe, and Edward Jones are at this tier today.
Best for: ISVs, integrators, vertical platform builders with a defined market and existing technical capacity.
Margin: built into the OEM commercial model. Track 3 motion.
SDT embedded inside a partner platform or hardware program as a Secured-by-Botdoc feature. Joint roadmap influence, dedicated engineering liaison, named-account program. Strategic partnerships only. Deal terms set in master agreement.
Best for: hardware OEMs, large platform vendors, distributors with platform ambitions.
PROOF, EAPs
The first proof group is Botdoc-built External Application Projects (EAPs) that channel partners resell into their customer base and that major platforms have embedded or white-labeled inside their own offerings. Each EAP carries the SDT Engine underneath with the same patented architecture and same compliance posture, branded for the vertical it serves.
Botdoc's EAP for regulated MFP fleets. Closes the scan-to-email encryption gap on existing devices. Brand-agnostic across HP, Xerox, Ricoh, Konica Minolta, Canon, Lexmark, Sharp, Kyocera, Brother, and Toshiba. Five-minute deployment per device. Sold 99 percent through channel partners. Visit securemfp.io for the partner-facing product page.
Botdoc's EAP for automotive retail. CRM-integrated and DMS-integrated dealership workflow for secure customer document exchange. Embedded inside CDK Global, Cox Automotive, and Drive Centric platforms today. Dealers reach Connect through the DMS or CRM they already use, with Botdoc as the underlying transport. See the Connect product page.
Botdoc's EAP for smaller dealers and franchise groups. Same SDT transport, lighter integration footprint. White-labeled by KPA and sold inside their Vera Suite compliance platform as "Secure Messaging for Dealers" under public partnership attribution. This is the textbook private-label EAP arrangement. See the Lite product page and KPA's Secure Messaging page.
PROOF, TPIs
The second proof group is partner-built products that ship under partner brands on the SDT Engine. Each Third-Party Integration partner brought a vertical specialty and a customer relationship; Botdoc supplied the transport and the API.
Edward Jones built SDX, a secure document workflow for their financial-advisor network, on the Botdoc SDT API. Public user guide OLM-16043B-A. Internal advisor-to-client document delivery without portals, passwords, or app downloads. See the SDX TPI page for build details.
Cloud Maven built a Salesforce-native secure file exchange product on the SDT Engine. Listed on the Salesforce AppExchange under the explicit "Powered by Botdoc" attribution. Cloud Maven publishes outcomes of 58 percent fewer lost documents, 41 percent faster turnaround, 37 percent fewer manual follow-ups, and 52 percent reduction in compliance exceptions. See the Cloud Maven build page for details.
VedaPointe built a HIPAA-compliant patient communication channel for healthcare on the SDT Engine. Integrated with EPIC, the largest EMR in healthcare. Use cases include imaging results, lab results, advance directives, and care or birth plans. A fax killer for healthcare. Public Powered-by-Botdoc attribution. See the VedaPointe.Send build page.
THE ECONOMICS
Public-facing economics for the three tracks below. Specific list prices, volume breaks, deal-registration mechanics, and co-marketing budgets are confirmed in the partnership conversation per the partner type and the track.
| Track | Partner margin or pricing model | Deal-flow ownership |
|---|---|---|
| Track 1: Sell | Starts at 35 percent. Scales toward 50 percent with volume tiers and white-label arrangements. | Partner owns customer paper and renewal. Standard 90-day deal registration. |
| Track 2: Build | Partner sets retail pricing. SDT Engine usage fees apply per transaction. See API page for engine rate card. | Partner owns the product, the customer, and the roadmap. Botdoc co-markets with the partner where mutual fit exists. |
| Track 3: Embed | Per-API-call engine pricing built into the partner's commercial model. OEM volume terms in master agreement. | Partner owns the platform and end-customer relationship. Botdoc is invisible to the end customer. |
Deal registration runs nationwide on any U.S. territory. International partnerships handled by exception in the master agreement. We do not intentionally route the same lead to multiple partners. If a conflict surfaces, the Botdoc partnership team resolves it directly.
THE SUPPORT MODEL
Channel partners get four operational layers from Botdoc, each tuned to the partner motion (sell, build, or embed). The deeper the partner motion, the more direct technical enablement we provide.
Persona talk tracks for CISO, CTO, COO, CFO, and operations roles. Objection-handling libraries by vertical. Channel-partner-specific co-marketed content. Asset library of one-pagers, customer-facing decks, and vertical content templates.
Founder-led LinkedIn cadence drives inbound. Warm leads route to channel partners by territory and customer-fit. Vertical content series and lead magnets capture and qualify.
For Track 1, four-hour deployment certification. For Track 2, full developer enablement including SDT Engine API documentation, a sandbox environment, scoping support, and direct technical access to the Dev team. For Track 3, dedicated engineering liaison through OEM integration.
Asset library free to partners. Co-branded customer-facing decks. Joint webinar production. Vertical-association co-sponsorship for qualifying partners. Powered-by-Botdoc attribution for Track 2 and Track 3 partners where partner consent exists.
WHY NOW
Every major system roadmap will include Secure Digital Transport in the next five years as a build concept and an overall business strategy. A market-shift is already underway and Botdoc is pioneering what SDT is today and what it means in the future. Partners who define what SDT looks like inside their vertical or their platform earn the relationship and the recurring revenue that follows.
SDT is what comes next. The partners who help define it for their market or their platform are the partners who carry the category forward.
FAQ, ONBOARDING
Discovery call to executed agreement: two to four weeks for Track 1, longer for Tracks 2 and 3 depending on scoping. Sales enablement for Track 1 runs in a single afternoon. Technical certification for Track 1 is four hours. Track 2 scoping varies by product complexity.
None at agreement. Performance tiers kick in based on activity. We invest in partners who invest in the relationship. We do not impose minimum-revenue commitments at signing.
Helpful but not required for Track 1. EAPs fit across finance, healthcare, education, automotive, and legal verticals today. For Track 2, an existing customer base in a defined vertical is the strongest signal. For Track 3, an existing platform with embedded transport needs is the prerequisite.
FAQ, OWNERSHIP AND IP
Track 1: the partner. Sold on partner customer paper, partner invoicing, partner renewal. Track 2: the partner. Their product, their brand, their pricing, their customer paper. Track 3: the partner. SDT is invisible to the end customer. In all three cases, the customer is the partner's customer.
The partner owns the product they build. Botdoc owns the SDT Engine and the underlying patents. Partner branding, partner UX, partner business logic, and partner workflow are partner IP. Engineering details are spelled out in the partner agreement and the API terms.
Engine usage is metered per transaction with volume tiers. The published rate card lives on our API page. Enterprise-volume terms negotiated in the partner agreement.
FAQ, DEAL FLOW
First-to-register protected on the opportunity for Track 1. Standard 90-day window with renewal on active engagement. Conflicts resolved by the Botdoc partnership team directly. We do not intentionally route the same lead to multiple partners.
Yes. A Track 1 reseller who finds a build opportunity in their book can scope a Track 2 product alongside their existing resale motion. A Track 2 build partner who later wants to embed SDT inside an existing product they already ship can pick up Track 3 in parallel. The tracks are partner motions, not partner classifications.
If the customer is on an existing EAP and you are bringing them a new EAP or a Track 2 build, that is a clean expansion deal you register and earn on. If the customer is already on the same EAP through another channel, deal registration covers conflict resolution.
Thirty minutes with our partnership team covers your customer base, your existing stack, which of the three partner tracks fits your motion, and what a first deployment or build would look like inside your customer relationship. The conversation is not a pitch deck. It is a working session that ends with either a yes-and-here-is-the-next-step or a clean no based on territory, vertical fit, and commercial structure. Most Track 1 partner conversations move to an executed agreement within two to four weeks of the discovery call. Track 2 and Track 3 conversations move into scoping rather than directly to agreement, since the product or platform we are building together needs to be specified before commercial terms can be finalized. The scoping work runs in parallel with the legal review on both sides.
PARTNER SPOTLIGHT
Live deployments showing what each partner track looks like in practice. Ironcore is the financial-services Track 1 example, deploying the full Botdoc stack (Spark, SecureMFP, ID Verify) for community banks and credit unions under GLBA, FFIEC, and NY DFS Part 500 frameworks. FordDirect is the Track 3 platform example, with Botdoc available as a preferred vendor on The Shop by FordDirect so Ford and Lincoln dealers can procure Connect, Lite, ID Verify, and SecureMFP through a single supplier relationship rather than evaluating each product separately.
Ironcore deploys the Botdoc stack for community banks and credit unions. Spark, SecureMFP, and ID Verify under one workflow. GLBA, FFIEC, and NY DFS Part 500 aligned.
Botdoc is a preferred vendor on The Shop by FordDirect. Connect, Lite, ID Verify, and SecureMFP available to Ford and Lincoln dealers through one-stop procurement.