Shipped, building, and next.
A public, honest look at where piRevenue is today and where it's headed. Priorities shift as we learn from early teams — treat this as directional, not a commitment, and check the changelog for what's already confirmed to be live.
Built in the open, reprioritized in the open.
We're an early product, which means our roadmap moves faster than a mature company's — and that a public roadmap is more useful, not less. We publish what we've shipped, what we're actively building, and what's still just an idea, so a team evaluating piRevenue can see exactly where we stand before they commit. Nothing here is a contractual promise; it's the best current read on where engineering time is going, updated as often as the underlying work changes rather than on a fixed schedule.
Three lists, one honest picture.
"Shipped" ties to entries in the changelog. "Building now" is in active development. "Next / exploring" is under consideration — not yet started, not yet promised. Nothing moves between columns without a matching change in the product itself; we don't relabel an idea as "Building" just because it sounds more finished.
Live today
Everything below is running in the product right now, for the early teams already on piRevenue. Each line has a matching entry in the changelog.
- Live pipeline board with drag-and-drop stages
- Voice-to-deal capture, field and desktop
- Auto-capture from forwarded email (private beta)
- Agentic follow-up drafts with human approval
- Live, self-updating forecast
- Local-currency pricing: India, UAE, Saudi Arabia
- Arabic RTL and Hindi voice capture
- Full keyboard navigation (accessibility)
In active development
Code is being written against these today. Some are already in front of a small group of early teams; none are broadly live yet.
- Deeper CRM data import (Salesforce, HubSpot)
- Slack notifications for deal risk flags
- Bahasa Indonesia and Vietnamese voice capture
- Team-level forecast rollups for RevOps leaders
- WhatsApp Business capture — early design, not live
Under consideration
Nobody is writing code against these yet. They're the ideas we hear most often from early teams, and the ones most likely to become "Building now" next.
- Two-way messaging channels: WhatsApp, SMS, Telegram
- Accounting integrations: Tally, Zoho Books, QuickBooks
- Latin America and Africa currency & language expansion
- Compliance audit exports for regulated industries
- A dedicated native mobile app
Directional, not a promise. WhatsApp and other messaging channels are on the roadmap — they are not live in the product today. Every item that moves to "Shipped" gets its own entry in the changelog.
We build what early teams tell us is actually blocking them.
With a small number of live teams, we can talk to nearly everyone using piRevenue directly. Roadmap priority mostly comes from those conversations — what's slowing a rep down this week, not what looks good on a slide. That's why messaging channels like WhatsApp sit under "Building now" and "Next" rather than "Shipped": we'd rather ship it once it holds up to real usage than announce it early and walk it back.
If something on this page matters to your team, telling us moves it up the list. If something you need isn't here at all, that's useful information too — reach out and we'll factor it in. We'd rather a roadmap shift because a real team told us what's blocking them than because it made a tidier slide internally.
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.