Odoo for engineering firms

Why RFP-driven work is not a sales pipeline

Most CRM software assumes a salesperson moving a lead toward a close. A firm that wins work through Requests for Proposals works differently, and the difference is the reason generic tools feel wrong.

Three dates govern a bid team's week: the submission deadline, any mandatory site visit, and the internal review date. A system for this work should show all three on every open bid without opening the record. It should also show what the firm is spending to pursue each one.

The bid workflow, step by step

1. RFP intakeA notice arrives from a portal, a client or a partner. It is logged with issuer, scope, value estimate and the key dates.
2. Go or no-goA principal decides whether to pursue, based on fit, capacity and likelihood. This is a judgment and stays with a person.
3. Site visitMandatory or optional visits are scheduled. Missing a mandatory visit can disqualify the bid.
4. Research and teamThe team is assembled, including sub-consultants. Questions to the issuer are tracked with their deadline.
5. Proposal and estimateThe technical proposal and the fee estimate are drafted, often by different people.
6. Internal reviewA senior reviewer checks scope, fee, risk and compliance with the RFP's requirements.
7. SubmissionThe proposal is submitted through the required channel before the deadline.
8. AwardThe result is recorded, won or lost, with the reason where known.
9. HandoffA won bid becomes a quotation and a project, carrying its scope and fee forward.

In Odoo, this is the CRM application with stages renamed and rebuilt for bids, and date fields shown on each card. In NGYN's implementation for a multi-entity engineering group, the pipeline runs from first notice of an RFP through research, proposal writing, estimate drafting and internal review, submission and award, with the submission deadline, any mandatory site-visit date and the internal review date on every card. That was done through configuration.

From award to delivery

Winning the bid starts a second workflow with its own stages.

Project stages

Engineering delivery moves through defined gates. In the NGYN implementation, projects move through percentage-complete stages: not started, concept design, engineering review, QA/QC review, client final review, final review and check, and complete, with on-hold and cancelled set aside. The stage alone tells the firm where a project sits between design and sign-off.

Your stages will differ. What matters is that they reflect real gates, especially quality review and client sign-off, and that everyone uses the same ones.

Resource planning

Professional firms sell time, so the scarce resource is people. Decide how you will see who is assigned to what. Odoo has a Planning application for scheduling people against projects, which is part of Enterprise. Some firms start with project and task assignment alone and add planning later.

Time and expenses

Time is recorded against the project and task. Two practices make it useful.

• Record proposal time separately. Give bids their own project or task so that business development hours are visible and do not disappear into overhead.
• Record daily. Time entered at the end of the week is reconstructed, not recorded.

Expenses are coded the same way. For bids, that includes printing, courier, bid-portal fees and association dues.

Documents

Proposals, contracts, drawings transmittals and correspondence need one structure with controlled access. Odoo's Documents application provides shared workspaces and access rules. It is a record of the firm's documents, not a replacement for your design and drafting tools or their file management.

Billing

Engineering firms bill by fixed fee and milestone, by percentage complete, or by time and materials with a rate schedule. Odoo supports invoicing from milestones and from timesheets as standard. Fee structures with multiple phases, sub-consultant mark-ups or client-specific rate tables may need configuration. State your billing models at scoping.

Profitability visibility

Because quotation, project, time and invoice share one system, the firm can compare budgeted and actual hours while the project is open. In the NGYN implementation, budgeted versus actual hours are flagged on each project card, so an overrun is visible immediately and not at invoicing.

Sub-consultants

Many bids and projects rely on sub-consultants. Track them as vendors with their own purchase orders against the project, so their fees appear as committed cost and their invoices are matched before payment. At the bid stage, record which sub-consultants were included and at what fee, because that is the figure the project budget inherits.

What each leader should expect to see

Bid cost and project cost: the relationship most firms cannot see

Ask a principal what the firm spent pursuing work last year and you will often get an estimate. Yet pursuit cost decides which opportunities are worth chasing.

None of this needs complex software. It needs two habits: logging proposal time against the specific bid, and creating the project from the won opportunity so the link is kept. With those, a firm can answer the go or no-go question from its own history.

We are careful here. The case study does not publish win rates or pursuit-cost figures, and we do not offer any. What it shows is that the structure to see them was built with standard applications.

Multi-entity design and shared services

Engineering groups often operate as several related companies: an engineering practice, a planning practice, a design-build arm, a consulting corporation. They share staff, a contact list and back-office functions.

Odoo's multi-company setup supports this in one database. In the NGYN implementation, four related companies share one system for contacts, documents and HR, with HR departments mirroring the legal entities and recruiting, appraisals and time off in the same system.

Decisions to make early:

• What is shared. Usually contacts, employees and document structure.
• What is separate. Ledgers, tax registrations, bank accounts and some reports.
• Who can see across entities. Principals and finance usually can. Project staff may not need to.
• How shared staff are charged. When someone employed by one entity works on another's project, decide how the cost is transferred.

