That stressful period, full of uncertainty and half-articulated thoughts, as you figure out the basic concepts, how they inter-relate, form goals, make things fall into place conceptually.
Personally, I don't find staring at a blinking cursor helps. During this phase, long walks work the best for me.
Also great of you to mention walking, I walk a lot during 'work hours'. To outsiders it's so hard to explain that yes, walking is actually part of my process, and yes, walking around in the nearby forest is in some sense my job.
This would save from having to parse anything.
To create a bill-of-materials you simply would attach a bunch of invoices from a bunch of vendors. There are jobs out there of people who fetch invoices and then transform them into in-house systems all manually.
Since digital bookkeeping is ubiquitous nowadays, one could argue that invoicing is simply about sharing digital transactions between systems, and should not need to be 'pretty' or human readable at all.
I'm trying to bridge this gap, and I know that given enough time, my service will become obsolete.
But I'm goign higly off-topic now ;-)
I don't think you need to worry for a long time.
Currently I'm working on a new startup which tries to tackle a rather hard problem (a generic document parser for invoices). Sometimes I'm stuck for days on a particular problem, and I feel like I'm not productive at all, I just stare at a blinking cursor all day. However, in my head I'm constantly working on the problem, and one could say that the moments where I don't write code are actually the most productive, even though it does not feel that way. It's rather counter intuitive.
So I don't think there really isn't a pattern in actual productivity (at least not in my case), although there might be a pattern in how productive you feel.