Let's Build It

Where We Stand

Registration is live. Startland packet is ready. Friday's meeting locked shirt qty, city tee naming, gift bags, and partner timing. Promo mode is next.

Done: Spark walkthrough, lockup, partner one-pager, Intuidy.com registration URL, Startland packet, founders kept in copy, meeting notes integrated, changelog, partner first-touch on Oct 2. In flight: partner replies, Keystone still with Grayson, shirt order at 125, gift bags, panel, food. Waiting: expo tables, post-event follow-up. Backlog: AV live test.

The Room Leaves As Advocates

Everything on this page serves that sentence, so decisions stay easy.

Measure it: RSVPs vs attendance, time booked, partner orgs in the room, and post-event follow-up.

The Countdown

What still has to get done. Check items off as they land.

GS Grayson SmithDL David LickimbatJG Justin GardnerJA John Anderson

Run of Show

Thursday, October 29th. Space booked 3:00–10:00 p.m. through Austin (six hours). The public agenda matches the Intuidy registration page. The event runs 5:00 to 9:00 PM.

Staffing math: 5 station staff at doors, converting to 5 breakout facilitators at 6:30, plus a host, plus a gift-bag strike team (can be overlapping). Minimum team of 7. Merch: 125 tees planned (vinyl in, blanks not ordered); first 100 at check-in; 250 gift bags at exit/breakouts.

Keynote and panel

Drafts for Thursday, October 29. Rehearse them. Do not read them aloud from the page. Grayson keynotes. Justin moderates. Three panelists: David Lickimbat, Miles Finch (State Farm), Mychal Shaw (Uwazi). Mark Truman is not on the panel. Mychal's answer lines are not written. A guest can strike any line. Email a guest only the sheet at the bottom of this section.

Justin, welcome

Hey everybody, my name is Justin Gardner, and welcome to Intuidy's very first Let's Build It event. We're joined by the founders of Intuidy, Grayson and Gentry Smith, COO David Lickimbat, Miles Finch of State Farm, and Mychal Shaw, founder of Uwazi.

If you're building with AI tools, or if you're curious about where the future of business is headed, you're in the right place tonight. Many of you are already building, both for yourself and inside the companies you work for. In fact, I bet some of you are doing that inside companies that might not even call themselves a tech company.

Tonight I'm really excited to introduce you to the team, discuss why a technology like Intuidy is great for builders, and also for the companies you're working for.

So without further ado, let's welcome Grayson up to say a few words.

Cut Gentry's name if Gentry is not in the room. If the keynote is still going at 5:45: "Grayson, I'm gonna hold you there. The challenge is already in the room. Panel, come on up."

Grayson's keynote

Short version, about half the old draft. Same spine: invisible builders, Monday morning, the plumbing, one engagement at a time, a harness for builders, and tell your group. Grayson keynotes. Justin sits with the panel.

Kansas City already has AI builders. Most of them are invisible to each other.

They're not on a demo stage. They're in insurance shops, logistics companies, studios, manufacturers, public departments. Real systems, shipped quietly. They never end up in the same room, so the city learns nothing. That's why you're here.

People want to talk about the new model. Models matter. They're also getting easy to rent.

What still hurts is a demo versus Monday morning. The plumbing. The permissions. The definitions. The governance. Who can see what. What a word means in your shop. Who owns it when the system is wrong. That's the whole job, and it's unglamorous.

Until now, Gentry and I did this ourselves, one engagement at a time. We stayed with each company long enough to learn how it really works, right down to what the words mean in that shop. That's how this got good. Out of that work we built a harness for the builder space. You bring an idea for your business. Intuidy gives you a place to build it, with a lot of flexibility and a lot of options as you keep going. Your data, the systems you already run, the models you want to use. You can change those as the business grows, and the harness still holds.

Justin is going to sit down with three people I'm really glad are here. One of them builds right alongside us. One brings this into an organization that serves people every day, where getting it right really matters. One builds so people can understand the thing in front of them. He'll ask them what they've learned. How a person stays in charge when a model misses. What they still want a human to do. And what has to stay true in their shop when the model changes next year.