Odoo's pricing page lists multi-company under its Custom plan, so check your plan when budgeting. See Odoo Community vs Enterprise for the edition question and Odoo ERP pricing and implementation cost in Canada for what drives the budget.

Internal operations

One useful detail from the case study: the firm pointed Odoo Helpdesk at its own internal operations, as a queue for system changes, access requests and administration. Internal work gets the same visibility as client work. It is a small configuration with a noticeable effect on a shared-services team.

AI for document intake and summarization, with traceability

RFP documents are long, and the facts a bid team needs are scattered through them: dates, mandatory requirements, evaluation criteria, submission format. Reading them is exactly the kind of task language models can assist with. It is also a task where an error can disqualify a bid.

So the rule is strict. AI may assist with intake and summarization only when two conditions hold.

1. Source traceability. Every extracted date, requirement or figure is shown with the page or section it came from, so the reviewer can check it against the original in seconds.
2. Named human review. A specific person, usually the proposal lead, confirms the extracted information before it is used. The system records who confirmed it and when.

Three limits apply.

• AI does not produce or check engineering. Calculations, designs, drawings and sealed documents remain the work and responsibility of qualified professionals.
• Confidentiality. RFP documents and client material may be confidential. Decide what may be sent to a model provider and confirm that your agreements allow it.
• Version. Odoo documents its AI application for version 19, including agents that can be restricted to supplied sources. On earlier versions, an external integration is the usual route.

The ERP AI readiness checklist covers the data, access and review conditions to meet first. For where AI sits beside rules and integrations, see the Odoo automation and practical AI hub.

Where Odoo fits an engineering firm, and where it does not

The NGYN implementation used standard Odoo CRM, Project, Timesheets, Expenses, Accounting and Documents, configured with custom pipeline stages, cost tagging and cross-linked applications, with no custom development. That keeps maintenance simple. It also means the firm had to make decisions about its own process, which is the real work. If you are weighing how much to do yourselves, see when you need an Odoo consultant.

Proof: a multi-entity engineering group

NGYN implemented Odoo for a multi-entity professional engineering, planning and design-build group operated as four related companies. Most of its new work originates as competitive proposals issued by public-sector bodies.

The system covers the RFP pipeline, project delivery stages, time and expenses tied to the bid or project, quotations from won opportunities, shared documents and HR across the four entities, and an internal operations queue. The firm has run on it since 2020.

The case study reports figures such as the number of related companies, projects tracked at once and contacts consolidated. We summarize the structure here and leave the numbers on the page where they are sourced: the engineering firm case study.

A sensible order of rollout

Firms that try to change everything at once tend to stall on time recording. A phased order:

1. Bid pipelineConfigure stages and the three dates. Load open bids. The proposal team works from one board.
2. Time and expensesEveryone logs time daily against bids and projects. This is the habit the rest depends on.
3. Project stagesDelivery stages and quality gates. Budgeted versus actual hours become visible.
4. Quotation to invoiceWon bids become quotations and projects. Billing runs from milestones or time.
5. Documents, HR and shared servicesShared structure across entities, then internal requests.

The first two phases give visibility quickly and ask little of finance. The later ones depend on the habits the first two build.

What an implementation asks of the firm

• A decision on stages. For bids and for projects. Fewer, clearer stages work better.
• Agreement on time recording. Daily, against bids and projects, by everyone including principals.
• A named owner. Someone in operations or finance who decides how the process works.
• Clean contacts. One client, one record, across all entities.
• A first phase with edges. For example, the bid pipeline and time recording first, then project stages and billing.

Frequently asked questions

Can Odoo CRM really work as an RFP pipeline?

Yes, with configuration. Stages are renamed and rebuilt around bid preparation, and deadline, site-visit and review dates are added to each record. NGYN's engineering implementation did this without custom development.

Does Odoo replace our design and drafting software?

No. Odoo manages the business around the engineering: bids, projects, time, documents, billing and people. Design, drafting and calculation tools remain separate.

Can we track what each proposal costs to prepare?

Yes, if time and expenses are logged against the specific bid. That requires a dedicated project or task for proposal work and a habit of recording time to it.

How does Odoo handle several related companies?

Through its multi-company setup, where entities share a database, contacts and document structure while keeping separate ledgers and reporting where needed.

Can AI read our RFPs for us?

It can assist with extracting dates and requirements and drafting a summary, provided every item is traceable to its source and a named person confirms it. It should not be relied on for compliance without that review.

How long does implementation take for a firm our size?

It depends on the number of entities, the processes in the first phase and how quickly the firm agrees its stages and time-recording practice. We set a timeline in a written scope after discovery.

Next step

If your bids live in spreadsheets and your project status depends on asking around, book a free 30-minute ERP fit call. We will walk through your bid-to-delivery workflow and tell you plainly whether Odoo is a sensible fit.