Search creators⌘K
  1. Home
  2. Creators
  3. David Crowder

David Crowder

David Crowder builds AI systems for manufacturing. Crowder describes their work as “software manufacturing” and focuses on making AI useful in real shops, including smaller operations with limited staff and imperfect production drawings.

3.1K followersManufacturing AIBased on 10 posts · latest Oct 2026
LinkedIn

At a glance

David Crowder is most useful for explaining why manufacturing AI fails on real shop drawings and small-team conditions.

Best for

A manufacturing AI vendor seeking a co-authored piece on real shop drawing failures.

Not for

A national reshoring advocacy campaign aimed at legislators, media, or large plant executives.

Key takeaways

  • A drawing looked normal but had duplicated file text, so AI read 0.5 as "0.50.5".
  • Another drawing had notes printed at an angle, which the system did not find.
  • Crowder says products assuming dedicated IT or compliance staff do not fit small shops.

Check first: Confirm whether their LinkedIn audience is shop owners and decision-makers, not vendors or observers.

Main ideas
Judge manufacturing AI on real shop drawings, not clean demos · Software that assumes a plant ten times the size of its customer · The small shops are the industry, and the base of any manufacturing comeback
Audience
3,114 LinkedIn followers
Read first
Why AI demos pass on drawings real shops never receive
Sources for this section

What they are known for

David Crowder builds AI systems for manufacturing and describes the work as “software manufacturing.”

  • In four LinkedIn posts, they focus on whether AI can handle the conditions real shops face: imperfect drawings, small teams, and limited time and technical support.
  • They say they are not a machinist; their stated perspective comes from years around manufacturing and building software for the industry.
  • The posts also connect shop-floor problems to broader questions about US manufacturing capacity.

Crowder makes manufacturing AI problems concrete.

  • One post describes a drawing that looked normal to a person but contained duplicated text in its file data, causing an AI system to read 0.5 as “0.50.5”; another describes notes the system missed because they were printed at an angle.
  • They use these examples to ask whether systems have been tested on real job files, not just clean demonstration PDFs.
  • They also focus on who must operate the software: products designed around dedicated IT or compliance staff do not fit many small shops, where owners already handle quoting, production, customers, and bookkeeping.
  • These posts are worth following for their practical focus on the gap between polished demos and shop conditions, as well as arguments about the capacity and resilience of the manufacturing base.
Sources for this section

Ideas and priorities

David Crowder writes about the gap between how manufacturing software is sold and how manufacturing shops actually work.

Read more

Two arguments run through the material: AI products are demonstrated on clean, desktop-fresh files, then meet their first real customer drawing on a live job; and most are designed for a plant roughly ten times the size of the shop buying them.

  • Crowder widens the same point into an industrial-base argument: small shops make up three quarters of US manufacturers and are where capacity lives, but the country has lost the ability to convert that base at scale.
  • They describe their own authority as a maker and software builder who has spent 35 years alongside the industry, not a machinist or shop owner.

Judge manufacturing AI on real shop drawings, not clean demos

Crowder’s central claim about AI in manufacturing is that test conditions matter more than the pitch.

Read more

Vendors demonstrate on crisp PDFs that have never left a desktop — clean lines, clean text, everything where it should be — while shops receive drawings that have been scanned, faxed, folded in half, written on in pencil and passed through several hands.

  • A system that passes the demo meets its first genuine customer drawing when a real job depends on it.
  • The practical question for buyers is simple: what did the system get tested on, and did any of it come from a real job?

One incoming drawing looked completely normal on paper, but its file had saved every word twice beneath what the eye sees: a value of 0.5 came back as "0.50.5," and every check failed on a drawing any machinist would have read without squinting.

  • On a second drawing, notes printed at an angle weren’t found at all.
  • Both files, Crowder argues, are ordinary — the kind that arrive from customers, engineers and purchasing departments.

Read original

Software that assumes a plant ten times the size of its customer

