Systems & AI Diagnostic

Larkspur Arts Collective

How the organization's six tools connect, where they break, what to fix first, and where AI can safely help.

Organization
Community arts nonprofit (fictional)
Size
12 staff, 18 teaching artists
Review period
8 business days
Access used
Read-only, 6 tools

About this sample. Client reports are confidential, so this one describes a fictional organization. The people, systems, domains, and numbers are invented. The structure, depth, and kind of findings match what clients receive at the end of a diagnostic.

  1. Board summary
  2. System map
  3. Patron journey: before and after
  4. Findings
  5. Ranked fix list
  6. AI plan
  7. Method
1 · Board summary

The tools work. They don't work together.

One page for the board and the executive director.

Larkspur runs on six tools. Each one does its own job well. But none of them shares data with the others, except the donation form. Staff fill the gaps by hand, every week.

~6 hrs
staff time per week spent exporting and re-entering data
3
separate accounts a patron creates to buy a ticket, donate, and take a class
21%
of donor records are duplicates of another record
19 days
average wait before a donor receives a thank-you letter

One urgent risk

Medical and emergency-contact information for youth class students is copied into a shared spreadsheet. Eleven people can open it, including two former contractors. This should be fixed this month, whatever else the board decides.

Recommendation

Phase 1 (now, about $500–1,000): move youth medical data out of the spreadsheet and remove old access.
Phase 2 (one integration sprint, about $9,000–15,500): connect ticketing and class registration to the donor CRM, clean up duplicates, and sync the email list. This ends the weekly exports and gives Larkspur one record per patron.
AI (after Phase 1): start the three approved uses in section 6, under a one-page AI use policy. The patron chatbot waits until Phase 2 is done.

Decision requested: approve Phase 1 now. Approve Phase 2 scope and budget for the next quarter.
2 · System map

Six tools, three domains, no single sign-on

Every tool a patron or staff member touches, and how data moves between them today.

Patron Donor login (#1) Ticket account (#2) Class account (#3) larkspurarts.example tickets.stagebox.example larkspur.classhub.example Website builder + embedded donation form Ticketing platform performances, exhibitions Class registration adult + youth classes Back office (staff only) Email newsletter 4,800 contacts Donor CRM intended system of record Accounting bookkeeper only Donations (automatic) Weekly CSV export (by hand) Weekly CSV export (by hand) Monthly upload Re-keyed
Patron creates a separate account Connected automatically Moved by hand

What the map shows

3 · Patron journey

One patron, one season, before and after

A typical path we walked through using test accounts.

Today

Buys a ticket
Ticketing platform
Creates account #2. Email saved as m.alvarez@…
Donates at intermission
Donation form → CRM
Creates donor login #1. CRM doesn't know she bought a ticket.
Signs her child up for a class
Class registration
Creates account #3 with a different email. Medical form copied to a shared spreadsheet.
Gets thanked
CRM + mail merge
Thank-you letter arrives 19 days later. She receives the newsletter twice.
Result: 3 logins, 2 donor records for the same person, and no single view of her as a ticket buyer, donor, and parent.

After the recommended fixes

Buys a ticket
Ticketing (guest checkout) → CRM, nightly
No account needed. Her purchase appears on her CRM record the next morning.
Donates at intermission
Donation form → CRM
Matched to her existing record by email and phone.
Signs her child up for a class
Class registration (separate login)
The class vendor doesn't support single sign-on, so she keeps one extra login. Her details are pre-filled, and the medical form stays inside the vendor's protected fields.
Gets thanked
CRM + AI draft, staff review
A personal thank-you letter goes out within 3 days. One newsletter.
Result: 2 logins instead of 3, one patron record, no medical data in spreadsheets, and thank-you letters 16 days sooner.

The class step stays partly separate on purpose. Replacing a tool that teaching artists like, just to remove one login, would cost more than it saves.

4 · Findings

What we found, by severity

Each finding comes from the review, a staff interview, or the journey walk-through.

High · Risk

Youth medical data in a shared spreadsheet

Emergency contacts and medical notes for 140 youth students are copied each term into a spreadsheet shared with 11 accounts. Two of those accounts belong to contractors who left last year.

High · Cost

Weekly manual exports

Staff export ticket and class data every Monday, clean it in a spreadsheet, and import it into the CRM. This takes about 6 hours a week, about 300 hours a year, and fails when the person who does it is out.

Medium · Data

Duplicate patron records

21% of CRM records duplicate another record. Most come from patrons who use different emails for tickets and classes. Duplicates split giving history and distort reports to funders.

Medium · Donors

Slow thank-you letters

Letters are written by hand once the weekly import finishes. The average wait from gift to letter is 19 days.

Medium · AI

AI in use with no policy

Four staff members use free AI chat tools for grant drafts and donor letters. At least one has pasted donor names and gift amounts into a personal account.

Low · Website

Slow mobile pages

The events page loads slowly on phones, mostly because of uncompressed photos. Staff can fix this with a short guide.

5 · Ranked fix list

What to fix, in order

Ranked by risk first, then by hours saved per dollar. Costs are ranges until the work is scoped.

#FixEffortCost rangeWhat it unlocks
1Move youth medical data into the class platform's protected fields. Delete the spreadsheet. Remove access for former contractors.1 day$500–1,000Removes the largest risk. Phase 1
2Connect ticketing to the CRM with a nightly sync. Turn on guest checkout.3–5 days$3,000–5,000Ends half of the weekly export. Removes one patron login. Phase 2
3Connect class registration to the CRM with a nightly sync.3–5 days$3,000–5,000Ends the rest of the weekly export. Phase 2
4Merge duplicate records and set matching rules (email, then phone).2–3 days$1,500–2,500One record per patron. Accurate funder reports. Phase 2
5Sync CRM segments to the email newsletter automatically.1–2 days$1,000–2,000No more monthly uploads or double sends. Phase 2
6Export template from the CRM for the bookkeeper's monthly entries.1 day$500–1,000Ends re-keying of donations. Phase 2
7Photo compression guide for the website.2 hoursStaff can do itFaster event pages on phones. Anytime

Phase 2 total (fixes 2–6): $9,000–15,500 as one fixed-scope integration sprint.

6 · AI plan

Where AI helps, and where it doesn't yet

Start these only after Phase 1, and after staff adopt the AI use policy below.

Safe to start

  • Draft donor thank-you letters from CRM fields (name, gift, program supported). A staff member reviews each letter before it goes out. Goal: letters within 3 days.
  • Summarize class feedback surveys each term into themes for the program director.
  • First drafts of grant report sections from attendance and program data that contains no personal details.

Not yet

  • A chatbot that answers patrons on the website. Today it would answer from scattered, out-of-date data, and give wrong dates and prices. Revisit after Phase 2.
  • Anything that touches youth medical data. Not now, and not without legal review.

Policy and training

7 · Method

How this diagnostic was done

  • Read-only access to all six tools. Nothing was changed during the review.
  • Two staff interviews: the development director and the box office manager.
  • One end-to-end journey walked with test accounts: ticket, donation, class registration.
  • Review of the export spreadsheets and their sharing settings.
  • A 60-minute walkthrough of these findings with the executive director, before this report was finalized.