Blog

Insights on video, web, and software.

updatesAug 29, 2026

The Scoping Call Has One Job: Name the Number

We redesigned our intake process around a single question: what's the one number this system has to move? If you can't name it in 30 minutes, we don't take the build.

webAug 28, 2026

Operating Software Is Not the Same as Supporting It

We rewrote how we describe the retainer. 'Support' implies a queue. 'Operation' means someone is running the system every day.

updatesAug 27, 2026

We Killed the Offer Ladder

We had four offers. The bottom one never produced a lead. We collapsed the whole ladder into one engagement structure and it's already cleaner.

webAug 26, 2026

Stop Putting Vendor Names in Your Marketing Copy

We removed n8n, Zapier, and every other tool name from our site copy. Here's why, and where the real risk was hiding.

webAug 25, 2026

Three Planning Rounds Were Not Enough. A Test Was.

When we migrated the site to new positioning, we planned the copy sweep three times. Every round missed something. Here's how we made the fourth round permanent.

aiAug 24, 2026

Not Every Skill in the Pack Was Built Here

When we shipped five Claude skills for an ag sales team, three came from existing sources and two were built from scratch. That split was a decision, not an oversight.

aiAug 23, 2026

A Skill Nobody Uses Is Just a File in a Folder

When we shipped the Freedom Ag skills pack, we shipped five skills and five scenario prompts. The prompts are why the skills get used.

aiAug 22, 2026

The Tool Without the Training Is Just Another Login

Skills don't land unless the earlier modules already worked. That's not a content problem. It's a trust problem, and the curriculum is how you solve it.

aiAug 21, 2026

Symlinks Break Claude Skill Zips

When packaging Claude skills as distributable zips, plain zip stores the symlink pointers, not the files. The install silently ships nothing.

aiAug 20, 2026

Leave It Zipped

When we shipped the Freedom Ag skills pack, most of the product design work happened in the README, not the skill files.

aiAug 19, 2026

The Fastest Way to Build a Skill Is to Stop Describing It

Claude's new Skill Creator lets you record your screen doing something you already do, hand Claude the video, and get a reusable skill back. We noticed it while shipping five hand-crafted skills for a client. The contrast is instructive.

aiAug 18, 2026

Five Skills for an Ag Sales Rep

The hardest part of building a skills pack isn't the technical side. It's picking which frameworks actually match how this business runs.

aiAug 17, 2026

The Prompt That Teaches Any Skill You Install

Instead of writing a separate tutorial for each skill we ship, we wrote one prompt that makes Claude open the skill, read it, and explain it in terms the client already knows.

aiAug 16, 2026

Brackets Are the Proof It Didn't Fabricate

When you run the business file builder and see [square brackets] in the output, that is the prompt working. Claude marked what it didn't know instead of guessing.

aiAug 15, 2026

A Correction You Make Twice Is a Missing Rule

Most people fix bad AI output by rewriting the prompt. The problem moves to the next session. The third prompt in module 4 exists to convert a live correction into a permanent rule in the business file.

aiAug 14, 2026

The Pressure-Test Prompt Finds What Your Business File Can't Stop

Writing a business file feels like finishing something. The second prompt in module 4 exists to prove you are not done. It attacks the file before you start relying on it.

aiAug 13, 2026

Personalization Is the Last Module, Not the First

We put the business file module last in our Freedom Ag curriculum on purpose. A business file written before you've used Claude is full of guesses. You need real corrections first.

automationAug 12, 2026

The Automation Audit That Ranks by What It's Worth

We built a free prompt that puts a monthly dollar cost on every manual task in your business and ranks what's actually worth automating first.

aiAug 11, 2026

The Marketing Prompt That Argues Back

We built a grower-acquisition thinking partner for ag supply that refuses to give you ideas without also telling you why each one might fail and what common move to kill entirely.

aiAug 10, 2026

One File, Three Homes: Teaching Claude Who You Are

Most people re-explain their business to AI in every chat. The fix is a single written file that lives where Claude reads it automatically.

aiAug 9, 2026

