Proposal to signature, run as one record
The Onboarding Suite is how FigsFlow packages proposals, engagement letters and signature into a single governed flow. One client, one document lineage, one fee — from the moment a proposal goes out to the moment a client signs and delivery picks up the job.
Partner or owner, start with the live tour below to see a client move through the suite. Practice manager or ops, go straight to how this compares to running three separate tools.
- Proposal Sent 08/14 · accepted 08/17
- Fee $4,200 · carried straight into the letter
- Letter Assembled from the accepted scope · v1
- Signature Signed 08/19 · dated and stored
- Handover Job created on signature · no re-entry
five days, one record, no retyping
Nobody designed the gap between "they said yes" and "they signed." It exists because three tools don't talk.
The client replies to the proposal on a Tuesday: "This looks great, let's go." Somebody now has to turn that reply into a signed engagement — and that means opening a second tool.
The accepted scope and fee live in the proposal tool. The letter template lives in a shared drive, or a separate document generator. Someone re-types the services, re-types the fee, and hopes the wording matches what was actually agreed — because the letter tool has never seen the proposal.
Then it goes out for signature. In an inbox, or a third tool again. If the client asks for one change to scope, that change now has to be walked backward through all three systems by hand, because none of them are the same record — they are three documents about the same client, agreeing to disagree.
One record, from accepted proposal to a job your team can start
This is what makes it a suite rather than three products with the same login. The proposal, the letter and the signature are stages of one record — so the handoffs in the last fold are not shortened, they are gone. The onboarding suite has to survive scope changing mid-negotiation, and that is the test this flow is built around.
The service, scope and fee are set in the pipeline and the pricing engine before a proposal ever goes out.
The proposal sends from the priced deal, the letter assembles from the accepted scope, and the signature closes the record — no re-typing between any of the three.
The signature event closes the deal automatically. The signed date and the won date are the same event, not two entries somebody has to reconcile.
The signed scope becomes the job. Deadlines and tasks are created from the same services that were on the proposal — the handover is a status change, not a document.
- The priced deal — the service, scope and fee agreed in the pipeline populate the proposal directly
- Your approved clause library — the letter draws only from wording your partners have signed off
- The entity and service type — the letter's clauses vary by these without anyone rewriting it
- Jobs and deadlines — created from the signed scope, not re-described from memory
- The client record — proposal, letter and signature history travel with the client, not with the deal
- The firm's reporting — time from proposal to signature, by service and by partner
Watch one client move through the suite
A partner opens the record and sees the whole engagement — what was proposed, what the letter says, and whether it's signed. The client sees a short, plain checklist with one thing to do next. Switch the view, then click through the three stages.
The one record that never needs reconciling
Selling the work and documenting the work are supposed to meet at the signature. In most setups they don't — so somebody clears the difference by hand every time a client says yes. What you're stitching together determines how wide that gap is.
Judge onboarding software on that gap rather than on a feature list. The question isn't whether a tool can generate a letter — it's whether the fee the client actually accepted, the exact scope they agreed to, and who approved the wording are still the same answer by the time the signature lands.
One record. The proposal, the letter and the signature are the same object, so there is nothing to reconcile and nothing to re-key between them.
Three tools. The gap is where the accepted fee, the agreed scope, and the reason a clause was worded a certain way stop existing on paper — and somebody re-types it to bridge the difference.
Every size of firm, and where the suite earns its keep
A proposal-to-signature gap costs a different amount depending on how many people are touching it. At every size, the fix is the same idea — one record instead of three documents — but what breaks first is different.
Same choice as the comparison above — pick once, both sections follow
Growing firms
The trigger is a partner asking how long onboarding actually takes, and nobody being able to answer — because the clock starts in one tool and stops in another that doesn't talk to it.
Short list, honestly labeled
The onboarding suite connects to the two things a US firm already runs onboarding through — the mailbox and the payment rail. Everything else on this page is what is not connected yet, because finding that out after you switch is worse than reading it now.
Proposals and letters send from Outlook on the client's existing thread, and the documents themselves stay in your tenant rather than a third-party store. Sign in with the identity your firm already administers.
- OUTLOOK — SEND FROM THE CLIENT THREAD
- DOCUMENTS RETAINED IN YOUR TENANT
- ENTRA ID SSO
For firms that collect a deposit or first invoice at signature. Payment is captured against the same engagement record, so the fee, the letter and the payment reference the same fee figure rather than a separate reconciliation.
- DEPOSIT AT SIGNATURE
- PAYMENT LINKED TO THE ENGAGEMENT
The proposal that opens the suite is generated from the deal already in your pipeline, priced from your existing rate cards — nothing entered twice to get an engagement started.
- DEAL & SCOPE CARRIED FORWARD
- FEE FROM YOUR PRICING ENGINE
Signature through the onboarding suite covers proposals, engagement letters and firm documents. It is not e-file signature authorization — it does not cover Form 8879 or Form 8878.
Not in this releaseWhich plan tier includes the onboarding suite, and the exact US launch date, are confirmed on the pricing and availability pages rather than here.
[SLOT: confirm plan tier and US availability date before publication]No integration with return-preparation tools a US firm files from. The suite tracks the engagement being sold and signed; it does not push data into tax software.
Not in this releaseWhat firms ask before switching on the suite
Is the onboarding suite a separate product, or does it replace Proposals and Engagement Letters?
It's the governed flow that connects them. Proposals, Engagement Letters and E-signature & Approvals remain their own modules with their own detail pages — the onboarding suite is how they run as one record instead of three, from an accepted proposal through to a signed letter.
Does e-signature through the suite cover IRS e-file authorization?
No. Signature covers proposals, engagement letters and firm documents. It is not e-file signature authorization, so it does not cover Form 8879 or Form 8878.
Can I use my firm's own engagement letter wording instead of FigsFlow's?
Yes. The letter draws from an approved clause library — adopt the starting set as drafted, edit any clause, or replace it entirely with wording your firm already uses. Approval at firm level is what makes the set yours.
What happens if the client wants to change scope after the proposal is accepted?
The proposal is re-scoped and the letter regenerates from the updated services and fee — you're not editing a static document by hand. The signature still closes on whatever scope was last accepted.
Which plan includes the onboarding suite?
[SLOT: confirm plan tier inclusion for the onboarding suite before publication.]
When is the onboarding suite available in the US?
[SLOT: confirm US availability date for the onboarding suite before publication.]
Bring a proposal you're sending this week
We'll build the record on screen: the accepted scope, the letter drafted from your clause library, and the signature that closes it — on the actual client you're onboarding.
Once the letter is signed, the scope it carries becomes the job your team works to. Jobs & Workflow →
Start Smarter. Grow Faster.
From proposals to pricing, streamline every step with automation designed particularly for accountants, bookkeepers and tax advisers.