I think you should A/B test the entire project.
How you do that is up to you, but I'm sure the community could have some fun with it.
If you create an app for the consumer side, create another one for the vendor side, and see how the problems conflict, or explore the synergies.
If you build something that searches, build something that turns those searches into social discovery or sharing.
If you build something that floats, build something else that seeks to sink it. Chaos monkey comes to mind.
I recognize it isn't true split testing, but you might discover a part of a chain that others have been ignoring, and you might also ignite a passion for a problem you didn't realize you had.
Best of luck.