Every Prompt in the Skills Pack Has an Interview Gate

We built five free AI prompts for small business owners as part of a client training module. Every single one refuses to produce output until it has interviewed the owner. That constraint is the point.

aiAug 8, 2026

The Prompt Asks Before It Builds

Every prompt in our client marketing skills pack has one rule: interview first, generate nothing. Here is why that constraint matters and what it prevents.

webAug 7, 2026

The Upload Token Has to Know Overwrite Is Allowed

Training videos are too big for a Next.js API route, so the server mints a scoped token and the client uploads directly to blob storage. One field on that token determines whether a corrected take can replace the original.

webAug 6, 2026

One Field Invalidates Every Cookie for That Tenant

We needed a way to force re-authentication for one client without rotating the shared signing secret. The answer was a version number baked into the HMAC payload.

aiAug 5, 2026

Build the Voice File Before You Schedule the Task

We built a training module teaching clients how to automate morning inbox triage with Claude. The first prompt in the workflow isn't the triage prompt. It's a prompt that captures how the person actually writes.

webAug 4, 2026

The Prompt Was On a Different Page Than the Video That Promised It

We built a client training portal and got the data architecture wrong on the first pass. The prompt the trainer promises on camera lived on a different page than the video. Here's how Zod made that failure invisible and what we did about it.

automationAug 3, 2026

The Form Fires Four Things at Once. Only One of Them Can Fail.

We launched the AI Operations Academy with a $750 readiness assessment as the entry point. When someone submits that form, four operations fire simultaneously. Here's how we decide which ones matter.

webAug 2, 2026

preload='none' Was Correct. Until We Fixed the Server.

We spent two days debugging a training portal video player. The preload attribute started at 'metadata', landed at 'none' as a workaround, then went back to 'metadata' once the server was actually ready for it.

aiAug 1, 2026

The Same Word Means Something Different Depending on Who Said It

We built a free AI and software glossary for business owners. The hardest part wasn't the definitions: it was the words that mean one thing to a developer and something completely different to everyone else in the room.

webJul 31, 2026

The Route That Never Touches the File

Training videos are 50-100MB. Vercel serverless functions cap out at 4.5MB for request bodies. We solved it by writing an upload route that only mints a token.

webJul 30, 2026

74MB Down Before the First Frame

Our training portal video required downloading almost the entire file before playback could start. The moov atom was at the wrong end.

webJul 29, 2026

curl Was Happy. The Video Player Wasn't.

We proxied private training videos through a Next.js API route, curl returned data without complaint, and the browser video element refused to play. Here's why and what fixed it.

aiJul 28, 2026

We Built a Gated Training Portal. The Second Tenant Is One JSON File.

Client training shouldn't live in a Google Drive folder. We built a password-gated portal with tenant isolation, then designed it so adding a second client requires no code at all.

webJul 27, 2026

The Build Passed and the Page Didn't Exist

Our /book page was referenced by CTAs across the site, local builds passed, and the file had never been committed. Here's how that happens and what we're doing about it.

aiJul 26, 2026

We Built a 76-Term AI Glossary and Didn't Put a Form on It

The new /glossary page defines every acronym a software or AI vendor is likely to throw at a small business owner. It's free, ungated, and that's a deliberate call.

automationJul 25, 2026

Three Nodes to Wire an AI Intake Triage in n8n

The spec-form triage we recommended for Coan Engineering isn't a vague AI concept. It's three n8n nodes: webhook, AI draft, route to review. Here's exactly how it wires together.

automationJul 24, 2026

Nothing in the Shop Got Replaced. It All Got Connected.

The most common automation hesitation we hear is 'we'd have to change everything.' The Coan Engineering audit is a useful counterpoint: five workflows, zero platform migrations.

automationJul 23, 2026

Five Workflows Found. The Order We Build Them Matters.

An audit that surfaces five workflows worth automating doesn't produce five equal projects. The sequence you build them in determines whether the engagement succeeds.

automationJul 22, 2026

The Return Form Is the Last Paper Process in the Shop

