Think of a system like stripe, but for validation(s)
Currently, we see a lot of new SaaS products (and this is another one) being built on IH/PH/Kernal.
There are already "no-code builder" tools and boilerplates for SaaS systems for repetitive tasks (users, dashboards, etc).
Any mildly experienced founder (even a technical one) will leverage any tool that can cut TTM or save $$$ (or better yet, both).
Their product can be built in-house from scratch in an afternoon but, not dealing with security, maintenance, and infrastructure is enough to make it a $200 million/year product.
Still haven't decided who the first target users/audience is but any digital product (internal or customer-facing) that requires validation/verification of some sort.
I have been cooking up some product ideas, and by talking with very smart people (during validation) this lower-level building block came up, it is mostly extracting this engine from one of the projects and making it abstract enough to be usable to a significant number of use cases (the original project will dogfood this system).
Any new or current digital product that uses or needs some sort of verification system (eg: logistics, verifiable purchased testimonials/reviews, etc.)
For now, I'm dogfooding it with another product that I'll build on top, after the MVP I would reach out to logistics platforms + local engineering industry companies.
Building a validation system takes a long time, making sure the code is bug-free, the system scales, and there's redundancy, all these are crucial when dealing with mission-critical code.
Similar to how stripe deals with billing, this product will deal with verification/validation, a "simple" integration to your system that will evolve, scale, and adapt to your use case.
Haven't really found anything even related, hence why I'm trying to validate the idea.
Build the system internally and deal with developing, fixing, maintaining, and providing infra.
Would love to hear the community feedback.
# Built the core system!
So I've been working on building the core for a possible MVP (the system/engine only, no frontend yet).
I'm also (trying to) build in public on Twitter but since I haven't been able to set a proper schedule it has been harder to write up.
Got some good leads already and interest in the capability/potential of this engine, adding the ability to build products on top.
## Next steps
Build a landing page to better explain the product and validate the idea.
Do an ad run for some more potential leads
I was fine building a core/MVP system because I can actually dog-food it and it will be very useful to me even if I can't find any paying customers.
--
Would love to hear your feedback ;)