Crowder argues that almost everything sold as AI for manufacturing is built for the wrong buyer — a facility with an IT department, a compliance team and someone whose job includes integration.

Read more

A polished demo can read a drawing, run a compliance check, flag an issue and route it to the right person; it doesn’t answer who sets it up, maintains it or handles it when it breaks.

  • In a shop with a dozen people, the owner is already quoting parts, running the floor, handling customers and doing the books.
  • There’s no spare person to become the AI person.
  • Crowder’s priority is operability over capability: whether a tool survives contact with a small team, not whether it performs on a screen.

Crowder cites the scale of the problem directly: 74 percent of US manufacturers have fewer than 20 people in the whole building, against more than 239,000 manufacturers overall, three quarters of them small operations. Vendor answers to questions about setup and maintenance assume infrastructure that exists at a 200-person plant but not at a shop with 12.

Read original

The small shops are the industry, and the base of any manufacturing comeback

Crowder treats small manufacturers not as a niche market but as the capacity itself: "The 74 percent are the industry."

Read more

Widening the lens turns the same structure into a resilience argument.

  • In World War II, the whole country converted: factories that made consumer goods switched to batteries, tires and tanks, and that is how the war was won.
  • Crowder says that couldn’t happen now because those facilities are gone, and notes China’s roughly four times the population and somewhere around 70 percent more manufacturing capacity.
  • The position holds two things at once: the United States is still the second-largest manufacturer on earth, and Crowder wouldn’t bet on it in a long manufacturing war.

The reasoning rests on a scale comparison rather than a single incident.

  • During COVID, the country needed two products and couldn’t make its own N95 masks — a portion of what arrived from overseas did not meet performance standards — while the national ventilator stockpile held roughly 20,000 units and 200,000 more had to be ordered under the Defense Production Act.
  • A long conflict, Crowder argues, demands everything a country can build, all at once, for years.

Read original · Original 2

"Software manufacturing": a builder's vantage point, not a machinist's

Crowder states the limits of their own authority before making any claim about shop work: not a machinist, and never pretended to be one.

Read more

Their expertise is as a maker and builder of AI systems, and the parallel is deliberate — Crowder calls the work "software manufacturing" because both are constrained, both demand precision, and both break when someone skips a step; the only real difference is a physical constraint versus a virtual one. The stated background runs from Thomas Register, through years at MFG, to founding an additive manufacturing factory recognised by the World Economic Forum, described as 35 years around people who make things — standing next to the work rather than running machines, quoting parts or managing the floor.

Crowder draws the line in their own words: "I am not the shop owner.

  • I am also not the tech vendor pitching from a slide deck."
  • The positioning is an argument about where useful manufacturing software comes from: close enough to the work to understand it, and experienced enough in software to know what it can’t do inside a real operation.

Read original

Sources for this section

Start with their work

Why AI demos pass on drawings real shops never receive

Start with the clearest example of the gap Crowder describes: the difference between clean files vendors test on and files that arrive from an actual job.

Read more

Crowder describes a drawing that looked normal on paper but had saved every word twice beneath the visible text.

  • A value of 0.5 came back as "0.50.5," and every check failed on a drawing any machinist could read without squinting.
  • On a second drawing, the system missed notes printed at an angle.
  • The point is testing conditions: most manufacturing AI is demonstrated on crisp PDFs that have never left a desktop, making the first genuine customer drawing the system’s first real test.
  • Crowder’s question for buyers is direct: what was the system tested on, and did any of it come from a real job?

For brands planning a campaign

Use this as the technical spine of a co-authored piece on AI failures in small shops. It turns an abstract reliability claim into a testable one: state what the system was trained and tested on, then show it handling scanned, folded, pencil-annotated drawings.

The 74 percent: AI built for plants ten times the size of its customers

This piece explains who the buyer actually is and why most AI products sold into manufacturing target a customer that mostly does not exist.

Read more