Every shop we audit has at least one workflow still running on paper. For the transmission shop in Kokomo, it was returns: a downloadable PDF, filled out by hand, emailed back, and re-keyed manually with no tracking number issued.

webJul 21, 2026

The Trust Strip Has to Be Real

When we rebuilt our homepage, we skipped the client counter. We built a live ticker showing real production projects instead. Every claim has to be something a visitor can verify right now.

automationJul 20, 2026

Three Form Types, One Inbox, No Assignment Rules

When spec forms, repair forms, and contact forms all land in the same sales inbox, leads get read by whoever happens to see them first. That is not a routing system.

webJul 19, 2026

We Built a PWA for SWAT Teams. Here's What That Demanded.

Command Post is a multi-tenant operations platform for tactical teams: mission planning, after-action reports, training tracking, team management. It's live with paying teams. Building it required domain knowledge most developers don't have.

aiJul 18, 2026

AI Coaching Before the Build

Not every business is ready to commission a custom portal or automation pipeline. AI coaching is the engagement that comes first: map the workflows, find the highest-ROI starting point, and leave with a clear plan.

automationJul 17, 2026

The Custom-Build Quote Has a Three-Day Window

A high-ticket custom-build quote that doesn't close on the first call depends entirely on someone remembering to follow up. Most don't. The customer shops elsewhere, or just keeps running the old part.

automationJul 16, 2026

The 'Where's My Converter' Call Is a Tax on Your Shop Floor

Inbound status calls look like customer service. They're actually a hidden labor tax: five to ten minutes of staff time per call, paid by people who could be doing something else.

aiJul 15, 2026

We Keep a Handoff Doc in Every Repo So AI Sessions Don't Start From Zero

Every AI session starts fresh. A structured HANDOFF.md at the repo root lets the next session pick up exactly where the last one left off, without spending 10 minutes re-establishing what already happened.

webJul 14, 2026

How We Built a Portal for 100+ Early Intervention Providers on Top of Airtable

Airtable is not usually the answer for a production portal with 100+ providers. We made it work by building a caching layer and optimistic-save UX that keeps the app fast even when the API isn't.

aiJul 13, 2026

We Built a Weed-ID Assistant Into a Farm Supply Platform

A grower standing in a soybean field shouldn't have to call the extension office to identify a weed. We built an AI assistant into a farm supply platform that gives instant, sourced herbicide recommendations on the spot.

webJul 12, 2026

We Stripped the Prices From Our Homepage

Our homepage listed 'Free' and 'From $4,500' on the offer cards and guaranteed payment protection. We removed all of it. Here's why transaction framing was working against us.

webJul 11, 2026

We Built a Type Lab to Pick One Font Pairing

Before shipping Fraunces serif headings sitewide, we built a throwaway page that rendered five font pairings against real UI components. Here's how that process worked and what we decided.

updatesJul 10, 2026

We Deleted 22 Components to Make Our Site Better

Our old site had 3D scenes, cursor glows, gradient blobs, and a terminal animation. We deleted all of it and built something clients can actually read.

aiJul 9, 2026

A 40-Field Spec Form Is a Job Description for an AI

High-performance transmission shops don't have an admin problem. They have an AI triage problem: skilled techs spending 20-35 minutes on every custom spec submission before a human even starts the quote.

automationJul 8, 2026

A Prospect Audit Is a Commit, Not a Feature

Our ops audits live at a URL, ship as a PDF, and get deleted from the repo when the sales window closes. The git log is the audit trail.

automationJul 7, 2026

Five Workflows a Medspa Audit Almost Always Finds

Medical practices built on repeat visits already have the data to automate patient recall, lead response, and review generation. The PMS knows who's due. Nothing is triggering it.

aiJul 6, 2026

A Build Spec Without a Payback Period Is Just a Scope of Work

Phase 2 delivers two documents per workflow: a technical spec and an ROI model. The number that closes the decision is payback period, not an abstract percentage.

aiJul 5, 2026

Every Phase Has a Deliverable You Keep

