[ TL;DR ]
A complex tender draws on some of the most expensive and experienced people in a business. Engineers develop the solution. Estimators prepare the price. Commercial teams examine the terms. Bid managers bring the submission together. Directors decide what the company is prepared to promise.
Much of their time can disappear into the work surrounding those decisions: finding the right previous answer, checking which document is current, chasing a colleague, comparing supplier returns and explaining the same requirement to another department.
CSM built a custom AI-native workspace around that process. It connects the people, documents, specialist agents and approval stages needed to move a tender from initial review to submission and delivery handover.
Luna is the demonstration environment used to show this approach. Each client workspace is designed around that company’s tender process, team, information and controls. The screens illustrate how the experience can work; the implementation is tailored to the business.
• Time returned: less repeated searching, drafting, copying, chasing and assembling across the tender team.
• Better visibility: requirements, evidence, responsibilities and unresolved risks remain connected as the bid changes.
• Knowledge retained: approved answers, decisions and lessons remain available when people change roles or leave.
Understand
Prepare
Review
Submit and hand over
One shared process, with accountable people at each decision.
[ THE CHALLENGE ]
A tender arrives with a deadline. Behind it is a substantial commitment of people, time and money before the business knows whether it will earn anything from the opportunity.
The bid manager needs a compliant response. The technical team needs a workable solution. The estimator needs a price that includes the actual scope. The commercial director needs confidence that the commitments, exclusions and contractual risks are understood.
Those tasks compete with live projects, customer requests and other tenders. When information is fragmented, experienced people spend their day reconstructing work the business has already done.
Someone remembers a useful answer from a previous bid. Someone else has the current project reference. The supplier has revised its quotation, but the estimator is working from the earlier version. An engineer has changed the methodology, while the programme still reflects the original approach.
Each issue may look small in isolation. Together, they create repeated interruptions, late changes and a final review under pressure.
What the research tells us
• Nine contributors per RFP, on average. Loopio’s 2026 research reports that most teams involve between six and 15 people. This is a cross-industry benchmark, not the staffing count for this client. Loopio, 2026 proposal statistics.
• 33 hours per RFP response. Loopio reports this general response benchmark. It should not be treated as the full estimating, engineering, procurement and approval effort for a complex project, or multiplied by the contributor count. Loopio’s 2026 research announcement.
• 50% of teams cite bandwidth as a top challenge. The same 2026 research reports that RFPs influence 40% of company revenue, showing how commercially significant this workload can be. Loopio’s research announcement.
• 46 public tenders per year, with a 21% average success rate. These were findings among relevant respondents in the Irish CECA-commissioned Idiro study published through CIF in 2022. The private-tender success rate was 27%. These are historical civil-engineering findings, not current universal win rates. Idiro / CIF, pages 6–7.
• 108 and 180 working hours in tender review meetings. A 2013 study reported these figures for two contractor cases. They illustrate the potential scale of coordination alone; they are not an industry average or hours that should all be removed. ASCE, Nature of Tender Review Meetings.
There is no single defensible number for the time every complex tender takes. The answer depends on design responsibility, package count, evidence requirements, revisions and approval stages. A multidisciplinary team can accumulate hundreds of hours even when each contributor spends only part of their week on the bid.
For example, ten people contributing an average of 15 hours a week over four weeks represents 600 team hours. At an assumed fully loaded internal cost of €65 an hour, that is €39,000 of staff capacity committed to one tender, before external bid costs. This is a worked example, not a reported client cost.
The investment must be funded whether the company wins or loses. Repeating avoidable work on unsuccessful bids consumes capacity that could have supported a better opportunity, a live project or a customer relationship.
The dependency sitting underneath the workload
Often, a small number of people know where the useful information lives and why earlier decisions were made. They become the route through which everyone else gets answers.
When one is unavailable, the process slows. When one leaves, the company may keep their files while losing the context needed to use them confidently.
The challenge is to make the team’s expertise easier to apply, preserve and pass on, while giving those people more time for the work that needs their judgement.
[ WHAT CSM BUILT ]
We built the workspace around the work a tender team needs to complete: understanding the opportunity, organising the response, assembling evidence, preparing the commercial basis and reaching an informed submission decision.
An AI-native workspace means AI assistance is part of those everyday steps. The team works from a shared tender record, with documents, responsibilities, evidence and decisions connected to the relevant task.
Luna illustrates the core areas:
01
Pulse: understand where the tender stands. The bid director sees deadlines, readiness, outstanding decisions and blockers. Readiness is based on defined checks, with the reasons visible.
02
Requirements: know what must be answered. Tender obligations are linked to their source, owner, evidence and due date. Ambiguous wording is raised for review.
03
Compose: write with the evidence beside you. AI retrieves approved material and prepares draft responses. The writer can check the source and adapt the answer to this buyer and project.
04
Team: see who owns the next step. Contributors work against shared responsibilities, with outstanding inputs and dependencies visible to the bid manager.
05
Packages: bring supplier returns into the process. Quotations can be compared against a common scope, with exclusions, missing obligations and validity dates highlighted for the estimator.
06
Exceptions, Approvals and Release: make decisions explicit. Issues move to a named person for resolution, qualification or escalation. Approval records connect the decision to the version reviewed, and release checks support final authorisation.
Ask Luna provides a conversational route into this information. A team member can ask what changed in an addendum, which packages remain uncovered or what needs director approval, with sources and limitations visible in the answer.
Every design shown is an example of what we can tailor to a client. The roles, screens, agents, terminology, document formats, integrations and approval rules are specified around how that company actually tenders.
[ INSIDE THE TENDER TEAM ]
The exact team changes with the contract. In engineering it may include several design disciplines. In technology it may involve solution architects and security specialists. In facilities management it may involve mobilisation, staffing and service-delivery leads.
The following is a practical role map for complex bids. Several responsibilities may sit with one person, or one responsibility may involve several specialists.
Team member
Work they own
Where a tailored agent can help
Bid director or business development lead
Opportunity fit, bid strategy, client priorities and go/no-go decision
Assemble the opportunity brief, previous relevant experience and unanswered qualification questions
Bid manager
Tender programme, responsibilities, contributor deadlines and submission coordination
Organise requirements, prepare status updates and surface missing inputs
Proposal writer or bid coordinator
Narrative, response structure, word limits and supporting evidence
Retrieve approved answers and produce a first draft with its sources
Estimator or quantity surveyor
Quantities, labour, materials, rates, allowances and estimate completeness
Organise pricing inputs and identify gaps for checking against the estimating system
Engineers or solution architects
Technical solution, specifications, interfaces and feasibility
Locate relevant technical evidence and identify requirements needing specialist interpretation
Planner or programme manager
Sequence, resources, milestones and delivery dependencies
Highlight changed dates and commitments that require a programme review
Procurement or supply-chain lead
Enquiries, supplier returns, scope coverage and commercial comparisons
Prepare comparison schedules and flag exclusions, missing returns and expired validity
Commercial or contracts manager
Contract terms, qualifications, liabilities and commercial risk
Organise clauses and exceptions with source references for professional review
Health, safety, quality and environmental leads
Policies, accreditations, method statements and project-specific commitments
Retrieve current evidence and draft supported sections for specialist approval
Finance and insurance specialists
Cash flow, bonds, insurance evidence and financial capacity
Assemble required documents and flag missing or out-of-date evidence
HR, sustainability or social-value leads
People, CVs, training, environmental and community commitments
Retrieve approved credentials and track evidence behind proposed commitments
Operations or delivery lead
Buildability, mobilisation, capacity and the eventual handover
Review what the bid promises and prepare a structured record for delivery
Authorised director
Final price, material risk acceptance and permission to submit
Receive a concise decision pack showing unresolved issues and the evidence reviewed
These responsibilities inform how we configure the workspace. An agent needs a defined task, access to the right information and a person responsible for reviewing its output.
The opportunity is to prepare useful work before it reaches a specialist: an evidence-backed draft, a quotation comparison or a clear exception. That lets the specialist reach the decision sooner.
[ WHERE TIME IS SAVED ]
The same requirement and supporting evidence stay connected as work moves between people. The next person can continue from the work already done.
[ A TENDER FROM BRIEF TO DRAFT ]
Consider an illustrative tender for the design, supply, installation and commissioning of a technical system. The buyer requires a methodology, delivery programme, project references, named personnel, supplier pricing and commercial returns.
The company has relevant experience, but the evidence is spread across previous bids, project folders and different teams.
The workspace brings that preparation together:
01
Read and organise the tender pack. Requirements are extracted into a register for validation, separating mandatory returns, evaluated answers and commercial obligations. Each retains its source so the team can check the interpretation.
02
Find relevant company experience. A knowledge agent retrieves approved project references, methodologies, CVs and evidence. A previous answer is treated as a candidate for reuse, with its age, context and suitability checked.
03
Give each specialist a prepared starting point. The engineer receives the technical obligations. The planner sees milestones and dependencies. The estimator sees scope and pricing questions. The writer has relevant evidence beside the response.
04
Prepare the first response. AI drafts from the approved information available. Missing credentials, unconfirmed resources and unsupported statements become questions for the owner to resolve.
05
Carry changes through the bid. When an addendum changes a commissioning date, the workspace can flag the affected programme, method, supplier commitments and pricing assumptions for the relevant reviewers.
The value of the fifth step is easy to miss. A changed date can affect overtime, equipment hire, subcontractor availability and what the company has promised elsewhere in its response. Making that connection early helps the team deal with the consequences while there is still time.
The specialists decide what the change means. The system helps them find the affected work and record the resolution.
[ PREPARING THE PRICE ]
A well-written answer can create a problem if it promises work the estimate does not include.
The tender might commit to additional testing, temporary services, specialist attendance or an accelerated programme. Each commitment needs to be considered alongside the price, supplier coverage and qualifications.
Luna’s package and exception workflow illustrates five connected steps:
01
Establish the scope being compared. Supplier and subcontractor returns are organised against the same package requirements and current tender revisions.
02
Make differences visible. Exclusions, provisional items, testing obligations, temporary services and quotation validity are brought forward for review. The lowest headline price may cover a different scope.
03
Check coverage against commitments. The team can examine whether the proposed methodology and programme create obligations that are absent from the commercial basis.
04
Resolve the gaps. The estimator decides whether to obtain a revised price, include an allowance, change the proposal or raise a qualification where permitted by the procurement rules.
05
Record the basis selected. The chosen quotation, assumptions and decisions remain connected to the estimate and approval record.
Historic tender information is useful context, but current quantities, supplier returns and approved company rules determine the price. AI supports preparation and comparison; accountable people approve the estimate and commercial position.
[ REVIEWING AND SUBMITTING ]
The final review should make it possible to answer three questions clearly:
01
Have we answered what the buyer requires? Check mandatory returns, evidence, signatures, response limits and the controlled submission files.
02
Can we deliver what we have promised at this price? Review the technical solution, programme, supplier coverage, assumptions and material exceptions together.
03
Has the right person accepted the remaining risk? Each issue needs a recorded resolution, permitted qualification or escalation. Final authorisation belongs to the company’s authorised approver.
Luna illustrates approval gates from tender launch and mid-tender review through settlement, submission authorisation and award acceptance. Each gate connects the decision to a named approver and the tender evidence reviewed.
The release process keeps missing information and unresolved blockers visible. Generating a document does not itself authorise a submission.
After submission, clarifications and revised offers remain part of the same record. If the bid is successful, the accepted price basis, qualifications, commitments, risks and decisions move into the handover process.
The delivery team can see what was sold, what was included and which assumptions need attention, without having to reconstruct the bid from old emails.
[ RESULTS ]
The figures below are an illustrative CSM planning model, not measured savings from the unnamed client or the Luna demonstration. They show how a meaningful saving can come from several parts of the process while retaining substantial specialist work and human review.
The starting assumption is a complex tender requiring 600 active team hours. The activity allocations below are explicit assumptions to validate against a company’s own records.
Tender activity
Before: team hours
With workspace: team hours
Hours released
Intake, requirements register and initial allocation
55
25
30
Finding and validating previous evidence
70
30
40
Drafting and adapting written responses
100
50
50
Engineering, methodology and programme development
90
75
15
Estimating and commercial price preparation
75
65
10
Supplier-return administration and comparison
60
35
25
Coordination, status reporting and revision tracking
50
25
25
Specialist review, risk decisions and approvals
60
50
10
Submission assembly and handover preparation
40
20
20
Tender work subtotal
600
375
225
Additional workspace upkeep allocated to this tender
0
20
-20
Total, including ongoing upkeep
600
395
205
The after figures include the people time needed to check sources, correct outputs and complete the tender work. The additional 20 hours covers allocated knowledge upkeep and workflow administration. Each hour is assigned to one activity to avoid counting the same saving twice.
This scenario produces:
• 205 net hours released per tender, after ongoing upkeep.
• 34.2% fewer total team hours, rounded to 34% in the headline figures.
• 25.6 eight-hour working days of capacity returned across the team per tender.
• 410 net hours per month at two comparable tenders, assuming the workflow is used as modelled.
• 4,920 net hours per year at 24 comparable tenders, equivalent to 615 eight-hour working days across the team.
• €13,325 of internal capacity value per tender at the illustrative €65 hourly cost, before software, implementation and other external costs.
These figures describe staff capacity. They are not automatic payroll savings, extra profit, a guaranteed faster submission date or a promised increase in wins. One-off implementation, training and knowledge preparation also need to be included when assessing the investment.
For perspective, a 20% net reduction on the same 600-hour baseline would release 120 hours per tender, or 240 hours a month at two tenders. The business case should be tested at a lower saving as well as the central scenario.
Less repeated preparation
Approved company knowledge supports the first draft. Requirements and source references are organised once and carried through the process, reducing the effort spent starting again.
More useful time with specialists
Engineers, estimators and commercial reviewers receive prepared information and specific questions. Time released from coordination can be directed towards the solution, commercial judgement and response quality.
Knowledge that remains in the business
The tender leaves behind a record of its evidence, decisions and lessons. With deliberate review and upkeep, that record makes future work easier to prepare and hand over.
Actual results should be measured across comparable bids, using active hours by role and stage, including review, corrections and upkeep. Submission quality, compliance and rework should be checked alongside time. This gives the company a reliable basis for deciding where to improve the workspace next.