One challenge, and I'll say it again before you leave. If tonight helped, tell every builder group you're in about Intuidy. We're still invisible to each other. The next person only shows up if someone they trust tells them.

Justin, the floor is yours.

If he still runs long, drop in this order: the harness lines, then the handoff to Justin. Never drop invisible builders, Monday morning, the harness, or the challenge.

Close at 9:00

Thanks for staying with it. You've got the room, the platform, and each other. If tonight helped, tell every builder group you're in about Intuidy. That's how the next person finds this. Get home safe.

Same challenge. No second talk.

Panel questions

Forty minutes. Three panelists. Audience left to right: David, Miles Finch, Mychal Shaw. Miles sits in the middle, not on an end, not first. Same first question to each, in that order, about two minutes.

How you became a builder

In one sitting: what do you actually build, and what pulled you into building it yourself instead of waiting for a vendor to hand it to you?

About two minutes each. Justin cuts in with "Hold the rest for the next question" rather than letting a strong talker spend Miles's minutes.

• David. He builds with operators who already own the pain and the data. He got tired of demonstrations that could not survive a Monday. One concrete scene, then stop. He does not preview the product.
• Miles. Four sentences, on a card, practiced out loud twice. What they operate. The pile of work that used to live in spreadsheets and inboxes. The moment they stopped describing the problem and started building inside it. One result a peer in the room would recognize (time returned, a queue that closes, a definition the whole office now shares). No architecture.
• Mychal Shaw. Founder of Uwazi. Civic clarity, in his own words. His answer lines are not written. Do not use the old public-safety draft. That draft was for Mark Truman, who is not on the panel.

Justin says this once, before the field questions:

These are questions about the work, whoever's tools you use. Answer from your own shop.

1. Demo versus Monday morning — Miles first

Most of what gets called AI inside a company dies as a demo. In your operation, what is the actual difference between a demo and a system somebody is graded on?

Miles, short enough to memorize: "A demo impresses a meeting. A system we depend on has an owner, a definition everyone uses, and a way to see that it is wrong. We [one concrete thing: a queue, a submission, a file] had all three missing. We built those before we let a model anywhere near the work. The model was the last piece, not the first."

David follows, two or three sentences: that pattern shows up everywhere he sits. The unglamorous pieces are the plumbing, the permissions, and the definitions. Then he stops and lets the guest stay the authority.

2. When the model is wrong — Mychal Shaw, once he has seen the question.

When the model is wrong, who is on the hook? Not the vendor who sold the demo. Who in your world owns that, and what do they look at before they trust an answer?

Mychal's line is not written. The old public-safety draft was for Mark Truman, who is not on the panel. Do not hand that draft to Mychal. He answers in his own words.

3. The harness — David

The model you are using today will be a different model next year. What did you have to build around it that still has to be true after the swap?

David: "The model is a component you rent. The harness is the part you own: who can call it, what definitions it is bound to, what gets logged, how you know it is still good, and which human signs the outcome. If those are solid, you can change the model on a Tuesday. If they are not, a better model just fails you faster."

4. What you refuse — Mychal Shaw, then Miles if he nods, then David

What have you refused to automate on purpose? And what did you have to make explicit about how your organization actually works before any automation was safe?

Mychal's line is not written. Do not use the old public-safety draft.

If Miles nods, Justin asks: "Same boundary in your shop, in a sentence?" Card line: "We will not let a model invent a coverage position or talk to a customer as if it were the company. It can prepare. A person decides."

David lands it, and this is the digital-twin beat, said as a field practice: "That map is the work. Sites, people, assets, processes, the words your systems use, connected on purpose. If you automate before you have drawn it, you automate the misunderstanding. The builders who get to Monday morning are the ones who drew the organization first." He does not name a module. Breakouts exist for the how.

Into the room — not a new question

You've heard what this can do for a builder. At 6:30 your number is your breakout. Bring the question you still want to ask, and talk it through at the table. How a harness like this could give you room to build the idea, and room to keep your options open as the business grows.

