---
url: /handbook/start-here/run-a-company.md
description: >-
  How an advisor takes one company from its website to a governed agent, in 9
  steps, with the status of each step.
---

# Run a company in 9 steps

This page follows one company through DutyGraph, from its website to an agent with governed access. It is written for a new advisor or forward-deployed engineer (FDE). You can do most of it from a phone.

::: warning
**Built** means the step works in the app today. **Partial** means part of the step works and the rest is Planned. Do not show a Planned item to a client as available.
:::

## Before you start

1. Open **Settings › Research & AI keys**. Save and **Test** the keys you have: OpenAI, Anthropic (Claude), Exa and Resend. Research needs Exa or a source your operator set up. Email needs Resend; without it, you send private links yourself.
2. For each company, open **Settings › Connections** and select **Approve firm key for this company**. Without it, answers are not polished, the Repo does not read answers into facts and DutyGraph Agent does not answer. Research, the sponsor packet, the kickoff and the team questions work without AI.
3. Optional: open **Settings › Workspace › Phone notifications** and select **Turn on notifications on this phone**.

## The 9 steps

### Add the company and research it

**What you do.** On **Home**, select **Add a company**. Enter the name, website and contact. Select **Add account**, then **Research `<company>` now**. When the run ends, select **Open company workspace** and read the Overview and the Repo.

**Behind the scenes.** DutyGraph creates an account, a contact and an engagement. Research reads public sources. Each finding keeps its source and stays **Inferred** until a person at the company confirms it. Code proposes a company shape: departments and main processes. If research finds nothing, the Overview says so. DutyGraph does not invent a value.

**On your phone.** The dialog, the Overview and the Repo work on a phone.

**Status: Built.** See [Company research](../discovery/company-research.md) and [Company Repo](../discovery/company-repo.md).

### Build the sponsor packet

**What you do.** Select **Prepare first touch for `<name>`**. Edit the questions and the email wording. Select **Save draft** and read the preview.

**Behind the scenes.** Nothing is sent yet. The sponsor's page is a private link that opens without an account. The sponsor checks the company picture, answers the questions, uploads the team list and ticks who joins the executive kickoff. **Here's what we heard** shows the answers back before they send. DutyGraph always keeps the sponsor's own words.

**On your phone.** The composer works on a phone. The sponsor's page is built for a phone first.

**Status: Built.** See [Sponsor packet](../discovery/sponsor-packet.md).

### Send it and get the answers back

**What you do.** Select **Send batch** when email is set up. Otherwise, select **Create a private link**, then **Share…** or **Copy**. When the Inbox shows "`<name>` sent the answers back", open it. Select **Confirm roster & populate org chart**.

**Behind the scenes.** The answers are stored as one record with the team list and the kickoff ticks. DutyGraph notifies you by email, and by a phone notification when the server has push keys. The notice never contains the answers. The roster import shows a preview of problems first.

**On your phone.** The Inbox groups items as **Review**, **Decide** and **Send / Chase** cards.

**Status: Built.** Email needs Resend. Phone notifications need push keys on the server. See [Accounts and Inbox](../advisors/accounts-and-inbox.md) and [Phones and notifications](../advisors/phones-and-notifications.md).

### Plan and schedule the kickoff

**What you do.** Select **Prepare meeting agenda**, then **Approve agenda**. Select **Schedule and invite**, set the date, time and place, then **Send kickoff invitations**. Without email, select **Create links without email**.

**Behind the scenes.** Code builds a standard 2-hour agenda. No AI writes it. Each executive gets a private pre-read page with the agenda and a reply.

**On your phone.** It works. Check the time zone field.

**Status: Built.** "Schedule" means a calendar file (.ics). A calendar connection is Planned. See [Executive kickoff](../discovery/executive-kickoff.md).

### Bring the kickoff transcript in

**What you do.** After the meeting, open **Transcript or additional notes** in the kickoff step. Paste the transcript or your notes. Select **Save outcomes & review team**.

**Behind the scenes.** DutyGraph saves the transcript as evidence. An AI job (OpenAI) drafts each person's role, manager and duties as proposals for you to review. If the job fails, your records do not change.

