Why I’m showing Portioned before it is finished.

The version people first saw was already becoming an older version. That is not a reason to hide the process. It is the reason I want to document it.

A simple question that was not simple to answer

A few weeks ago, I asked my friend a straightforward question: “How much did you actually make that month?”

The answer was harder to find than I expected. When income does not arrive as one predictable salary, money can come in at different times, in different amounts and from different places. You know you are earning, but getting a clear picture of what arrived, where it went and what remains is not always straightforward.

That conversation stayed with me. Eventually, it became Portioned.

Turning the question into a working system

Portioned is a percentage-split budgeting tool I am building for irregular income. When money comes in, you choose the relevant profile and the income is divided into portions using percentages you have already set. When you record spending, it comes out of the relevant portion so you can see what remains and what each part of the money still needs to do.

The idea sounds simple when written in one paragraph. Building it requires many smaller decisions: how income should be recorded, how profiles should remain separate, how expenses should affect available balances and how the interface can make the whole picture understandable without creating more work for the person using it.

The product changed after I recorded it

The first video I shared did not show the version I had by the time I published it. I recorded the screen while I was still building, and I had already made several changes by the following day.

That could have been a reason to wait. I could have kept every early version private until the product looked settled. But the changing version is part of the story. A product does not move neatly from idea to finished result. It is shaped through questions, experiments, corrections and decisions that become clearer only after something real exists on the screen.

Why I want to show the middle

I do not want UriBuild to document only finished products. The finished result matters, but so does the work between recognising a problem and creating something people can actually use.

Showing that middle means keeping a record of what changed, what did not work, what became simpler and what real use revealed. It also makes each decision easier to understand later. Instead of presenting Portioned as though it arrived fully formed, the Build Log can show how the product earned its final shape.

Building in public without pretending it is complete

Sharing an unfinished product does not mean presenting it as ready. Portioned is still being developed and prepared for real testing. The purpose of sharing now is to be honest about that stage and to invite people into the thinking behind it.

The Private Beta will add another layer to this process. Real people will use Portioned with real income patterns, and their experience will reveal things that cannot be learned from building alone.

What this entry marks

This is the point where Portioned became more than a product I was quietly building. It became a process I chose to document.

The screens will change. Some decisions will be replaced. New questions will appear. The Build Log will preserve those moments one at a time, because useful products are not only defined by where they finish. They are shaped by everything learned along the way.

Portioned is one of the products I am building under UriBuild. Give every income a purpose.