No audience questions on the mic. A nervous guest and an open floor is a bad trade. People who need a question get a breakout, and they get a person.

If someone freezes

The version I hear from people in that seat is [one sentence from their card]. Did I get that right?

David's bridge. Then he stops talking. The guest gets the last word, even if the last word is "Yes, that's it." Justin never adds a follow-up Miles has not already seen.

What we do not ask

• How Intuidy compares with another product.
• Anything that requires a client to defend a roadmap, an uptime number, or a feature they did not build.
• Price, contract, or "would you recommend them."
• Crime detail, claims detail, or a customer's private facts.
• "Are you worried about AI taking jobs?" as a trap.

Clock

• 5:00 PM Doors Open.
• 5:30 PM Event Opening. Justin, then Grayson. Hard stop 5:45.
• 5:45 PM Hear from real users building on Intuidy.
• 6:30 PM Breakout Sessions.
• 7:30 PM Networking, food, and music.
• 9:00 PM Event ends. Grayson closes on the same challenge. No new speech.

If Grayson is still in the keynote at 5:45, Justin stands and uses the handoff line. They agree on that in rehearsal. The hard questions are about the field, not a trial of Intuidy's architecture. If a question turns into "so how does your product do X," David answers the requirement in the field and points the mechanism to the breakout.

Prep

• Before Fri Sep 25 — Justin. Send the guest sheet below. Do not offer the seat to Chris Kovac.
• This week — David. The panel is three people plus Justin. Field questions, their draft answers attached, they can strike any question.
• Oct 15 — David and the guests. Written yes on name, title, org string, and which questions they will take. Miles has read his two card answers aloud.
• Oct 19–25 — Justin. One walk of the arc. No scripts for Grayson, David, or Mychal. Miles may keep the card. Time the keynote once.
• Oct 22 — Grayson. Opening and close rehearsed with the challenge both times.
• Oct 29, 4:40 — Justin. Mics, seat order, cards on Miles's chair, not in his hand on camera.

Send the guest sheet. Do not send the freeze line or the camera rules.

The record

There is no photographer in the budget. Capture is a team job. One person cannot shoot and catch quotes.

• Stills. One owner with the best phone or a real camera. Name them before Oct 19. John if he will do only this. One group photo in the shirts, early. Grayson at the mic, mouth closed or mid a clean word. The panel wide, all three, once. One frame of each panelist speaking and composed. For Miles, shoot the card answer and stop. Two breakout frames: hands, laptops, a facilitator, the work. Not plates of food. One detail: the shirt line, or the room from the door.
• Quotes. A second person, notes app, not the photographer. Verbatim line, speaker, rough minute.
• Audio. A phone at the board, voice memo, keynote through panel. Never posted raw.
• Edit. Justin, next morning. A one-page quote sheet and 12 frames.

Night of: files into the capture folder. Nobody posts from the room. Next morning Justin sends the quote sheet and the frames to Grayson, David, Miles, and Mychal.

• Grayson and Mychal may post about the room as soon as they like their own lines. They do not quote a client.
• David posts only after both clients have answered.
• Each client owes a yes, a strike, or a silence. Silence is a no.
• Mark Truman is not on the panel. Nothing about him ships.
• Miles Finch may be named as Startland printed him: agent and regional leader at State Farm. A line from his mouth still waits for his yes.

Keep the hard question next to the clean answer. Cut stumbles, product troubleshooting, and any sentence that sounds like the platform is still being figured out on stage. Miles's quote is chosen from his card. David is quoted on the harness and the map of an organization. Mychal is quoted only from a line he approves. Grayson is quoted on invisible builders and the Monday-morning gap. Each person gets one pull quote a stranger could read without a caption. Do not pitch Startland a second story until their first piece has published. Offer Austin three approved quotes and two frames if he asks.

Check-in card

We may photograph the room. Tell us at check-in if you need to stay out of photos.

In the note David sends with the questions

We will record audio for our own notes and send you any line we want to publish. Your name and organization appear only as you approve them. You can strike a line after the night. Public-safety and insurance answers wait for your written yes.