The four-phase structure on our /ai page isn't formatting. Each phase ends with a named output the client keeps, and that's the actual mechanism that makes a 6-week custom build a credible ask.

automationJul 4, 2026

What an AI Operations Engine Handles Before You Open Your Inbox

The ticker on our /ai page lists five sample activities. Here's what each one actually means technically and why all five should run without a human touching them.

aiJul 3, 2026

The Service Page FAQ and the City Page FAQ Do Different Jobs

We use FAQPage schema on both our /ai page and our six city landing pages. But the two FAQ strategies are completely different, and mixing them up wastes one.

aiJul 2, 2026

The Phrase Has to Match Everywhere Before AI Search Can Quote It Right

We aligned one service phrase across our meta description, FAQ answers, city page copy, and Service JSON-LD. Consistency across all four is what lets AI engines resolve the entity correctly.

aiJul 1, 2026

Five Questions AI Search Needs to Describe Your Service

When an AI assistant fields a query about a local service business, it synthesizes an answer from what it can read. We structured five FAQ questions to pre-answer everything it needs.

aiJun 30, 2026

Three Claims We Narrowed on Our /ai Page Before AI Search Could Quote Them

AI search engines quote your page verbatim. We ran our /ai page through a quote-back test and found three claims that needed to change before a prospect could cite them back to us on a call.

aiJun 29, 2026

Why We Named the County Before the Cities in the /ai Meta Description

Our /ai meta description groups four Hamilton County cities under the county name. That structure covers county-level queries and city-specific queries at the same time.

aiJun 28, 2026

Eight Checks Before We Call a Page GEO-Ready

After rebuilding our own /ai page for generative engine optimization, here's the concrete checklist we'd run on any service page before calling it done.

aiJun 27, 2026

Service Schema Tells Search Engines What You Do and Where

FAQPage schema answers questions. Service schema identifies the offer. We added both to /ai and tied them to six cities with areaServed.

webJun 26, 2026

Every City Page Traces Back to One TypeScript File

We have six city landing pages. Each one has unique content, geo-targeted metadata, and server-rendered schema. All of it comes from a single array.

aiJun 25, 2026

AI Search Quotes Your Page. You Can't Walk It Back on the Call.

We audited our own /ai page for claims we couldn't back up, and changed three of them. Here's why it mattered and what we were looking for.

aiJun 24, 2026

The Meta Description Is What AI Search Quotes

We changed one line on our /ai page and spent the rest of the day making sure every other surface said the same thing.

aiJun 23, 2026

FAQPage + Service Schema: Two Jobs, One Page

We added two JSON-LD schemas to our /ai page this week. Each one does a different job for a different engine, and you need both.

webJun 22, 2026

One Field Closes the Lead Loop in Both Directions

Every notification email we send from a form route sets replyTo to the lead's email. Every confirmation email sets replyTo to our real inbox. One field per send, fully bidirectional.

webJun 21, 2026

PostHog Does Two Jobs In Our API Routes

Every form route on the site calls both PostHog capture and captureException. One tracks funnel events, the other monitors failures. Here's why we use one tool for both and what that requires.

webJun 20, 2026

The User Email Is a Promise. The Airtable Record Isn't.

When an API route has multiple side effects, not all failures deserve the same response. Here's how we split fatal from non-fatal across five routes.

webJun 19, 2026

Config Data Has Invariants. Test Them.

TypeScript can tell you a city has a slug. It can't tell you all slugs are unique or every city has a non-empty FAQ. Those guarantees come from tests.

automationJun 18, 2026

Five Funnels, One Table: How We Keep Lead Attribution Clean

We have five different entry points into our business. Every one of them writes to the same Airtable table with a source tag. Here's how one shared function keeps attribution clean across all of them.

webJun 17, 2026

Design the HTML for the PDF You're Going to Generate

Our ops audit lives at a URL and ships as a PDF. Both come from one Next.js page. The decisions that make Playwright produce a clean PDF are baked into the HTML, not bolted on after.

webJun 16, 2026

