A working discovery brief for the next chapter: Jeffrey Abramowitz as the authority layer, And Then What Consulting Group as the commercial engine, and And Then What Foundation as the mission engine -- connected by one database, one AI assistant, and one deliberate digital backbone.
This section is deliberately short. It is the working agreement as I understood it, written down so we can correct it early if I heard anything wrong.
Syracuse students are building the And Then What web presence across two semesters, currently without day-to-day technical supervision. I come on as a contractor to oversee that build, so the work lands as one coherent, owned product instead of a relay race between student cohorts.
I design and build a unified database of your world: contacts, organizations, businesses, boards, funders, and the relationships that connect them, across all three pillars of your work. Your network and history become an organizational asset instead of something you carry in your head.
On top of that database sits an AI assistant, built on the same architecture as the one I showed you on our call. It answers from your real data: who you know, how you met, what was promised, what comes next.
You send the NDA and the contractor packet; I return both promptly. You answer eight discovery questions (sent by email, repeated below). I return a written Statement of Work with phases, deliverables, and pricing.
The strongest structure is not one giant website. It is a coordinated ecosystem in which each pillar answers a different question while sharing one deliberate digital backbone.
Who is Jeff? Why should institutions trust him? Biography, expertise, speaking, media, writing, credentials, and reputation. Your existing site already carries a deep archive here; it needs to be re-pointed at who you are now, not who you were.
Current personal siteWhat problems can the organization solve? Services, methodology, qualified leads, consultations, engagements, proposals, and outcomes.
andthenwhatconsulting.orgWhat public-interest work exists? Programs, partners, funders, grants, direct assistance, and measurable community outcomes -- particularly for justice-impacted individuals and communities.
Your network spans education, corrections, workforce development, philanthropy, government, nonprofits, employers, media, and advocacy. The right data model turns that network into an organizational asset without reducing relationships to a mailing list. One relationship graph, with the LLC and the Foundation kept cleanly separated where law, funders, or ethics require it.
Most AI tools answer from the general internet. Yours answers from your database: your contacts, your history, your commitments, your pillars. That difference is the entire value.
Who is this person, how do we know them, what did we last discuss, and what did we promise? Answered in seconds, from your own records.
Who in my network should meet whom? Which funder cares about this program? Which partner has capacity in this city? The graph answers what memory cannot.
The assistant tracks what comes next: open commitments, stalled threads, warm introductions never made. It applies your own question to your own operation.
A two-semester student build can produce excellent work or an unmaintainable orphan, and the difference is almost entirely supervision. Oversight here means the students still do the building and still get the learning; the organization gets a product it owns and can operate after they graduate.
A written technical brief the students build against: stack, accessibility, performance, content structure, and brand architecture. Reviewed work merges; unreviewed work does not.
Version control, documentation, and handoff notes required as part of the work, so the second cohort continues instead of restarting, and graduation is not a data-loss event.
Domains, hosting, accounts, and code live in organization-owned accounts from day one. No student laptop is ever the system of record.
The website is only the visible layer. The real leverage is a clean operating system for relationships, opportunities, institutional knowledge, analytics, and automation -- added only where the workflow justifies it.
Personal authority site, consulting presence, and Foundation presence with shared design logic and clear cross-linking. Built by Syracuse, supervised to one standard.
Contacts, organizations, referrals, opportunities, funders, partners, engagement history, and next actions. The core asset.
The intelligence layer on top of the database: recall, connection, and follow-through from your real data.
Canonical bios, speaking history, publications, case studies, and approved messaging. One source of truth for every proposal and press moment.
Teach the internet, and the AI systems people now ask instead of Google, exactly who Jeffrey Abramowitz and And Then What are today.
Lead routing, follow-up, meeting preparation, and reporting -- only where a real workflow proves the need.
Traffic, conversion, source attribution, and opportunity movement. Reporting that informs decisions, not dashboards for their own sake.
Organization-owned domains and data, MFA, permissions, backups, documentation, and a clean off-ramp from any vendor -- including me.
These are the same eight questions from my email, repeated here for convenience. I will not recommend custom technology simply because it can be built; these answers determine what deserves configuration, integration, or custom development. Answer in whatever form is easiest: bullets, a voice memo, or another call.
A practical first scope creates the minimum durable architecture needed to operate professionally now, while preserving room for the system to evolve once real usage patterns are visible.
NDA and contractor packet from your side; eight answers from yours whenever they are ready; then a written Statement of Work from mine with defined phases, deliverables, ownership, timeline assumptions, and pricing. No need to decide the entire technology stack before that.
The design principle: Jeff and And Then What own the accounts, domains, data, and intellectual property. The Midnight Garden earns its place by understanding and operating the system exceptionally well, not by creating dependency through access control.