The brief
A fit-out company receives a brief for three office floors, with a March start and a request for similar past projects.
Briefs → reviewed proposals
Proposal drafts from
your own material.
Stop starting from a blank page. Altersoft builds workflows that turn a call or a client brief into a first draft in your format and tone, assembled from proposals and case studies you have already written.
brief-to-proposal.flowIllustrative example
Before: Start every proposal from a blank pageWith automation: Edit a first draft built from your own material
- Brief arrivesCall notes or a client's project brief
- AI searches your libraryPast proposals, case studies, price guide
- Draft in your templateSections filled in; price marked provisional
- Your team editsScope, wording and price checked by a person
- Approved to sendNothing goes to the client unapproved
From brief to draft
Keep the expertise.
Skip the blank page.
For consultancies, agencies, construction firms and professional services teams who write similar proposals or tender responses again and again, copying sections from old documents and fixing the details by hand.
It works best with a library of past proposals, approved case studies and current pricing guidance. Strategy, risk and the final price stay with your team; the draft only saves the assembly.
Capture the brief
Use call notes, a transcript you are allowed to process, or the client's brief. Requirements, deadlines and evaluation criteria are pulled out and listed for checking.
Search your library
Find relevant sections from past proposals, case studies and service descriptions you have approved for reuse. Out-of-date or client-confidential material can be excluded by rule.
Draft in your template
Assemble a structured first draft in your format and tone, with each reused section linked to where it came from so reviewers can check it.
Mark what needs judgement
Prices, timelines and anything not covered by the library are marked as provisional or missing, rather than invented.
Review and approve
Your team edits, prices and approves the proposal. Nothing is sent to a client until a person has signed it off.
Illustrative example
An office fit-out brief.
One section needs an expert.
Fictional scenario, not a customer case study or a live demonstration. Outcomes depend on your documents, data and systems.
The draft
The summary, scope and a matching case study are assembled from the company's library. The price section is marked provisional, because the rate guide does not cover one specialist item.
The decision
A director rewrites the scope, prices the specialist item and approves the final version. The draft simply removed the copy-and-paste work.
Systems & safeguards
Built around
your source of truth.
We assess access and data quality before promising a connection. These are integration options to scope, not ready-made connectors included in every project.
Documents & storage
Read approved folders in SharePoint, Google Drive or similar. Agree which documents can be reused and keep client-confidential material out of the library.
CRM & call notes
Pull the brief and contact details from your CRM or meeting notes where access allows. Recording and transcription need the participants' consent.
Review & version history
Keep drafts in your normal editor, with sources listed, so edits, approvals and the final sent version are easy to trace.
Agree how your data is handled before connecting it
We scope who can access documents, which hosting and AI providers are used, retention and deletion, and what appears in logs. Use redacted samples for discovery. This page does not accept uploads or process any of your data.
Scope, delivery & pricing
Start with one
proposal type.
A fixed project quote follows a review of your inputs, systems and approval rules. The website's general starting price is not a price promise for this workflow.
Define a small pilot
Pick one recurring proposal or tender type, a curated set of past documents, your template and a reviewer. Compare drafts with proposals your team wrote by hand before using it on live bids.
What affects the cost?
Document variety, data quality, integration access, rule complexity, permissions and volume. We agree delivery dates after this assessment; system access and data cleanup can extend the work.
Make running costs explicit
The proposal should separate the build from hosting, AI usage, third-party licences, maintenance and future changes, specifying what is included and who owns each ongoing task.
Estimate the opportunity using your own numbers
For illustration only: 8 proposals a month × 3 hours less assembly each = 24 hours of capacity. At an assumed £45 per hour, that is £1,080 of staff time before software costs and review. It is not a measured result or a promise of more wins; validate the assumptions in a pilot.
See our general pricing approach · Meet the engineer who builds it
Free first chat
Which proposals
eat your week?
Tell us roughly how many proposals or tenders you write, what they have in common and where your past documents live. No confidential documents needed for the first conversation.
Discuss your proposal workflowOr call +44 7441 113592