Let’s talk

Engineering R&D services · Software and SaaS

Engineering design programmes costed to completion, milestone by milestone

An engineering R&D firm takes on a design programme priced on effort estimated before the specification was settled. It then bills against milestones the customer's engineers approve. We cost each programme from the engineers, tools and lab time it actually consumes and re-estimate what remains, so overruns appear while there is still time to act.

In one paragraph

Engineering services and R&D firms — embedded software and electronics design, semiconductor design services, mechanical and product design, simulation and testing — usually turn over ₹10–300 crore. Their customers are often global OEMs. Owners and finance heads carry a different cost base from IT services. Design and simulation licences are expensive, prototypes and lab work add spend, and specifications change as long programmes proceed.

Who usually engages us

Managing director or CEO, often with the head of engineering

The economics

How the money moves in this trade

Revenue is usually a mix of dedicated engineering teams billed monthly and fixed-scope programmes billed on milestones such as design freeze, prototype delivery or validation. Costs include specialist engineers and design and verification licences, which are among the largest costs per engineer. Prototype builds, test equipment and travel to customer sites add more. Most of those costs are shared across programmes and are rarely allocated to them.

Customers expect firm prices while specifications move, so change requests are frequent and often agreed informally. Intellectual property usually passes to the customer. The firm's investment in reusable components and test benches therefore needs a clear accounting treatment. Many firms export most of their services, carrying foreign-currency receivables and export records through long programmes.

The problem

Where the numbers usually break down

Tool licences treated as overhead

Design, simulation and verification licences are expensed centrally, so programmes that depend heavily on them look more profitable than they are.

Milestones billed, effort not tracked against them

Invoices follow customer approvals, but nobody compares effort spent with the share of the programme delivered.

Change requests agreed in meetings

Scope changes are accepted by programme managers without a costed change order, so extra work is delivered free.

Prototype and lab spend scattered

Boards, samples, test fixtures and lab consumables are booked to general purchase heads rather than to the programme that used them.

Reusable assets with no stated treatment

Frameworks, libraries and test benches built in-house are neither tracked as assets nor attributed to the programmes that benefit from them.

What we do

The work, and the result each part produces

Programme costing

Engineer hours, tool-licence seats, lab time, prototypes and travel booked to each programme.

Each programme shows its real cost to date.

Estimate to complete by milestone

Remaining effort re-estimated with programme managers each month and compared with the milestone value left to bill.

Overruns surface before the final milestone.

Tool-licence allocation

Licence cost allocated to programmes by seat usage or hours, with idle seats reported.

Tool cost is priced into bids and unused seats are visible.

Change-order discipline

A costed change order for every scope change, logged against the programme and tracked to billing.

Extra scope is billed rather than absorbed.

Lab and prototype ledger

Prototype, sample and lab purchases tagged to programmes, with test equipment tracked as assets.

Hardware spend is attributed and controlled.

Export receivables view

Milestone invoices tied to remittance records, with foreign-currency receivables aged by customer.

Long programmes do not quietly tie up cash.

Where we start

The first steps of an engagement

  1. Programme contracts and effort data

    We ask for programme contracts and milestone schedules, timesheets, tool-licence seat records, lab and prototype purchase records and the change requests on file.

  2. Cost to date by programme

    Engineer hours, licence seats, lab time and prototypes are assigned to each programme. Cost to date is compared with the milestone value billed.

  3. Change orders and licence allocation

    A costed change order becomes the only route to new scope, and licence cost is allocated to programmes by seat usage.

  4. Programme margin at completion

    The first report shows margin to date and estimated margin at completion for each programme, with idle licence seats listed.

How it is measured

The reports the work is judged on

Each is recorded as a baseline before the work starts, so later reports have an honest comparison.

  • Programme margin to date and at completion
  • Effort spent against milestone value billed
  • Tool-licence cost and seat utilisation, by programme
  • Change orders raised, approved and billed
  • Prototype and lab spend by programme
  • Foreign-currency receivables by customer and age

Who it suits

Written for, and not the right fit for

Not the right fit if
  • You need the statutory audit or a transfer-pricing report signed; an independently engaged CA does that.
  • You want a research-related tax deduction approved or certified; we prepare the cost records, and eligibility, approval and certification sit with the relevant authority and a licensed professional.
Written for
  • Embedded, electronics, semiconductor and mechanical design services firms serving OEMs.
  • Firms running fixed-scope programmes alongside dedicated engineering teams.
  • Indian design centres billing an overseas customer or parent for engineering work.

Common questions

Questions owners in this trade ask

Is programme costing worth it when no two programmes are alike?

That's exactly why it's worth it. Because no two programmes are alike, the only way to know which kinds of work earn money is to cost each one from what it actually consumed.

How do we stop absorbing scope changes?

Make the change order the only route to new scope, and cost it before it's agreed. Customers rarely object to paying for a documented change. They do object to a surprise at the final milestone.

Should reusable frameworks be capitalised?

Possibly, if they meet the recognition criteria, and it's a judgement your auditor will review. We help you set the policy, track the effort and keep the evidence, so the treatment can be examined rather than argued about.

Scope and professional coordination

5th Quadrant prepares programme costing, export records and the cost records behind any research-related claim. Approval of such a claim rests with the relevant authority, and statutory audits, transfer-pricing reports and prescribed certifications are signed by an independently engaged licensed professional, coordinated through 5th Quadrant. Full detail is on our Professional Scope page.

Explore further

Other trades in this sector

SaaS companiesGateway payouts and annual plans tend to be booked as revenue the day the cash lands, until deferred revenue is rebuilt contract by contract and every payout is matched to its invoices.View trade ↗AI productsModel and GPU bills usually land as one cloud expense with no link to customers, so gross margin stays unknown until each customer and feature is costed from its inference.View trade ↗Enterprise softwareLicence, implementation and support are often invoiced and recognised as one milestone, though each part is delivered on its own pattern and earns a different margin.View trade ↗IT servicesUtilisation is usually measured on hours logged rather than hours billed; matching timesheets to invoices and costing projects from the people on them shows where margin goes.View trade ↗CybersecurityLicence resale, managed services and testing usually share one revenue line, which hides what each earns after the vendor's cost and which business the firm is really in.View trade ↗Cloud and infrastructure servicesHyperscaler bills, customer invoices and committed-spend discounts are rarely matched account by account, so unbilled consumption and misapplied credits stay hidden in the total.View trade ↗Product development studiosFixed-price builds slip and change requests go unbilled at many studios, and costing each engagement sprint by sprint against the signed scope makes both visible.View trade ↗Global capability centresThe cost-plus invoice to the parent is often raised on budget and never trued up, and a written cost base, with cross-charges reconciled to it each quarter, is what fixes that.View trade ↗
Back to Software and SaaS ↗

Tell us how your business actually runs.

Discuss your requirements