Proposals
The client says yes, and their setup is already done.
Send a proposal in your colours that names one of your packs. Your client reads it without making an account, and accepts with a code sent to their email.
The moment they accept, their workspace exists, the pack is installed switched off, the accounts they still owe you are listed, and their portal is ready.
Thrum opens soon. Sign up now and you’ll be among the first in.
From proposal to client in four moves
01
Write it
A title, your fee, your terms in plain text, and the pack it sets up. The page lists what accepting will create, in your client’s words.
02
Send the link
It opens on the portal address your client will use, so they sign where their portal will be.
03
They accept
Their name, a six-digit code sent to their email, and a box to tick. They can download the agreement as a PDF.
04
It sets itself up
Workspace, workflows and forms switched off, the accounts to ask for, and a portal sign-in. All of it, or none of it.
The handover
Everything left to do, and proof of what they signed.
Once the client is set up, the proposal becomes the handover: the accounts they still owe you, the values left blank, the workflows waiting to be switched on and the forms waiting to be published. Nothing runs until you have checked it and switched it on.
Below it sits the acceptance record: who accepted, when, from which address and browser, the exact text they saw and the agreement PDF. Nothing can change it afterwards.
What is left to set up
Who accepted, and when
Specs
Proposal details
- Accept codeLasts 10 minutes, 5 tries, used once
- 6 digits
- A proposal is openOr 1 to 365, chosen when you send it
- 30 days
- AcceptedA second press or a replay sets nothing up
- Once
- Set up inAll of it, or none of it
- One transaction
- KeptWho, when, address and browser
- Text, its SHA-256, the PDF
Questions about proposals
Does my client need an account to read it?
No. They open the link, read it, and accept with a code sent to the email you sent it to. Their portal sign-in is created when they accept.
Whose name is on it?
Yours. The proposal is in your name and colour, on the portal address your client will use.
Is it a proper signature?
It is a simple electronic signature with an audit trail: the exact text, its SHA-256 fingerprint, who accepted, when and from where, and the PDF. That is normal for a service agreement between a freelancer and a small business.
What happens to my client’s accounts?
Nothing is connected for them. The pack declares which accounts it needs, and the handover lists them until your client supplies each one. Nothing runs until you switch it on.
Can I change a proposal after sending it?
Yes. Editing it stops the old link and puts it back to draft. You send it again with a new link, so your client always reads what they accept.
Does it email the proposal and the portal invitation for me?
Not yet. You copy the link when you send and pass it on yourself; it is shown once. Your client’s portal sign-in exists when they accept, but no invitation is sent for you.
Does it take my fee?
No. Your fee is in the proposal and you collect it as you do today. The monthly texts and emails can be billed with client invoices.
What if accepting takes me past my plan’s client limit?
The signature stands and your client sees “Accepted”. The proposal waits as signed but not set up, with Set Up Now for when there is room. Your client never sees your billing, and a setup that stops part-way is picked up again by the hourly check.
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.