Skip to content
invent.me

Work

Things we’ve made, tested, and learned from.

Every entry follows the same shape: the question, what we made to answer it, and what reality said. Some of these were a GO. Some were not, and that is the point.

  • Consumer appArtifact pending
    GO

    The question

    What if local sports worked more like a living league than a group text?

    What we made

    A hyperlocal app for teams to schedule games, join tournaments, chat, and meet nearby players.

    What we learned

    The product question and the density question are different questions. Building the app answered the first one quickly and made the second one measurable.

    AndrewWesley
  • Consumer appArtifact pending
    GO

    The question

    How small can a useful product be?

    What we made

    A scoring companion for a card game, built small and shipped in many languages.

    What we learned

    Narrow travels. The app found an audience well beyond where it started, without growing into a platform.

    Wesley
  • AIArtifact pending
    GO

    The question

    What can you learn when the deadline is tomorrow?

    What we made

    An automated booking and question-answering system for service workers, built inside a day.

    What we learned

    A 24-hour deadline is a scoping tool. It forces the question of what actually has to exist for the idea to be judged, which is the same question a Sprint asks with a longer clock.

    Wesley
  • HardwareArtifact pending
    GO

    The question

    What if three months became three weeks?

    What we made

    An accelerated UAV redesign run against a government solicitation deadline.

    What we learned

    Most of the traditional schedule is handoffs and waiting rather than work. Compressing the research and trade-study phases moved the whole critical path.

    TylerClient anonymized
  • HardwareArtifact pending
    GO

    The question

    What if a complex deployable mechanism could be manufactured flat?

    What we made

    Research into flat-manufactured compliant mechanisms that deploy into three-dimensional motion.

    What we learned

    The approach preserved kinematic performance while substantially reducing both build volume and material use.

    Tyler
  • SoftwareArtifact pending
    HISTORICAL BUILD

    The question

    Inventing useful writing tools before AI writing was a category

    What we made

    Writing products and platforms that reached a large audience long before generative AI existed.

    What we learned

    Tools that answer a narrow, recurring question outlive the technology cycle they were built in. Both properties are still live today.

    Robert
  • Consumer appArtifact pending
    ITERATE

    The question

    A habit of building the small version first

    What we made

    A collection of self-initiated products and experiments, shown as a pattern rather than as individual wins.

    What we learned

    Most of them taught something the next one used. Presented individually they would overstate; presented as a practice they show how the front end of invention actually behaves.

    Andrew

Some of our work is covered by client confidentiality and is not shown here. Where a client has not cleared their name, the story appears with the client anonymized rather than not at all.

What’s the idea you never have time to explore?

You don’t need a deck. You don’t need requirements. You don’t even need to know whether the answer is software.

Tell us what keeps making you say “What if?”

Bring it to invent.me

We’ll tell you quickly whether it sounds like an invent.me problem.