What's new in PartnersWatch

New

• Automatic TLS for partner domains: certificates are issued on demand, only for hosts that pass verification, and renewed automatically.

• Outside-in domain probe: every custom domain is checked for DNS, then TLS, then a real HTTP request. Badges and readiness read that verdict (live, HTTP error, no certificate, no DNS, unreachable) rather than any claim, and certificate expiry is tracked.

• Portal host vs product host: a partner domain serves either the partner portal or the vendor's product, and it can be repointed without losing verification.

• Token-on-host proof: besides a DNS TXT record, a domain can be proven by serving a token on the host itself.

• Brand icon: a brand now carries a square icon next to its logo, used anywhere a compact mark is needed.

• Partner rail: partner.connected, partner.updated, and partner.disconnected events set a reselling partner up in your product before their first customer.

Improved

• Each provisioning delivery stores the vendor's reply and shows it in the console, so you can see what your product did with an event.

• A short outage during a vendor deploy no longer drops a partner event; delivery retries.

• Oct 1: a customer who already has an account in your product is no longer asked to create another.

New

• Signed provisions: every delivery is HMAC-signed over the timestamp and body. Two signatures are sent during secret rotation, so you can rotate with no downtime.

• Typed, versioned events: account.created, account.suspended, account.cancelled, plan.changed, credits.granted, units.granted, feature.changed, and custom.applied.

• Subscription rail: your product reports subscription state back (active, trialing, past due, paused, cancelled, churned).

• Integration manifest: declare endpoints per environment, auth, payload version, events, and plan-code mapping in one document. Submitting it configures the connection.

• Provision policy: limit which kinds partners can grant, cap quantities, and require a plan.

• Domain claims: a DNS TXT record proves a partner owns their custom domain.

• Brand legal links: brands carry support, billing, terms, and privacy URLs.

• Integration MCP server: operator-scoped tools and guided prompts for vendor coding agents, with readiness reports and an end-to-end self-test.

New

• Live and test API keys and OAuth clients, each visibly marked by its prefix.

• Test activity is stamped as test and kept out of commissions, payouts, and dashboards; only live rows touch money and reporting.

• Products hold one connection per environment, and the console switches between live and test views.

New

• Unified Library: documents and materials in one explorer with a shared folder rail and a type toggle.

• Export to PDF, HTML, and PPTX with every variable resolved exactly as it renders on screen.

• Contract set: Reseller & Channel Partner Agreement, Order Form, MSA, Mutual NDA, DPA, SCC cover & module selector, and Sub-processor addendum templates.

• Invoice numbering series: independent sequences per partner, with prefixes, padding, and resets.

Improved

• Credit packs can be tied to a specific product.

• Price books can target a partner tier, so pricing follows promotions automatically.

New

• Assistant chat in the console and in the partner portal, limited to what each user is allowed to do.

• Manager and role agents: configure roles with their own instructions and tools; the manager delegates and composes the answer.

• Approval policies: approve outward actions (default), only destructive ones, or none.

• Background runs: queue or schedule agent work, with a full step-by-step trail.

New

• Journeys: enroll customers into a funnel (reach out, onboard, offer, sign, provision, then won or lost). A background worker advances each enrollment.

• Three offer strategies: a template offer, an AI-drafted offer, or a manual one.

• Quotes: line items across credit, seat, usage, flat, and wholesale billing models, with discounts. Quotes move from draft to sent to accepted, declined, or expired.

• Sending a quote creates its document, and accepting it fans out the matching provisions.

New

• Provision kinds: credits, units, plan, feature, and custom, each with its own quantity, unit, and attributes.

• Per-product connections: each product carries its own endpoint and credentials for delivery.

• Credit grants recorded as their own ledger, separate from cash.

New

• Missions & points — build guided mission paths for new partners; missions auto-complete from real events (first deal registered, first customer, course finished) or manual check-off, and pay out points on a ledger that is fully separate from money.

• Partner tier ladder — define tiers with your own names, ranks, and thresholds (points, customers, won deals). Partners are promoted automatically the moment they qualify — never demoted — and every promotion emits a tier-change event your automations can react to.

• Mentorships — pair experienced partners with new ones; both sides see the pairing in their portal, and assignments emit events for onboarding playbooks.

