Features
Board, budget, docs, and an AI agent crew that builds and tests Salesforce stories — every screenshot below is the product.
AI agent crew
Web, iOS, Android, Oracle, Python, Java, .NET or Salesforce — hand a story to the crew and watch it move through spec, design, build, and test. The agents run on Claude Code or Codex on your own Mac or server — your existing subscription, not per-token API bills. If the Mac is offline, the server picks the work up.
Grounded in your org
The agents read your repository first — modules, endpoints, tables, screens — and, for Salesforce, the connected org’s objects, fields, flows and permissions. Every component in the design says whether it already exists and how that was checked, so nothing is built twice and nothing infeasible gets past the design gate.
Traceable delivery
Every build and test command the agents run is recorded with its result and output. Each deployment — to your staging site, a TestFlight / Firebase build, a dev schema or a Salesforce sandbox — lands on the story with what changed and a link to open it. Production is never a target.
QA with evidence
QA turns the acceptance criteria into positive, negative, edge and permission scenarios, automates and runs them with your test commands, and records screenshots of your preview site (or Salesforce pages) as proof. Failures become bugs that go straight back to Dev — up to the rounds you set.
Git, the safe way
Connect your repository and every story gets its own branch named from its key and title. Dev commits and pushes after each build or fix and opens a pull request when development is done. Nobody but you merges to main.
Branch from develop
feature/FSC-2-kyc-and-compliance-flags-on-financial-account
Import any file
Excel, CSV, Word, PowerPoint, PDF, JSON, Markdown, or plain text. Odd headers, title rows, extra sheets, and "As a / I want / So that" columns are cleaned up and mapped before anything is created — with duplicates and rows that need a look called out.
Your drive, your files
Sign in with Google or Microsoft and pick a folder. Every project gets its own sub-folder with a document per story, every upload, and every QA screenshot. A small cache keeps pages instant and uploads sync in the background — and new projects can't start until Git and storage are connected, so nobody loses a day later.
Search & dashboards
PQL is Pravadh's query language — fields, custom fields, dates like -7d, currentUser(), blocked items and sprints, with ORDER BY. Save searches, share them with the team, and turn any of them into a dashboard widget: counts, pies, bars, lists and created-vs-closed trends.
Dashboards
Start from a ready-made overview — my open work, overdue, blocked, by status, by owner, created vs closed — or build widgets from any saved search. Every number links back to the exact list behind it.
Automation
When an item is created, changes status, changes a field, gets a comment — or on an hourly or daily schedule — and it matches a search, run up to ten actions. Starter templates cover the common ones: bugs into the active sprint, round-robin incidents, overdue nudges.
Service desk
Turn on the portal and customers search your published pages and send requests from your forms — no account needed. Suggested articles appear as they type. They follow replies from a private link or by email, and replying reopens a closed ticket.
BRD-grounded
Put the BRD, solution design and user-story workbook on the project. Create pulses straight from them, and every agent gets the parts of the BRD relevant to its story — plus any pages you link to the pulse. Secrets in files are masked before anyone sees them.
Agent hours
Hours per agent, project and ticket, first pass vs rework, failed steps, bug rounds and engine cost — on every project and in Reports. Find the stories that keep bouncing between Dev and QA before they eat the month.
Goals
Objectives with key results — a number you update, or a search whose items get done. Nest goals, set owners and periods, and watch progress update as stories close.
Plan the people
See points per person per week with overloaded weeks in red, drag due dates on a calendar, start a timer from any item, track estimates against actuals, and let stand-ups and reports create themselves.
Board and money together
Spent, planned, still to come, and budget sit above the board for every space. Board, list, timeline, roadmap, agents, costs, and settings are one tab apart — and the whole space exports to Excel with status, deployments, bugs, and QA results.
Command Center
The copilot watches pulses, dates, hours, and budgets and puts the next move in front of you — the SOW that's over, the pulse that's stalling, the review nobody picked up. Rename it and point it at your own model on Studio.
Pages
Runbooks, playbooks, and meeting notes live beside the board. Everyone types in the same page at once, comments anchor to the exact line, and pulse references show live status.
Costs
Budget is the client cap. Planned is who you loaded. Spent is hours actually logged. Missed hours show up as the plan that should already have hit Spent.
Roadmap
Phases and bars for requirements, build, test, and go-live, with today marked. Drag to re-plan; milestones and tentative work are clear at a glance.
Integrations
One Git host, one test tool, a real Salesforce connection, two-way Jira sync, and Slack or Teams for the events you choose. Collaborators — up to 25 per space — get email on status, owner, bug, and work changes.
The platform
Delivery
FMC-4 is a pulse. REL-1 is an incident. Board, list, timeline, and roadmap all read the same work. Every story opens in its own browser tab with story points, owners, tests, time, and activity — and exports to Word in one click.
AI agent crew
BA writes the spec, Architect designs against your org, Dev builds and deploys to the sandbox, QA tests and files bugs back to Dev — every step a comment on the story. The person who owns the story approves the design and steers.
Money
Paint people on the loading sheet — that is still planned. Spent stays 0 until someone logs time. Burn bands show who is at 60% and who is over. Personal or internal spaces can switch costs off entirely.
Docs
22 templates, tables, checklists, anchored comments, version history, Word/PDF export, and live multiplayer editing. A pulse reference in a page shows its live status, not a stale link. Business plan and up.
Runtime
Logo and colors on every plan. Studio puts it on pm.yourcompany.com with an @company signup lock. Enterprise is a signed Docker image plus a license key — no source on your box, no Pravadh marks.
And the rest
Pulses
The unit of software work. Pulses sit next to epics, tasks, and bugs on the same keys — with story points, owners, and a QA owner.
Story pages
Open a story from the board, list, or timeline and it gets its own browser tab — story, agents, Salesforce, tests, time, and activity. Export it to Word with screenshots.
Agents as owners
When agents are on for a space, Dev and QA agents can be the build or QA owner anywhere a person can — on the board, in imports, and on bugs.
Import
Excel, CSV, Word, PowerPoint, PDF, JSON, Markdown, or text — up to 500 rows and 15 MB. Columns are matched, values cleaned, and duplicates flagged. Business plan.
Exports
A single story exports to a formatted Word document with design, deployments, QA, and screenshots. The whole space exports to Excel with status, story points, deployments, bugs, and QA results.
Collaborators
Add comma-separated emails to a space. They get batched mail on status, owner, bug, and work changes — and admins hear right away when something goes wrong.
Timesheets
Loading people is a plan. Spent stays 0 until hours are logged from the board or Timesheet. No fake burn.
Workflow
Rename statuses, add lanes, and decide which status can move to which. A pulse can be held at Done until sandbox, QA, and statement-of-work checks pass.
Permissions
Viewer, Contributor, and Delivery Lead out of the box; custom sets on Studio and Enterprise. More admins as the plan grows.
Service desk
ITSM on the same keys as software work, with urgency and SLA. Studio and Enterprise.
Guests
Members count toward the cap when they are on a project. Guests stay free.
Notifications
Each person picks which events reach them — status changes, assignments, mentions, comments, due dates, missing time.
Demo spaces
Each one is a real seeded space — pulses, burn, and a couple of Pages docs already in it.
01
Name, email, password. We send a verify link — you sign in after that, not before.
02
Members count toward the seat cap when they are on a project. Guests do not. Studio and Enterprise lock signup to @company.
03
Demo already has FMCG through Energy if Salesforce is part of the mix. Or start empty. Drop any backlog file. Turn on the agent crew for Salesforce stories — or just start delivering.
04
Starter is the board. Business is money and import. Studio adds your copilot and ITSM; agents are a per-project add-on on any plan. Enterprise is a signed image on your metal. Extra seats never unlock a higher tier.