Hey Product Hunt — I’m Rob, maker of Project Foundry. Most software work goes wrong before anyone writes a line of code. Someone asks for a change in a meeting. It gets pasted into a ticket. IT guesses the build. Nobody sizes training or the day-to-day change. Leaders say yes on a vibe. QA never sees what the business actually asked for. Project Foundry is the all-in-one software lifecycle for that problem. A business person describes the idea in their own words. Guided questions fill the gaps. Business and IT put estimates on the same record. A leader records yes, no, or not yet. After a yes, requirements, sprints, testing, and release stay on that same request. It is not a project management tool. If you are organizing a campaign, a hire, or office work, this is the wrong product. If engineering is locked into Jira, you do not have to rip it out. Foundry is the Business–IT filter in front. Jira can stay the system of record. Native boards are there if you want the work to stay on the Foundry thread. We are in private alpha — waitlist only, not self-serve. If you run software change with both a business side and an IT side, I would like your honest take: what would make this a hard no, and what would make you join the waitlist? Happy to answer anything.

Project Foundry

Align Business and IT on a software change, then deliver it.

Align Business and IT on a software change, then deliver it.