Hey Danny, we’re still very much in the design and development phase, so no decisions have been made yet about time frames - I’m just keen to dig in to what would and wouldn’t work for people, without us jumping to conclusions on how best to solve the problem (especially if we can find a technically simpler approach that we can release faster!).
There are also different version of custom reporting periods with varying complexity (months with a custom start date vs. completely flexible lengths that are always different etc).
Potentially, we could stick to calendar months, but understand how much you are due to be paid, and when - so you can budget ahead of pay day, without having to think about the exact day your income hits (A model a little closer to what @anon44204028 described). We want to make sure the default experience is simple enough for the majority, whilst making sure we don’t exclude too many people with more complicated needs.
Regarding Pulse, we know it’s less-than-ideal currently, I think once we get this logic right in the Spending analysis view, we’ll sync up Pulse to follow the same rules, so the graph lines up with however you have your analysis set up.