Should I insist on a BA?

[Project Monkey]

Recruitment time would take too long - that's the issue. If we recruit it would delay the whole project.

So what will happen if you don't hire a BA...

a) you do the BA work, neglect your PM work, risks are missed, issues happen and project gets delayed.
b) ignore all BA work, client doesn't sign off UAT because it's not what they wanted, project gets delayed.
c) get someone else to pretend to be a BA, requirements turn out to be a waste of paper, client won't sign off, project gets delayed.
d) etc, etc, project gets delayed.

...if you know you need a BA, then you also know you don't have a credible plan to deliver on time. It sound like the project has ALREADY been delayed so you need to call out the issue and deal with it.

[Project Monkey]

You're screwed then. And you were screwed from the day you accepted the contract without checking the project team makeup....

Rubbish! Who ever accepts a PM contract on the basis that the project is in great shape to start with?

For many contract PMs, their whole business is based on fixing projects that the client has already knackered.

[Project Monkey]

Set out the options to the client and ask what they'd prefer, laying out the risks/benefits for each.

Hire a BA (contract)
Hire a BA (Perm)
No BA - less PM
etc.

Get them to decide, in writing.

...and make your recommendation clear.

[TykeMerc]

Rubbish! Who ever accepts a PM contract on the basis that the project is in great shape to start with?

For many contract PMs, their whole business is based on fixing projects that the client has already knackered.

No kidding, it's certainly made a sizeable lump of my income for years.

The start point is to identify where the problems are, how or if they can be mitigated and get plans that feel sensible in place. If it looks like a BA is required to make it work then make the case, set the expectations and get it done.