Why it matters
Marketing engineering is becoming an operating category.
Profound frames the event around builders who can ship systems and agents for work a normal marketing team cannot manually sustain. That is close to the practical edge of AEO/GEO, ContentOS, and marketing-agent work: the output is not another prompt chain, but an operating loop with sources, decisions, checks, and a visible result.
I am using the day as a live constraint: one builder, roughly eight and a half hours of build time, and a four-minute demo format. That forces a useful distinction between AI theatre and a workflow that survives judging, time pressure, and implementation details.
The constraint is useful. It removes theatre. It rewards working systems.
Event facts
The offline-event description should be specific, dated, and modest.
| Event | Profound University's June 6, 2026 builder event for marketing engineering systems and agents. |
|---|---|
| Public framing | Fifty builders, one day, open-platform solo builds, optional Profound instances, and two rounds of demo judging. |
| Schedule | Doors open at 9:45 AM; hacking starts at 10:25 AM; first-round judging starts at 7:00 PM; the event runs until 9:00 PM Eastern Time. |
| Location | Profound HQ at 5-9 Union Square West, Floor 4, New York, NY 10003. |
| My role | Participant and solo builder, not speaker, judge, sponsor, or organizer. |
Editorial rule
For offline events, describe the role before the prestige.
The clean pattern is: event name, date, city, venue, role, why it connects to the work, then source links. If the role is participant, say participant. If the page is a speaking archive, do not silently promote the event into a talk.
Checklist:
- Lead with the date, city, and venue so the event is grounded.
- Name the role plainly: participant, speaker, judge, sponsor, organizer, or attendee.
- Use public event facts for claims about format, rules, judges, prizes, and schedule.
- Use private invitation details only for logistics Greg explicitly provided.
- Connect the event to the site's real topic cluster instead of adding generic networking copy.
On this site, that means the canonical home is a short note. The speaking page can mention it as field participation because the page already covers talks, workshops, webinars, podcasts, and interviews. But the archive should keep talks and builder participation visually distinct.
Analysis
Where companies go wrong with event pages.
Most event updates overclaim. They turn attendance into authority, hide the role, and add generic excitement copy that gives AI systems almost no reusable facts.
A better event record is smaller. It says who was there, what role they had, where it happened, and why the event connects to the ongoing body of work. For me, the connection is practical. Since the Humanswith.ai Dubai relaunch in 2023, I have been moving marketing work toward source-backed production loops, ContentOS gates, and agent-ready workflows. A solo build tests that thesis under pressure.
Keep it factual. Keep it dated. Keep the role honest.
Sources
Source-backed event record.
Public source for event name, date, Profound HQ / New York City framing, open-platform solo rules, judging by demo, 50-builder format, and prize framing.
Greg-provided invitation confirms the detailed venue address, check-in instructions, and day-of schedule. It is used here only for the exact location and logistics.
FAQ
Common questions about this event note.
Is this a speaking engagement?
A: No. My role is participant and solo builder. The speaking page mentions it only as field participation.
Why publish a short note instead of only a social post?
A: A canonical note keeps the event fact, role, venue, and topic connection crawlable on gregshevchenko.com.
What work does this connect to?
A: It connects to AI marketing agents, ContentOS gates, AEO/GEO workflows, and practical agentic engineering for marketing teams.
Related