Most AI tools still work in one mode: you prompt, it responds. Perplexity Computer works differently. It’s an agentic research tool — you define the task, it runs a multi-step process autonomously, and you return to a finished deliverable. That shift is meaningful and surfaces tradeoffs that aren’t obvious until you’re mid-session. Here’s what one session actually looked like.
The Task
I needed internal briefing documents on child savings account programs in six states and cities, including program names, administering agencies, seed deposit amounts, enrollment figures, eligible populations, contacts, and citations. Detailed, specific, and verifiable.
I’ve used Perplexity’s standard research tool quite a bit and find it useful. This project was a reasonable candidate for Computer, their newer feature available to Pro accounts, which manages multi-step research autonomously across parallel threads.
What It Produced
I requested research on three states. Computer launched three simultaneous research threads — one per state — each independently drawing on primary sources: state treasury websites, program annual reports, vital statistics databases, and nonprofit program pages. It organized the findings into a briefing document with an executive summary, state-by-state program sections, a federal policy section on Trump Accounts, population tables, a source list, and two appendices distinguishing active from discontinued programs. It also produced a matching spreadsheet: one row per program and 21 data columns.
The session ran 90 minutes.I ran in it 3 thirty minute segments so I could check and direct the work. I was able to do other work while it ran, reviewing periodically and asking for corrections mid-session.
The output quality justified the time investment. It might have taken me 12 hours to pull all this data together; I got the whole project done in four hours, in one intense day.
What It Required of Me
The preparation mattered more than I expected. An established document structure from prior work gave Computer a clear template to follow. At the start, I scoped the task precisely: named geographies, specific program types, a defined output format, and a clear sense of the audience.
Mid-session, I reviewed outputs and flagged corrections, which added time. I also closely oversaw fact-checking rather than treating citations as verified.
At the end, I asked Computer to reflect on what would have saved time and tokens. It told me that starting with all source documents uploaded would have been more efficient. It also failed to account for the fact that some of those documents were edited versions of work it had produced during the session — they didn’t exist at the start.
Two Things Worth Examining Before You Start
Permissions and system access
Claude‘s integrations are permission-driven. When you connect it to Google Suite, it can be configured to ask before taking actions, such as uploading a file or adding a calendar item. That layer of consent is clear.
Perplexity Computer’s default behavior is different. There was no discussion of access or permissions at the outset, though the documentation notes that it can operate autonomously and take actions on your computer. When it produced a deliverable, it didn’t offer a download — it informed me that the document was now in my Google Drive.
I asked it not to upload anything without checking first, and it agreed. For organizations managing confidential program data or funder relationships, the default behavior warrants a conversation before the first session.
Cost structure and visibility
A live usage tab showed token consumption in real time, but it provided no projected total or estimate for the session as a whole. For a new user, that’s a source of uncertainty — I thought of a shopkeeper I know who called me in a panic after accidentally setting his Google AdWords budget to $900 a month and not knowing how to cancel it: different stakes, same dynamic.
My session used 3,210 of the 5,000 tokens I’d purchased at $0.004 per token ($20) — $12.84 for 90 minutes of parallel research across three states. I’d set my extra tokens to a $20 batch with no auto-renewal, which helped keep me confident about no extra hidden costs.
The unit cost was reasonable for what it produced. The harder question is what the cost looks like at scale.
- Three comparable sessions per week fall between $155 and $193 per month on a pay-as-you-go basis.
- A Perplexity Max subscription at $200/month includes 10,000 monthly credits for autonomous tasks, plus unlimited standard searches and file uploads.
- Pro at $20/month includes 4,000 credits with caps on high-tier queries.
The break-even point depends on session frequency and complexity — but it’s a calculation worth making.
Before You Run a Session
Questions to answer first.
- What data will be in scope, and are you comfortable with the tool’s default access behavior for that data (ie your data privacy) ? This is a governance question, and it’s easier to address before the session than after.
- At what task volume does the per-session cost compare favorably to a subscription, given your actual usage pattern? This is arithmetic, but it requires knowing your usage pattern well enough to be honest about it.
Perplexity Computer is well-suited to research that is multi-source, parallel, and structured around a deliverable format you’ve already defined. It doesn’t replace knowing what you’re looking for or how you want it organized — those decisions still belong to you. What it does is execute the research at a pace and scale that would otherwise take considerably longer.
A Note on Getting Started
Perplexity’s help center is a good starting point. The Computer overview covers how credits work, which apps and services you can connect to, and how Computer differs from standard Perplexity search. The skills guide explains how to create custom instructions that shape how Computer organizes and formats its output — the equivalent of the document template I brought into my session.
One pricing detail worth knowing: Perplexity offers discounted Enterprise Pro plans for nonprofits and government agencies. The rate has varied across sources, so the most reliable path is to visit perplexity.ai/enterprise or contact them directly at enterprise@perplexity.ai to confirm current pricing and eligibility. That tier covers standard Perplexity search and research features, not Computer specifically, but it’s a reasonable entry point for organizations that want to evaluate the platform before committing to a Max subscription.
Working with these tools
If you’re interested in building a Perplexity research space for funder prospecting or donor research, I offer short-term project work — typically five to thirty hours over a month or two — to help organizations set up and test these workflows or to run the research directly. I also work with development staff who want to learn the methodology and build it themselves.
Feel free to reach out if either sounds like a fit: get in touch
Most AI tools still work in one mode: you prompt, it responds. Perplexity Computer works differently. It’s an agentic research tool — you define the task, it runs a multi-step process autonomously, and you return to a finished deliverable. That shift is meaningful and surfaces tradeoffs that aren’t obvious until you’re mid-session. Here’s what one session actually looked like.
The Task
I needed internal briefing documents on child savings account programs in six states and cities, including program names, administering agencies, seed deposit amounts, enrollment figures, eligible populations, contacts, and citations. Detailed, specific, and verifiable.
I’ve used Perplexity’s standard research tool quite a bit and find it useful. This project was a reasonable candidate for Computer, their newer feature available to Pro accounts, which manages multi-step research autonomously across parallel threads.
What It Produced
I requested research on three states. Computer launched three simultaneous research threads — one per state — each independently drawing on primary sources: state treasury websites, program annual reports, vital statistics databases, and nonprofit program pages. It organized the findings into a briefing document with an executive summary, state-by-state program sections, a federal policy section on Trump Accounts, population tables, a source list, and two appendices distinguishing active from discontinued programs. It also produced a matching spreadsheet: one row per program and 21 data columns.
The session ran 90 minutes.I ran in it 3 thirty minute segments so I could check and direct the work. I was able to do other work while it ran, reviewing periodically and asking for corrections mid-session.
The output quality justified the time investment. It might have taken me 12 hours to pull all this data together; I got the whole project done in four hours, in one intense day.
What It Required of Me
The preparation mattered more than I expected. An established document structure from prior work gave Computer a clear template to follow. At the start, I scoped the task precisely: named geographies, specific program types, a defined output format, and a clear sense of the audience.
Mid-session, I reviewed outputs and flagged corrections, which added time. I also closely oversaw fact-checking rather than treating citations as verified.
At the end, I asked Computer to reflect on what would have saved time and tokens. It told me that starting with all source documents uploaded would have been more efficient. It also failed to account for the fact that some of those documents were edited versions of work it had produced during the session — they didn’t exist at the start.
Two Things Worth Examining Before You Start
Permissions and system access
Claude‘s integrations are permission-driven. When you connect it to Google Suite, it can be configured to ask before taking actions, such as uploading a file or adding a calendar item. That layer of consent is clear.
Perplexity Computer’s default behavior is different. There was no discussion of access or permissions at the outset, though the documentation notes that it can operate autonomously and take actions on your computer. When it produced a deliverable, it didn’t offer a download — it informed me that the document was now in my Google Drive.
I asked it not to upload anything without checking first, and it agreed. For organizations managing confidential program data or funder relationships, the default behavior warrants a conversation before the first session.
Cost structure and visibility
A live usage tab showed token consumption in real time, but it provided no projected total or estimate for the session as a whole. For a new user, that’s a source of uncertainty — I thought of a shopkeeper I know who called me in a panic after accidentally setting his Google AdWords budget to $900 a month and not knowing how to cancel it: different stakes, same dynamic.
My session used 3,210 of the 5,000 tokens I’d purchased at $0.004 per token ($20) — $12.84 for 90 minutes of parallel research across three states. I’d set my extra tokens to a $20 batch with no auto-renewal, which helped keep me confident about no extra hidden costs.
The unit cost was reasonable for what it produced. The harder question is what the cost looks like at scale.
- Three comparable sessions per week fall between $155 and $193 per month on a pay-as-you-go basis.
- A Perplexity Max subscription at $200/month includes 10,000 monthly credits for autonomous tasks, plus unlimited standard searches and file uploads.
- Pro at $20/month includes 4,000 credits with caps on high-tier queries.
The break-even point depends on session frequency and complexity — but it’s a calculation worth making.
Before You Run a Session
Questions to answer first.
- What data will be in scope, and are you comfortable with the tool’s default access behavior for that data (ie your data privacy) ? This is a governance question, and it’s easier to address before the session than after.
- At what task volume does the per-session cost compare favorably to a subscription, given your actual usage pattern? This is arithmetic, but it requires knowing your usage pattern well enough to be honest about it.
Perplexity Computer is well-suited to research that is multi-source, parallel, and structured around a deliverable format you’ve already defined. It doesn’t replace knowing what you’re looking for or how you want it organized — those decisions still belong to you. What it does is execute the research at a pace and scale that would otherwise take considerably longer.
A Note on Getting Started
Perplexity’s help center is a good starting point. The Computer overview covers how credits work, which apps and services you can connect to, and how Computer differs from standard Perplexity search. The skills guide explains how to create custom instructions that shape how Computer organizes and formats its output — the equivalent of the document template I brought into my session.
One pricing detail worth knowing: Perplexity offers discounted Enterprise Pro plans for nonprofits and government agencies. The rate has varied across sources, so the most reliable path is to visit perplexity.ai/enterprise or contact them directly at enterprise@perplexity.ai to confirm current pricing and eligibility. That tier covers standard Perplexity search and research features, not Computer specifically, but it’s a reasonable entry point for organizations that want to evaluate the platform before committing to a Max subscription.
Working with these tools
If you’re interested in building a Perplexity research space for funder prospecting or donor research, I offer short-term project work — typically five to thirty hours over a month or two — to help organizations set up and test these workflows or to run the research directly. I also work with development staff who want to learn the methodology and build it themselves.
Feel free to reach out if either sounds like a fit: get in touch