A civic idea meets the paperwork

The exciting version of StreetShape is relatively easy to describe. Somebody has an idea for their street, creates a visual version of it, shares it with other people, finds support, and perhaps eventually sees some version of that idea become real.

What is much more complicated is deciding what kind of organization should exist behind that process.

Building StreetShape in Germany has forced several different questions together for me. I need to understand how the business itself should be structured, what kind of civic role StreetShape should eventually have, and whether a future initiative that accepts donations to help fund real improvements can or should exist alongside the software company.

Those questions might sound like boring administrative details compared with designing the actual product, but the moment StreetShape begins making promises beyond software, the structure behind it becomes extremely important.

Running an application already creates responsibilities because there are users, accounts, data, payments, and a service that people expect to continue working.

Working directly with a municipality adds another layer because public institutions have their own requirements, expectations, and processes.

Accepting donations to support a real physical project creates an even larger responsibility. If people contribute money because they believe a particular street improvement will happen, somebody has to be able to clearly explain who controls that money, what it can be spent on, who is responsible for implementing the project, what happens if permission is refused, and what happens to the funds if the project cannot go ahead.

I am still working through what the correct structure for all of this would be.

For now, the direction that makes the most sense to me is to establish StreetShape properly as a software business and keep the donation-funded implementation idea separate until I understand exactly what would be required to do it responsibly.

Part of me finds that frustrating because I see all of these things as parts of the same overall idea. However, separating them into stages also makes it much clearer which responsibilities I am actually ready to take on today and which ones need more preparation.

I have therefore started to see the paperwork as part of building StreetShape rather than something happening outside the project. StreetShape obviously needs a useful product, but if I want it to eventually support real-world changes, then it also needs an organization capable of standing behind the promises it makes.