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.

I want to tell you about the call that broke me.

Client was happy with the proposal. Ten minutes before we wrapped up, she said: "Actually, what if we move the reporting features into Phase 1? We need that earlier than we thought." Reasonable request. I'd handled that question a dozen times. But I had a spreadsheet with 400 rows, nested IF formulas, and three cells that had been wrong since Q1 I'd just never had time to fix them.

I said "let me get back to you tomorrow."

We lost the bid.