Professional services
Turning a scope call into a priced proposal by the next morning
A five-partner consultancy hands ORA the notes from a scope call and gets a structured, priced proposal back to check.
Before
Proposals were written at night, after client work. Each partner wrote them differently, and the pricing had to be rebuilt from memory each time.
The request
“Draft and verify the tender response for Friday”
The work packages 8ORA made
- 01Read the scopePull the call notes and any prior work for the same client into one picture.
- 02Structure the responseLay the proposal out in the firm's own order, section by section.
- 03Price the workApply the firm's rate card to the stated scope and show the assumptions used.
- 04Assemble supporting answersReuse approved wording from previous submissions where it fits.
- 05Flag every claimMark anything that asserts capability, experience or a figure, ready for sign-off.
Where IrisKey steps in
Nothing is sent. IrisKey holds the send action until a partner has read the flagged claims and released it.
What changes
Honest outcomes.
- The first draft exists before anyone sits down to write it, so partner time goes on judgement rather than layout.
- Proposals read consistently because they are assembled from the same approved structure and wording each time.
- Claims that need evidence are visible in one list rather than buried in the document.
What it does not do
- The pricing is only as good as the rate card and scope you give it.
- A partner still reads and releases every proposal — 8ORA does not send work on its own.
This is an illustrative example written by us to show how 8ORA works. It is not a customer story, and it contains no client names, figures or claimed results.