Procedure: Meeting prep. Revision 15 — October 22, 2026. Index: https://ancreationoffice.com/sop.txt Kept by: b-business-manager. b-analyst drafts the documents and builds the packet. May write: the meeting's correspondence folder AN-Creation//correspondence/YYMMDD-NN-X-slug/ (the meeting file, the packet, the notes; https://ancreationoffice.com/sop-correspondence.txt) and its row in correspondence.csv, rows in the Business action log, decision log, contacts.csv and market-evidence.csv, and hand-off lines to b-project-manager. Builder: https://ancreationoffice.com/meeting-packet.py . Examples: https://ancreationoffice.com/example-mousetrap/Default-org/Snap-mousetrap/Office%20files/business/correspondence/261028-01-M-distributor-buyer-meeting/buyer-packet.html , https://ancreationoffice.com/example-mousetrap/Default-org/Snap-mousetrap/Office%20files/business/correspondence/261024-01-M-molder-a-quote-meeting/manufacturer-packet.html , https://ancreationoffice.com/example-mousetrap/Default-org/Snap-mousetrap/Office%20files/business/correspondence/261104-01-M-community-lender-meeting/lender-packet.html , https://ancreationoffice.com/example-mousetrap/Default-org/Snap-mousetrap/Office%20files/business/correspondence/261112-01-M-family-investor-meeting/investor-packet.html , https://ancreationoffice.com/example-mousetrap/Default-org/Snap-mousetrap/Office%20files/business/correspondence/261208-01-M-accountant-year-end/accountant-packet.html , https://ancreationoffice.com/example-mousetrap/Default-org/Snap-mousetrap/Office%20files/business/correspondence/261023-01-M-patent-agent-consult/patent-packet.html , https://ancreationoffice.com/example-mousetrap/Default-org/Snap-mousetrap/Office%20files/business/correspondence/261119-01-M-pest-control-company-licensing/licensee-packet.html , https://ancreationoffice.com/example-mousetrap/Default-org/Snap-mousetrap/Office%20files/business/correspondence/261109-01-M-insurance-agent-quote/insurance-packet.html , https://ancreationoffice.com/example-mousetrap/Default-org/Snap-mousetrap/Office%20files/business/correspondence/261105-01-M-business-attorney-consult/attorney-packet.html , https://ancreationoffice.com/example-mousetrap/Default-org/Snap-mousetrap/Office%20files/business/correspondence/261102-01-M-partner-tool-and-die-maker/partner-packet.html (each folder has its meeting.csv) Goes with: https://ancreationoffice.com/principles-bm.txt , https://ancreationoffice.com/sop-funding-packet.txt WHY THIS EXISTS An inventor starting a business has to win over people who have seen many inventors before: a store buyer, a molder, a banker, an investor. Each one has worries, and each worry is answered by a document or an analysis the inventor has never had to make. The bot knows what each one will want to see, has the pieces ready, and sends the inventor in prepared. THE TRIGGER Any mention of a meeting, a call, a visit, an email to send, or a person to approach: "I'm seeing the farm-supply buyer Thursday." "The molder wants to talk." "Should I go to the bank?" Ask three things, one at a time if they are not already clear: who, when, and what the inventor wants out of it. WHO'S ACROSS THE TABLE, AND WHAT THEY WANT TO SEE - Buyer (distributor, store buyer, business customer). Worries: can you deliver, will it sell, will it cause trouble. Packet: https://ancreationoffice.com/sop-packet-buyer.txt - Manufacturer, toolmaker or supplier. Worries: is this real, can you pay, is the volume believable, are the drawings clear. Packet: https://ancreationoffice.com/sop-packet-manufacturer.txt - Banker or lender. Worries: can you repay, what if you can't, how much of your own money is in. Packet: https://ancreationoffice.com/sop-packet-lender.txt - Investor (friends and family, an angel, crowdfunding backers). Worries: is it worth it, will you see it through, what happens to my money. Packet: https://ancreationoffice.com/sop-packet-investor.txt - Grant reviewer, pitch competition or advisor. Worries: is it new, is the plan credible. Packet: the funding packet (https://ancreationoffice.com/sop-funding-packet.txt) plus the program's own form (sop-funding.txt). - Licensee. Worries: does it sell, can they own it, what will it cost to make. Packet: https://ancreationoffice.com/sop-packet-licensee.txt - Accountant, tax preparer or bookkeeper. Worries: are the records complete, is business money kept apart, what will they have to answer. Packet: https://ancreationoffice.com/sop-packet-accountant.txt - Patent attorney or agent, a patent clinic or the USPTO's free help. Worries: what exactly is new, what is out there, who has seen it and when, who owns it. Packet: https://ancreationoffice.com/sop-packet-patent.txt - Insurance agent or broker. Worries: how could it hurt someone, what has been done about it, how much will sell and through whom. Packet: https://ancreationoffice.com/sop-packet-insurance.txt - Business attorney. Worries: what needs their eyes and by when, who owns what, what has been signed. Packet: https://ancreationoffice.com/sop-packet-attorney.txt - Possible partner (a co-founder, a skilled friend, a shop offering help for a share). Worries: is this real, what would I do and get, who decides. Packet: https://ancreationoffice.com/sop-packet-partner.txt THE STEPS 1. Who, when, what they want out of it. Name the counterpart type from the list. 2. Open the packet procedure for that type. List what that person will want to see. 3. Dust off what exists (parked documents come out for this meeting and go back after, https://ancreationoffice.com/sop-document-life.txt DUSTING ONE OFF). Check what exists: the business record (AN-Creation//) and copies of b-project-manager's project record. Ask b-project-manager for current copies of anything product-side through office-handoff (the cost sheet, specs, drawings list, risk table, charter); never retype them. 4. Draft what is missing, honestly. A pre-revenue company has no sales history, no credit and maybe no insurance yet: the packet says so, says what is being done about it, and puts it on the action log. Never invent a fact to fill a gap (principle-never-invent-facts.txt). 5. Write the meeting file, meeting.csv: who, when, the goal, the ask, the walk-away (principle-walk-away-number.txt), the questions they will likely ask with the answers, and what to leave behind. Two record rows tell the builder where the sheets are, relative to the meeting folder: ../../funding/ (the funding folder, with company.csv, pricing and the copies of b-project-manager's sheets) and ../..//Office files. 6. Build the packet: python3 meeting-packet.py AN-Creation//correspondence/YYMMDD-NN-X-slug . The packet's last page is the prep sheet; it is for the inventor and is not handed over. The builder runs on working copies in your Shell; save the packet back with office-save. Without a Shell, write the same pages by hand from the packet procedure's list, from the same sheets. 7. Before the meeting, tell the inventor in a few lines: what is in the packet, the two or three questions most likely to come up, the ask, and anything still missing. 8. After the meeting, before anything else: the meeting notes in the meeting's folder and its row in correspondence.csv, the trip row with the miles if they drove (trips.csv), and every cost with its receipt (expenses.csv), per https://ancreationoffice.com/sop-business-record.txt . Then add what they said or did to market-evidence.csv when it is a signal; update contacts.csv with the next step and date; put every promise on the action log; write any decision to the decision log. RULES - Rigor scales with whose money is at risk (principle-rigor-scales-with-money.txt). A lender's or investor's money, or a contract to sign, brings the standing advice: get legal and professional counsel before signing. - The inventor sends, signs and attends. The bot prepares (principle-owner-acts-bot-drafts.txt). - Decide on the patent before showing how it works (principle-patent-before-public.txt). A buyer packet shows what it does, not how it is made, until there is a filing or an NDA. - Every spec, rating, certification, rate or term in a packet traces to its source (principle-trace-to-source.txt). Run check-sources.py on the folders the packet draws from before building it. - After the meeting, park the sources again in plan.md with the date; the packet itself is kept as given. - Packets are copies built for one meeting and kept in that meeting's correspondence folder, never changed afterwards, so the correspondence log shows exactly what each person was given and when.