Our Bot Filter Has No CAPTCHA

We filter form spam with a honeypot: a hidden 'Company' field that bots fill and real users never reach. Here's how the React implementation differs from traditional HTML forms.

webJun 15, 2026

Six City Pages, One Entity: The @id That Holds Them Together

When we added city landing pages for Central Indiana, each page emitted its own LocalBusiness schema. Without a stable @id, Google could read them as six different businesses.

webJun 14, 2026

Nav CTAs Should Break Tests. Hero Headlines Shouldn't.

We updated our homepage copy and two test files failed. One failure was correct. The other was noise. The difference is how you wrote the test to begin with.

webJun 13, 2026

Prospect Pages Don't Need a Login. They Need a Random Slug.

Our ops audit deliverables are live URLs, not password-protected portals. Here's the design decision behind that choice and how we keep them off search engines.

webJun 12, 2026

Your Root Layout Owns the main. Don't Write Another One.

When we built the audit page, it rendered two main elements at once. One from the root layout, one from the page component itself. That's an ARIA landmark violation, and screen readers notice.

aiJun 11, 2026

The Agent Writes JSON. The Code Writes the PDF.

When we built the ops-audit pipeline, the agent's job isn't to write the document. It's to produce structured data. The presentation is handled by code.

webJun 10, 2026

Type Assertions Don't Validate JSON. Tests Do.

When we built the ops-audit content loader, TypeScript's `as Audit` cast looked like validation. It isn't. Here's what actually protects the shape at runtime.

webJun 9, 2026

ISO Dates Default to UTC. That Broke Our Audit.

We caught a bug in the ops-audit deliverable where the date rendered one day early for every US-based prospect. Here's what caused it and the two-character fix.

aiJun 8, 2026

The Next Step Lives Inside the Deliverable

Most audits and proposals end with 'let us know if you have questions.' Ours end with the price, the path, and a button. Here's why we embed the offer inside the document.

aiJun 7, 2026

We Read Their Job Posts Before the Sales Call

The four public sources we check before every ops audit, and why job postings are usually the most honest signal a business publishes.

automationJun 6, 2026

Our Ops Audit Is a URL That Becomes a PDF

We built a Playwright pipeline that turns a JSON audit file into a branded PDF deliverable without ever opening InDesign or Figma.

webJun 5, 2026

Don't Add aggregateRating Until Your Reviews Are on the Page

Adding a fake star rating to your JSON-LD is a policy violation that can pull a manual penalty. Here's what we did instead and when we'll add it for real.

webJun 4, 2026

Your Primary GBP Category Is Your Maps Pack Bet

Google Business Profile lets you pick one primary category. For a multi-discipline agency, that choice determines which searches put you in the Maps Pack. Here's how we made the call.

webJun 3, 2026

Testing the Schema You Actually Ship

Most SEO advice stops at 'add JSON-LD.' We test that the structured data is actually in the rendered HTML and matches what the component displays, using renderToStaticMarkup in Vitest.

webJun 2, 2026

Keep Your JSON-LD in Server Components

In Next.js App Router, putting structured data in a client component risks crawlers seeing empty script tags. Here's how we structured our schema components to guarantee server-rendered JSON-LD.

webJun 1, 2026

City Pages That Don't Get You Penalized

City landing pages are a local SEO requirement, but near-identical pages with swapped city names get flagged as doorway spam. Here's the architecture we use to thread that needle.

aiMay 31, 2026

Bing Places Is Your AI Search Strategy

ChatGPT and Copilot pull local business data from Bing. If you're only optimizing for Google, you're invisible to half the AI assistants your customers use.

webMay 30, 2026

Why We Write Our FAQ Questions as Search Queries

FAQPage schema isn't just for rich results. When you write the questions as verbatim search queries, each city page becomes a targeted answer to the exact thing someone typed into Google.

webMay 29, 2026

One Config File, Six Cities: Our Local SEO Architecture for Central Indiana

How we built a local SEO system in Next.js that keeps all NAP data and city content in a single TypeScript file, with server-rendered JSON-LD on every page.