• Bookable services — publish service packages (training sessions, managed sprints, dedicated support) with hours and credit prices. Partners book from their portal; confirming a booking debits their credit wallet in the same transaction.

• Product usage mirror — your product's metering pushes per-partner usage through a machine-scoped ingest API (idempotent on external reference, safe to retry). Partners and operators see the same read-only numbers; billing stays in your source system.

• Brand variables in materials — tokens like {{brand.name}} render as each partner's approved brand on public share links, so one template ships correctly branded for every partner.

• Materials studio — full redesign: a full-height folder explorer, a document-style canvas you edit inline (headings, text, bullets, stats, quotes, images), live preview, and a variables panel that detects every token and lets you populate sample values without ever baking them into the content.

Improved

• Usage metrics are tenant-defined end to end — every org and product pushes its own metric names and units; nothing is hard-coded to any one kind of product.

• New admin Growth area (Engagement, Services) and portal Missions and Services pages, all permission- and feature-gated.

New

• Configurable commercial models — commission, resale, white-label, and agency programs, each with its own platform gates and defaults.

• Credit wallets and bulk credit packs — partners hold credits distinct from cash balances; packs are purchasable in bulk.

• Price books — per-partner and per-tier pricing with effective dates.

• Plan & billing — subscribe to the platform itself with Stripe-backed plans and a self-serve billing page.

Changed

• Wallets carry an explicit kind (cash vs credit) so ledgers, payouts, and credit spend can never mix.

New

• Customer 360 — one profile per customer: deals, tickets, surveys, health, documents, and activity in a single view.

• Unified event timeline — every domain event (deal moved, document signed, ticket escalated) on one chronological feed.

• Custom metric definitions — define the KPIs your program cares about and track them per customer or partner.

• Custom dashboards — compose metric tiles, charts, and tables into shareable operator dashboards.

New

• Service desk — tickets with public and internal conversation threads, assignment, priorities, and SLA escalation.

• Customer health — scored health per customer with trend history, feeding alerts and playbooks.

• Surveys — CSAT and NPS surveys with response tracking rolled into customer health.

New

• Full OpenAPI reference — every endpoint documented and browsable, generated straight from the running contracts.

• Machine API keys — scoped, revocable keys for server-to-server integrations; the plaintext key is shown exactly once.

• Inbound webhook triggers and outbound webhook actions — external systems can start playbooks, and playbooks can call external systems.

• Copilot — an in-product assistant that answers from your own program data and proposes actions, gated by the caller's permissions.

New

• Folder trees for materials and documents — nested folders with breadcrumbs, scoped per tenant and product.

• Configurable pipelines — define your own stages with colors and semantic flags (initial, won, lost, closed); run multiple pipelines per entity type.

Changed

• Agreements folded into the documents stack — one legal engine for templates, generation, and signing; legacy agreement links redirect.

New

• Document templates — sectioned legal templates with variables, levels, and categories.

• Document generation — create documents from templates or ad hoc; track revisions, statuses, and signatures end to end.

• Document bundles — group related documents (MSA + order form + DPA) and send them as one set.

• Compliance center — subprocessor registry and compliance pages partners can reference.

New

• Visual playbook builder — triggers, conditions, delays, and actions on a node graph with live validation.

• Event triggers — react to anything that happens in the program: deals moving, documents signed, partners joining.

• Action library — send templated email, create tasks, generate documents and invoices, grant credits, call webhooks.

• Run history — every enrollment and step logged and inspectable, with per-step retries.

New

• Referral links & tracking — per-partner links with click and conversion attribution.

• Partner groups & segments — group partners for targeting content, automations, and reporting.

• Training courses — course and completion tracking, ready to gate certifications on.

• Email templates — reusable templated email for partner and customer audiences.

New

• Commission rules & ledger — per-program rules with a full earning ledger per partner.

• Invoices — draft, send, and track invoices with line items and statuses.

• Payout runs — collect approved earnings into payout batches and mark them paid.

New

• Multi-tenant organizations with role-based access — operator, manager, finance, viewer, and partner seats, scoped in the data layer.

• Partner applications & onboarding — application forms and a kanban onboarding flow.

• Deal registration & pipeline — partners register deals, operators run the board.

• Customers, activity feed, and the first operator dashboard.