**On your phone.** You can paste on a phone, but a long transcript is easier on a computer.

**Status: Partial.** Paste only. No audio, no file upload and no speaker detection; these are Planned. The drafts need an OpenAI key. See [Executive kickoff](../discovery/executive-kickoff.md).

### Send asks to each person

**What you do.** Select **Make team questions**, pick the people and select **Save drafts**. In Discovery › **Asks**, select **Review and send**. Without email, select **Create links for all**. When a person answers, select **Accept answer**, then **Draft task cards**.

**Behind the scenes.** Each person answers one question per screen, by voice or by typing, and confirms **Here's what we heard**. One question asks for hours a week as a range. Code reads the range, with no AI. **Draft task cards** uses OpenAI. Each drafted card is **Proposed** until a person accepts it.

**On your phone.** The answer pages are built for phones.

**Status: Built.** See [Team asks](../discovery/team-asks.md) and [Task Cards](../discovery/task-cards.md).

### Find AI opportunities

**What you do.** Open **Opportunities › Your team** to see each person's Task Cards in hours a week. Open **Repo › To review**. For each proposed AI mode, owner or hours answer, select **Accept the mode**, **Accept the owner**, **Accept** or **Not now**. Open **Proposed agents**.

**Behind the scenes.** Code builds this page. No AI call makes a proposal. Code proposes an AI mode with a plain reason, the person who does the work and an owner. Nothing changes until you accept. A proposed agent acts for one named person, inside that person's access.

**On your phone.** The page leads with one line of numbers and a card for each person.

**Status: Partial.** Each proposal needs your accept. Time with an agent is predicted only on the sample companies. See [Opportunities](../opportunities/opportunities.md).

### Turn an opportunity into a governed agent

**What you do.** Once per company, open **Agents › Rules › Set up governance** and load the 6 packs. Then open a proposed agent with **Open draft** and select **Save draft**. The Task Card's owner selects **Start the access request**. Each approver decides in **Agents › Review queue**.

**Behind the scenes.** Code compares the agent's scopes with the owner's access and the rule packs. Each decision goes into the hash-linked ledger. After issue, the gateway checks each call. DutyGraph reads an uploaded access export. It does not connect to the identity system or provision the agent.

**On your phone.** Setup, the builder and the review queue work on a phone. A long access export is easier on a computer.

**Status: Built** for any company after **Set up governance**. On the illustrative distributor sample, the identity and business systems are **Simulated**. Reviewer SSO (single sign-on) is Planned. See [Set up governance](../governance/set-up-governance.md) and [Request a governed agent](../governance/request-a-governed-agent.md).

### Show the person their agent plan

**What you do.** In the builder, find **Share the plan with `<person>`**. Select **Create a private link for `<first name>`**, then **Copy link**, **Share** or **Send by email**. Read the answer from the Inbox and select **Mark reviewed**.

**Behind the scenes.** Code builds the plan from the saved agent. The page reads "Proposed plan · not deployed". The link works for 30 days and opens only this plan. The person answers **This looks right** or **Something's off**.

**On your phone.** The plan page is built for a phone first.

**Status: Built**, by private link only. The person cannot yet open the plan from their own sign-in. See [Share the agent plan](../agents/agent-plan.md).

## Try it on a sample

* **Cobalt Industrial Supply (fictional sample).** On Home, select **Open the sample**. It shows the path from research to Task Cards, Opportunities and the agent builder. It sends no messages, and its main AI features make no AI calls. Governance is not set up on it.
* **An illustrative distributor sample.** It runs the governance path end to end. Its people, access and approvals are illustrative. You start the request as a sample persona and switch personas with **Acting as**.

::: info
**Status.** Steps 1, 2, 3, 4, 6, 8 and 9 are **Built**. Steps 5 and 7 are **Partial**. Identity and business systems on the governance sample are **Simulated**. Audio and file transcripts, a calendar connection, reviewer SSO, live identity connectors and the person's own sign-in to the agent plan are **Planned**.
:::
