Engagement models
Three shapes of engagement. We quote after reading your brief, as a written proposal with scope, milestones and acceptance criteria. We publish no universal prices or timelines because they depend on the work.
Review
A close look at a design, firmware or software you already have.
Teams with a design or device that misbehaves, or that want a second opinion before they commit.
- Measurements of the problem, with methods
- A written report with the causes we found
- A ranked list of fixes, cheapest first
Examples
- A PCB layout and DFM review before fabrication
- A firmware review for a device that drains its battery or resets
- A feasibility report for a connected product idea
- Length
- Agreed in the written scope
- Pricing
- Proposal-based
Build sprint
A defined piece of work, delivered against written test criteria and milestones.
A new board, a firmware release, a cloud platform, or a complete first version of a connected product.
- Working designs, firmware or software, as scoped
- Test notes against the scope
- A handover pack
Examples
- A schematic and PCB design with fabrication files
- Firmware for a sensor node, with OTA updates
- A device dashboard and API with deployment guide
- Length
- Agreed in the written scope
- Pricing
- Proposal-based
Retainer
A set number of engineering days every month.
Teams with a product in development or in the field that needs steady engineering support.
- A monthly plan agreed with you
- Regular bench notes
- Agreed response times, written into the plan
Examples
- Ongoing firmware and cloud work on a product in the field
- Remote engineering support for your own team
- Regular design reviews as a product evolves
- Length
- Month to month
- Pricing
- Proposal-based
What moves the price
- How much is unknown
- A device that has never been built carries more risk than a fix to one that works. We price that honestly, or suggest a short review first to shrink it.
- How it's powered
- A mains device is simpler than one that must last a year on a cell. Battery targets add measurement and design time.
- How many boards, how many features
- A single-sided prototype differs from a multilayer board with several firmware and cloud components. More parts add design, review and documentation effort.
- What already exists
- Working firmware, a schematic or a server you already run all lower the cost. Tell us what you have.
How a quote arrives
- You send a brief. Rough answers are fine.
- We reply with questions, then a written scope with the price, milestones and test criteria.
- Payment terms for sprints and retainers are written into the scope before work begins.