What’s on your mind?

We’re testing a small Akron-first help loop.

The idea is simple: people usually do not arrive with a clean problem statement.

They arrive with something stuck in their head.

A form they do not understand. A local resource they cannot find. A repair that keeps slipping. A phone call they do not know how to make. A confusing process. A neighborhood issue. A question that feels too small for an agency and too practical for a comment thread.

So we are not starting with an application.

We are starting with a question: What’s on your mind?

If something local is confusing, frustrating, broken, hard to navigate, or just sitting in your head, tell us about it. You do not need to know the answer yet.

That is the point.

Belt.works is trying to build a small loop that can take messy real-life friction and turn it into something useful:

• a practical next step,
• a resource path,
• a phone or email script,
• a checklist,
• a plain-language explainer,
• a printable handout,
• or a small tool.

Not every submission will become something public. Not every problem will be something we can solve. We are not an emergency service, a case-management agency, or a magic machine.

But we can look for patterns.

We can ask: what is actually blocking this person? Is it information? A phone call? A confusing form? A missing local resource? A gap between what exists and what people can actually use?

That matters because barriers to help are bugs.

Sometimes the useful thing is not a new app. Sometimes it is a better script for calling the right office. Sometimes it is a plain-language guide. Sometimes it is a list of local options that does not shame people or bury them under ads. Sometimes it is noticing that the same problem keeps showing up from different directions.

This is also why we are keeping the loop broad at the door and structured after entry.

The first question should be easy to answer: Tell us what’s on your mind.

It can be a problem, a question, a complaint, something confusing, something broken, or something you wish existed.

After that, we may ask a few grounding questions: where this is happening, how urgent it feels, what kind of help might be useful if you know, whether we can share an anonymized version, and whether you want a way for us to follow up.

The rules are important:

• manual review,
• no public scoring,
• no gig-work nonsense,
• no promises we cannot keep,
• no sharing personal details without permission,
• no pressure to donate to be heard.

Support is appreciated if people want more of this kind of work to exist. It is not the gate.

The first version will probably be imperfect. That is fine. The goal is not to launch a polished intake machine. The goal is to start listening for real friction and turn the useful pieces into artifacts people can use.

Akron first. Local before broad. Useful before polished.

If something is on your mind, bring us the messy version.

We will see what can be made useful.