We launch a new website https://www.uclusion.com that is backed by videos explaining what we do. We had been blogging for a while but for the first time we have a strong enough landing page to complete the funnel. So a year and a half in of a two full time founder bootstrapped company we finally have a product and explanations of that product which are compelling enough for us to confidently launch.
We encourage people in our network to log in and give us their opinion. We also being a series of demonstrations of the product to in network connections willing to talk to us. Rapid tweaks to the feature set result as well as continued technical debt efforts.
All communication with contractors now solely inside Uclusion. Other than bug tracking all Uclusion product communication now using Uclusion. Of course there are a lot of bugs found and fixed this way and the features expand greatly as we require them ourselves.
We got the backend sorted out to support all the primitives we needed, and the core integration testing in place. The front end for the first draft of the new direction began. We switched out the entirety of the logic representation to better model "exchanges of state" that maps closely to the state of stories, decisions, initiatives, et al.
We decide that a more general decision making tool is a better approach. Making a decision with customers is really a subset of general collaboration - and a harder subset at that. Plus including software developers in our ideal customer profile allows us to use what we build for ourselves while we build it.
Ben and I had worked together at Adobe Sign and now we quit together to work on our own company. Our original idea is to collect feedback from customers on what features should be built next by giving them points to spend. At this point we had been laying the technical ground work as a side project for almost a year.
Uclusion exists to help people work on what is most important. We built an opinionated collaboration tool that out of the box replaces group chat, Kanban boards, long email threads and ambiguous requirements.