The keyboard comes back from the factory. The shape checks out, so does the color, but the switches are different from what was expected, the backlighting behaves differently, and the keycaps wear out faster than they should. The manufacturer did exactly what it was told – but it wasn’t told enough. 

Behind this scenario is a missing technical brief. It’s the only tool that translates a product vision into the factory’s language. Without it, every decision the client considered obvious becomes, for the manufacturer, a question with no answer. And unanswered questions always land somewhere – in a prototype that needs fixing, or in a production run that can’t be undone. 

Documentation errors at the specification stage account for roughly 70% of problems in the production process and generate the largest costs. A good technical brief is an investment that pays for itself before the first delivery even ships. 

A technical brief is not a wish list 

Many companies treat a brief like a preliminary request for quote: a few sentences about the product, a rough budget, and a request for pricing. That approach works for ordering a pen with a logo on it. It doesn’t work for manufacturing a keyboard. 

A technical brief is a document that defines the product’s parameters precisely enough for the manufacturer to prepare a reliable quote, a realistic schedule, and the right selection of components on that basis. It’s nothing more or less than a specification written in engineering language. 

The difference between a vague brief and a precise one is the same as the difference between a quote based on guesswork and a quote based on facts. One produces a price spread of several hundred percent; the other becomes the basis for a real conversation. 

Before the first drawing appears – business context 

A good brief starts with a question: why is this product being made, and who will use it? The answer shapes every decision that follows. A keyboard for medical applications needs different materials, different sealing, and different certifications than a gaming keyboard. A product intended for mass distribution is designed differently from a device meant for a narrow group of specialist users. 

The brief should also define the cooperation model. In an OEM model, the client supplies a complete design and the factory builds it – intellectual property stays with the client. In an ODM model, the client picks a ready-made platform from the manufacturer’s portfolio and introduces its own modifications. The choice between these two paths determines the scope of documentation required and the cost of entry. 

Technology and construction – the choices that define the project 

Mechanical, membrane, capacitive – each of these technologies carries different usability characteristics, different durability, and a different production cost. That’s why every brief starts by defining the keyboard type.  

The next element is the key layout – the ANSI and ISO standards determine the number of keys on the finished keyboard, the shape of the Enter key, and the availability of special characters for specific language markets. On top of that comes size: full-size, TKL, or compact. 

The material of the keycaps matters both functionally and from a production standpoint. ABS is cheaper and takes saturated colors more easily, but loses its matte finish over time. PBT is more durable and more resistant to wear. The choice of a specific material should be stated in the brief; otherwise, the manufacturer will pick one at its own discretion. 

Electronics and documentation – what the manufacturer needs to receive 

Without complete electronic documentation, the manufacturer can’t start work on the board. It’s essentially a precondition for starting the process at all. 

Board documentation and the bill of materials 

The technical brief should include production files for the printed circuit board: copper layers, solder masks, drill files. Add to that a bill of materials with precise part numbers for every component, and a Pick & Place file for the assembly machines. Missing even one of these elements either stops the process outright or – worse – forces the manufacturer to select substitutes on its own that no one has approved. 

Connectivity, firmware, and additional features 

The brief needs to specify the communication interfaces: USB-C, a 2.4 GHz wireless module, Bluetooth – or some combination of these. For wireless models – battery capacity and charging modes. For models with advanced logic, the firmware requirements also need to be described: anti-ghosting, macros, backlighting control. Each of these features has its own consequences for the electronics design and for component cost. 

The keyboard’s operating environment shapes the requirements 

A keyboard on an executive’s desk and a keyboard on a production line in a food processing plant are two different products, even if they look similar from the outside. 

The brief should describe the device’s operating environment precisely. If the keyboard has to work in dusty conditions or undergo regular washing, the required IP protection rating needs to be specified – and at the concept stage, not after the housing order has already been placed. IP65, IP67, and IP68 classes differ enough in construction requirements and sealing costs that changing assumptions mid-project can throw the whole schedule off. 

The same applies to chemical resistance, electromagnetic shielding, and protection against electrostatic discharge. In industrial and medical environments, these are baseline requirements that need to be in the brief so the manufacturer can factor them into the design and the quote. 

Certifications and standards – not an afterthought, but a starting point 

Certification is something many clients push to the end. That’s a mistake. CE marking is mandatory for electronic equipment placed on the EU market. Wireless keyboards are additionally subject to the Radio Equipment Directive (RED). The RoHS directive restricts the use of hazardous substances in components – it applies directly to the electronic parts, solder alloys, and plastics used in the product. 

If these requirements only surface at the prototype stage, changes can get expensive. If they’re already in the brief, the manufacturer will factor them in at the material selection stage.   

Schedule, volume, and budget – numbers that matter 

A schedule isn’t just a launch date. The technical brief should break the project into stages: time for the prototype, time for testing and fixes, time to ramp up serial production. Each of these stages has its own logic and its own risks – and a manufacturer that doesn’t know the planned rhythm of the project can’t reliably assess whether it can deliver on it. An overly optimistic schedule with no buffer for iteration is one of the more common causes of delays that formally fall on the factory but actually start with faulty assumptions on the client’s side. 

Production volume directly affects the choice of technology. Digital printing is cost-effective for prototypes and short runs. Screen printing wins for mass production. The difference in unit price between these methods is significant. The same economies of scale apply to component selection: the price of a switch at an order of a thousand units is different from the price at a hundred thousand. 

Budget shouldn’t be a secret in the relationship with the manufacturer. Sharing a range – even a rough one – lets the manufacturer tailor its proposal to realistic possibilities, instead of guessing what price bracket you’re working within. Quotes prepared without this information usually end up fitting everywhere and nowhere at once. 

The mistakes that most often come back from the factory 

A handful of things show up regularly in problem projects. 

Overly generic phrasing is the classic one: “the keyboard should be durable,” “high-quality materials,” “modern design.” Every one of these phrases sounds fine, but none gives the manufacturer any basis for a quote. What each of them does is let the factory fill in the gaps with its own judgment. 

Not having a non-disclosure agreement in place before handing over documentation is a risk many companies underestimate. A complete technical specification, drawings, a bill of materials – this is data that should be covered by an NDA before it reaches anyone. 

Not breaking the schedule into stages – prototyping, testing, serial production – leads to a situation where it’s unclear what’s supposed to be ready when, and who’s accountable for delays. The same goes for supplier certifications – an importer bringing goods without CE marking onto the EU market is personally liable for that. 

The brief as the basis for a conversation, not the opening move of a negotiation 

There’s a certain temptation to treat a technical brief like a tender document – the more general it is, the more room it leaves to maneuver. That logic works in commercial negotiations. It doesn’t work in electronics manufacturing. 

The more precise the brief, the better the quote. The better the quote, the fewer surprises during execution. A factory that receives a complete specification can offer realistic prices, a realistic schedule, and – most importantly – a realistic alternative when one of the parameters turns out to be a problem.  

At Qwerty, the brief is always the starting point 

At Qwerty, every project starts with a conversation about what the client actually needs – not with a catalog. More than thirty-five years of designing and manufacturing keyboards has taught us that the most common source of problems isn’t technology. It’s incomplete documentation at the start. 

That’s why we help clients put together technical briefs that actually work. Not to complicate the process. To shorten it.