Bill a job the client agreed to on a handshake
Not every yes arrives as a signature. They sign a paper copy on the tailgate, they text back "looks good, let's go", they shake your hand in the driveway and the crew starts Monday. Until now every invoice in BidCraft hung off that little finger-drawn signature — so a job that closed the old way had no way to get billed.
Open the project, tap the Payments chip, and there's a new button: Invoice this proposal.
It does exactly what a signature would have done. If BidCraft collects your payments, it builds the milestone invoices from the payment schedule on the proposal and emails the deposit to your client — Pay button and all. If your invoices run through HighLevel, it creates the invoice there and keeps tracking it in your Payments section.
There's a tick box worth ticking
In the confirmation window: The client already signed (paper, text, or handshake).
Tick it and the project moves to Signed while the invoice goes out. Your job tasks generate, the win gets recorded, and the project stops sitting in your pipeline pretending it's still waiting on someone. Nothing about it goes to the client.
Leave it unticked if you're taking a deposit to hold a spot and the paperwork is still coming. You can mark it signed later.
The small print
- You need a payment schedule on the proposal when BidCraft collects your payments — that's what the milestone invoices are built from. No schedule, no invoices; set one up under Catalog → Proposal Settings.
- It only runs once. If the project already has invoices, it says so instead of billing your client twice.
- Owners and admins. Sales can see the Payments section; billing from it is still a billing action.
While we were in there we fixed the HighLevel invoice card's copy, which used to read like it only worked after a signature. It never did — it's always worked before one too.