There's innumerable scenarios we can concoct but I think the point is that there's no industrial-labor model for quantifying "effort" in a knowledge-based business.
As a software developer my value increases exponentially beyond the menial tasks I face at my job as I learn to curate good ideas, cultivate processes for generating new ones, and avoiding bad ideas. Any attempt to quantify my value based on lines of code, number of repository commits, or any other indicator is essentially meaningless without context. I may only make a single commit after a couple of weeks that changes two files and less than a dozen lines of code... but the network effects of the efficiency I just introduced allows to process N^k more data points per second which may pad your bonus with a couple of extra zeroes in the next quarter.
So I would recommend:
1. Learn how to value people differently. They bring more to the table than just a warm body.
2. Model the contractual obligations and profit sharing based on the core values of the business. Does working 1 hour have a directly positive impact on profits of some constant (or near-constant) amount? Split profits on hours worked. Is it more ephemeral based on the experience and qualities of the individual? Split it based on responsibility and risk (as a rule of thumb).