Direct answer: Give a dot an ongoing fundraising responsibility, the smallest useful set of connected context, and clear rules for what it may do. OpenAI's dots are always-on agents in ChatGPT, powered by GPT-6 Astra, with their own cloud computer and the ability to keep making progress between conversations. Pair that continuity with reviewed Finta relationship and deal context to produce a persistent diligence coordination queue. Keep every consequential relationship decision, record change, file share, and external message under human review.
Your dot keeps questions, source materials, owners, and review decisions connected across a multi-week diligence process without replacing legal, financial, or investment judgment.
The job to give your dot
Coordinate diligence questions, source documents, owners, and reviewed answers across a multi-week process. The useful shift is from asking an occasional question to assigning a continuing responsibility with a recognizable output, cadence, and approval boundary.
| Layer | What it contributes | What remains controlled |
|---|---|---|
| Finta | Relationship records, pipeline state, approved documents, meeting context, and recorded commitments | Finta remains the source of truth for the fundraising workflow |
| Your dot | Ongoing research, synthesis, drafting, scheduled review, and progress between conversations | It can use only the apps, accounts, and permissions you choose to connect |
| You | Judgment, corrections, consent, approval, and the final decision | You set Custom Rules and review consequential work before it affects people or systems |
Choose how your dot receives Finta context
Dots use ChatGPT's plugin ecosystem and connected apps. In ChatGPT, open Settings > Plugins, review the apps available to your account, and grant only the permissions this job requires. If Finta appears as an available plugin or approved connection, confirm the intended Finta organization and begin with retrieval. If it does not appear, use a reviewed Finta brief, approved Share Page, selected document, or export as a deliberate handoff. Do not treat a general ChatGPT or MCP connection as proof that every dot can access Finta.
- Plugin path: Use only when Finta is visible in the dot's available tools and the requested permission matches the job.
- Reviewed handoff: Provide the smallest useful Finta artifact when a direct connection is not available.
- Browser or computer access: Enable only when needed. Local-computer access starts off and requires a separate user decision.
Set up the responsibility
- Create your first dot on desktop. Open dots in ChatGPT from the desktop app or desktop web. Initial creation is not available on mobile.
- Connect only the required apps. Confirm the exact accounts and permissions in ChatGPT's Plugins settings.
- Describe the job. Name the responsibility, audience, cadence, expected artifact, and decisions that must come back to you.
- Write Custom Rules. Require sources, block unsupported outreach, and specify when the dot must ask first or hand work back.
- Start with a read-only run. Ask the dot to show the information it can access before it interprets or drafts.
- Add a schedule only after review. Once the first result is useful, set the recurring cadence and define the stop condition.
- Follow the work in Activity View. Inspect progress, add context, redirect the task, pause it, or stop it.
Copy this responsibility brief
Coordinate this investor diligence process using only the permitted document sources and reviewed Finta context. Build a queue with each question, the supporting source, the accountable owner, the current evidence state, the draft answer, and the next review step. Use present, missing, unverified, and not applicable as explicit states. Never imply legal, financial, tax, compliance, or investment completeness. Do not share a file or send an answer without scoped authorization.
What the dot should bring back
| # | Output | Expected behavior |
|---|---|---|
| 1 | Question and evidence state | Bring back proactively |
| 2 | Supporting source and observation date | Bring back proactively |
| 3 | Accountable human owner | Keep visible for review |
| 4 | Draft answer and unresolved risk | Keep visible for review |
| 5 | Approval and delivery status | Keep visible for review |
Worked example
A lead investor opens a 27-question diligence list. The dot maps 18 questions to current room materials, finds four answers that need management confirmation, marks three items missing, and identifies two as not applicable. It prepares a review pack while the founder and counsel retain responsibility for the response. This is an illustrative workflow, not a claim of a measured customer result.
Use the underlying Finta method
This page owns the dots working experience. The durable operating method remains in the related Finta Workflow. Use that method for review criteria and failure states, then bring the reviewed context into the dot only through a connection or handoff available to your account.
Controls that make the workflow trustworthy
- Proactive research is read-only. OpenAI says background research cannot send messages, change plugin content, or control a browser or computer. Any follow-up action goes through the normal rules and checks.
- Custom Rules set your preferences. You can allow supported actions, require approval, block actions, or require a handoff within OpenAI's built-in safeguards.
- Auto-review checks consequential actions. A separate system reviews planned actions against instructions, Custom Rules, and safety requirements.
- Activity View keeps the work visible. You can follow, correct, redirect, pause, or stop ongoing work.
- Dots can still make mistakes. Reopen the source and review consequential work before it affects a relationship, record, file, or account.
Workflow boundary: A dot can analyze permitted documents and update work as evidence changes. It does not certify a data room, perform complete diligence, or replace legal, financial, tax, compliance, or investment judgment.
Availability and limits
As of 2026-09-29, dots are rolling out to ChatGPT Pro and Business Premium users in eligible markets. Enterprise, Edu, and Healthcare workspaces can access a beta when an admin enables it, and it is off by default. Access, plugins, plan limits, regions, and interfaces can change. OpenAI says the first dot is included with eligible Pro and Business Premium plans, but launch-period usage terms should not be treated as permanent pricing.
- Finta is not a proprietary investor, LP, company, or property database.
- A relationship path, reply gap, or engagement signal does not establish interest, consent, or permission to contact someone.
- Connected data can be incomplete or stale. Require sources and observation dates.
- Do not paste passwords, access tokens, unrestricted exports, or confidential material outside the approved task boundary.
- Plugin access varies by plan, region, workspace policy, and the permissions granted to the selected account.
Start with one responsibility
Create your dot in ChatGPT, choose one recurring job, and run the responsibility brief with the smallest useful set of permitted context. If you use a reviewed handoff, start with Finta Networks, Finta Documents, or an approved Finta Share Page.
Sources and editorial note
- OpenAI: Introducing dots
- OpenAI Help: Getting started with your dot
- OpenAI: Safety, security, and privacy in dots
- OpenAI plugins and connected-app examples
- OpenAI DevDay 2026 recap
Research updated 2026-09-29. Written and reviewed by the Finta Editorial Team. OpenAI owns the dots name and product. Finta is not claiming sponsorship, endorsement, or a native dots integration. Verify the availability, connections, and controls presented to your own account before relying on this workflow.