Skip to content →
OppulenceOppulence
ProductFeaturesUse casesPricingResources
Sign inStart for free
See how it works
Sign inStart for free
ProductsFeaturesUse casesHow it worksPricingDownloadResourcesSecurity

Product

The Oppulence assistantOppulence WebOppulence DesktopOppulence VoiceDownload

Features

Follow-ups and commitmentsRelationship contextWork that needs youReview and approveMeeting captureLive notes

Use cases

Founder-operatorAccount managementMeetingsResearch and verification
Sign inStart for free
Loading

Keep the context. Take the next step.

Start on the webExplore the assistant
Oppulence

Product

ProductsThe Oppulence assistantWebDesktopVoicePricingDownload

Features

Follow-ups and commitmentsRelationship contextWork that needs youReview and approveMeeting captureLive notesLocal vaultAgents

Use cases

Founder-operatorAccount managementMeetingsResearch

Resources

Resource hubGuidesChangelogIntegrationsSecurityCompareAnswer hubBlogCustomers

Compare

CRMMeeting notesInboxAI assistants

Company

ContactPrivacyTermsResponsible disclosureDiscord
Oppulence

© 2026 Playbook Media · Oppulence

Oppulence is an email-first personal assistant built around your relationships. It connects email, meetings, and notes so you can review the context, prepare a reply, and follow through.

OppulenceWeb, Desktop, and Voice

One assistant,
wherever you work.

An email-first personal assistant that brings your relationships, meetings, and notes into the work at hand. Find the context, prepare the reply, and keep the next step in view.

Start on the webExplore the assistant
  1. 1. Recall the meeting

    Find the conversation behind the question.

  2. 2. Prepare the reply

    Review the draft beside its sources.

  3. 3. Follow through

    Approve the action and check the result.

Today
Concept preview
Needs youStateSourceNext step
Customer reply
Review
2 emailsCheck the prepared draft
Meeting follow-up
Approve
MeetingReview two next steps
Relationship match
Confirm
Voice noteChoose the right person
Rollout schedule
Waiting
EmailAwaiting a response
Explore Web

Showing Web

A preview of the connected experience in development.

Gmail
Calendar
Slack
HubSpot
Meetings

Start on the web. Add what you need.

Your work moves between a browser, your computer, and conversations. We are building one assistant that keeps the people, context, and next steps connected across all three.

Oppulence Web

Your work, organized.

Start in your browser. Review relationships, source material, prepared work, and approvals without installing an app.

Oppulence Desktop

Your full working environment.

Add local files, a Markdown vault, an embedded browser, keyboard navigation, and native tools for deeper work.

Oppulence Voice

Your assistant within reach.

An optional companion for dictation, meeting recording, and thought capture. The shared Ask Oppulence connection is in development.

The next email should remember the last meeting.

A customer asks about the rollout. You discussed the deadline on a call, sent the plan last week, and wrote down one concern afterward. We are bringing that context beside the reply, with the source of each detail clear.

  1. 1. Before the meeting

    Bring prior emails, previous meetings, relevant notes, and open questions into a short brief.

  2. 2. During the conversation

    Capture with appropriate consent and a visible recording indicator. Stay focused on the person speaking.

  3. 3. After the call

    Review the transcript, correct speakers and relationship matches, and choose what becomes shared context.

  4. 4. When the next email arrives

    Prepare a reply with the relevant meeting and earlier correspondence beside it. Check the sources and uncertain claims.

  5. 5. Until the work is done

    Approve the next step, check its result, and keep the request visible while you wait for a response.

In development: the full journey from Voice capture to relationship history, plus shared Web and Desktop navigation. The previews show how these pieces will fit together.

The context behind a better reply.

A useful assistant connects what was said to what happens next. Source review and approval are the foundation of the email-first experience we are building.

Bring the history into view

Find the relevant conversation, meeting, and open question before you prepare a reply.

Review the next step

Read the proposed reply beside its sources. Correct it, approve it, or leave it for later.

Find the relationship.

Start for free

The memory behind the assistant.

Swipe to explore