Crowder notes that 74 percent of US manufacturers have fewer than 20 people in the whole building, out of more than 239,000 manufacturers overall, three quarters of them small.

  • The demos look convincing: a system reads a drawing, runs a compliance check, flags an issue, and routes it to the right person.
  • Then the owner asks who sets it up, maintains it, and handles breakdowns.
  • The answer assumes an IT department, compliance team, or dedicated integration person — infrastructure found at a 200-person plant, but not a shop with 12.
  • The owner is quoting parts, running the floor, handling customers, and doing the books, with no spare person to become the AI expert.

For brands planning a campaign

Reframe the campaign around operability, not capability. A co-authored piece could focus on deploying AI in a small team — setup, maintenance, and failure handling in a shop with no IT staff — rather than model performance.

96,000 bombers, 86,000 tanks, and a supply base that no longer exists

Read this to see how Crowder turns scale into a concrete argument and to gauge the breadth of the manufacturing conversation beyond software.

Read more

Crowder contrasts World War II output — 96,000 bombers and 86,000 tanks — with the present.

  • The country converted wholesale then because factories making consumer goods switched to batteries, tires, and tanks; that could not happen now because the facilities are gone.
  • The scale claim is specific: China has roughly four times the population and somewhere around 70 percent more manufacturing capacity, compared with 239,000-plus US manufacturers, three quarters of them with fewer than 20 employees.
  • The COVID comparison distinguishes a narrow test from a broad one: the country could not produce its own N95 masks, some of what arrived did not meet standards, the national ventilator stockpile held roughly 20,000 units, and 200,000 more were ordered under the Defense Production Act — two products, versus everything a country can build, all at once, for years.

For brands planning a campaign

This is the furthest of the four from the software campaign need, but it shows Crowder’s reach into arguments about capacity, resilience, and the supply base. Cite it if the campaign expands from shop-floor AI to the industrial base that depends on it.

Not a machinist: how Crowder describes their own vantage point

This answers the newcomer’s first question — why Crowder is worth reading about manufacturing AI — in their own words.

Read more

Crowder states plainly that they are not a machinist and never pretended to be one, describing themselves instead as a maker and a builder who builds AI systems and calls the work "software manufacturing," on the grounds that both are constrained, both demand precision, and both break when someone skips a step, with the only real difference being physical versus virtual constraints.

  • The stated background runs from Thomas Register, through years at MFG, to founding an additive manufacturing factory recognized by the World Economic Forum, with 35 years spent around people who make things — explicitly standing next to the people doing the work rather than running machines, quoting parts, or managing the floor.
  • The positioning is deliberate: not the shop owner, and not the tech vendor pitching from a slide deck.

For brands planning a campaign

Use this to frame any co-authored placement. It addresses the first objection a machinist audience will raise — why a software person is writing about their shop — without overstating hands-on production experience.

Sources for this section

Topics and approach

AI for the realities of small manufacturing shops

Crowder argues that many manufacturing AI products assume a larger operation than the one they are meant to serve.

Read more

They point to small teams, no dedicated IT staff, and owners already handling quoting, production, customers, and bookkeeping. Their recurring test is whether a tool fits those working conditions, not just whether it looks capable in a demo.

Uses the shop owner's practical questions—who sets it up, maintains it, and fixes it—to expose assumptions hidden in product pitches.

For brands planning a campaign

A company targeting small and mid-sized shops could work with Crowder on content about setup, maintenance, staffing demands, and who handles failures. Make the piece specific about what a shop must do to use the product; avoid presenting a polished demo as proof it fits a small team.

Examples: Source 1

Test AI on real production drawings

Crowder contrasts clean demo PDFs with drawings that have been scanned, marked up, or processed in ways that confuse software.

Read more

They give concrete examples: duplicated text made a value read as “0.50.5,” while angled notes went unnoticed. Their argument is that evaluation should include files from actual jobs, not only pristine examples.