Guest sheet — this is the only part we email

Subject: Questions for Let's Build It, October 29

You are one of three panelists on a 40-minute panel at Let's Build It. Justin Gardner will moderate. The panel is David Lickimbat of Intuidy, Miles Finch, and Mychal Shaw.

The questions are about the field you work in. They are not a product review. You will not be asked to compare tools, talk price, or tell a customer story you would not tell a peer.

We will ask you:

1. What you build, and what pulled you into building it. About two minutes.
2. One of the field questions below. We will mark yours. You will see it in advance. We will not add a surprise follow-up.

• What is the difference, in your operation, between a demo and a system somebody is graded on?
• When a model is wrong, who owns that, and what do they check before they trust an answer?
• What has to stay true when the model itself gets swapped next year?
• What have you refused to automate on purpose, and what did you have to make clear about your organization first?

Please reply with the name, title, and organization you want said out loud; any topic you want left alone; which question you want, if you have a preference; and a yes or no on photography of you while you are speaking.

We will send you a short version of your own answer beforehand so the night feels like a conversation you have already had. After the event, nothing with your name goes out until you approve the line.

Still open

• Legal names and approved org strings for both clients.
• David's title as he wants it said.
• Mychal's title as he wants it said. His answer lines are not written.
• Who holds the camera, who holds the notebook.
• Whether Gentry is on stage for the welcome.

Budget

Venue, chairs, and AV cost nothing, so the spend concentrates on what attendees take home: the shirt, the food, and the film.

Music runs as a playlist over in-house AV. Partner sponsorships can still offset any line: the food spread, the drink station, or the shirt run can each carry a presented-by credit.

The Brand

A strong call to action. It takes Nike’s famous line and makes it a builder’s. The Intuidy mark is the period — eight slices, an Easter egg at the end of the line. Black and white only.

Anton, eight-degree slant, black and white only. The mark is the period. Kansas City is the subhead under Let's Build It, on the marketing lockup and the shirt. Back: full Intuidy logo in white. No creed. Never a second color.

Print files: line, white on blackline, black on whiteline, white inkline, black inkstackedboard

The Shirt

Black tee, white ink. Front is Let's Build It with Kansas City as the subhead (swap the city for future markets). The mark is the period. Back is the full Intuidy logo, all white. No creed. No date. Order 125.

Print-ready city front: white ink / black ink · also aliased as shirt-front-*-ink.png. Back logo PNG 300dpi / SVG. Mark is still the period. Order 125.

The Garments

Two black heavyweight cotton tees. Whichever we pick prints and ships. No separate printer to brief. 125 units (meeting 2026-09-11). White ink, two sides: Let's Build It with Kansas City under it on the front, full Intuidy logo on the back. Grayson and David approve the art, the vendor, and the spend. Quotes below were for 100 — rescale.

AS Colour 5026

Classic Tee. Regular fit. 6.5 oz, 22-singles, 100% combed cotton.

$2,750 (125)

Was $2,200 at 100. At 125: blanks 125 × $15.60 = $1,950. Print $6.40 × 125 = $800. Total $2,750. AS Colour does not print. A decorator prints and ships.

Color

Black

Blanks

$15.60 each at 50+ on ascolour.com. $1,560.

Print

1-color white, two locations. $3.20 per location at 100 (French Press 2026 public rate for 100–199). $6.40/shirt = $640. Screens usually waived at 100.

Our job

Front line + back logo, white ink. They print and ship.

Working total

$2,200. Not a firm shop quote.

Source

ascolour.com blanks. Print: French Press 2026.

LA Apparel 2017

6.0 oz crew, 20-singles, 100% combed cotton. Unisex. Made in USA. Via Blankstyle.

$2,341 (125)

Was $1,873 at 100. At 125: 125 × $15.23 = $1,904 at the decorated tier, plus $3.50 × 125 = $438 for the second location. Total $2,341.

Color

Black

In the $15.23

Decorated. 1 color, 1 location, sizes XS–XL.