Commitment register
5 rows
#CompanyScoreStatusContact
1Acme Corp94
Confirmed
Maya Chen
2Northstar88
Confirmed
Daniel Park
3Meridian72
Review
Eva Chen
4Forma91
Confirmed
Sam Rivera
5Brightwave86
Confirmed
Morgan Lee
New row

Follow-ups and commitments

Keep your promises and outstanding requests visible, with the original conversation attached.

Acme Corp
Needs you
  • Outbound promise
    Open
    Security review by Friday
  • Inbound promise
    Kept
    Signed order form
  • Change
    At risk
    Champion went quiet for 9 days

Relationship context

Bring emails, meetings, participants, and open questions into one relationship history, with the sources available to inspect.

Today
Concept preview
Needs youStateSourceNext step
Customer reply
Review
2 emailsCheck the prepared draft
Meeting follow-up
Approve
MeetingReview two next steps
Relationship match
Confirm
Voice noteChoose the right person
Rollout schedule
Waiting
EmailAwaiting a response

Work that needs you

Review open requests, missed dates, and conversations waiting on a response, with a reason for each proposed next step.

Follow-up draft

Hi Maya — confirming the security review we discussed lands Friday. Let me know if the window still works on your side.

Source: thread from Mar 14 · Acme Corp

Review and approve

Email, Slack, calendar, and CRM writes are proposed, checked, and held until a person approves them.

  • Approval before send

    Gmail, Slack, and HubSpot writes are drafted and held for a person.

  • Inspect the source

    Open the email, meeting, or document behind a claim before relying on it.

  • Local when needed

    Meeting audio, vault notes, and on-device transcription can stay on the desktop.

  • Sharing by choice

    The shared experience must preserve explicit sharing: signing in is not consent to upload private notes.

  • Bring your own keys

    Use your model provider keys where the desktop stack supports it.

  • Documented self-host path

    The desktop coworker stack runs on your machine today; backend deployment is documented for teams who need it.

Your context. Your decision.

Inspect the sources, keep private notes distinct from shared evidence, and review proposed actions. Understand what stays local and what a connected provider receives.

Security overview
  • Security overviewHow local vault, sync, and connector tokens are handled.
  • Responsible disclosureReport a vulnerability through the published channel.
  • PrivacyWhat we collect when you sign in, and what can stay on the desktop.

The things people ask before they start.

These are the questions that stop a careful team. The answers are the product constraints, not slogans.

Oppulence is an email-first personal assistant built around your relationships. It brings together conversations, meetings, and notes to help you understand the context, prepare a reply, and follow through. We are connecting Web, Desktop, and Voice around one assistant and one history of actions.

No. Start with Oppulence Web in your browser. Desktop adds local files and native tools. Voice is an optional companion for dictation, thought capture, and meetings. Desktop and Voice have separate installers today.

Desktop includes email, local notes, meeting capture, live notes, background tasks, and an embedded browser. Web and the shared API provide relationship views, assistant work, and approval flows, subject to rollout. Common Today, Inbox, People, Library, and Activity navigation, the full web inbox experience, Ask Oppulence in Voice, and the complete Voice-to-relationship handoff are planned improvements.

You can keep using Gmail alongside the connected assistant. Desktop also has an email view. Voice can dictate into other apps, including Outlook, but dictation does not connect that app as a relationship data source. Outlook is not in the current first-party relationship connector set.

The governed action flow holds external sends and writes for your review. Check the proposed content and sources before approving. A prepared draft, an attempted action, and a verified result are different states.

A private note is your perspective, not evidence that a customer said something. The shared experience is being built to distinguish source evidence, private notes, and assistant inferences, with uncertain identities and interpretations open to correction.

It depends on the capability and provider you select. Local transcription can keep audio on your device; a cloud model receives content needed for its request. The connected experience must preserve explicit artifact sharing. Signing in is not consent to upload every private note. See the privacy and local-data guides for current behavior.

The public relationship connector catalog covers Gmail, Google Calendar, Slack, and HubSpot. Desktop also supports local notes, meeting imports, and MCP tools. Availability and permitted actions depend on the connector and rollout stage.