No-Code: NYC Brings AI Builds Show & Tell to Times Square

An AI workflow becomes a different proposition when somebody else has to use it. That handoff is the useful operating question behind AI Builds Show & Tell + Morning workshop, a free No-Code: NYC gathering scheduled for November 21, 2026, from 10am to noon EST at Nomadworks Times Square in New York.

The planned morning combines hands-on building and participant demonstrations, with sponsorship from XRay.Tech, Barndoor Automations and Base44. For founders, builders and operations teams, the attraction is the chance to examine work in progress with peers. A community demo can make the distance between a promising prototype and a repeatable working process easier to discuss, while the project is still small enough to change.

What the No-Code: NYC workshop puts on the table

The organizer's published agenda allocates 30 minutes to a guided walkthrough, 30 minutes to open building and 60 minutes to community show and tell. Introductions, bagels and networking frame that sequence. Participants are asked to bring laptops, and unfinished experiments are explicitly welcome alongside more polished projects.

That invitation changes the preparation a builder might make. A concise explanation of the problem, the current version and the point of friction can be more useful than a rehearsed product pitch. Someone demonstrating a routing workflow, for example, could explain how an input reaches the next person and where a judgment call still enters the process. That is an illustrative operating question, rather than a promised item on the workshop curriculum.

No named speaker roster has been announced in the reviewed event materials. The published format puts participant work at the center, so readers should evaluate the morning on its build-and-demo structure rather than assume access to particular founders, investors or executives. The most useful preparation is a project another person can inspect and a question specific enough to start a conversation.

Why unfinished AI work deserves a useful audience

A working prototype carries assumptions its maker may no longer notice. The right input format, a familiar sequence of actions or a manual correction can become part of the routine without ever becoming part of the explanation. Showing the project to somebody outside that routine creates an opportunity to surface those assumptions before another colleague inherits them.

For a founder, that conversation might sharpen the distinction between a feature somebody enjoys trying and a workflow somebody can keep using. For an operations lead, it might help identify the step that still needs a clear owner. Those are potential benefits of peer review, with their value dependent on the actual projects and conversations that emerge. A free workshop supplies a setting; the useful work still has to happen inside it.

The commercial consequence is concrete: a handoff has to survive a change of user. A builder who can explain the inputs, exceptions and recovery path has given a potential collaborator something more durable than a successful run on a familiar laptop. The November gathering offers a reason to prepare that explanation while a prototype remains open to revision.

Three sponsors, three parts of the operating problem

The sponsor list provides relevant context for the questions attendees could bring. XRay.Tech describes its business around workflow design, AI and automation for teams. Its perspective connects naturally to the practical issue of fitting a new tool into an existing process, including the people who must understand and maintain the result.

Barndoor Automations describes a platform built around defined workflow steps, scoped model context and checked outputs. Those product descriptions put control and repeatability into the discussion. They should be read as the company's stated approach, rather than independent proof that an arbitrary AI process will run reliably or that the November workshop will certify anyone's implementation.

Base44 offers natural-language app construction with backend, authentication and database capabilities. That creates a different set of useful questions for a builder: what information persists, who can access it and what the next user is supposed to do. Taken together, the three sponsors span integration, governed automation and app creation. Their sponsorship establishes a connection to the gathering; it does not establish which employees will attend or what individual projects will achieve.

A community cycle with something to bring back

No-Code: NYC's October 2026 community update linked earlier automation and assistant-building workshops to the November show and tell. That sequence gives the gathering a specific local context: people have a reason to return with an experiment and show where the work has gone. Earlier sessions remain historical context, not a promise that their offers, instructors or activities carry into November.

Readers comparing local formats can also examine DevCuration's coverage of the Money Talks 3 finance AI hackathon, scheduled for the same day. Its finance-mentor format serves a different purpose from this community show and tell. The editorial significance of No-Code: NYC's sequence is the opportunity for continuity. A community can become more useful when participants recognize a problem from an earlier discussion and can see the next version. Repeated contact around a real project gives potential collaborators something concrete to remember. Readers should still avoid treating that possibility as a guarantee of introductions, customers or investment.

For someone deciding how to spend a Saturday morning, the question is whether there is work worth putting in front of another builder. A small project with a stubborn exception may create a more productive exchange than an expansive description of a future business. The event's willingness to include unfinished work makes that a reasonable way to prepare, with the quality of feedback left to the people who actually join the conversation.

Registration and the questions to carry into the room

Registration runs through the organizer's Luma page, which confirms the date, free admission and venue name. The published Nomadworks Times Square venue listing places the coworking site at 240 West 40th Street, New York, NY 10018. Exact event access details are provided through registration, so that general venue address should not substitute for the organizer's instructions.

A useful preparation exercise is to decide what another person should be able to understand after a short demo. That could be the trigger for a workflow, the information it uses, the boundary of an automated decision or the handoff when something needs attention. Keeping the question narrow gives a potential collaborator a way into the work without requiring a tour of every tool involved.

The November 21 morning ends at noon, but the operating question can travel back with each project. When the next person opens the workflow, the explanations tested in that room may still be doing useful work. The unfinished piece a builder chooses to show is where that next conversation begins.