Why your old project should not die when you start a new one
You launch something new and the old thing goes quiet. Not because it stopped working, but because you only have one head and it is now somewhere else. Three months later the old project still has users, still has revenue, and has not been mentioned anywhere in ninety days. This is the belief the whole tool is built on: a project should not die just because your attention moved. Forgefy treats every project as a separate world with its own voice, calendar, connected accounts and revenue, so keeping five alive costs roughly what keeping one alive costs elsewhere.
Step 1: Each project is its own workspace: its own brand, tone of voice, connected plat…
Each project is its own workspace: its own brand, tone of voice, connected platforms and content history. Switching here swaps everything: voice, calendar, accounts, revenue. Nothing bleeds between projects.
Step 2: Switch project, drop one update, walk away. A dormant project needs maybe ten m…
Switch project, drop one update, walk away. A dormant project needs maybe ten minutes a week to stay visible.
Step 3: The year view tells you the truth about which project you have been neglecting,…
The year view tells you the truth about which project you have been neglecting, per project, at a glance. Green is published, outlined is still waiting on you. Gaps are visible before they turn into months.
Good to know
Project isolation is enforced, not cosmetic. Selected platforms and provider mappings never carry over from the previous project when you switch. Language is per project. A Dutch project keeps writing Dutch even if you type your update in English. Revenue rolls up across projects on the founder view, while each project keeps its own chart.
Is there a limit on projects?
It depends on your plan. Builder covers two, Studio five, Portfolio unlimited. The plans exist because portfolio founders are the people this was built for.
Does a dormant project cost me anything to keep alive?
Only the minutes you spend on it. There is no per-project setup ritual after the first time.
Related