Makes a broad concern about AI reliability tangible through specific input defects and their consequences.

For brands planning a campaign

For a manufacturing AI company, a co-authored piece could explain a practical drawing-test protocol and show how messy inputs affect results.

  • Use representative, permission-cleared examples and describe both failures and limits.
  • Ask for evidence that the product passes this test.

Examples: Source 1

Manufacturing capacity and the case for small shops

Crowder connects the concentration of small manufacturers to a broader concern about national production capacity.

Read more

They contrast the scale of wartime manufacturing with current reliance on overseas supply, and argue that small operations matter to any manufacturing comeback. Their posts use historical and pandemic-era examples to make the stakes legible, rather than treating shop technology as an isolated software issue.

Moves from national-scale examples to the structure and constraints of individual manufacturers.

For brands planning a campaign

This theme may suit an industry or policy-facing campaign about manufacturing resilience, especially if it can connect the argument to concrete shop needs. Verify the figures and historical claims independently before using them as campaign facts.

Examples: Source 1 · Source 2

A builder's perspective, not a machinist's claim

Crowder says they are not a machinist.

Read more

They present their perspective as that of a maker and software builder who has spent years alongside manufacturing workers, and compare building AI systems with manufacturing through their shared demands for precision and process.

Defines the limits of Crowder's expertise while explaining why they consider their software-building experience relevant.

For brands planning a campaign

A campaign can draw on Crowder to discuss translating shop-floor realities into software requirements, while accurately describing their role. Do not position them as a machinist or as speaking for every shop; their own post distinguishes proximity to the work from operating machines or managing a shop.

Examples: Source 1

Sources for this section

Brands and businesses

Crowder names two stops in their 35-year manufacturing career: Thomas Register, where they say they started, and MFG, where they spent years.

Read more

They also say they founded an additive manufacturing factory recognised by the World Economic Forum, but do not name it; ask for the business name to assess that experience. The posts disclose no sponsorship, affiliate arrangement, client engagement or investment; ask about any relevant relationships.

Thomas Register

Employment

Crowder says they started their career at Thomas Register, the industrial sourcing directory business, before moving into other manufacturing roles.

Read more

They describe it as the start of 35 years working alongside manufacturers.

View example

MFG

Employment

Crowder says they spent years at MFG, a manufacturing sourcing and quoting platform, during their career working alongside manufacturers.

Read more

They describe both companies as the background to building AI tools for machine shops.

View example

Sources for this section

Topics and similar creators

David Crowder writes about the distance between how manufacturing software is pitched and how a shop actually runs.

Read more

The best entry point is the drawing-reliability piece, which shows how a system trained on clean demo PDFs behaves when a scanned, hand-marked customer drawing arrives: a value read as "0.50.5" because the file saved every word twice, or notes printed at an angle the system never saw.

  • From there, the argument widens.
  • Crowder makes the case that AI built for a 200-person plant is being sold to shops where the owner already quotes parts, runs the floor, answers the phone and does the books—and that the small shops making up roughly three quarters of US manufacturers are where the country's production capacity genuinely lives.
  • Their stated vantage point is that of an AI systems builder who has spent decades alongside manufacturing, not a machinist or shop owner.
  • Follow the small-shop thread for adoption constraints and the capacity thread for industrial policy; the creators below cover adjacent ground from different positions.
Manufacturing AI Small manufacturers Manufacturing capacity and industrial base Testing AI on real inputs Manufacturing software Shop-floor operations LinkedIn posts Machine shop owners

Sercan Esen

Esen writes about new technology on real production floors, grounding the case in field detail rather than vendor language: counts of customer onsites, plant-floor conversations, and the gap between what a dashboard reports and what a frontline leader can decide in the moment.

Read more

Both writers treat adoption as an operating problem rather than a purchase.

