Plain-English status, purpose, and what matters now.
Current focus
Mid-to-late June regroup package
A working prototype for organizing discovery. Local-only for now; no AMPT data is sent externally.
Questions, workflows, stakeholders, and operational pain.
Data boundaries, human review, consent, and risks.
The next agenda, follow-up, or pilot decision.
The next step is being organized carefully.
Choose one practical workflow before discussing tools.
Keep the work moving without rushing AMPT.
We are organizing the work before recommending anything.
The work is about capacity and practical support, not technology for its own sake.
Keep the relationship warm and help fund a small pilot after AMPT chooses the workflow.
One-minute story
This work is about starting carefully, learning from real workflows, and protecting trust before recommending anything.
Confidence meter
Key takeaway
Start with one safe workflowChoose one workflow to understand before recommending anything.
AMPT stays in control.How to say it
Call close
Close with one clear decision and one safe next step.
Follow-up note
Copy-ready language after the conversation.
Nothing needs attention today.
No critical dependency has been selected.
No material is ready yet.
Working tools
Open Choices
Open choices to close before the project gets more specific.
Plain-English Brief
Copy-ready summary for the selected view.
Capture From Call
Park something from the call without leaving the dashboard.
Next Steps
Waiting On
Meeting Notes
Action Items
Operating Principles
- Protect personal and community data.
- Lead with operational efficiency, not AI hype.
- Lead with anti-racism, consent, and equity.
- Keep humans responsible for decisions and external communication.
- Use technology to support staff capacity, not replace judgment.
Reusable product layer
AI capacity platform
A product shell for moving nonprofit engagements from discovery to governed pilots.
One workspace for discovery, trust, and pilot readiness.
Use the platform to organize stakeholder views, map workflows, hold governance boundaries, and generate plain-English materials for the next conversation.
Local-first demo with reusable structure and client-specific seed data.
Audience cockpit
Internal, leadership, and sponsor views keep the same work legible for different people.
Workflow discovery
Track recurring work, friction, data sensitivity, owners, and candidate pilot fit.
Governance guardrails
Make consent, privacy, equity, human review, and data boundaries visible before testing.
Brief builder
Generate meeting agendas, follow-up notes, pilot summaries, and stakeholder-ready language.
Build path
What turns this into a real platform
Separate client-specific notes from repeatable workflow, governance, and readiness objects.
Move local state into project records, stakeholder tables, workflow maps, and generated briefs.
Give each audience a clean, permissioned view instead of exposing the working cockpit.
Call-ready
Briefing view
A simplified one-page view for live conversations.
Meeting design
Audience agenda
A clean meeting flow based on the selected view.
Live walkthrough
Demo path
A tight walkthrough for the selected audience.
Regroup package
Materials tracker
The concrete materials Angela expects before the next AMPT conversation.
Conversation design
Call prep
Use this to keep Angela, Barb, and Denis conversations grounded and non-threatening.
Talk Track
Language Guide
Product shape
Three working views
The same hub can show different information depending on who is using it.
Relationship map
Stakeholders
Relationship follow-through
Stakeholder follow-ups
A lightweight relationship tracker for the next touchpoint with each person.
Workflow map
What to observe
A practical map of current-state workflows and what evidence to collect before picking a solution.
Candidate solutions
Validate operational pain before building
Pilot definition
Pilot charters
Draft kickoff shape for each candidate solution once AMPT chooses a first workflow.
Selection model
Candidate solution comparison
A simple scorecard for deciding what should become the first AMPT pilot.
Discovery
Pre-onsite intake questions
Pre-onsite survey
Question pack
Questions grouped by who should answer them and what decision each answer informs.
Observation plan
Chicago onsite agenda
A draft 1-2 day structure focused on seeing real work before prescribing solutions.
Research queue
What we need to learn next
Keep outside learning tied to a decision, not background curiosity.
Guardrails
Risk register
Use this as a live checklist before any pilot touches AMPT systems or data.
Data boundaries
Data classification matrix
A practical rule set for what can be used in prototypes, pilots, and AI-enabled workflows.
Shared language
AMPT-friendly glossary
Use consistent plain language across Angela, Barb, Denis, and future partner conversations.
Source library
Documents and source inputs
Track what exists, what is still needed, and what is safe to use.
Show readiness
Angela-ready checklist
A simple gate before presenting the prototype or any pilot concept as AMPT-facing.
Working memory
Meeting notes
Project memory
Decision log
Value model
Time and funding assumptions
Early numbers to pressure-test value without pretending we know the final pilot yet.
Build readiness
Tech stack and deployment
Tracks the practical path from standalone HTML to Railway, Supabase, and GitHub.
Sustainability
Handoff and maintenance checklist
A reminder that small nonprofits need maintainable systems, not fragile demos.
Network pathway
AMPT partner rollout model
A draft model for moving from AMPT's internal pilot to partner nonprofit support.
Path to pilot
Prototype-to-onsite roadmap
A simple sequence for moving from this hub to a real AMPT pilot.
Draft helper
Local draft builder
Generated Draft
Choose a draft type and generate.