What your client sees when you send an offer
The page, the verification code, the sign step, and what your client gets after accepting.
Your client gets an email with a link and an 8-digit code to verify it’s them. It arrives under your workspace’s legal name. No Billow account is needed to open it.
The page
Your logo and your legal name sit at the top, then:
The offer title and who it’s for
Recipient and Contractor details, theirs and yours, with your tax registration numbers in the contractor popover
The offer date and how long it’s valid
Your offer note, if you wrote one
Your deliverables, with descriptions, prices, and timelines where you set one
Totals, with tax unless you’ve hidden it
Your payment structure, if you set a deposit: “50% Upfront Deposit. You’ll receive an invoice after the project is accepted.”
The contract to download, if the offer has one
While the offer is still open, your client can download a PDF and copy the link to forward internally.
Add-ons
Deliverables you marked as upsells show a green Add-On badge with a Decline action.
Declining turns the badge red, strikes the price through and drops the line from the total right away. Add back on the red badge reverses it while they’re still deciding.
A declined add-on never reaches an invoice and stays out of the contract they sign.
Accepting
Accept Offer, then the 8-digit code. The code stays usable if they back out at this point.
With a contract on the offer: the contract opens in full, headed “Your Contract with {your legal name}”. Sign Contract moves them on.
The sign step: full name, company, a signature drawn or uploaded the same way you signed yours, and a consent line naming them and confirming the electronic signature is binding.
An offer without a contract goes straight to a shorter version of the sign step: name, company, and the consent line, with nothing to draw.
The page then switches to Offer Accepted / Thank you for your business, and states that the documents went to whoever signed.
On your side, the project goes Active, your invoices get drafted, and Billow emails you.
The documents
The person who signed gets an email right after accepting: the accepted offer as a PDF, with the signed contract attached when the offer had one.
It is sent under your legal name. Replies go to whoever created the project, or to the workspace owner if that person has since left.
That email is your client’s copy of the signed documents. The offer page stops handing out downloads once they sign. Your copies are on the project page.
Declining
Decline asks for the code and nothing else. No reason and no comment are collected. Billow emails you.
The page then reads Offer Rejected / Contact {your company} if you have questions.
The verification code
Required for both accepting and declining. There’s no way around it.
Single use. Once used: “This verification code has already been used.”
Never expires on its own. It works while the offer is pending and inside its valid-until date.
The code is stored hashed. Neither you nor anybody at Billow can read it back.
Resending the code replaces your client’s code and leaves the offer, its number, and its link exactly as they were.
After the decision
The link keeps working. What it shows depends on how the offer ended.
Outcome | What your client sees |
|---|---|
Accepted | The offer in full while the project runs: the scope, the totals, and the date they accepted. Declined add-ons are gone from the list. |
Rejected or cancelled | The title, who it was for, the offer date, and a panel reading Offer Rejected or Offer Cancelled, pointing them back at you. |
Completed | The same Offer Accepted panel, with the scope removed. |
On a rejected, cancelled or completed offer, the deliverables, prices, taxes, the deposit, your note, the contract and both addresses are stripped out before the page is built.
