Skip to main content
MTD for Income Tax is now live for landlords earning over £50,000.See what changes for you
Client login
FigsFlow

How to Customise Proposal Templates Using FigsFlow

Customise proposal templates in FigsFlow two ways: firm branding once, client proof when it counts.

Image

You customise proposal templates using FigsFlow in one of two ways. You set up a firm wide template once, so every proposal you send carries your branding, your expertise, and the standard sections you want every client to read. Or you open a single proposal and tailor it for one client, swapping in service-specific testimonials, sharpening a service description, and attaching the documents that close the deal.

Most firms jump straight to editing individual proposals and never touch the template. That gets the effort backward.

This article shows you both ways to customise proposal templates, what each one controls and which to reach for when.

Why Customise Proposal Templates

A generic proposal competes on one thing: price. If a client cannot see why your firm fits their situation, they pick the cheapest quote in the inbox. Personalising to client needs is not a nice to have. It decides whether you are considered or skipped.

Two layers do that work, and the first happens on its own. Build a proposal from a FigsFlow template, and it arrives already personalised. The client’s name, their entity, the services selected, the fee drivers behind each line, all of it flows in from pricing. They read it and feel it was written for them.

Customisation is the second layer, and it is the one that earns trust. Your logo, your fonts, your colours, the faces of your team, testimonials from clients like them. That is what tells a prospect you are an established firm worth committing to, not a quote pulled off a shelf. A generic, unbranded template says nothing about who you are. Strip the customisation out and you give the client no reason to choose you over anyone else.

Did you know?

FigsFlow’s Proposal Analyzer scores your proposal against 13 parameters, each weighted by its impact on conversion, then flags exactly which ones to fix before you send. Source: FigsFlow Proposal Analyser.

The Two Ways to Customise Proposal Templates in FigsFlow

The two methods to customise proposal templates solve two different problems. One – you set up once and forget. The other you touch only when a specific client warrants it.

Way 1: Template levelWay 2: Proposal level
ScopeEvery proposal you sendOne client, one proposal
ControlsBranding, firm story, standard sections, email automationService descriptions, service specific testimonials, attachments, dynamic variables
You set itOncePer proposal, only when needed
Best forReflecting what your firm does and proves across all servicesAdding proof and detail relevant to this client's situation

Way 1 is the foundation. Way 2 is the exception.

Way 1: Customise the Template Behind Every Proposal

This is where you make the proposal template your own. Everything you set here applies to every proposal built from it, so it holds what stays constant across clients: your brand, your credentials, and the proof that lands whichever service a client picks. You build it once in Template Setup, and every future proposal inherits it.

Way 1 to Customise Proposal Template - Customise the Template Behind Every Proposal

Three tabs shape what the client sees.

  • Cover Page: the first impression, on your brand. Set the template title, a description, and your brand colour, then swap the system default for your own cover image (PNG or JPEG, up to 500 KB) and add your logo. The client opens to your firm, not a stock layout.
  • Proposal Body: where trust is built. Arrange the blocks every client should read, Introduction, Our Fees, Terms and Conditions, Next Steps, and a Service Summary, then strengthen them with the Textbox, Image, and Testimonial tools or a Custom Page. This is the home for proof that applies to any prospect: your qualifications, your regulatory memberships, the testimonials that hold true regardless of the service.
  • Proposal Footer: the details that never change. Fix your company name, a short description, contact number, email, website, the three address lines, and postcode in one place. Set once, it stays identical on every proposal, so nothing drifts as your team sends quotes.

Set the follow up once, then forget it.

The template’s Email Settings link a predefined email to each stage, so the right message sends itself. Client emails cover Send Live, Won, Signature Reminder, and Point of Contact. Staff emails cover Send Live, Won, and Lost. The chasing runs whether or not you remember to chase.

Way 2: Tailor a Single Proposal to One Client

Open the edit icon on a proposal’s preview to reach the Edit Proposal Report view. The pricing already filled in the client’s details, so most of this layer you leave alone. The move worth making is adding proof that fits this service and this client.

How to Customise Proposal Templates Using FigsFlow - Way 2
  • Edit the service description only where it differs. Each service arrives with a default covering the statutory duty, deadlines, and scope. Change it where this client departs from the standard, leave it where it does not.
  • Toggle blocks, do not rewrite them. Introduction, Terms, and Next Steps each have a switch. Turn off what does not apply. Curation, not authorship.
  • Insert dynamic variables. Placeholders like [CLIENT_NAME] and [BILLABLE_RATES_TABLE] fill themselves with live client and firm data when the proposal renders.
  • Attach proof that answers this prospect’s question. A service specific case study, or a review from a client in the same niche. A landlord’s testimonial lands harder on a property proposal than a generic five star average.

Which Method to Use, and When

The two methods are not either/or. They stack, and the order is what matters. A rule of thumb keeps your effort where it pays.

  • Way 1 is your default. Branding, credentials, standard sections, and email automation hold true for every client, so they live in the template and apply on their own. Once it is set, most proposals need nothing more.
  • Way 2 is the exception. Pricing has already made the proposal client specific, and the default descriptions already say the right thing. Reach for it only to add targeted proof, a testimonial or case study that speaks to this client’s situation.

Editing for its own sake spends the time the template was built to save.

Set your proposal template up once, and every proposal starts ahead of the last. Start a free trial and build your firm template before your next quote goes out.

Conclusion

Customisation works on two levels. The template holds what is true of your firm for every client. The individual proposal holds what is true of this client and this service.

Set the firm layer once and it pays you back on every proposal that follows, each one inheriting the same credible, consistent pitch. Leave it unset and you rebuild that story by hand every time, slower and never quite the same twice.

So before your next proposal goes out, ask yourself: does it show this client something a generic template never could?

Practice Management, Simplified

Run your firm on one platform

Proposals, engagement letters, pricing and AML — built for ACCA, ICAEW, ATT, CIOT, AAT and CIMA firms.

See it run on your own practice.

Screen-shared, using your services, your client mix and your deadlines. You will see where FigsFlow fits, and where it does not.

Design previews, not a shipped build — we will tell you on the call what is live today.

9:41
SignatureEngagement letter
Ready to sign
Engagement letter 20263 signatories · you are firstSign
Audit trailIP, device and timestamp recordedOn
Also waiting
Letter of representationDue 30/09Due
HomeDocsTasksChatProfile
9:41
Tasks3 open
Upload bank statementsVAT Q3 · due todayDue
Sign engagement letterOnboarding · due 05/09Sign
Approve VAT returnQ2 · due 07/09Review
Confirm payroll changesAugust · doneClosed
HomeDocsTasksChatProfile
9:41
Client portalRidgeline Foods Ltd
Upload Sign Pay Ask
Your services
Annual accountsYear end 31/03/2026Live
VAT returnsQuarterly · next 07/10Filed
PayrollMonthly · 14 employeesCurrent
Your team
Amara · ManagerUsually replies within a day
HomeDocsTasksChatProfile
9:41
DocumentsStored in your SharePoint
Recent
Bank statement — AugUploaded by camera · 2 MBSynced
Sales ledger Q3Shared by AmaraNew
Accounts 2025Signed 14/06/2025Final
Add a document
Scan with the cameraEdges cropped automatically
HomeDocsTasksChatProfile
9:41
MessagesAmara · Manager
This job
Re: VAT Q3Amara · 2 hours agoNew
Statement attachedYou · yesterday
Next deadline
VAT Q3 filing07/10/2026 · 15 daysSoon
HomeDocsTasksChatProfile