Building BAM: what would make you trust software from an unfamiliar developer?
A polished landing page can tell you what an app promises. A business owner also needs evidence that it works.
BizAppsMarket (BAM) is a work in progress I am building around that problem: a marketplace for small-business software with a review process covering eight areas and human sign-off before listing.
The public site explains the proposed approach and accepts founding-developer applications. The buyer catalog is planned to open once the first apps pass. Its sample listings and reports are illustrations, not proof of an established marketplace.
I would value two perspectives: owners choosing software, and independent builders prepared to have their work reviewed. What should the report show? What would make the process useful and fair?
I am happy to discuss the workflow and use your feedback to shape it while it is still being built.
See the project: bizappsmarket.brainit.site/
Skool community: skool.com/codedungeon-1002
My demos and tutorials: youtube.com/@BrainITConsulting







Comments2
Selling email software to small businesses at iContact taught me that owners worry less about features and more about whether the company will still be around and answering support next year. I'd put that front and center in the BAM report: who the developer is, how fast they reply to support, and how an owner gets their data out if the app shuts down.
Great idea, thanks Ryan
2 comments
Selling email software to small businesses at iContact taught me that owners worry less about features and more about whether the company will still be around and answering support next year. I'd put that front and center in the BAM report: who the developer is, how fast they reply to support, and how an owner gets their data out if the app shuts down.
Great idea, thanks Ryan