Esen covers safety and operations from inside a vendor, focusing on EHS leaders, control rooms and workforce frameworks.

  • Crowder focuses on small-shop software fit and AI reading real drawings, writing from outside any single product.
  • Esen builds arguments around structured research—a World Economic Forum human-machine collaboration framework and a 22,487-mile customer tour—while Crowder builds them around specific cases.

Read original · Original 2

Kris Hutchinson

Hutchinson's teaching approach resembles Crowder's: take two honest numbers that disagree—a partner's 80 to 85 percent conversion against the client's actual 35 to 40 percent—and show that the underlying problem is a definitions issue nobody has owned.

Read more

Crowder makes the same move with demo performance versus shop-floor performance. Both writers trace a misleading metric back to the unglamorous practice that prevents it.

Hutchinson covers B2B revenue operations, CRM data and marketing measurement, not machinery; Crowder covers drawings, shop staffing and manufacturing capacity. Hutchinson writes as an operator auditing hundreds of companies over twenty years, while Crowder positions as a software builder alongside the industry.

Read original · Original 2

Chris Matan

Matan owns a manufacturing business and writes about adopting AI there, asking what the technology will do to work, hiring and cost over the next decade.

Read more

The overlap with Crowder is the manufacturing owner's-eye view of AI and a willingness to pose open questions rather than sell an answer.

Matan writes about subjects well beyond the shop, including commercial real estate investing, market timing, retirement and household costs, as well as resource downloads and show promotion.

  • The questions stay broad.
  • Crowder stays inside the shop, making a specific, testable argument about whether a system has seen a real job's file.

Read original · Original 2

Sources for this section

Audience

David Crowder’s manufacturing writing addresses operators of small and mid-sized machine shops: businesses with fewer than twenty employees, which they describe as three quarters of US manufacturers.

Read more

Their LinkedIn follower count was about 3,100 on 11 October 2026.

  • The topical match is strong, but audience-size information is thin.
  • Their recent posts argue that AI products built for 200-person plants do not fit a shop with twelve people, and that vendors demo on clean PDFs rather than the scanned, annotated drawings shops actually receive.
  • Those are arguments a manufacturing AI vendor would want in a co-authored piece, pitched at the buyer they want to reach.
  • The key question is whether followers and engagers are shop owners and decision-makers rather than vendors, consultants, or sector observers.
  • Ask Crowder for recent LinkedIn analytics, including impressions, engagement rate, and any follower breakdown by industry, role, or company size, plus any audience survey results on occupation and seniority.
  • Request results specifically for posts about AI failing on real shop drawings and small-team constraints, the closest available proxy for how the proposed piece might perform.

LinkedIn followers

3,114

David Crowder's LinkedIn profile; a profile-level count captured in the same the research as the four LinkedIn posts cited in the summary, not a per-post figure · 2026-10-11

Sources for this section

Partnership options

David Crowder’s four long-form LinkedIn posts cover manufacturing capacity, small-shop constraints and how AI tools fail on real production drawings.

Read more

They offer no sponsorship package, rate card, media kit or partner format, and don’t pitch sponsor placements or explain how brands can book a collaboration.

  • They do, however, show subject-matter depth: firsthand accounts of drawings that break document-reading systems, the staffing gap at shops with fewer than 20 employees, and a stated position as someone who builds AI for manufacturing rather than runs machines.
  • For a manufacturing AI vendor, the practical route is an editorial or co-authored contribution built around that expertise, negotiated directly rather than booked through a published format.
  • The posts don’t say whether Crowder accepts sponsorship.
  • Ask for an official inquiry route and current partnership terms.
Sources for this section

Campaign fit

A campaign to shortlist

Strong fit on subject and angle. The open question is audience, not topic.

Read more

Brief

A manufacturing AI software company selling into small and mid-sized machine shops wants David Crowder for a co-authored piece on why AI tools fail on real shop drawings and under small-team constraints.

