Give the product a job to do.

Tools, controls, fabrication, and useful household technology all belong on the bench. Bring a practical question and a product that can help answer it.

Propose a collaboration Download the collaboration brief
BUILD BRIEFSTATUS / OPEN
01 / PRODUCTWhat is it, and what problem does it solve?
02 / TESTWhat useful question should the build answer?
03 / CONSTRAINTSTimeline, budget, disclosure, and non-negotiables.
04 / OUTCOMEA clear story, honest result, and something worth making.

See the work before proposing a fit.

Start with these channel builds to see the subjects, practical questions, and approach.

View the public channel

Need current audience information?

YouTube shows the public channel and current subscriber count. For dated reach, audience information, availability, or a media kit, request the current information before planning a campaign.

Request current audience information

The product earns its screen time.

Good collaborations start with a practical problem and leave the audience with something more useful than an ad read.

  • TOOL
    Tools and shop equipmentUsed in a real build, comparison, repair, or stress test.
  • CTRL
    Controls, automation, and electronicsExplained clearly enough for a curious maker to follow.
  • FAB
    3D printing and fabricationPrototype, torture test, repair, or improve something tangible.
  • HOME
    Smart-home and family technologyPractical integrations that solve an actual household problem.

Formats worth discussing.

Suggest the format that answers the useful question. Include the intended distribution and any requested reuse of the finished work in your brief.

Build integration
Put a tool or component to work inside a practical project, with the product’s role visible in the result.
Product test or comparison
Propose a specific question, test conditions, and success criteria. Leave room to show the observed result.
Technical walkthrough
Explain a setup, workflow, or integration so a maker can understand how to use it.

A useful first email is short.

Four pieces of context are enough to decide whether there is a real build here.

  1. 01The product or idea

    What it does and why this audience would care.

  2. 02The honest constraint

    Timeline, required disclosure, review expectations, and anything off-limits.

  3. 03The build angle

    A proposed test, failure mode, or practical problem worth solving.

  4. 04The contact

    Your name, company, budget range if applicable, and fastest reply route.

Have a part worth testing?

Send the brief