Build a Fundraising Chief of Staff With a dot

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 fundraising coordination brief. Keep every consequential relationship decision, record change, file share, and external message under human review.

Your dot keeps fundraising priorities, meetings, diligence, and follow-up moving between conversations, then brings back decisions that need you.

The job to give your dot

Review the active raise, keep meetings and diligence connected to the right relationships, and return a short list of decisions that need the fundraising lead. 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

Act as my fundraising chief of staff. Use only the connected sources and reviewed Finta context I authorize. Maintain a current view of active investor relationships, upcoming meetings, open diligence questions, promised materials, and next actions. Each morning, return: what changed, what is blocked, what is due, and the three decisions that need me. Separate source-backed facts from inference. Never send a message, change a CRM record, or share a file unless the action is specifically authorized and passes the applicable review.

What the dot should bring back

#	Output	Expected behavior
1	Pipeline movement and stalled relationships	Bring back proactively
2	Upcoming meetings and missing preparation	Bring back proactively
3	Open diligence questions and accountable owners	Keep visible for review
4	Promised materials and due dates	Keep visible for review
5	Decisions, drafts, and actions awaiting review	Keep visible for review

Worked example

A founder is running a 40-investor process while preparing a board meeting. The dot notices that two meetings lack briefs, one promised data-room item has no owner, and a high-fit investor has been waiting three days for an answer. It prepares the briefs, assembles a decision queue, and asks which follow-up should be approved first. 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: Chief of staff is Finta's workflow analogy, not an official OpenAI product category. The dot coordinates the work; the founder, GP, or team retains relationship judgment and authority.

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

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.