Reasons

  • Crowder has already made this exact argument in public, with examples the vendor can reuse: one drawing looked normal on paper but had every word saved twice underneath, so a reading of 0.5 came back as "0.50.5" and every check failed; a second drawing had notes printed at an angle, which the system did not find. Their stated lesson is that most systems are tested on clean PDFs that have never left a desktop, so the first real customer drawing becomes the system’s first genuine test. That is a ready-made spine for a co-authored piece, and it is testable rather than rhetorical: ask the vendor what its system was trained and tested on, and have it show the system handling scanned, folded, and pencil-marked files.
  • The brief’s second half, small-team constraints, echoes Crowder’s argument about who sets up, maintains, and repairs the tool. The shops in question run without IT staff while the owner quotes parts, runs the floor, handles customers, and does the books. That reframes the piece from capability to operability, which is where a small shop actually decides. A vendor writing this with Crowder can address setup and failure handling directly instead of treating a clean demo as proof of fit.
  • Crowder’s own description of their vantage point answers the first objection a machinist audience will raise. They state plainly that they are not a machinist and never pretended to be one, describing their work as software manufacturing and their years alongside people who make things rather than running machines or quoting parts. A vendor-authored piece that has to survive shop-floor scrutiny benefits from that framing without overclaiming hands-on production experience.
  • The commercial route is editorial rather than a packaged sponsorship. Crowder’s posts include no rate card, media kit, sponsor policy, or partner format, and no official inquiry page was found. Ask directly about rates, terms, and the process for arranging a contribution.
  • Two checks should run before the campaign does. Audience composition is unmeasured: the only figure published here is a LinkedIn follower count of about 3,100, with no breakdown by role, employer size, seniority, or engagement. Ask for recent analytics before committing. The numbers Crowder cites — 74 percent of US manufacturers with fewer than 20 people, more than 239,000 manufacturers overall with three quarters of them small — come from their posts and should be verified against Census or comparable data before a vendor puts them in branded content.

Source ids

dfe8f0328ec26939c55193b042037f2e1636f73e9d7ad9cdc2b04bb6f2c1c569

4e5f51a977d951514b60f4bb4085e0461215a052df01f421d426e93d5c37fbfe

15987df15402f4fa2a8f6f7493cdf7db20a304518b7fdc334fabc32cce8da0d1

3a14427ab35ab548ba6bd4ab86c6345b1c1de9da24c5269cdaee59df9560b6f6

When to choose a specialist

Weak fit as scoped. The subject overlaps, but the campaign would lean on the least-supported part of the posts and target a different audience.

Read more

Brief

A national manufacturing advocacy coalition wants a paid public voice arguing for reshoring and industrial-base investment, aimed at legislators, national media, and executives at large plants.

Reasons

  • The capacity argument appears in the posts, but it rests on figures Crowder asserts there: US wartime output of 96,000 bombers and 86,000 tanks, China at roughly four times the population and somewhere around 70 percent more manufacturing capacity, a national ventilator stockpile of roughly 20,000 units with 200,000 more ordered under the Defense Production Act, and a N95 mask shortage where part of what arrived did not meet standards. A campaign repeating these figures inherits the verification work and the reputational risk if any do not hold up.
  • Crowder’s posts do not show them reaching legislators, national press, or executives at large plants. They write for shop owners and the vendors selling to them. The only measured audience number is roughly 3,100 LinkedIn followers, with no breakdown of who they are. Paying for a policy audience the posts cannot demonstrate is a spend risk, not a fit decision.
  • Crowder’s authority in the posts comes from proximity to shop-floor work, with a deliberate boundary: not a machinist, not running the floor, not the shop owner. That is the right position for a technical co-authored piece aimed at small shops and the wrong one for a national spokesperson role, which needs institutional standing or policy access that the posts do not demonstrate.
  • A policy campaign would leave the strongest material unused. The concrete drawing-failure examples and the 12-person shop that cannot absorb a software project are the most specific, checkable things Crowder has published, and they are the parts a large-plant or legislative campaign has no reason to cite.
  • There is no documented disclosure, contracting, or paid-placement path. Ask Crowder what arrangements and disclosure terms would apply before pursuing a paid advocacy engagement.