webMay 28, 2026

Card-Style Form Selects Without a Component Library

Our audit form's service, timeline, and budget pickers are clickable card grids, not dropdowns. Built with native HTML inputs inside Tailwind labels. No library needed.

aiMay 27, 2026

We Removed the Pricing Block and Made the Audit the Only Door

Our /ai page used to have pricing tiers and two separate product pages. We collapsed it to one page with one CTA: book the free audit call.

aiMay 26, 2026

Telling People They're Not a Fit

Our /ai page has a strikethrough list of reasons not to hire us. It converts better than a list of reasons to hire us.

aiMay 25, 2026

Show the Output, Not the Feature

Our /ai hero has a fake operations log. It's not real data, but it's more honest than a feature list.

aiMay 24, 2026

The Preflight Gate That Stops Generic AI UI

We built a Claude Code skill called /impeccable that refuses to write a single line of code until it has passed five context gates. That gate is what makes the output look intentional.

aiMay 23, 2026

Selling on the Call, Not the Page

We removed the pricing tiers from our AI service page and made the free audit the only CTA. Here's the logic.

webMay 22, 2026

Three Things Happen When You Submit Our Audit Form

Every Operations Engine audit request triggers three async writes in parallel. Only one of them can fail without showing the user an error.

webMay 21, 2026

One File Owns the Form: Zod as a Single Source of Truth

When we built the Operations Engine audit form, we colocated the field options, TypeScript types, and display labels in one schema file. Adding a service without its label is a compile error.

automationMay 20, 2026

