We consciously chose our product build strategy as — build a basic MVP, get continous customer feedback and iterate the product based on that. This means there is tons of customer feedback, input, and discovery that's happening all the time.

One of the challenges we face because of that is that my co-founder feels he is not getting enough context about the customer needs. I proposed the following 2 solutions

He joins as many sales calls as possible — both of us agree that's not scalable bcz there is enough work on the build

Whenever there is an interesting call, I post a summary of what was discussed, the founder should go through the sales call recording and then we have a quick huddle about customer discussion.

I feel the second approach is scalable —without taking too much time on both sides (there's some work in pointing him to the right snippets in the sales call). But he is not okay with that and suggested the following

For every call where a new customer feature was discussed, I fill out a document like this https://limewire.com/d/jBSpt#RpKvNtv5ka

My hesitation in doing that is

Way too much documentation overhead for the stage at which we are at

It's hard to transfer all the context in written docs, unless the docs are very well written and cover difference scenarios — which again takes a lot of time

Discourages in-person discussions - which I believe is very important for the stage at which we are

I would love to get feedback on this issue. What's a good way to handle this?