Source ids

3a14427ab35ab548ba6bd4ab86c6345b1c1de9da24c5269cdaee59df9560b6f6

4e5f51a977d951514b60f4bb4085e0461215a052df01f421d426e93d5c37fbfe

dfe8f0328ec26939c55193b042037f2e1636f73e9d7ad9cdc2b04bb6f2c1c569

A worked campaign example
Angle

A co-authored LinkedIn article plus a downloadable one-page drawing test, written jointly by the vendor’s engineer and Crowder. Instead of a customer success story, publish a test: take three real drawings from a customer shop, run them through the system, and report what happened, including any failures. The vendor supplies the product detail and honest limits; Crowder supplies the buyer’s test and explains why it matters. Publish the failures; that is the part shop owners will trust.

Brief

The manufacturer AI software company brief: reach small and mid-sized machine shops and show why AI tools fail on real shop drawings and under small-team constraints.

Next steps

Confirm with Crowder whether they will write as a named co-author and what review rights they want over the vendor’s technical claims.

Get written permission to use anonymised customer drawings, and agree who signs off on publishing a failure.

Line up the vendor engineer who will answer the setup, maintenance, and failure questions in the article, and get the answers before drafting begins.

Build the downloadable checklist as a standalone resource, then test it on a blank drawing a reader has never seen before publishing.

Request recent LinkedIn analytics — impressions, engagement rate, and any follower breakdown by role or company size — to check whether a co-authored piece will reach shop owners rather than vendors and consultants. Treat that as a go/no-go input, not a formality.

Outline

Open with the file the demo never sees. Use Crowder’s two examples: a drawing whose hidden duplicate text turned 0.5 into "0.50.5" and failed every check, and a second drawing whose angled notes the system looked straight past. The point is not that the system is bad, but that the test set was clean. Make the article’s first question the buyer’s: what was this system tested on, and did any of it come from a real job?

Move to who operates it. Name the constraint plainly: these shops run without an IT department, and the owner is already quoting parts, managing the floor, handling customers, and doing the books. Setup, maintenance, and who gets called when it breaks belong in the vendor’s answer, not in a footnote.

Publish the test the vendor ran. Use three permission-cleared, anonymised drawings from real jobs — ideally one scanned, one folded or written on, and one with angled or offset notes. Show what the system read correctly, what it got wrong, and what the vendor changed or could not fix.

Give readers the checklist as a portable resource: ask what the system was trained and tested on; run your own worst drawings through it before buying; get a named person for maintenance and failures, not a support queue. It should work as a standalone page a shop can print and fill in.

Close with the vendor's stated limits and next step: a trial using the shop's own files, starting with a real drawing.

Keep Crowder's positioning accurate throughout: they build AI systems and have spent years alongside manufacturing, but they are not a machinist. Say so as their own post does, without implying machinist credentials or speaking for every shop.

Verify the supporting statistics before presenting them under the vendor's brand. The 74 percent small-shop figure and the 239,000-manufacturer count come from Crowder's posts; confirm them against Census or similar data, or attribute them to Crowder.

Title

Test it on the drawing that came in Tuesday

Sources for this section

Who else to consider

Sercan Esen

Choose Esen when the piece needs to reach EHS, operations and IT leaders at larger manufacturing sites, or when the subject is safety and how people and machines work together.

Read more

Esen has published directly on that ground: a five-point account of what changes on real shop floors when vision systems, robotics and autonomous equipment arrive, including the argument that automation should remove exposure rather than people; and a separate write-up of three months and 159 customer onsites across 11 states and 12 industries, reporting five patterns heard from 47 EHS leaders, 32 operations leaders, 10 IT leaders and about five executives. A vendor whose product is bought by a committee rather than a single shop owner gets a closer audience match, and a co-authored piece can present those patterns as findings rather than opinion.

