Product software and build-ready hardware your team can take over.
We're a small senior engineering team for product teams. Bring us an app, a backend, firmware or a board design, as separate work or one project. You keep the repository and the source files; we write the decisions, tests and notes clearly enough for your engineers to carry the work forward. That keeps changes visible while they are still cheaper to make.
Projects usually start with a Technical Review: we read what you have, write down the risks we can see and suggest a next step. From there it can go to a Paid Discovery and a written scope before any build work begins. A written scope keeps the first spend focused, and makes changes visible before they become rework.
On hardware, there are two ways to work. You can buy the parts and build the boards yourselves from our files, which say what to buy, which parts can be swapped and how to check the first board when it powers up. Or we can source the parts, have the boards made and assembled, test them and ship them to you, from a first prototype through to production. You get an itemised quote first: parts, boards, assembly and shipping at cost, with our service fee listed separately. Either way, site safety, local regulations and any certification you haven't handed to us are yours to look after.
Software, hardware or both
Software · Build-Ready Hardware
Where to start
How a project runs
- 01 Review
- 02 Design
- 03 Build and source
- 04 Verify
- 05 Hand over
Work
| Date | Title | Summary |
|---|---|---|
| 2026-10-16 | Measuring brand visibility in AI search answers | A platform that samples AI search answers on a schedule, extracts brand mentions and citations, and tests whether weekly changes exceed sampling noise. |
| 2026-10-16 | Configurable gateway for regulatory safety reporting | A reporting platform that maps enterprise data to standard objects and then to each regulator's message format, configured through a nine-step wizard. |
| 2026-10-16 | Bringing drifted copies of a dispatch product back to one | Drifting copies of a dispatch product brought back to one authoritative codebase per component, without pausing development. |
Who you'd work with
Team profiles go up here once each person has read and approved what's written about them.
NDAs, IP and handover
We put the NDA, IP ownership and the handover plan in writing at the start of every project, so it's clear from day one what changes hands at the end: source files, the BOM, test records and the notes on why decisions were made. The same written scope shows what is out of scope, so a change does not quietly become an extra bill. Each project also has a lead who owns it and a backup who knows it well enough to step in.
Recent posts
| Date | Title | Summary |
|---|---|---|
| 2026-10-16 | DevSolder Services and Site Languages | The DevSolder site describes two lines of work, software and build-ready hardware, across eight service stages, with pages in eight languages. |
| 2026-10-24 | Transactional Outbox: Side Effects with the Business Write | When a business write must also send email, a webhook or an ERP push: write an outbox row in the same transaction; a relay delivers at least once. |
| 2026-10-22 | EMC Pre-Compliance Testing Before the Lab: A Bench Plan | How to run EMC pre-compliance on a prototype: conducted and radiated scans, near-field probing, ESD checks, margins to the limit and when to book the lab. |