> I forsee problems connecting with the right market
Finding the right market is hard work and consists entirely of rejection until you find it and entirely of rejection if you don't.
> * Clients who have meaningful IT budgets...
> * Clients who are too small...
Selling is hard work and mostly or entirely rejection. Finding reasons not to sell is much easier and avoids the hard work and the psychological tolls of rejection.
> How would you sell what I've built?
One customer at a time. That's how selling is.
On a brighter note. Hardware is a useful abstraction. Customers with big budgets will pay handsomely for annual service contracts and you can fly out in business class, stay in a nice hotel and markup the cost 25% in the materials section of your time-and materials invoice.
Nothing is impossible, so best of luck to the OP, but to add to the above, the kind of clients with the budget for your solution might also be the kind where their legal department requires that you have audited compliance procedures for various certs. It sounds like you design your solutions with the tech work for that already in mind, but it’s something that needs extended to the paperwork side of things to get past the gatekeepers
Finding the right market is hard work and consists entirely of rejection until you find it and entirely of rejection if you don't.
> * Clients who have meaningful IT budgets...
> * Clients who are too small...
Selling is hard work and mostly or entirely rejection. Finding reasons not to sell is much easier and avoids the hard work and the psychological tolls of rejection.
> How would you sell what I've built?
One customer at a time. That's how selling is.
On a brighter note. Hardware is a useful abstraction. Customers with big budgets will pay handsomely for annual service contracts and you can fly out in business class, stay in a nice hotel and markup the cost 25% in the materials section of your time-and materials invoice.
Good luck.