The vantage is enterprise and committee-driven.

  • The argument runs from boardroom to plant floor, through shared ownership of outcomes among EHS, operations and IT, and toward standardisation across shifts and sites.
  • The twelve-person shop with no IT staff—the buyer for a campaign aimed at shops of that size—barely appears.
  • Esen’s posts also focus on safety technology sold to larger sites, so a co-authored piece inherits a safety-and-surveillance frame that the drawing-and-AI vendor does not sell into.
  • If the campaign’s central question is who sets up and maintains the tool, and who answers when it breaks in a small shop, this alternative takes the discussion elsewhere.

Examples: Source 1 · Source 2

Chris Matan

Choose Matan when the campaign wants a first-person owner-operator account of using AI in a manufacturing business rather than a technical test of a system.

Read more

Matan writes as an owner in manufacturing and commercial real estate, has described using AI to save time and become more efficient, and asks peers how they are using it and where they think it is headed.

  • The posts also show a working format: an episode of a named show, a downloadable guide and a comment prompt.
  • That suits a vendor seeking a podcast-length or conversational placement rather than a written argument about product behaviour.

The published posts do not discuss how software behaves on real drawings or the setup, maintenance and staffing limits of a small shop.

  • One turns to commercial real estate investing, market timing and why investors regret decisions they cannot change.
  • Both posts link to a lead magnet, a show subscription and videos, placing a sponsored piece inside a real-estate-plus-manufacturing content funnel.
  • A reader whose drawing failed every check would not find that problem addressed, and the vendor would pay to reach an audience split between manufacturers and property investors.

Examples: Source 1 · Source 2

Kris Hutchinson

Choose Hutchinson when the article should end on measurement discipline: whether a tool’s results can be trusted, what counts as a conversion and why two systems report different numbers for the same event.

Read more

Hutchinson has published two worked examples.

  • One follows a company told its conversion rate was 80 to 85 percent when its own delivered numbers were 35 to 40 percent, tracing the problem to two honest definitions with different denominators.
  • The other covers twenty years of B2B reporting stacks and argues that companies that grow treat marketing numbers as they treat their books, with a named owner and a reconciliation schedule.
  • A vendor that wants to pair the drawing test with a buyer-side test of its own claims—or reach sales and operations leaders alongside shop owners—gets a stronger match on that half of the argument.

Esen’s posts do not involve manufacturing, machine shops, drawings or shop-floor work.

  • The examples are a referral-partner conversion dispute and an audit of CRM and advertising stacks.
  • The framing shifts from whether a system survives a real drawing to whether a company can trust its own numbers—a different buying conversation that the drawing-test angle does not need.
  • Ask for evidence of overlap with small machine shops before buying reach into this broader B2B operations audience.

Examples: Source 1 · Source 2

Sources for this section

Build your campaign brief

Editable Markdown templates for planning a campaign with this creator.

Campaign brief (portable blank)

Completed brief: co-authored drawing-test article with David Crowder

Completed brief: declined — advocacy campaign for a manufacturing coalition

Sources for this section

Research methodology

  • This profile rests on four LinkedIn posts written by David Crowder and read in full, covering manufacturing AI, the fit of AI tools for small machine shops, US manufacturing capacity, and Crowder's own account of their career.
  • The posts carried no publication dates, and no videos, transcripts, comments, or other channels were available, so no change over time is described and the posts here are LinkedIn text only.
  • Figures Crowder cites in those posts — the share of US manufacturers with fewer than 20 employees, the total number of US manufacturers, wartime production counts, and comparisons of manufacturing capacity — come from the posts themselves and were not independently checked against Census or other data.
  • Employers are reported as Crowder describes them.
  • Earlier signature work that could explain a name search, such as books, shows, or named businesses, is not established by the posts and remains an open gap.
  • A LinkedIn follower count of roughly 3,100 was observed on 11 October 2026.

Brands they talk about