Was neu ist​

• Verbesserungen am Dashboard und an den Vertriebs-Workflows

Warum das wichtig ist​

Feature-Updates sollen nicht nur im GitHub-Verlauf verschwinden. Sie müssen auch für Kunden, Interessenten und interne Stakeholder sichtbar werden. Deshalb wird dieser Blog bei Produktupdates mitgepflegt und kann direkt für Kampagnen, Demo-Links und Sales-Kommunikation genutzt werden.

Nächster Schritt​

Live-Demo starten · App öffnen

What's new​

Four partner types with tiered revenue share​

The final rate is confirmed individually between 15–25% on approval.

A lead pipeline instead of a click-link​

Unlike the individual referral link, partner organizations typically work a prospect for weeks before they ever sign up. That's why every approved partner gets their own six-stage pipeline:

Prospect → Contacted → Demo → Trial → Won / Lost

Partners can add prospects manually and advance the stage anytime from their dashboard.

UTM tracking + per-channel attribution​

Every lead — whether added manually or registered via the short link (/sx/<code>) — carries utm_source, utm_medium and utm_campaign, so partners can measure their own campaigns against each other.

Partner dashboard​

At /earn/partners, approved partners see:

• Pipeline overview — lead count per stage
• Conversion rate — won / total leads
• Earned (€) / Pending (€)
• Commission history with payout status
• Personal partner link to share

Type-specific onboarding​

The application asks for partner type, company name and an optional note (client base, certifications, focus market) — admins review it and confirm the final revenue-share rate on approval.

Why it matters​

The M5 (Platform & Scale) growth strategy rests on three levers: individual referrals (Earn-G-1, live since July 7, 2026), partner channels via the Signal Exchange (Earn-G-2), and SEO landing pages (Earn-G-3, also live). Agencies, HubSpot partners and China consultants act as an instant structured sales channel — their existing client base can be tapped without additional marketing spend.

How it works​

1. Apply: /earn/partners → choose partner type, provide company name
2. Approval: admin confirms the revenue-share rate (15–25%)
3. Add prospects: manually in the dashboard or automatically via the partner link
4. Manage the pipeline: update each lead's stage until Won
5. 12 months of revenue share: monthly commission payout once a lead converts to a paying customer

Next step​

Open partner dashboard · Live demo

Was neu ist​

• working unsubscribe link + per-tenant marketing-email toggle

Warum das wichtig ist​

Feature-Updates sollen nicht nur im GitHub-Verlauf verschwinden. Sie müssen auch für Kunden, Interessenten und interne Stakeholder sichtbar werden. Deshalb wird dieser Blog bei Produktupdates mitgepflegt und kann direkt für Kampagnen, Demo-Links und Sales-Kommunikation genutzt werden.

Nächster Schritt​

Live-Demo starten · App öffnen

What's new​

• Crypto invoice for the winner — after auction settlement, the winning bidder can pay their commission directly via a crypto invoice (BTC, ETH, USDT and 150+ other coins via NOWPayments)
• Automatic confirmation — status polling and the IPN webhook confirm the payment and automatically mark the commission as "paid" once it's confirmed on-chain
• Manual confirmation still works — the existing admin button remains available as an alternative for other payment methods (e.g. bank transfer)
• API: POST /api/lead-auction/auctions/{auction_id}/nowpay/create, GET .../nowpay/status/{payment_id}

Why this matters​

A commission model with no real proof of payment is just a bookkeeping number. By wiring into the already-live NOWPayments integration (already used for plan checkout and the signal marketplace), the Lead Auction becomes a feature with a real, traceable money flow — without needing an entirely new payment integration to get there.

Next step​

Start live demo · Open app

Was neu ist​

