Design a project with your agent

Describe the work you want to track, and your agent designs and creates a project with the right record types, fields, and links.

When to use this

• You are starting a project that needs more than notes, tasks, and decisions — for example, clients and cases, customers and orders, or jobs and invoices.
• You want records that stay consistent, so you can filter, count, and report on them later.

Before you begin

• A connected AI tool. See Connect your AI tool.
• Permission to create projects in your organization. For a team project, you need to be able to create Org-shared projects.

Steps

1. Tell your agent what you want to track, in business terms. For example: "Set up a Patchnet project to track our consulting clients, their contacts, engagements, and the notes we take on each engagement."
2. The agent loads Patchnet's project design guidance. Depending on how much detail you gave, it builds right away or asks up to three short rounds of questions: what the business does, what you track, and how things connect.
3. Review the proposed design. The agent describes it in plain terms: the record types, the main fields, and which records link to which, such as each engagement belonging to a client.
4. Ask for changes, or approve it. The agent checks the design and creates the project.
5. Ask the agent to add one or two sample records to confirm everything works. Open the project in the browser to check them.

Tips for a good design

• Say what repeats. Things that happen often — visits, calls, time entries, notes — work best as their own record type linked to a parent record.
• List the statuses you use. A fixed list such as open, waiting, closed keeps records consistent and easy to count.
• Say what links to what. "Every case belongs to a client" becomes a link the agent can follow later.
• Start small. Begin with the three or four record types you use every day. You can add more later.

Changing record types later

Only a project Owner can change a project's record types. Ask your agent to propose the change first. Changing or removing a field can affect records that already use it. Patchnet makes the agent acknowledge those records before the change applies, so ask it to tell you which ones first.

If something fails

• The agent cannot create the project — you may have reached your project limit, or you cannot create shared projects. See Limits and Roles and access.
• Your work does not fit a common pattern — describe it in full detail: record types, fields, and allowed values. The agent can build a custom design from a full description.

See also

• How Patchnet Projects is organized
• Work with Patchnet from your AI tool