Our job

Two locations. Pad $3.50 × 100 for the back.

Working total

$1,873 proposed

Source

blankstyle.com

Open (GS/DL): approve city-front art, pick vendor, approve spend for 125. Blankstyle working $2,341. AS Colour working $2,750. Size curve still open. Working blank estimate ~$9 wholesale — confirm with shop before PO.

Copy for intuidy.com

Live on intuidy.com. Mirror the registration page here. Dark hero for our kit; their live page uses their own chrome. Date is Thursday, October 29, 2026. Title on their page: Let's Build It. Kansas City.

Eventbrite header, 2160×1080. B Split is the one for the website and the listing. Lockup owns the left. Inviting orgs sit on the right. Date is type, not a date lockup.

Source HTML and render script: marketing/eventbrite/. Listing fields: LISTING.md. Captions: POSTS.md.

Social posts that name the event and explain the night. Dark or paper. Partners can post either.

Short social, partners can post as-is:

Newsletter blurb:

Meta title: Let's Build It. Kansas City. Meta description matches the live Intuidy.com page. Registration URL locked. OG on their page uses Grayson's Drive banner.

Date, time, and Spark (1475 Walnut St) are on every graphic. Partner marks are labeled Inviting — they have not confirmed. KC Tech Council and Spark are official logos knocked to white. KC Digital Drive, KC Tech Forward, and Keystone CoLab are typeset until we have clean knockout files. Hold the printed date if Austin has not confirmed October 29 in writing.

Startland News — Tuesday email

Materials for Startland News (Tommy on email; Austin on story). Updated from Grayson's 2026-09-13/14 thread. Copy lives here so we do not email a zip.

4. Image + Startland ad sizes

4b. Startland ad exports (visual QA)

Live: banner · box. Drive logos/banner from Grayson: Drive file. Checklist: lockup readable at email width, no muddy crop, link target is the Intuidy.com registration URL.

Markdown twin: send/STARTLAND-NEWS-PACKET.md + send/STORY-QUOTES-DRAFT.md. Newsletter image: newsletter-header.png.

Partner one-pager

Written for KC Digital Drive, KC Tech Forward, KC Tech Council, Keystone CoLab, KC AI Club, and KC Area Development Council. Justin sent the first touch on Thu Oct 2, except Keystone. KC Tech Forward is Intuidy's own list and was not emailed outside. Names stay off the event page until that org says yes.

What your org gets. Named as a partner on the event page and in the room. An expo table during the 7:30 networking block. A stage mention in opening and close. Ready-to-post copy and graphics so the push costs you nothing. Your people in a room of 100.

What we need from you. The night on your list and channels the week Intuidy opens registration. One or two people in the room, table optional. Co-branding on your post: Let's Build It, hosted by Intuidy, your name as partner.

Ready-to-post copy. Let's Build It. Kansas City. Thursday, October 29 at Spark Coworking, 1475 Walnut St, KC, 5 to 9. Let's bring the Builder community together. Meet Grayson & Gentry Smith, the founders of Intuidy, and hear from real builders and companies using Intuidy. https://intuidy.com/events/let-s-build-it-kansas-city

Thu Oct 2: Justin sent KC Digital Drive, KC Tech Council, KC Area Development Council, and KC AI Club. Grayson and David were copied. Grayson still sends Keystone to Kevin McGinnis.

What we need this week

Open actions for the week of Sep 21–27, after the Mon 9/21 room. October 29 is booked 3:00–10:00 p.m. Panel names are locked. Partner first-touch went out Thu Oct 2. Keystone is still Grayson's send.

GS GraysonDL DavidJG JustinJA John

Countdown phase this week: Lock the program (Sep 21–27). Venue window and panel names are locked. Promo mode starts when Startland ships. Notes: weekly/log/2026-09-21-meeting.md.

What's new

Operator history lives on its own page now — feedback → change, owners, what Justin shipped, and how it landed.

Markdown twin: CHANGELOG.md. Meeting notes: weekly/log/2026-09-21-meeting.md. Live page: /changelog/.