Accessible Engineering Innovation, home Talk to an engineer
Engagement

How we engage

From a first technology review to the complete device, and support after it ships. Start with a small, fixed piece of work at the stage your product is in. You decide after the pilot and after every milestone, and the handover leaves your team able to maintain the product.

We engineer the industrial communication and embedded systems inside your product: a protocol stack, a driver, an information model, a board and its firmware, or a complete purpose-built device from specification to production. Pick the stage your product is at to see the engagement that fits, what you get first, and how it is usually priced.

By product stage

Where is your product today?

A new technology, and no decision on it yet.

Technology consulting and training

When
Typically a newer standard such as TSN, OPC UA or DDS, with open questions about whether it fits your product, what adopting it costs, and what your team needs to learn.
What you receive
An architecture and technology-selection review with the trade-offs written down, and training that gives your team one vocabulary for the technology and for the work that follows.
Pricing that usually fits
Fixed fee for the review. Training with a support period, a block of hours your team uses for the questions that follow it.

Smallest first step A technology training for your team, or a review of one technology decision.

Related services Data Distribution & MessagingReal-Time EthernetOPC UA & Information Modelling

An idea you want to test before committing budget.

Feasibility study and proof of concept

When
You need evidence that the technology works on your hardware, or on an evaluation board, before a development budget is approved. A proof of concept also works as a first project with us, at any stage of your product's life.
What you receive
A pilot team builds a proof of concept on your hardware or an evaluation board, and a test report tells you how well the technology fits your product. Where it fits, you also receive a minimum viable product you can demonstrate, sample source and a framework your team can build on, and technical material for your own white papers and sales documents.
Pricing that usually fits
Fixed fee.

Smallest first step A feasibility check on an evaluation board, before any work on your own hardware.

Related services Embedded Systems

A specified product with a ship date.

Product engineering, turnkey or co-developed with your team

When
Your team needs engineering capacity or expertise it does not have in house, for part of the product or for all of it.
What you receive
Milestone releases into your build, each tested as it lands, and at handover the source, documentation and test evidence your team needs to maintain the product.
Pricing that usually fits
Fixed price per milestone once the specification is settled. Time and materials, or a dedicated team, while it is still moving.

Smallest first step A single first milestone, such as one protocol stack or one board bring-up, delivered into your build and tested before the rest is committed.

Related services Embedded SystemsReal-Time EthernetFieldbus & Device NetworksOPC UA & Information ModellingAutomated Test & Measurement

A product already shipping, or a plant already running.

Field support, upgrades and brownfield integration

When
It needs a new protocol, a new gateway interface or an integration into an MES, or support for the units already installed.
What you receive
Technical field support from the engineers who know the product, component and platform changes, and new features. In existing plants: new devices and protocols, IIoT connectivity, and machine-to-cloud and MES integration.
Pricing that usually fits
A support period, with time and materials for larger changes.

Smallest first step A support period for your team on the product line, or one protocol or interface added to an installed product.

Related services Device & Network IntegrationIndustrial IoT & Edge IntegrationProtocol Migration

A product whose parts, stacks or protocols are being discontinued.

Migration and obsolescence engineering

When
The product has to stay on the market, often as one of a family of devices or boards that share the same parts.
What you receive
An obsolescence review of the design: which components, stacks and protocols are at risk, and what can replace each one. Then the product migrated to current silicon or a current protocol, with its behaviour verified against the version it replaces.
Pricing that usually fits
Fixed fee for the review. Fixed price per migration, or a dedicated team for a multi-year obsolescence programme across a family of devices or boards.

Smallest first step An obsolescence review of one device or board, with advice for each part at risk: a last-time buy, a drop-in replacement, or a redesign.

Related services Obsolescence Management & Platform MigrationProtocol Migration

Getting started

From your first message to signed work

  1. You write to us

    An engineer reads your message and replies within one working day.

  2. A mutual NDA, if you need one

    Signed before you share designs, data or architecture.

  3. A call about your product

    Its stage, your goal, your deadline, and what is already in place, with the account manager who stays your contact from here to handover.

  4. A written proposal within a week

    The scope, an estimate, the commercial model that fits, and the first milestone.

  5. Agreeing the price and the paperwork

    Smaller work needs only our quotation and your purchase order. Larger or ongoing work runs under a master services agreement, with a statement of work per project, under Indian, EU or US law or on your own contract template.

  6. Kick-off

    With the team that will do the work, and a sprint plan. For a multi-milestone engagement it is the entire plan, reviewed and updated during sprint reviews.

