PomoZentraWe are building an honest answer to one question.
Did your focus go where you planned? Nozentra builds PomoZentra so that people who decide their own week can find out while the week can still change, instead of guessing on Friday. That is the whole company, and we would rather do one thing accurately than ten things approximately.
Where this came from
PomoZentra started from a specific frustration rather than a market gap. Every focus timer we tried could tell us how long we had worked, and none of them knew what we had decided the week was for. A day that drifted entirely into admin produced the same satisfying report as the day that went exactly to plan.
The information needed to tell those two days apart already existed. It was available on Monday, when the week was decided, and again at the end of every block, when you still knew whether the work had moved. Nobody was writing either of them down, so every tool was left measuring the one thing that was easy to capture: elapsed time.
What still needs to change
Work is now spread across calendars, task lists, messages and documents, and the shared assumption behind most productivity software is that the problem is capture. Record more, in more places, and clarity will follow.
It usually does not. The harder problem is deciding what deserves your attention and then finding out honestly whether it got any. That is a measurement problem, not a storage problem, and it is the one we are trying to solve.
What we are working toward
Focus should be measured against a decision you already made, never against an ideal invented afterwards. Three things follow: the target has to come from your own plan, so meeting it is always achievable. The score has to be per work area, so surplus in one cannot hide a shortfall in another. And the question has to be asked at the end of the block, while you still know the answer.
It also rules things out, which matters more than it sounds. No leaderboards, no streak guilt, no productivity grade. A partly-honest answer is worth more to you than a perfect-looking one, so the model is built to accept it. The full reasoning is on the method page.
What we build
One product, deliberately narrow.
PomoZentra
A weekly plan-alignment focus tracker. You name about six work areas, decide before the week starts how many focus blocks each one should get on each day, then run an ordinary 25-minute timer. When a block ends you pick the area and answer one question: did this move it forward? Yes, partly, or no.
Two numbers come back and update through the day. Plan alignment: of the blocks you planned per area, how many you matched. Weekly focus share: of everything you logged, how much reached the areas you named as this week's priority.
New to it? The setup guide walks through the seven steps, or the method page explains why it is built this way.
Who we build it for
People who decide their own week and are measured on output rather than hours. Not everyone, and not equally.
Founders
Splitting a week between selling and building, where building always wins the tie.
Freelancers
Whose income depends on how much of the week reaches billable work.
Consultants
Whose pipeline quietly disappears during a busy engagement.
Creators
Who publish, then lose the next week to everything except publishing.
If your calendar is filled by somebody else, or you need team seats, hourly billing or integrations, PomoZentra is the wrong tool and we would rather say so here than after you have spent a fortnight on it. The FAQ lists the limits in full.
Where the company is right now
Stated plainly, because it should affect whether you adopt this.
Early access
The product is in early access and free to use, with no credit card and no billing system connected. Core functionality works and is being improved through real usage.
Independent and unfunded
Nozentra funds PomoZentra itself. No investors, so no external pressure to grow the product past the point where it is still useful.
Shipping continuously
Plan-relative scoring, trends, exports and self-serve account deletion all landed in June 2026. Everything released is listed on the changelog.
What we are not showing you
No user counts, no customer logos, no testimonials and no growth chart. We have numbers internally, but publishing them this early would be marketing rather than information, and the whole product is built on not doing that. When there are users willing to be quoted, they will appear with their names and their permission.
How we decide things
Four rules that have each cost us something, which is the only way to tell whether a principle is real.
No invented numbers
Every figure on this site comes from the product's own logic. If a claim cannot be verified, it gets cut, including claims that would have helped. This page has no user count for exactly that reason.
Say what it cannot do
The FAQ and the comparison pages list the product's limits directly. It costs us signups from people who would have churned, and we would rather have the smaller number.
Refuse to guess
The wins-and-leaks report returns nothing at all under ten logged blocks, because a finding from thin data is noise wearing a confident tone. The product says nothing rather than something plausible.
Your data stays yours
Export as CSV or JSON at any time without asking. Account deletion is self-serve and removes the server copy. Nothing is held back to make leaving harder.
The team
PomoZentra is built by Nozentra, an independent product studio. Abdul Moiz founded it and leads product direction; design, engineering and research are handled by the wider studio team.
Responsible for product direction and the scoring model behind plan alignment. Writes most of what appears on this site, and reads every message that arrives through the contact page.
The rest of the studio
Design, engineering, research and support are covered by the Nozentra team rather than by one person. The studio has been building software since 2016; PomoZentra is the product it works on in the open.
Individual profiles are not published yet. We would rather list nobody than pad a team page, and the names will go here when the people on them have agreed to it.
How the work actually happens
Where each change comes from, and what has to be true before it ships.
What we are focused on now
Opening up, and making the first week worth it
The immediate priority is opening public access and making sure the first run is worth someone's time: the onboarding path, the empty states, and the first real week of a workspace. After that, removing the storage ceiling that currently caps how much history the product can hold.
Everything already released is listed on the changelog.
Why it is free right now
PomoZentra is free during early access, with no credit card required. We may introduce optional paid features in the future, but pricing and plan details have not been decided, and there is no pricing page because we cannot fill one in honestly yet.
Any pricing change will be communicated clearly before it takes effect.
Working with us
There are no open roles listed, and we would rather say that than run a careers page with nothing behind it.
Be an early user we can learn from
The most useful thing anyone can give us right now is two weeks of honest logging and a description of where the method failed. That shapes the roadmap more than anything else does.
Start freeEverything else
Partnerships, press, or a question about the studio: info@pomozentra.com. It is one inbox and it gets read.
If you want to work with Nozentra and there is nothing listed, send what you do and why this problem interests you. It will be read even when there is no role to point you at.
Decide the week, then find out.
Five minutes on Monday, one tap per block. That is the entire product and the entire company behind it.