Genuine question for other PMs and delivery managers here: how many of you have opened Jira or MS Project to build a proposal, and felt like you were forcing a square peg into a round hole?
Here's the mismatch I keep running into. Jira is built to track work that's already been broken down and assigned. MS Project is built to schedule work that's already been scoped. Both assume the hard part - figuring out what the work even is and how confident you are in your numbers - already happened somewhere else.
But the initiation phase is exactly where that hard part lives. You're sitting with a client who hasn't signed anything yet. You don't have a backlog. You don't have a confirmed scope. What you have is a rough idea of tasks, a gut feeling about risk, and a need to produce a number you can defend.
Neither tool gives you that. Jira will let you create epics and stories, but it has no concept of "this task could take 40 hours or it could take 90, and here's how confident I am." MS Project will let you build a Gantt chart, but the moment a client asks "what if we cut this feature," you're not adjusting a live model - you're rebuilding a schedule and hoping the dependencies don't break.
Hey Product Hunt 👋
I'm a PM. Part of the job is sitting down with clients to scope projects and build the plan together.
For years, the most frustrating part wasn't estimation itself. It was getting precious time with the client and then not being able to use it.
They'd ask "what if we move this to phase 2?" and I'd freeze. Not because I didn't know, but because the spreadsheet couldn't give me the answer live. I'd have to say "let me recalculate and come back." Find another slot in their calendar. Prepare again. Show up again. Hope they hadn't lost interest.
You only get a limited number of shots with a client. Every time you leave without a decision, you burn one.
That's what AxioPlan is built for. Scope your tasks before the call. Open it in the meeting. When they ask "what if?" - adjust on the spot, and P50/P85/P95 delivery dates recalculate in real time.
Answer the question. Close in the room.
Does this sound familiar? I'd love to hear how others handle it 👇
If you want to try it - first project is free at axioplan.io, no credit card needed.
How do you handle the moment the client pushes back on the number?
The re-cost happens instantly, which is great. But cleints rarely just accept it. They say "can we do it for less?" and now I need to negotiate scope live. Can I run multiple scenarios side by side, or do I have to undo and redo? The tool that lets me say "here's the 38000$ version and here's the 44000$ version" wins the room.
Hello @tumasas , thank you for sharing your thoughts with us!
Actually there is an option to create several projects simultaneously, so you could show the client a few versions already on the call, for example one with the team of 5 or with the team of 8.
Costs are counted as soon as you enter the rate for the role or a specific individual. This way you can also share the summary page with the client to see different proposals.
What are you struggling the most with the bid phase of the project?
@anastasija_pm Thanks for your reply.
The bid phase pain that costs me the most is late scope additions that I didn't price for. The client signs a proposal, then two weeks later says "oh we assumed login with Google was included" or "we'll need a mobile version of that dashboard." By then I've already anchored them on a number and any change feels like a surprise to them even though it wasn't in the original scope.
So I guess what I'm really asking is: does AxioPlan help me be more explisit about what is in and what's out during that room conversation, so the client can't plausibly claim later they didn't know.
@tumasas That's exactly the use case. Every task you add during the call whether it's "login with Google" or "mobile version of the dashboard" is itemized, not bundled into a vague total. Each one has its own confidence level (high/medium/low) and hours, so the client sees individually what's in and what's been left out.
You've got a record of exactly what was discussed: every task, its confidence level, and its estimated hours, tied to that specific version of the scope. If they come back two weeks later with "we assumed Google login was included," you're not relying on memory or a vague verbal exchange - you've got the actual breakdown showing it wasn't there, or showing exactly what confidence you flagged it at if it was discussed but not committed. The read-only version of the project can also be shared with the client.
It also means there's no need to argue about what was agreed. If they want to add something new, you adjust the scope right there and see the cost and timeline shift in real time, with them watching.
How granular does the resource planning get with fractional FTEs? If someone's split 30/70 across two projects, does the capacity math account for that cleanly?
@justas_bogusas thank you so much for your question! For now in this version we can pick full FTEs, although we are planning to add fractional allocation in our upcoming release.
One thing I'd love your take on while we're scoping it: when someone's split 30/70 across two projects, do you mainly need their cost prorated correctly in the estimate, or do you need the tool to actually account for their reduced availability when calculating how long their tasks will take? Those are pretty different problems to solve, and I want to build the one that actually matches how you plan.
For me - if the tool models reduced availability stretching the duration of their tasks, that's the killer feature!
Hey, I'm the developer behind AxioPlan 👋
I built this after watching Anastasija deal with the same frustrating loop over and over - get time with a client, hit a question she couldn't answer live, and have to go rebuild the numbers and find another slot to come back. I wanted to take that problem off her plate.
Part of what drove this was watching her struggle to find other tools that let you size a team before you even have the team members in place - and lay out a few options with pricing alongside them. Nothing did it cleanly, so we built it.
If this helps other PMs and delivery managers avoid that same loop, that's exactly why we built it. Happy to answer anything about how it works under the hood 👇