Agile model

The workflow, and your decision points

The work passes between you and our team, with your go/no-go decisions after the pilot and each milestone.

ConsultPilotSpecifyDevelopIntegrate and testCertifyHand overField supportReviewYouConsultantPilot teamEngineering teamQuality assurance
ReviewGo/no-goafter the pilot
ReviewSign-offspecification & acceptance criteria
ReviewGo/no-goat each milestone
YouRequirement briefGoal, deadline, what is in place
YouWhat you provideHardware, access and a named contact
YouSprint reviewsSprint-level demo; change request consolidation
YouAcceptanceTested against the agreed criteria
YouCertificationAt an accredited lab(if needed)
ConsultantTechnology consultingYour objectives and the technology match
ConsultantTrainingEnd-goal visualisation and a standard vocabulary(if needed)
ConsultantScope and specificationRequirements, architecture, milestones and team
Pilot teamProof of concept & MVPOn your hardware or an evaluation board(if needed)
Engineering teamDevelopment in sprintsProduct increments, tested as they land; co-located or remote
Engineering teamIntegration and pre-complianceOn site with your engineers if needed; pre-compliance for certified products
Engineering teamCompliance testing support(if needed)
Engineering teamHandover and IP transferSource, documents, test evidence, knowledge transfer; ownership passes to you
Engineering teamWarranty and supportAn agreed warranty period, then an extended support period if you need one
Quality assuranceAlignment & feedbackWhat you expect from the product and from working with us is recorded at the first call, reviewed at each milestone and checked at handover.
Working together

What working with us looks like

  • Roles

    • We build the communication and embedded parts of your product, or the complete device: see our services.
    • Your team keeps the product, the roadmap, the customer relationship and the certification decision.
    • Our team aligns with your product owner or project manager through sprint-level status and progress reviews.
    • Optionally, we coordinate with your stack and silicon vendors, from part selection and vendor shortlisting to support issues, and keep you in the loop.

  • Handover and ownership

    • Source code, documentation, test evidence and knowledge transfer; optionally, the build configuration and source control integrated into your CI environment.
    • Rights to what we deliver pass to you on commercial closure.
    • Third-party components keep their own licences. Our pre-existing tools stay ours.

  • Continuity

    • A dedicated engineering team that keeps the know-how for your product, including across long-term and multi-year engagements.
    • An account manager who carries the record of your projects, decisions and domain detail from one engagement to the next.
    • Design decision traceability maintained.
    • Product versions maintained for field deployments and roll-backs, with their test records and history.
Questions

Questions before a first engagement

Do you certify our product?

No. We run pre-compliance and conformance testing against the same test suites the certification body uses, so the product reaches the test lab ready. The certificate itself comes from the protocol organisation or an accredited lab.

How do you price the work?

The model follows the scope and the stage of your product, and the proposal names it. A small first step is usually a fixed fee; larger work is priced once the scope is agreed. Where the scope is still moving and the work runs on time and materials, it can carry a cap.

Which hours does a dedicated team work?

The hours are agreed for each engagement, so that the team's working day overlaps with yours.

Can you work to our coding and process standards?

Yes. Where you have your own, we work to them. Where you do not, we work to the standard that suits your target application. For example, our team delivers safety-critical software to MISRA C, with compliance checked by static analysis and each requirement traced to its tests.

Can you work with our existing stack or silicon vendor?

Yes. We integrate commercial stacks under your licence and raise issues with the vendor on your behalf.

Can you work with export-controlled technology?

Yes. Your export classification decides whether a licence is needed before the technology is shared with us. We sign the end-use and non-transfer declaration your compliance team asks for, and use the technology only for your project.

The work itself

What we engineer

Start one

Scope the first step with us

Tell us where your product is stuck, and an engineer will reply.

Talk to an engineer Read our engineering notes