Skip to content

New client engagement letter and filing packet with a submit gate

For a law, accounting or advisory office, it runs the client intake, drafts the engagement letter and checks the filing packet for gaps. A browser agent fills the portal form but stops at the review page until a person approves that exact filing.

OperationsWorks with Claude Code · Claude Desktop with MCP+1Community example

What it does

  • Interviews the new client and saves a checked client record
  • Drafts the engagement letter from your template with marked gaps
  • Checks the packet against your rules for fields, documents and file limits
  • Fills the portal form and reads back what it will send
  • Logs every step and decision

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Sending the letter to the client
  • Submitting the filing on the portal

You decide what happens next.

More about this workflow

This setup is for operators and managers who keep the busywork moving. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it interviews the new client and saves a checked client record. Next, it drafts the engagement letter from your template with marked gaps. Then it checks the packet against your rules for fields, documents and file limits. After that, it fills the portal form and reads back what it will send. Finally, it logs every step and decision. It works with your docs, CRM and web fetch, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before sending the letter to the client and submitting the filing on the portal, and says plainly if a step cannot be undone.

“A human approves anything that cannot be undone.”
Juankia Juankia on GitHub · Oct 9, 2026
Before you startDocs · CRM accessScoped permissionsClaude Code or Claude Desktop with MCP
Explore required tools and model recommendations

Tools and access

  • Google Docs

    Handles the docs part of this job. Grant one folder, create and edit only.

    API required: Yes. Needs a Google Cloud OAuth app with the Docs API turned on.

  • HubSpot CRM

    Handles the crm part of this job. Grant read scopes, plus notes write.

    API required: Yes. Needs a HubSpot private app or OAuth app with the CRM scopes you choose.

  • Web fetch

    Handles the web fetch part of this job. Grant public pages, no logged-in sessions.

    API required: No. Built into most agent harnesses. It reads public pages with no login.

    No sign-up needed

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

GPT-6.1 Sol

Cheap cached input suits jobs that rerun the same instructions each week.

$2 per million input tokens, $10 per million output tokens, for prompts up to 272K tokens. Longer prompts cost $4 in and $15 out.

OpenAI docs as of October 11, 2026

Cheaper backup

Gemini 3.5 Flash-Lite

Low cost for simple data pulls and matching.

$0.30 per million input tokens, $2.50 per million output tokens.

Google docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

required fields and documents

2Your prompt

4 of 4 still empty
Fill these in before you run it: [LETTER TEMPLATE] [FILING RULES: required fields and documents] [JURISDICTION] [FILING PORTAL] You are the New client engagement letter and filing packet with a submit gate agent. For a law, accounting or advisory office, it runs the client intake, drafts the engagement letter and checks the filing packet for gaps. A browser agent fills the portal form but stops at the review page until a person approves that exact filing. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Interviews the new client and saves a checked client record - Drafts the engagement letter from your template with marked gaps - Checks the packet against your rules for fields, documents and file limits - Fills the portal form and reads back what it will send - Logs every step and decision What you must never do without a yes from a person: - Sending the letter to the client - Submitting the filing on the portal Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Claude Desktop with MCP, OpenAI Agents SDK

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Google Docs with its own login, not yours. Grant one folder, create and edit only.
  2. 2Connect HubSpot CRM with its own login, not yours. Grant read scopes, plus notes write.
  3. 3Set up Web fetch. Keep it to public pages, no logged-in sessions.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  6. 6Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: sending the letter to the client, submitting the filing on the portal.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 78.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for New client engagement letter and filing packet with a submit gate](https://trustcase.dev/badge/new-client-engagement-letter-and-filing-packet-with-a-submit-gate.svg)](https://trustcase.dev/use-cases/new-client-engagement-letter-and-filing-packet-with-a-submit-gate)
HTML
<a href="https://trustcase.dev/use-cases/new-client-engagement-letter-and-filing-packet-with-a-submit-gate"><img src="https://trustcase.dev/badge/new-client-engagement-letter-and-filing-packet-with-a-submit-gate.svg" alt="Trustcase trust score for New client engagement letter and filing packet with a submit gate" height="20"></a>

Other workflows that use the same tools

  • Proposal first draft

    Sales. Builds a proposal from your template and the discovery notes.

  • Competitor watch

    Marketing. Keeps an eye on what competitors change on their sites.

  • Ideal customer profile builder

    Sales. Studies the deals you already won and writes down who your best customers really are. You get clear filters for new leads and a list of warning signs.