Four people. None of them are hypothetical — they are the people who wrote to us during the beta, lightly disguised.
For most of history, the people who could build things and the people who needed things built were the same people. A farmer who needed a better plough made a better plough. Then industry got good — extraordinarily good — and making things became something that happened elsewhere, at scale, for a market. If your need was shared by a million people, you got a product. If it was shared by four hundred, you got nothing.
Something changed in the last thirty years, and almost nobody noticed. Manufacturing came back within reach. Five prototype boards from a factory in Shenzhen now cost less than a week of groceries and land on your desk in nine days. The factory does not care whether you are Samsung or a second-year student; the quote is the same.
But the design did not get cheaper. It still takes years to learn to read a datasheet properly, to know that this sensor wants five volts and this microcontroller will be damaged by five volts, to know which of the four thousand near-identical parts is the one still in stock. That knowledge is entirely public — published, free, sitting in PDFs on manufacturer websites. It is just enormously expensive to assemble in one head.
So we have arrived somewhere strange: the machines are democratised and the expertise is not. The bottleneck on new hardware is no longer capital or access to a factory. It is the number of people who can design a board. That number is not growing, and the number of things worth building is growing very fast.
Synqit is a bet that this particular gap can be closed with software, and that closing it changes who gets to make things. Not a world with fewer engineers — a world with far more people able to get as far as a working prototype before they need one.
Diego Rivera, Man, Controller of the Universe. A person at the centre of the machinery, hands on the controls. It was a controversial idea then and it is a controversial idea now: that the operator and the owner might be the same person.
He knows exactly which corner of the field dries first and exactly how many days of warning would save the crop. The soil probes he can buy are built for hundred-hectare operations and priced accordingly. What he needs is four sensors, a solar panel and something that sends him a message. Nobody will ever make that product, because there is no market in it — only a need.
Thirteen, in a city flat, with a phone and an enormous amount of time. He has already built everything that can be built in software, and he is bored of it, because none of it is a thing. He does not have a lab, a mentor, or anyone to ask. He has the internet and a pocket-money budget, which used to be nowhere near enough and is now almost enough.
Her grandmother forgets whether she has taken her tablets. Every device sold to solve this is designed for a hospital, costs a fortune, and assumes a carer is present. She knows what the right object looks like — she has been describing it to people for a year. The gap between describing it and building it is four years of study she is not going to do.
Her department has the equipment, but it is booked, and the person who knows how to use it graduated last year. Her whole project depends on one instrument that does not exist commercially and would take a week to design if she knew how. She has three months. This is the most ordinary story in engineering and the most expensive one.
Every argument on this page ends in the same place: an object that exists, made by the person who wanted it, working well enough to be useful. Not a rendering, not a pitch deck, not a prototype of a prototype. A board, populated, powered, doing the thing.
That is the only outcome we are optimising for.
