New piRevenue is live for early teams across India, MENA & Southeast Asia. Read the manifesto →
Integrations

What connects today — and what's next.

piRevenue is an early product, and we'd rather tell you exactly what works right now than imply a connector that isn't there yet. Here's the honest state of every integration.

Why we're this specific

Most integration pages oversell. This one doesn't.

It's tempting for an early product to list every integration it plans to eventually support and let the reader assume they're all live. We'd rather lose that first impression than the trust that comes after it. So every connector on this page carries one of three labels — Available, In beta, or On the roadmap — and we keep the labels current as things actually change, not as marketing wants them to read. If a label on this page turns out to be stale, tell us and we'll fix it the same day.

Remi, the piRevenue agent
Remi here. Right now I read deal context from email, voice notes and your calendar — that's how I keep the pipeline current without anyone typing it in twice. WhatsApp is a connector I don't have yet, and I'd rather say so than fake it.Remi · your piRevenue agent
Available

Works today, for every team.

These are how reps get deal context into piRevenue without extra data entry — through the channels they already use.

Available

Email capture (Gmail & Outlook)

Forward a sales thread and the agent extracts a structured deal — contact, value, next step.

Available

Voice-note capture (mobile)

Log a deal by voice between meetings, from the field, in English or Hindi today.

Available

Calendar sync (Google & Outlook)

Meetings on your calendar feed context into the deals they relate to, automatically.

Available

CSV import & export

Bring existing pipeline data in, or take yours out, any time — no lock-in.

In beta

Working, with a limited group of teams.

These connectors exist and function, but we're still hardening them with a small set of early customers before opening them up broadly.

In beta

CRM data import (Salesforce, HubSpot)

Import existing accounts, contacts and deal history from a legacy CRM you're moving away from.

In beta

Slack notifications

Risk flags and forecast changes posted to a Slack channel your team already watches.

In beta

Zapier & webhooks

Connect piRevenue to other tools you already run through custom automations.

On the roadmap

Designed, not yet built.

Including the channel we get asked about most. None of these are live — see the full roadmap for sequencing.

On the roadmap

WhatsApp Business

Messaging-based capture and follow-up, designed but not yet built or live in the product.

On the roadmap

SMS & Telegram

Additional messaging channels under the same human-in-the-loop approval model.

On the roadmap

Accounting (Tally, Zoho Books, QuickBooks)

Closed-deal data flowing into the books without manual re-entry.

On the roadmap

Native mobile app

A dedicated app beyond today's voice-capture experience.

Don't see a tool you rely on? Tell us — integration priority is set by what early teams actually ask for. Get in touch.

How a connector moves stages

Beta means it works, not that it's finished.

A connector moves from "On the roadmap" to "In beta" once it's built and running for a small group of early teams — that's the stage where we find the edge cases a spec never catches. It only moves to "Available" once it's held up across enough real accounts that we're comfortable recommending it to every team on piRevenue, not just the ones helping us test it.

Messaging channels — WhatsApp especially — are the integration we hear requested most often. They're staying on the roadmap deliberately: human-in-the-loop approval has to work as well over a messaging thread as it does today over email and voice notes before we'll call it ready. Shipping it early and quietly walking back a broken experience would cost more trust than the wait does.

Stop feeding the CRM. Watch it feed you.

Give your reps their week back. Start free in an afternoon, or see it on your own pipeline.