Vercel Killed Our Airtable Writes (And We Didn't Notice)

We replaced n8n with direct Airtable writes and thought we were done. Then we discovered that Vercel serverless terminates functions the moment the response fires, taking any pending promises with it.

webMay 19, 2026

Two Audiences, One Page: The Operator Door Pattern

Our /ai page pitches a developer tool. Service business owners land there too and see nothing for them. A slim callout band fixed the bounce without touching the main pitch.

webMay 18, 2026

We Write Our Transactional Emails as TypeScript Functions

Most transactional emails look nothing like the site that sent them. Ours are dark, typeset, and match the brand because we build them as functions, not files.

aiMay 17, 2026

How We Turned Repeatable Client Work Into a Productized AI Service

We kept building the same thing for service-business clients: quote pipelines, office automations, job history memory. We finally packaged it into a four-phase product with fixed deliverables and real pricing.

webMay 16, 2026

Wiring PostHog Into Next.js App Router Without Losing Pageviews

App Router's navigation model breaks PostHog's default pageview autocapture. Here's the exact setup we use: a Suspense-wrapped tracker, a server singleton, and dual-event lead confirmation.

webMay 15, 2026

We Packaged Our Proposal Workflow into a Toolkit for Other Videographers

Every interactive proposal we've built for clients uses the same workflow: Claude Code generates the page, /impeccable polishes it, Higgsfield generates the images, Vercel deploys it. We just made that workflow something anyone can pick up.

automationMay 14, 2026

When n8n's Quota Ran Out and Killed Every Form Submission

Our n8n cloud instance hit its execution quota. Every lead form on the site kept working, kept sending emails, and kept silently dropping every record. Here's how we cut out the middleman.

webMay 13, 2026

The Scroll-Triggered Terminal We Use to Show Case Study Data

Static screenshots don't convey what a production system actually does. Here's the component we built that boots a deploy log on scroll, and the decisions that made it work.

aiMay 12, 2026

We Used AI to Generate Our Website's Hero Video

We needed a background video for the homepage hero that felt premium and matched our brand. Here's how we generated it with Seedance 2.0 via Higgsfield and wired it into Next.js correctly.

automationMay 11, 2026

The Lead Pipeline Gap That Makes No Noise

We shipped a new lead form, emails went out fine, and we missed every lead anyway. Here's the pattern that fixed it and why new endpoints need two separate wiring jobs.

webMay 10, 2026

One File Controls Every Meta Tag on Our Site

We keep all Next.js App Router SEO metadata in a single TypeScript file. One helper, one record per page, zero duplication. Here's exactly how it works.

webMay 9, 2026

We Structured Our AI Services Page Like a Hormozi Offer

The /ai page used to explain what the /impeccable skill does. Now it argues for it. Here's the Grand Slam structure we used and why each section exists.

automationMay 8, 2026

What We Built Behind the New Homepage (It's Not What You'd Expect)

We rebuilt our homepage as a real sales page. Here's the lead pipeline we wired behind the audit form: Zod validation, Resend emails, and a fire-and-forget webhook to n8n and Airtable.

webMay 7, 2026

Five Motion Primitives We Built for Our Site Rebuild

We rebuilt our homepage and needed motion that felt premium without becoming a performance liability. Here are the five components we reached for and the tradeoffs behind each.

automationMay 6, 2026

We Built Our Own Inbound Lead Funnel in an Afternoon

A Next.js API route, one n8n webhook, and a PDF lead magnet: here's how we wired up full end-to-end lead capture without touching a third-party form tool.

aiMay 5, 2026

We Rewrote Our Lead Magnet Copy and Here's the Before/After

Our first version of the /ai landing page listed five useful automations. Our second version attached dollar amounts and named specific outcomes. The difference is the whole game.

webMay 4, 2026

We Turned Our 404 Page Into a Three-Act Magic Trick

We replaced our generic 404 with a typewriter monologue, a giant 404 reveal, and a 'Back to the show' CTA. Here's how it works and why we built it this way.

automationMay 3, 2026

We Generated Our Lead Magnet PDF from Code. Here's the Stack.

We built a full lead capture funnel for our AI services page: a Playwright-generated PDF, a Next.js capture API, and an n8n webhook handling Airtable, Gmail, and Slack downstream.

aiMay 2, 2026

We Stopped Sourcing Stock Photos for Storyboards. We Generate Them Instead.

For a fire department recruitment video proposal, we replaced manually sourced stock photos with Gemini-generated scene frames. The difference in how well each image communicates the intended shot is hard to overstate.

webMay 1, 2026

One Script Failing Shouldn't Break the Whole Page

While building a client proposal page, a Supabase CDN failure was silently killing our scroll animations. Here's the layered initialization pattern we settled on and a naming collision bug that made us appreciate it even more.

webApr 30, 2026

Why We Bundled a Free Website Into Our Top Proposal Tier

When we structured the pricing for a fire department recruitment video, we added a full recruitment website as a free bonus on the top tier. Here's why that decision made sense for the client and for us.

webApr 29, 2026

Your Contact Form Is Lying to You

We fixed a bug in our own contact form that returned 200 OK even when Resend failed to deliver the email. The user thought their message went through. It didn't.

webApr 28, 2026

We Replaced the PDF Proposal with a Live Web Page

For a fire department recruitment video proposal, we built a live site instead of a PDF: scroll animations, AI-generated storyboard images, and a Supabase-powered comment system so the client can react to every scene and approve the project directly in the browser.

aiApr 27, 2026

AI Consulting: Why We Added Advisory Work to Our Services

We expanded beyond pure implementation to offer AI audits, team training, and ongoing advisory support. Here's what changed and why.

aiApr 26, 2026

We Built a Soil Valuation Portal Powered by Live Fertilizer Prices

A farm management client needed to automate soil nutrient valuations. We built a full-stack portal with a custom MCP server pulling real-time FRED pricing data so the numbers are always current.

automationApr 25, 2026

The Daily Grind: How We Automated Our Own Content Pipeline with n8n and Claude

We built a 5-workflow n8n automation suite that runs every day at 5pm, generating content, finding prospects, and surfacing one skill to sharpen. Here's how it works.

webApr 25, 2026

Replacing a 3D Portfolio with Sticky Tabs and Scroll Tracking

We built an immersive WebGL scroll corridor for our portfolio section, then replaced it with something simpler and better.

updatesFeb 25, 2026

Hello World

Welcome to the Twenty One Media blog. We write about building things that matter.