How an engagement starts

Most embedded work that goes wrong was scoped before anyone knew what they were looking at. An inherited codebase, a board that has never been powered on, a port to silicon nobody on the team has used — the honest estimate for any of those is a range wide enough to be useless.

So for uncertain work BroadForge leads with a fixed-price technical assessment, typically 12–20 hours of work depending on the project, spent finding out what is actually true before either side commits to a schedule.

What the assessment produces

For a firmware port or inherited codebase, the assessment produces:

  1. Review of the available firmware and hardware documentation
  2. Inspection of repository structure and build system
  3. MCU, memory, peripheral, and board differences identified
  4. Toolchain established or verified
  5. A determination of whether the existing project builds
  6. Drivers, HALs, middleware, and hardware dependencies mapped
  7. Assumptions surfaced around clocks, timers, ADC, DMA, interrupts, calibration, memory layout, boot behavior, and FPGA interaction
  8. Missing equipment, access, files, licenses, or documentation identified
  9. Major technical risks documented
  10. A recommended implementation plan
  11. A supported schedule and cost estimate for the phases that follow

Ways to work with us

Most work starts in one of five ways. Each is led by the practice closest to the problem and draws on the others when the problem crosses into their territory — which, in embedded products, it usually does.

Each is normally quoted as fixed-price milestones; any of them can also run hourly.

Design Review

Led by
The practice that owns the design

An independent read of a schematic, layout, firmware codebase, enclosure, BOM or test plan before it costs money to get wrong. You get a written report of findings ranked by severity, with the reasoning behind each. It is a review, not an approval or a certification.

Idea Assessment

Led by
The practice closest to the hardest problem

For a product that is still an idea. A fixed price, agreed up front, for feasibility, architecture options, a rough parts cost at a few volumes, the main risks, a prototype plan, and a straight answer on whether to go ahead — including "not yet" or "no."

Prototype Build

Led by
ProtoForge

Works-like and looks-like prototypes built start to finish, quoted after an assessment as fixed-price milestones, with the design files behind every part.

Path to Production

Led by
LineForge

A program of fixed-price milestones from a working prototype to a product a manufacturer can build, with sourcing, the build package, production test, and pilot builds gated along the way.

Rescue & Modernization

Led by
Usually SignalForge

For a product that has stalled or outlived its parts or its original developer. It starts with the technical assessment described above.

BroadForge is paid for engineering, not for outcomes. It makes no promises about patents, sales, licensing, manufacturers, or investors; patent questions belong with a patent attorney. Work starts under a mutual NDA, and what you pay for is yours.

How work is structured

Fixed price by milestone

How most work is quoted. The work is split into milestones, and each one's deliverables, dependencies, acceptance criteria and client responsibilities are written down and priced before it starts. Changes go through a written change order.

Phased

When later work depends on what earlier work discovers. That describes most embedded projects.

Hourly

Available for any engagement, and the better fit when the scope or technical condition is genuinely uncertain and a fixed number would only be one nobody should rely on.

Rates are quoted against a specific scope rather than published, because a number without a scope attached is not an estimate.