An execution coach for one goal at a time. You declare one task each morning, file proof of it each evening, and your idea moves through five phases — IDEA, VALIDATION, BUILD, LAUNCH, TRACTION — by clearing a bar of accepted evidence rather than by you saying it is done.
It is free, it runs in a browser, and there is nothing to set up.
The name is not ours alone: Masterji is a 1985 Hindi film, the ordinary word for a tailor or a schoolteacher, and a coding-practice site at masterji.co. This one is none of those, and it lives at helpindiebuild.com.
Yes, and there is no paid tier waiting behind it. There is no payment code in this product — nothing to enter a card into, no trial clock, no plan to upgrade to.
If that ever changes, it will appear in the changelog before it appears in your way.
No. Nothing in the signup checks either one — any Google account works, from anywhere.
The product is written for first-time builders in India who never got a mentor, and the examples come from that world: a tiffin-delivery app, a hostel mess queue. That is who it is aimed at, not who it is limited to. If you are outside that, the loop works the same; some of the examples will not be yours.
Nothing. It is a website. You can add it to your home screen if you would rather it opened like an app, but that is optional and it is the same product either way.
No. If you do not have one there is a workshop that starts from what you have actually noticed — something that annoys you, something people around you keep doing badly — and ends with one goal written down.
If you arrive with an idea already, you can have it reworded instead. You can also walk through the product without signing in at all.
It depends on the phase, and the bar is written out in front of you before you file anything — you are never guessing what would count.
IDEA — the problem in a paragraph: who has it and what they do about it now; one specific place these people already are; how you would get one conversation this week.
VALIDATION — who you spoke to, things they said in their own words, what they last did about this problem, the commitment you asked for and whether you got it.
BUILD — a link to something running, or evidence a real user touched it.
LAUNCH — a link to your public post, evidence of a stranger's action or payment, or a real rejection, with the reason they gave.
TRACTION — a stranger who came back on their own, or a payment: who, how much, what for.
A real rejection counts. I posted it is not a stranger acting.
Your streak goes back to zero and starts again that evening. Nothing else happens: no lockout, no penalty, nothing taken away. Proofs you have already banked stay banked, and your longest-ever run is kept on the record even after the goal is retired.
One thing worth knowing about how it counts: a day is complete only when it was both declared and proved. Today never shows as a broken streak while it is still in progress — an unfinished morning is not a missed day until the day is over.
No. One active goal, and that is a database constraint rather than a recommendation.
This is the product's main opinion and the thing people most often ask to have removed. The reason it stays: a second goal is the most comfortable way available to avoid the first one. You can retire a goal and start another — you just cannot run two.
Yes, and the old one does not vanish. Retired goals stay on your record, read-only, with their day-by-day history and their longest streak — so quitting costs something to look at, which is deliberate. Nothing writes to a retired goal again.
Advancing a phase is a server decision: it counts accepted proofs in the database and refuses if they are not there. The coach can propose an advance, and the dashboard has a button, but both roads lead to the same check, and that check counts rows.
So leaving VALIDATION needs three conversations with three different people — the same willing friend three times is three rows and one person, and it will not clear. Leaving BUILD needs two proofs with at least one of them a real user touching the thing. You can argue with the coach for as long as you like; the count is still the count.
No. There is no repository integration, no editor plugin and no access to your files, and it does not produce your deliverable.
What it does: ask what you are doing today, help you think out loud when you are stuck, and draft tonight's proof out of what you told it — which you then file. If nobody does the work, nothing gets filed and nothing advances.
A commercial model from one of the major providers, hosted by them. Which one is a setting rather than a rewrite, so it can change — and when it does, the changelog says so.
By default, only you. Your goal title, your morning declarations, your proof text and everything you said in chat are yours. None of it is public, and none of it sits on a page search engines are allowed to index.
Two things can let something out, and both are an action you take: you generate a share link for your record, or you join a cohort. Both are below.
The phase you reached, the proofs you banked, and how many of them came from talking to real people.
The page carries no title with your goal in it — deliberately, because generating one would mean putting your goal's name into a search index you never agreed to. It is marked noindex, so a crawler that finds the link is told to forget it. It shares a page with one person, not with a listing.
Their board shows the phase you reached, your proofs from real contact, your proofs banked, and your day streak. It shows no goal title, no proof text, no reason you gave for closing an idea — not one word you wrote. A member between ideas shows as between ideas, unranked, rather than scored zero. What a coordinator gets is a page of its own.
You join with a code and you can leave. Nobody is counted inside somebody else's aggregate without having joined it.
And you can leave altogether: deleting your account overwrites your email and username, so nothing identifying is left holding your address, and hides everything hanging off the account from the product. Leaving is a route here, not a support request.