Portfolio note · June 6, 2026 · New York City

Building at Profound's Marketing Engineering Hackathon.

I participated as one of 50 selected solo builders at Profound HQ in New York City. The day was a practical test of the work I keep building toward: AI marketing agents that turn oversized marketing processes into source-backed, reviewable workflows.

Date
Location
Profound HQ, 5-9 Union Square West, Floor 4, New York, NY
Role
Selected participant · solo builder
Topic
Marketing engineering · agentic workflows

What this records

This is a portfolio field note, not a talk. It records the event, the selected-builder context, my role, and why the day belongs in the same body of work as AI Search visibility, ContentOS, and marketing-agent infrastructure.

Event record

One day, one builder, one marketing system to ship.

Profound's public brief framed the challenge around a marketing process that is too large or repetitive for a normal team to run manually: find it, then ship a system or agent that can run it. The event page lists 50 spots, open-platform builds, solo building, two demo rounds, and $40,000 in prizes.

The kickoff deck made the selectivity concrete: the event was 5x oversubscribed, every person in the room had earned a seat, and Gregory Shevchenko was listed in the first-round demo room assignments. That is the right way to say it: participant, selected cohort, solo builder.

Event facts

The role was selected participant and solo builder.

Event The Marketing Engineering Hackathon, hosted by Profound University.
Date and city June 6, 2026, New York City.
Venue Profound HQ at 5-9 Union Square West, Floor 4, New York, NY 10003.
Format Fifty builders, one day, open-platform solo builds, optional Profound instances, and two rounds of four-minute demos.
My role Selected participant and solo builder; listed in Room 3 for first-round demos in the kickoff deck.
Selection context The kickoff deck says the event was 5x oversubscribed and that every person in the room earned their seat.
Build prompt Find a marketing process that is inhuman in scope or scale, then ship a system or agent that runs it.

Portfolio thread

The day connects to my AI Search and marketing-agent work.

My work with Humanswith.ai is about making marketing operations legible to both people and AI systems: source packs, workflow gates, answer-ready pages, and agents that can produce useful work without hiding the chain of evidence.

The hackathon prompt maps directly to AEO/GEO work. AI Search visibility is not only a content problem; it is an operating problem. Teams need systems that can inspect prompts, compare cited sources, turn gaps into source-backed assets, and keep a human-reviewable trail.

That is why this belongs in the portfolio: it is a dated, source-backed record of building in the same category I write and ship around every week.

Sources

Source-backed event record.

Republished on DEV

Read and discuss the DEV.to version

Republished on Medium

Read and share the Medium.com version

On LinkedIn

Read and discuss the LinkedIn.com post

Related