Skip to content
Austin Kimbell
Tech by Austin / @techbyaustin

Real problems. Useful builds.

Meet the people behind the problem. Follow the build. See how AI and automation can make everyday work a little better.

Austin Kimbell at his multi-screen desk with a laptop, keyboard, microphone and ring light.

There’s a story behind every workflow. The repetitive task someone has learned to live with. The idea they keep putting off. The thing they wish worked a little differently.

Tech by Austin is where I’m exploring those stories. I want to show the conversation, the decisions at the desk, the first test, and the lessons that follow, not just a polished reveal.

I’m looking for small, practical problems to build around. What do you repeat every week? Who uses the process? Where does it get frustrating? Tell me about the task, without sharing private records.

Selected builds are scoped individually. Selection, filming, ownership, running costs, and ongoing support are agreed separately. An invitation to share an idea is not a promise of a free build.

Tell us about your idea

Watch the work

Useful software.
See it in action.

Explore real project recordings, then follow the builds on Tech by Austin on YouTube.

Ploposaurus

Actual gameplay from a game I built. This recording shows the result; the build story is a separate episode.

Read the recording description

A real gameplay recording shows tiles falling onto the board, matching numbers merging, and the resulting game state.

Explore this project

Suggest a community build

How I approach a build.

The person comes first.
  1. Start with the person.

    What are you trying to do? Where does it get frustrating? The useful idea starts there.

    More about this step

    A good starting point is a real task. Walk me through what you do today, who is involved, and what makes it difficult. We can then choose one concrete workflow to explore.

  2. Build something useful.

    Choose one workflow, make the decisions visible, and build around the way you work.

    More about this step

    Keep the first version focused. Make the inputs, outputs, decisions, and human handoffs clear. Use AI where it helps, and straightforward software where that is the better fit.

  3. Put it in real hands.

    Try the tool, notice what gets in the way, and make the next version better.

    More about this step

    A build is only part of the story. Test the workflow with the person who will use it, agree on ownership and support, and learn from what happens after the handoff.