From a box of business cards to a CRM table in one evening

Work with the folder [folder path] of scanned business cards.
Don't extract anything yet — just do a quality check.

Go through every file and return a table:
file | how many cards are in the shot | readability (good /
poor / unreadable) | what specifically is wrong (glare, blur,
cut-off edge, print too small, dark background)

At the end, give me:
- a list of files you'd recommend reshooting, and why
- how many cards are in the folder in total, by your count
- whether any shots look like the back of the same card as
  another shot

Don't organize, rename, or delete anything.

Work with the folder [path] of scanned business cards from
[trade show name, date held].

Go through every image and build a table, one row per card,
with columns:
first_name | last_name | title | company | email | phone | website |
address | context | contact_source | file | confidence

Rules:
- transcribe handwritten notes VERBATIM into the context column,
  don't interpret, shorten, or add to them; if there's no note,
  leave the cell empty
- write [trade show name] and the event date into the
  contact_source column, the same way for every row
- give the phone number in international format and keep the
  original notation in parentheses after it
- transcribe the email address character by character; for
  characters that get confused (lowercase l and capital I, zero
  and the letter O, the combination r n versus m), weigh the
  context of the name and company, but never guess the address
- combine the front and back of the same card into a single row
- anything you can't read, write as [ILLEGIBLE]; never guess
- in the confidence column, write high / medium / low based on
  how sure you were of the reading

Save the output as contacts.csv in the same folder, semicolon
delimiter, UTF-8 encoding. In the chat, give me just a summary:
how many rows, how many rows have low confidence, and which files
they're from.

From contacts.csv, take the rows where confidence is low or
where there's an [ILLEGIBLE], and go back through the matching
photos for those.

For each such row, tell me:
- which field is the problem
- what you can see on the shot, even if it's only a fragment
- two or three possible readings, ranked by likelihood
- whether a reading is checkable against another field (say,
  the shape of an email address based on the name and the
  company website's domain)

Don't write anything to the file yet. I'll make the call and
tell you what to fill in where.

Run a cleanup pass on contacts.csv. Don't delete anything —
create contacts-cleaned.csv and list the changes for me.

1. Duplicates: find rows that are probably the same person
   (matching email, or matching last name plus company). Don't
   merge them yourself — list them as merge candidates, including
   what differs between them.
2. Formats: standardize phone numbers into international form,
   emails to lowercase, company names with no trailing spaces and
   no double spaces inside.
3. Standardize legal-entity suffixes (Inc., LLC, Ltd. and similar)
   into one consistent form, but never shorten or add to the name
   itself.
4. Flag obvious typos in email domains (gmial, hotmial) as
   suspicious, but don't fix them.
5. Empty required fields: list rows missing both email and phone
   at once — those can't be worked with.

At the end, give me a summary: how many rows were adjusted, how
many merge candidates, how many rows are unusable.

Here's the sample import header from my CRM, [system name]:

[paste the exact header the CRM expects]

Convert contacts-cleaned.csv into import-crm.csv so it exactly
matches this header.

- write column names literally as in the sample, in the same order
- map my context and contact_source columns into the [note /
  description] field, in the form:
  "Source: [trade show, date]. Note from the card: [verbatim
  transcript]."
- leave fields the CRM expects but I have no data for empty;
  don't fill anything in or invent anything
- date in the format [YYYY-MM-DD]
- semicolon delimiter, UTF-8 encoding, first row is the header

In the chat, list the fields that stayed empty, and the fields
from my data that didn't fit into the header.

Add a new column, prep, to import-crm.csv.
For each company in the table, find and summarize:

- what the company does (one sentence, specific — not "provides
  solutions" but what it actually does and for whom)
- roughly how big it is (headcount or an order-of-magnitude
  estimate) and where it operates
- one recent development from the past year, if there is one
  (new product, expansion, acquisition, open position, leadership
  change)
- why my offering might interest them: [describe what you're
  offering]

Rules:
- cite a source for every fact (a link or the name of the page)
- write "not found" for anything you can't find — don't guess,
  and don't write generic phrases that would fit any company
- if you're not sure it's the right company (similar name,
  different country), say so explicitly and don't combine data
  across companies
- 4 sentences maximum per company, total

Process it in batches of [10] companies and pause after each batch.

Prepare a briefing for a meeting with [name, title] from
[company]. Note from the card: [verbatim transcript]. I'm
offering [what you're offering].

I want:
1. What the company does, in which market, and how it differs
   from competitors
2. What their current situation and priorities probably are
   (based on annual reports, press releases, job postings)
3. Who else in their industry deals with similar problems, and how
4. Three specific questions I can ask that show I looked into
   them
5. Two things that could be reasons this WON'T make sense

Cite a source for every claim. Where you have no basis, say so
instead of guessing. Don't write me sales pitches — I want facts
and questions.

For every contact in import-crm.csv where the context column is
filled in, prepare a draft follow-up email. Save them as
individual files in a drafts/ subfolder, named lastname-company.md.

For each email:
- subject line under 50 characters, specific, no exclamation
  marks, and no words like "offer" or "partnership"
- the first sentence recalls where and what we talked about — it
  must be drawn from the note in the context column and the event
  in the contact_source column
- the second to third sentence follows up on what interested them,
  not on what I want to sell
- one specific offer of a next step (a fifteen-minute call, sending
  one piece of material) — just one, not three options
- signature: [your name, company, phone]
- 120 words maximum total, formal/informal tone per the [column]
  [or: always formal]

Hard rules:
- don't send any emails and don't forward them anywhere, just
  save the files
- if the note in the context column is empty or unclear, don't
  write an email — just write "no basis, decide manually" into
  the file instead
- don't invent anything about the meeting; if the note doesn't
  mention a topic, don't include one
- no phrases like "it was a pleasure" or "hope you're doing well"

Here's a list of contacts from [event name, date] where my
context column is empty — I don't remember what we talked about:

[paste the rows: name, title, company, prep column]

Split them into three groups and write one sentence for each
saying why:
A) worth reaching out to — the field and role make sense given
   what I do [describe your offering]
B) leave in the database, no action
C) doesn't make sense at all, doesn't belong in the CRM

For group A, write a short message, 60 words maximum:
- admits upfront that we met at [event] and that I want to
  reconnect
- one sentence on why my work might be relevant to their role
- one closing question that can be answered in a single sentence
- no attachments, no meeting request in the first email
- don't invent anything about our conversation, no "as we discussed"

Read through the drafts in the drafts/ folder and go over them
like a strict editor of business communication. Don't rewrite
anything, just flag it.

For each email, list:
1. Sentences that would fit anyone — evidence the email isn't
   personal.
2. Places where I claim something that doesn't follow from the
   note on the card.
3. Sales-y phrases and superlatives.
4. An unclear next step (what exactly I want from the recipient).
5. A guess at how the email would land if the recipient didn't
   remember meeting me at all.

At the end, rank the emails from weakest to strongest, and tell
me which ones you think I shouldn't send at all.

Go through import-crm.csv as a check before importing it into
the CRM and give me three lists. Don't change anything.

1. Data that has no business being in the table: anything
   sensitive or private that made its way in from the notes
   (health status, family situation, judgments about a person,
   private addresses).
2. Notes in the context column that are phrased in a way that
   would be uncomfortable for me if that person ever saw them.
3. Rows missing contact_source — where I wouldn't be able to
   document where the contact came from.

For each finding, cite the row and what you'd suggest doing
about it.

Go through the context column of import-crm.csv and pull out
tasks with deadlines. Return a table:
contact | company | what to do | deadline | where it comes from

- convert relative dates from the notes ("follow up in September",
  "after their budget's approved", "in two weeks") into a
  specific date based on the event date [date], and keep the
  original wording in parentheses
- where a note doesn't include a deadline, propose one of three
  modes: follow up within 3 days / within 2 weeks / leave with
  no action, and justify it in one sentence
- list contacts with no basis at all separately, as "no action"

Sort by deadline. Don't write or create anything anywhere.

Here's the list of follow-ups sent from [event name] and what
happened:

[paste table: contact | company | had a note from the card
yes/no | day sent | replied yes/no | outcome]

Give me a breakdown in five points:
1. Overall response rate, and separately for contacts with a note
   versus without one.
2. Response rate by how many days after the event the email
   was sent.
3. Response rate by the recipient's field or role, if that's
   visible in the data.
4. What the emails that got a reply have in common — and what
   the ones that got nothing have in common.
5. Three specific things I should do differently at the next
   event (at the booth, when writing notes, when writing
   follow-ups).

If the sample is too small for a conclusion on any point, say so
instead of giving one. Don't calculate percentages from fewer
than [10] cases.