Home / About
An engineering firm, run by engineers
NE Solutions exists because connected products keep failing at the seams between hardware, cloud and application — and almost nobody is contracted to own those seams.
We build connected products for companies that put hardware into the field: firmware and embedded Linux on the device, the platform it reports to, and the software people use to run it. All three disciplines are staffed in‑house, which is the point. It is what lets us be accountable for how they meet rather than for our own slice.
The firm is deliberately structured around long engagements rather than volume. Products that live in buildings, plants and homes need engineers who will still recognise the codebase in three years, so we staff for continuity and turn down work we cannot support properly.
We are equally willing to say no. If a programme needs a discipline we do not have, or a regulatory route we have not walked, we will say so early. That answer costs us a project occasionally; the alternative costs a client far more.
What we are
- A product engineering firm, not a staffing agency
- Hardware, firmware, platform and application under one roof
- Built for multi-year product lifecycles, not one-off builds
- Direct engineer-to-engineer working relationships
What we are not
- A reseller of someone else's IoT platform
- A body shop that swaps people between accounts
- A supplier that discovers problems at handover
Principles
How we make decisions when nobody is watching
Design for the tenth year
Anyone can make a device work today. We optimise for the engineer who has to change it in 2033 — reproducible builds, readable code, documented decisions and an update path that still functions.
Own the seams
The interesting failures happen between layers. Whoever holds the boundary should be accountable for it, so we take the whole path rather than the comfortable middle of it.
Say the difficult thing early
A slipping date, a wrong architectural choice, a component that will not be available — reported when we notice, not when it becomes undeniable. Clients forgive bad news; they do not forgive late news.
Leave the client independent
Every engagement should end with you able to continue without us. Lock‑in is a business model we have chosen not to have, which means we have to keep earning the next phase.
Direction
What we are building towards
Our aim
To be the engineering partner a manufacturer keeps for the life of a product line — through the first launch, the awkward second generation and the migration nobody planned for.
How we get there
By being genuinely good at the parts other suppliers avoid: legacy firmware, field updates, device security, and the unglamorous integration work that decides whether a connected product is an asset or an ongoing cost.
Working with us
What the first month looks like
Week one
NDA in place, a technical conversation with the engineers who would do the work, and access to whatever exists already — code, schematics, documentation, or a whiteboard photograph.
Week two
A written view of the constraint, the architecture we would propose, the risks we can see, and an honest statement of what we do not yet know.
Weeks three and four
Scope and commercials agreed, the team named and introduced, repositories and pipelines set up, and the first increment underway.
Want to talk to an engineer?
The first conversation is technical and free. If we are not the right firm for your programme, we will say so and point you somewhere better.