Position or Imposition - or "How the hell do I classify my SaaS?"
Having built something which we reckon is ludicrously useful is one thing, but convincing our ICP about this really is quite another.
When launching and then running a SaaS (or any product for that matter), there’s only usually only one major hurdle to overcome and that is convincing people to use it.
Since introducing Metaport to the world in early 2025 however, it’s become quite apparent that we have in fact two such major hurdles, the other, primary one being:
Convincing people they actually have the problem, which the product solves for.
Amazingly, and quite unlike many founders we’ve encountered, we’ve actually worked in the same industry whose practitioners need the product. We’ve observed first-hand the problems Metaport solves, which is basically why we built it. No-engineer wants to be asked the same - seemingly menial - questions about a project they probably haven’t touched for months.
But, here’s the kicker: Metaport cuts across the traditional engineering/ops and project management/customer experience boundaries. So how how on earth do you position a product which isn’t AppSec but deals with security-related data (and stakeholder outcomes), isn’t an Observability tool, but observes an application stack from afar, and isn’t an Issue Tracker or Task Management tool, despite its bent towards project management?
Well what you don’t do is try and use words alone. We originally wrote about this in a LinkedIn piece last week, but as we summarised there too - a picture speaks a thousand words.
If you work in, or run a web-development agency, or an in-house development team, find out if Metaport is right for you at getmetaport.com.