• Reservoir NFT auction import (#352)

Warum das wichtig ist​

Feature-Updates sollen nicht nur im GitHub-Verlauf verschwinden. Sie müssen auch für Kunden, Interessenten und interne Stakeholder sichtbar werden. Deshalb wird dieser Blog bei Produktupdates mitgepflegt und kann direkt für Kampagnen, Demo-Links und Sales-Kommunikation genutzt werden.

Nächster Schritt​

Live-Demo starten · App öffnen

What's new​

• Sales Cycle Trend — average days-to-close per month, computed from data already tracked (created_at/closed_at), no new instrumentation needed
• Trend indicator — compares the first half of the window against the second half: negative means the cycle is getting shorter (good), positive means it's getting longer
• Line chart in the RevOps dashboard, right next to the existing velocity tile
• API: GET /api/revops/sales-cycle-trend

Why this matters​

A single average hides change over time: a sales cycle that's lengthening over several months is an early warning sign of pipeline trouble — well before it shows up in win rate. The trend makes that visible without sales teams having to enter anything differently.

Next step​

Start live demo · Open app

Was neu ist​

• story-match survey answers + mid-demo email capture

Warum das wichtig ist​

Feature-Updates sollen nicht nur im GitHub-Verlauf verschwinden. Sie müssen auch für Kunden, Interessenten und interne Stakeholder sichtbar werden. Deshalb wird dieser Blog bei Produktupdates mitgepflegt und kann direkt für Kampagnen, Demo-Links und Sales-Kommunikation genutzt werden.

Nächster Schritt​

Live-Demo starten · App öffnen

What's new​

• Account clusters — accounts with two or more open signals over the last few weeks are bundled automatically
• Composite score — higher than the strongest individual score, with a bonus for distinct signal types (three different signals count for more than three of the same kind)
• New "🔥 Account Moments" panel right above the existing "Top Today" list in the Signal Inbox
• API: GET /api/signals/account-clusters

Why this matters​

A sales team working signals one at a time can easily miss the account where several independent indicators are all pointing at buying readiness right now. Account Moments surfaces exactly that clustering as its own prioritized view, without changing any existing signal workflow (scoring, promote, ignore).

Next step​

Start live demo · Open app

What's new​

• Overdue signal — an open deal whose close date is in the past is immediately flagged as "at risk" instead of quietly aging unnoticed
• Slippage signal — Pragma now remembers a deal's original close date; if it's later pushed out, that shows up as its own warning (14+ days of slippage escalates to "at risk")
• Both signals flow automatically into the existing pipeline traffic light, the /api/deals/risk-scores list, and the Kanban cards — no new view required
• The lightweight deals-only board (Kanban without a lead link) now also shows an overdue/slipped badge directly on the card

Why this matters​

A close date that keeps getting pushed back is often the earliest warning sign of a stalling deal — earlier than inactivity or silence become visible. Previously this had to be tracked manually; now the pipeline surfaces it on its own, without sales or management having to learn a new metric.

Next step​

Start live demo · Open app

What's new​

• Gasless bidding for all stablecoin/token bids (USDC, USDT, WETH, DAI) on signal auctions — the bidder signs an EIP-712 message, the platform submits the bid and covers the gas
• Full on-chain transparency preserved — the bid is still correctly attributed to the real bidder's wallet, not the platform's relayer address
• Native POL bidding is unchanged (still a direct wallet flow)
• New smart contract (PragmaSignalAuctionV4) with ERC-2771 meta-transaction support, plus a dedicated forwarder contract
• API: GET /api/blockchain/relay/nonce/{address}, POST /api/blockchain/relay/bid-with-token

Why this matters​

For companies without crypto experience, having to hold POL for gas fees was a real barrier to participating in a signal auction at all — even if they already held USDC or another stablecoin. Gasless bidding removes exactly that barrier: anyone holding a supported token can bid immediately, without also having to buy and manage POL. That makes the Signal Exchange usable for a much broader, non-crypto-native audience — without giving up the trust guarantees of a real on-chain auction.

Next step​

Start live demo · Open app

What's new​

• Expansion score — every won customer is automatically flagged Low/Medium/High upsell potential based on activity, tenure, and whether an open deal is already in motion
• Expansion Potential (€) as a new metric — the sum of average deal value across all high-potential customers
• Expansion table with customer, avg. deal value, last activity, potential badge, and concrete reasons (e.g. "actively engaged & tenured", "multiple deals won")
• API: GET /api/revops/expansion-opportunities

Why this matters​

Churn Risk (S14) answers "who might be leaving?" — but the mirror-image question matters just as much: "who's in the best shape for more business right now?" An actively engaged, tenured customer with no open deal is an overlooked signal — exactly the right moment for a proactive check-in, instead of waiting for the customer to ask first. Expansion Opportunity surfaces that signal before it goes cold.

Next step​

Start live demo · Open app

What's new​

• Monthly MRR bridge — starting MRR, + new, + expansion, − contraction, − churn, ending MRR, all computed from real recurring deals (is_recurring + mrr_amount)
• Net Revenue Retention (NRR) per month and on average — the real metric, not the one-time-deal-value approximation used in Churn Risk (S14)
• Current MRR & ARR plus active paying customer count as headline metrics
• API: GET /api/revops/mrr-bridge

Why this matters​

Churn Risk and Expansion Opportunity show which individual customers are at risk or ready for more business — but the question that actually matters at month-end is the aggregate one: is recurring revenue growing net, or is churn eating back the gains from new logos and expansion? The MRR bridge answers exactly that, in the structure RevOps and finance teams already use for their own reporting.

Next step​

Start live demo · Open app

Was neu ist​

• compact 2x2 dashboard layout matching reference mockup

Warum das wichtig ist​

Feature-Updates sollen nicht nur im GitHub-Verlauf verschwinden. Sie müssen auch für Kunden, Interessenten und interne Stakeholder sichtbar werden. Deshalb wird dieser Blog bei Produktupdates mitgepflegt und kann direkt für Kampagnen, Demo-Links und Sales-Kommunikation genutzt werden.

Nächster Schritt​

Live-Demo starten · App öffnen

What's new​

• Customer risk score — every won customer is automatically flagged Low/Medium/High based on days since last activity plus any upcoming closing/renewal date
• NDR metric as a new KPI tile in the dashboard — baseline revenue from customers acquired before the last 90 days, plus expansion revenue from those same customers, minus revenue from customers currently flagged high risk
• Churn Risk table with customer, total value, last activity, risk badge, and concrete reasons (e.g. "60+ days no activity", "renewal in <30 days")
• API: GET /api/revops/churn-risk

Why this matters​

The existing RevOps panels (Forecast, Funnel, Deals Pipeline) all show how new business is created — but none of them show whether existing business is quietly breaking down. A customer who hasn't replied in 90 days is just as important a signal as a hot new lead. Churn Risk & NDR surfaces that signal before the customer actually cancels — sales and customer success see at a glance who to call today.

Next step​

Start live demo · Open app

Was neu ist​

• Verbesserungen am Dashboard und an den Vertriebs-Workflows

Warum das wichtig ist​

Feature-Updates sollen nicht nur im GitHub-Verlauf verschwinden. Sie müssen auch für Kunden, Interessenten und interne Stakeholder sichtbar werden. Deshalb wird dieser Blog bei Produktupdates mitgepflegt und kann direkt für Kampagnen, Demo-Links und Sales-Kommunikation genutzt werden.

Nächster Schritt​

Live-Demo starten · App öffnen

Was neu ist​

• explain Revenue Signal Network positioning in the empty state

Warum das wichtig ist​

Feature-Updates sollen nicht nur im GitHub-Verlauf verschwinden. Sie müssen auch für Kunden, Interessenten und interne Stakeholder sichtbar werden. Deshalb wird dieser Blog bei Produktupdates mitgepflegt und kann direkt für Kampagnen, Demo-Links und Sales-Kommunikation genutzt werden.

Nächster Schritt​

Live-Demo starten · App öffnen

Was neu ist​

• make Sales Funnel clicks stage-specific, not generic pipeline nav

Warum das wichtig ist​

Feature-Updates sollen nicht nur im GitHub-Verlauf verschwinden. Sie müssen auch für Kunden, Interessenten und interne Stakeholder sichtbar werden. Deshalb wird dieser Blog bei Produktupdates mitgepflegt und kann direkt für Kampagnen, Demo-Links und Sales-Kommunikation genutzt werden.

Nächster Schritt​

Live-Demo starten · App öffnen

Was neu ist​

• rebrand "Revenue Signal Network" to "Lead-Analysierungs-Plattform"

Warum das wichtig ist​

Feature-Updates sollen nicht nur im GitHub-Verlauf verschwinden. Sie müssen auch für Kunden, Interessenten und interne Stakeholder sichtbar werden. Deshalb wird dieser Blog bei Produktupdates mitgepflegt und kann direkt für Kampagnen, Demo-Links und Sales-Kommunikation genutzt werden.

Nächster Schritt​

Live-Demo starten · App öffnen

Was neu ist​

• make KPI dashboard the universal login landing page

Warum das wichtig ist​

Feature-Updates sollen nicht nur im GitHub-Verlauf verschwinden. Sie müssen auch für Kunden, Interessenten und interne Stakeholder sichtbar werden. Deshalb wird dieser Blog bei Produktupdates mitgepflegt und kann direkt für Kampagnen, Demo-Links und Sales-Kommunikation genutzt werden.

Nächster Schritt​

Live-Demo starten · App öffnen

Was neu ist​

• make RevOps Command Center the primary dashboard view

Warum das wichtig ist​

Feature-Updates sollen nicht nur im GitHub-Verlauf verschwinden. Sie müssen auch für Kunden, Interessenten und interne Stakeholder sichtbar werden. Deshalb wird dieser Blog bei Produktupdates mitgepflegt und kann direkt für Kampagnen, Demo-Links und Sales-Kommunikation genutzt werden.

Nächster Schritt​

Live-Demo starten · App öffnen