transcript-to-action-plan-client-email
Skill1 starsChanged 3 months agoMITView on GitHub
Turn a client meeting transcript into the professional follow-up email a Maryland SBDC consultant posts into Neoserra as the record of the meeting, with Next Steps, Notes, Things We Have Accomplished Since Our Last Meeting, and Relevant Links sections. Use whenever someone pastes, attaches, or describes a client consultation transcript, call recording, or meeting notes and wants a client-facing recap and action-plan email drafted from it — this is the client-facing deliverable, not internal meeting notes and not a re-engagement email to a lapsed client. Also trigger when asked to identify or flag Neoserra milestones from a conversation (certifications like 8(a), MBE, WBE, DBE, EDWOSB, WOSB, MDOT, SDB; business sales or expansion; legislative letters; AI tool adoption or AI-driven improvement; survey responses), to draft an SBDC next-steps or action-plan email, to summarize a client meeting into next steps and accomplishments, or to map a meeting to Neoserra/Nexus milestone and counseling dropdown selections.
In this repository14 other files it gives its agents.
- business-model-canvas-helperSkill
- business-service-provider-referral-engineSkill
- client-follow-up-and-reengagementSkill
- mdsbdc-debt-helperSkill
- proposal-buddySkill
- sbdc-grant-advisorSkill
- sbdc-marketing-plan-generatorSkill
- sbdc-success-storySkill
- sbdc-training-newsletterSkill
- sbdc-underwriter-and-capital-coachSkill
- sbdc-workshopsSkill
- tam-sam-somSkill
- transcript-to-meeting-notesSkill
- transcript-to-sopSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 13 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
If no transcript or file is attached yet, ask for it before drafting anything.
- Distinctive: line 20
Keep the tone professional throughout, and skip emojis — this is a document that becomes part of the client's official record.
- Very specific: line 149
Leave an unknown date as [unknown], with a rough year where the file implies one.
- Distinctive: line 150
Put partial, inferred, or ambiguous ("Potential") milestones in a separate table for Consultant Verification — never mix them with …
- Distinctive: line 151
Keep a running table of positive client testimonials found in the file — useful later for a success story.
- Distinctive: line 188
Every "never" in this skill, in one place:
- Distinctive: line 190
Never guess a missing client ID code — use the literal "Client ID".
- Distinctive: line 191
Never paraphrase a milestone category, and never file something that doesn't map to one as a milestone — it goes in Notes.
- Distinctive: line 192
Never put a potential or inferred milestone in the client email — it goes in the note to the consultant.
- Distinctive: line 193
Never put a client win in the milestone section, or carry it into the Neoserra mapping as a milestone.
- Distinctive: line 194
Never fetch SDAT / Maryland Business Express status automatically.
- Distinctive: line 195
Never deliver the Neoserra mapping as dropdowns alone — always with the full narrative.
- Distinctive: line 196
Never invent Prepare hours.
- Distinctive: line 197
Never use emojis, and never dump chronological notes in place of the template's sections.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Transcript to Action Plan & Client Email
This email is not just correspondence — it's the record that gets posted into Neoserra, and the milestones flagged in it are the same categories SBDC reports up to funders and government partners. A vague summary or a missed milestone isn't a formatting slip; it's data that never gets counted. Read the transcript closely and write like the email is the file.
When to use it — and when not to
- Use it for a client meeting transcript, recording, or notes that should become the client-facing follow-up email; or for a Neoserra client file whose milestones need pulling out (see the client-file mode below).
- Not for internal meeting notes (use
transcript-to-meeting-notes), a re-engagement email to a lapsed client (useclient-follow-up-and-reengagement), or turning a walkthrough into a procedure (usetranscript-to-sop). - If no transcript or file is attached yet, ask for it before drafting anything.
Draft the email
Write it as the Maryland SBDC consultant, in first person, to the client. Summarize the meeting in detail and sort what was discussed into the right section below — don't just dump chronological notes. Vary the paragraph phrasing to fit the tone of the actual transcript rather than reusing the same boilerplate every time; a terse, transactional meeting and a long exploratory one shouldn't read identically.
Keep the tone professional throughout, and skip emojis — this is a document that becomes part of the client's official record.
Output template
Subject: SBDC Next Steps - [Client ID Code] - [Client Company Name]
Hi [Client Name],
[Personal opening: two or three sentences about this client and this
meeting -- see "The opening paragraph" below]
Below are my notes, along with some helpful documents and links. If you
have any questions, please let me know. When you are ready to schedule
your next appointment, use the link in my signature block below.
Next Steps-
[Concrete next actions for the client's business]
Notes-
[Detailed checklist(s) of any processes, methods, tactics, advice, or
strategies discussed]
Things We Have Accomplished Since Our Last Meeting-
[Milestones — see list below]
[Other Progress Worth Celebrating-
Only when the client-wins toggle is on — see below]
Relevant Links from Our Meeting-
[Link title]
[URL]
[Consultant Signature Block]The opening paragraph
The opening is what makes the email read like the consultant wrote it rather than a form. Replace a stock "It was nice speaking with you today" with two or three sentences specific to this client and this conversation:
- Open on something real from the meeting: the progress they reported, the decision they reached, the problem they came in with, or what they are working toward. Name it concretely ("Congratulations on landing your first catering contract" beats "Great progress!").
- Where it fits, acknowledge the effort or the moment, such as a hard month, a big step, or a first meeting, in plain words.
- Then hand off to the notes with the standard housekeeping lines from the template.
Keep it warm but professional: no exclamation-point streaks, no flattery, no emojis, and nothing the transcript does not support. Never invent a detail, a feeling, or a personal fact to make it warmer. If the meeting was short and transactional, one honest sentence about what you covered is the right amount of warmth. Vary the wording from client to client; if every email opens the same way, the opening has failed.
For the subject line, pull the client ID code and company name from the transcript when they're available. If the ID code isn't in the transcript, use the placeholder "Client ID" rather than guessing one.
Next Steps — the client's concrete next actions for their business.
Notes — focus on what the client should do next, expressed as detailed checklists of any processes, methods, tactics, advice, or strategies that came up in the meeting. This is the section that carries the actual consulting content; don't compress it into a one-line summary.
Things We Have Accomplished Since Our Last Meeting — milestones only (see below). The source instructions named this section two slightly different ways — "Accomplishments Since Our Last Meeting" in one place, "Things we have accomplished since our last meeting" in the worked example — and listed the four sections in a different order than the example used. This skill follows the worked example's wording and order (Next Steps, Notes, Things We Have Accomplished Since Our Last Meeting, Relevant Links) since that's the literal text meant for posting; flag this for Brandon if he prefers the other phrasing.
Only confirmed milestones go in the client email. Partial, inferred, or "Potential" ones go in a short note to the consultant after the email, for them to verify — never mixed into the client-facing section. A first meeting usually has no accomplishments yet; say so plainly instead of leaving the section blank or padding it.
Client-wins toggle (off by default)
By default the accomplishments section is strictly Neoserra milestones. That is a compliance guardrail: the email is posted as the record, and the milestones in it are what SBDC reports upward. The trade-off is that real client progress that is not a Neoserra category (getting an EIN, opening a business bank account, a first sale, launching a website, finishing a course) drops out of the email, and the email reads more generic for it.
The toggle brings that progress back without touching the milestone section:
- Turn it on when the consultant asks for it in any words: "include client wins", "all milestones", "celebrate their progress", "add the things they got done", or by picking the client-wins letter from the follow-up menu. Once it is on, keep it on for every later email in the same conversation until the consultant turns it off.
- When it is on, add a separate section directly after the milestones: Other Progress Worth Celebrating-. List the client's confirmed accomplishments that do not map to a milestone category, each in one plain, warm line that credits the client ("You got your EIN and opened your business checking account — that's the groundwork done."). Write it in the same first-person voice as the rest of the email.
- Match milestones first. Anything that maps to a Neoserra category still goes in the milestone section, worded exactly. Registering a new business, for example, is usually Business Established, not a client win. Only what is left over goes in the new section, so nothing is double-counted. Anything you flagged as a potential milestone for the consultant to verify (a first sale that may be Change in Sales, say) stays in that note; it is never a client win, in the email or in the menu option that previews the wins.
- Confirmed only. The same rule as milestones applies: things the client said they plan to do, or that you are inferring, stay out. If nothing qualifies, omit the section rather than padding it.
- When it is off, those accomplishments can still appear as context in Notes, but never as a list of wins.
The new section is part of the client email, not the Neoserra mapping. Never carry its items into the milestone dropdowns or the Nexus narrative as milestones.
Relevant Links from Our Meeting — any resources, documents, or URLs that came up, each with a title and the link. Speech-to-text often garbles names, so resolve misheard people, programs, and organizations to the real ones before linking. When the client's entity documents came up, link their own SDAT entity page.
Check Maryland good standing (counselor click-through)
Automated good-standing lookups against SDAT / Maryland Business Express are blocked by Cloudflare, so don't try to fetch the status. Instead, surface the SDAT Business Entity Search link so the consultant can click it and read the Status field themselves:
- Maryland Business Entity Search — https://egov.maryland.gov/BusinessExpress/EntitySearch
When the consultant confirms the business is not in good standing (Forfeited, Not in Good Standing, or Dissolved), add a Next Steps line telling the client to resolve it — usually by filing the overdue Annual Report / Personal Property Return and paying any late penalties through Maryland Business Express (businessexpress.maryland.gov). If the business is in good standing, or has no registered entity yet, add nothing.
Milestones
Anything in the transcript that matches one of these gets pulled into the accomplishments section, worded plainly rather than left in transcript jargon. This list is not illustrative — it mirrors Neoserra's actual milestone categories, so match it exactly rather than paraphrasing a category into something close:
- 8(A) Certification Obtained
- Accepted Agreement Text
- Bought Business
- Business Established
- Business Expansion
- Business Start Impact
- Change in Export-related Staff
- Change in Exports
- Change in Full-Time Staff
- Change in Part-Time Staff
- Change in Profits
- Change in Sales
- Changed Legal Form
- Client Legislative Letter(s)
- DBE Certified
- EDWOSB Certification Obtained
- Entered New Foreign Markets
- Local Disadvantaged Business Certification
- MBE Certified
- MDOT Certification
- Potential to Start a Business Within the Next 6 Months
- Reopened Business
- Responded to SBA Impact Survey (CY 2015)
- Responded to Survey
- SDB Self-certified
- Sold the Business
- Strategic Growth Plan Success
- Success Story
- Temporarily Altered Business
- Temporarily Closed Business
- Trademark Obtained
- WBE Certified
- WOSB Certification Obtained
- AI Tools Implemented — the client has implemented at least one AI tool after receiving SBDC guidance
- AI Improvement Realized — the client reported a concrete improvement (revenue growth, cost savings, time savings, improved customer satisfaction, etc.) after implementing AI
This list is not exhaustive of everything a client might accomplish, but it is the exhaustive list of what Neoserra tracks — if something the client did doesn't map to one of these, it belongs in Notes, not in the milestones section.
Mining milestones from an uploaded Neoserra client file
Sometimes there is no transcript — the consultant uploads a Neoserra client record (an "All Activity by Client" report or a Survey Response report, usually PDF, sometimes Word) and wants every milestone and capital infusion pulled out of it. Handle that as a document-extraction mode of this same milestone work, matching against the milestone list above (the SBA and Neoserra definitions behind those categories are in references/milestone-mapping-reference.md).
Produce a copiable table with one row per milestone and these columns: Milestone, Date achieved or reported, Dollar value, Increase amount (for changes in sales, profits, staff, or exports), New hires (count, for staffing changes), and Source citation. The citation can be a direct quote, a section reference, or a general file reference tied to the client-file record date. Rules:
- One row per milestone. If a single event carries more than one milestone, list them as separate rows.
- Leave an unknown date as
[unknown], with a rough year where the file implies one. - Put partial, inferred, or ambiguous ("Potential") milestones in a separate table for Consultant Verification — never mix them with confirmed ones.
- Keep a running table of positive client testimonials found in the file — useful later for a success story.
- Parse a long PDF ten pages at a time: extract the table for pages 1–10, give it to the consultant for review, then ask whether to continue through the next ten pages. Repeat until the file is done.
After the email: offer a follow-up menu
Once the draft email is delivered, present a short lettered table of follow-up options for the consultant — the additional deliverables that would actually help this client, drawn from what came up in the transcript. Keep it tight: aim for six to eight letters total, not an exhaustive catalog. Assign each option a letter so the consultant can continue the conversation by just naming a letter.
Build the menu from three kinds of options.
1a. Always-present options — put these three in every menu, no matter what the meeting covered:
- Capital-readiness scorecard — score the business on what a typical SBA 7(a) lender scrutinizes (proof of demand, pricing, market category, letters of intent, management, DSCR) and turn it into a plain-language "here's what to fix before you approach a lender" list. It works for investor pitches too. Offer it even when little financial came up — frame it as a proactive readiness check. For a deeper, file-backed version, hand off to the Underwriter and Capital Coach skill.
- Recommended training plan — a top-ten list of SBDC webinars matched to what this client needs, each with the date and a one-line reason, sequenced in the order they should take them. If the consultant supplies the current Neoserra Training Events export, use it — and remind them to export the next six months, not the fiscal year, or it will recommend events that already passed. Offer a client-facing version reformatted as an email they can send directly.
- Maryland good-standing check — always give the SDAT Business Entity Search link (https://egov.maryland.gov/BusinessExpress/EntitySearch) so the consultant can verify the entity's status (see the good-standing section above). If they confirm it's Not in Good Standing, Forfeited, or Dissolved, that becomes a Next Steps line.
1b. Conditional standing options — include only when the transcript supports them:
- Funding and grant search — when the client needs capital or grant funding. When the Maryland Community Business Compass connector is available, run the search live through it — its funding-search and program-recommendation tools cover ~700 Maryland programs and can match by county, industry, and business profile — rather than listing programs from memory. For grant-readiness plus matched opportunities, hand off to the Funding Match / grant finder skill.
- Add client wins — when the toggle is off and the transcript contains confirmed client progress that is not a Neoserra milestone. Name one or two of the wins in the option so the consultant can see what they would get. Picking it turns the client-wins toggle on and re-issues the email with the Other Progress Worth Celebrating section.
- Hand off to another SBDC Toolkit skill — when the meeting points squarely at one, name it: Success Story (a fundable win worth writing up), Business Model Canvas Helper (early-stage client with no canvas yet), Proposal Buddy (government contracting, bid/no-bid), Marketing Plan Generator, or TAM-SAM-SOM. Only surface the one or two that genuinely fit.
2. Chaotic-good options — always generate two or three deliverables invented from this specific transcript, not pulled from the standing list: the sharp, non-obvious things this particular meeting calls for (a 30-day sprint with a Gantt chart, a competitor teardown, a one-page pitch aimed at a specific lender, a hiring plan — whatever the conversation actually implies). This is where the skill earns its keep, so keep these fresh and client-specific rather than defaulting back to the standing options.
3. Two required options, always present:
- One that maps the meeting to Nexus/Neoserra. When the consultant picks it, produce BOTH (a) the exact milestone + counseling dropdown selections to enter, AND (b) the full third-person Nexus/Neoserra counseling session narrative described below — never the dropdown table alone. Producing only the dropdowns is a drift error.
- One explicitly framed as "high value, minimum effort."
Neoserra / Nexus counseling narrative
The Neoserra-mapping option must always include a substantive, third-person, audit-grade session narrative that would survive an SBA Nexus / Form 641 review — not just the dropdown table. Include a header and then prose:
- Header: client name + Neoserra client ID (HOxxxx) + center + counselor; session date; session type (Initial vs Follow-up — attach a returning/referred client to their existing HOxxxx); counseling method (In-Person / Telephone / Email / Online-Virtual); Contact hours and Prepare hours recorded SEPARATELY — leave Prepare for the consultant, never invent a figure; client stage; special designations (veteran/SDVOSB and demographic) when known; primary + secondary topic areas mapped to SBA/Neoserra categories.
- Narrative: an objective third-person account of the topics discussed, advice given, referrals made, and next steps. Exclude anything said after the client left and any subjective judgment about the client. Record referrals and any milestones or economic impact (jobs, capital, sales, business formed) as confirm-before-recording — never assert an unverified milestone.
Guardrails
Every "never" in this skill, in one place:
- Never guess a missing client ID code — use the literal "Client ID".
- Never paraphrase a milestone category, and never file something that doesn't map to one as a milestone — it goes in Notes.
- Never put a potential or inferred milestone in the client email — it goes in the note to the consultant.
- Never put a client win in the milestone section, or carry it into the Neoserra mapping as a milestone; client wins appear only in Other Progress Worth Celebrating, and only when the toggle is on.
- Never fetch SDAT / Maryland Business Express status automatically; add a "not in good standing" Next Steps line only after the consultant confirms it.
- Never deliver the Neoserra mapping as dropdowns alone — always with the full narrative.
- Never invent Prepare hours; never include what was said after the client left, or a subjective judgment about the client, in the narrative.
- Never use emojis, and never dump chronological notes in place of the template's sections.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

